One of NYCR’s most popular weekly events is Lunar Laser Mondays using our Epilog mini-35 laser cutter. The only supported system is Windows with CorelDRAW and Epilog’s closed source driver, which doesn’t seem right for a hackerspace. Luckily, AS220 Labs has figured out how to talk to the Epilog using PJL. I’ve written a command line tool, epilog, that will translate the Postscript file into commands for the cutter.

There are a few differences from Epilog’s driver — the most significant is that with the epilog command line tool the home position is always the upper right of the page, not the center of the bounding box as in the Windows printer driver version. The other major difference is that the lines to be cut are distinguished by color, not width: anything that is #FF0000 will be translated into a vector cut.

To use it from inkscape you will need to write out a Postcript file by selecting “Print to file” and writing the output.ps file. Then you can run it through the tool like this:

epilog \
  --printer 192.168.3.4 \
  --dpi 300 \
  --raster-power 80 \
  --raster-speed 100 \
  --name "epilog test" \
  output.ps

One of the next steps is to build a set of presets for different materials and typical work flows (fast vector pass with no power to see outlines, raster only, vector only, etc). The ability to automate these common steps in scripts will really make it easier for repeat jobs.

There is no man page yet. Until then, here’s the description of the options:

Usage: epilog [options] < file.ps
Options:
 -p | --printer ip                  IP address of printer
 -P | --preset name                 Select a default preset
 -a | --autofocus                   Enable auto focus
 -n | --job Jobname                 Set the job name to display

Raster options:
 -d | --dpi 300                     Resolution of raster artwork
 -R | --raster-power 0-100          Raster power
 -r | --raster-speed 0-100          Raster speed
 -m | --mode mono/grey/color        Mode for rasterization (default mono)
 -s | --screen-size N               Photograph screen size (default  

Vector options:
 -V | --vector-power 0-100          Vector power
 -v | --vector-speed 0-100          Vector speed
 -f | --frequency 10-5000           Vector frequency

So, the folks over at Fubar Labs made a challenge to themselves and anyone else who wants to participate. Basically, write one program every day throughout the month of march. Any language, any function, but be creative. I doubt I can keep up the entire month, but it sounds like a really fun way to expand ones coding horizons and do some neat stuff. So anyways, here’s my first code for March Madness.

For my first madness script, I wrote a quick script to grab the most recent posts made to pastebin.com and grep their contents for any references to passwords. Then I display the URL to the posting and the line that matched. Pretty simple, and pretty fun. Watch what you put in those pastebins kids.

htink will be hosting a Linux tutorial, today Tuesday, Jan 26 2010. Both Ben Combee and Myself have volunteered to assist. This will not be at NYC Resistor however, look for it at Bug Labs ( your friendly neighborhood purveyor of fine open source micro-controllers ). I do not work for British Telecom =P.

If you’ve ever wanted some guidance in the Unix world, this is a tremendous opportunity. The folks that will be available to you are all very talented. If you’re interested, more details HERE!

So way back in the 2.4 Linux kernel days I operated a shell server. It was kind of like a “proto honeypot”. We set it up to portray a bunch of fake information about itself. We then released it into the wilds of IRC claiming it was a “machine we just owned here have a free account.” Then we monitored the systems use via ttysnoop applications and pulled copies of anything uploaded.

The result was we pulled about 4 gigs of exploit archives. And a bunch of logs of people trying to figure out why their x86 exploits weren’t running on the DEC alpha that was pretending to be the wopr.

Anyways, one of the neat side effects of my playing with the proc file system was finding a limit on the upper bounds of top. By setting up procfs to displays stats for 1048 processors I managed to get top to collapse after one iteration of showing cpu usage stats. Added a fun screenshot to the gallery.

Among the fun easy things you can do to tweak your kernel, upping your jiffy count to present 16 years of uptime, and customizing your HZ values are the most fun. I remember running HZ at 1024 back when the rest of the world was rocking it at 100 and slowing themselves down massively. Kernel tweaks are fun, relatively easy, and a great way to learn. Be fearless, be stupid, and be prepared to watch stuff explode catastrophically. But, don’t be afraid to slash and burn and start anew.

Widget and Hans stayed up til 2am hacking up some iPod sequencers at NYC Resistor. We are using pdPod on iPodLinux. You can hack your own iPods too, as part of the re-ware project, we are trying to make it easy: http://re-ware.org

Thanks to Bre Pettis for his camera work.

This my advert for the Intro to UNIX class I’ll be hosting on March 21st ( Saturday ) from 1:00 pm to 4:00 pm.
code is available at: nycr.c
compile with : gcc -o nycr nycr.c -lncurses

Register here: Register!

I figured writing an advertisement in C would be the truly best way to handle an Intro to UNIX course advertisement. C and UNIX were born together at bell labs and share the same father, so you could call them half brothers… or something to that effect. And UNIX formed the fundamental basis for the construction of many of the operating systems you use today. Mac OS X claims to be UNIX standard compliant, and Linux is touted as a UNIX like operating system. In fact even Windows has a Unix compatibility mode. Learning about UNIX and Linux is a great base for understanding how your operating system, or any operating system works.

With operating systems like Ubuntu, and netbook linux revisions popping up all over there’s never been more people using linux who have no idea how unix or linux operates under the hood. We won’t be going to deep into the internals of these operating systems but we will discuss basic structure and focus on learning the tools you’ll need to navigate on your own.

So if you or someone you know is interested in learning to grok unix. Then follow the “more details” link… for more details!

Hope to see you there!

I thought I’d make the first Software post to the blog. And since I am always on the hunt for good console, non-GUI, based applications to make my life easier, I thought I should share one of my findings.

For those of you who use ever used Linux or Unix in an environment where you only had access to a terminal, and you wanted to see an overview of system resources, you have probably used top. Top is nice little task manger that displays whats running, and its memory, cpu, owner and so on. But its ugly and a bit hard to understand. It looks something like this:

I don’t like it at all, and searching for a something to replace it, I found HTOP. Their website doesn’t really glorify how great this tool is, and their screen shots are blah, so here is one of mine.

As you can see everything is pretty =). Shows you what all yours cores are doing, even in my beefy 8 core machine. The ownership of a process not only by the user, but by another process which called it. It also supports mouse clicks (one of the few terminal applications that do). And can be customized completely to your liking for each user on your system. In public spaces people are often wowed by it, because it looks so kick ass, especially in full screen.

It took some time to understand what the colors in the graphs were, so I’ll label them here. Red is system usage, blue is idle usage, and green is user usage.

This has been an application I have used almost daily for the past year. Its also a rare sight, as most console applications lack in the level of control that htop gives you. Enjoy it!