Become a fan of Slashdot on Facebook


Forgot your password?

Review: Make: Raspberry Pi Starter Kit 74

XWWT writes "A few weeks ago Make offered to send us a sample of its Raspberry Pi Starter Kit to see if we would do a review of the product. Samzenpus asked around the engineering team to see if there was someone who would be willing to do an on-camera review of the device. With all of the buzz about Raspberry Pi, I was very excited to get hands-on time with the device so I could more closely examine the platform. At first we wanted to do this piece as a video but quickly realized that a) it would probably be boring to see some blinky lights and push buttons working on a sample project, and b) the amount of audio that would need to be bleeped to cover my frustration with parts of the kit would be annoying. On a personal note, I also wanted to document all of my experience here as I thought it would be beneficial for newcomers to the maker technology and sometimes having someone else’s experience documented can help you avoid pitfalls and mistakes. (Full Disclosure: I am the Director of Engineering for Slashdot Media. We were given a review copy of the Make: Raspberry Pi Starter Kit. We were not paid for this review but had fun doing it.)" Keep reading for the rest of Wes's review.
Unpacking the Box:
The box was nicely packaged with lots of little pieces parts in baggies and was well assembled. I immediately pulled out the Pi board and all of the packaged elements to see what was included. It became apparent that the shipping box would be useless to keep all the parts together once I unpacked it and found an old small plastic tool box to keep the parts in for future use and transport.

Included in the box was the 512MB Pi unit, 1A USB charger (underpowered for big projects), Pi Cobbler kit, Pi enclosure, 4GB Class 4 SDHC card, breadboard, a trimmed down version of the Medtronics kit, short HDMI cable, jumper wires (male) and the Getting Started with Raspberry Pi book. They seemed to be packed well as subassemblies so I tried to keep them together as such until later so I wouldn’t lose or mix parts.

The Medtronics kit had LEDs, resistors, capacitors, diodes, pushbuttons, switches, jumpers and some timer chips; all fun toys. Basically it is a collection that anyone doing electronics work would need in order to do a handful of projects. Most of these parts are cheap when bought in bulk, but getting variety collections like this tend to be expensive as you are buying only a couple of parts so it was nice to see them included. I was disappointed that I didn’t see any male-to-female jumpers in the box as these are useful in connecting pins but realized that was the point of the Pi Cobbler Kit.

After I had looked over the board itself, I thought it best to actually try to follow instructions since I was supposed to review the kit. I opened the included Getting Started with Raspberry Pi book and reviewed the first two chapters to get an idea of what was actually on-board the Pi itself and to see how the “Getting Started” would work for a first timer. Typically I find that getting started books from Make try to appear like How-To manuals blended with a lab book and they don’t do well being either. That was certainly the case with this book as I progressed.

The first chapter was really helpful as it laid out what the main components were on the board and what the actual available processing power. The board is an ARM11, 32bit, 700MHz processor. We happened to get the B version so it has 512MB of available RAM. The physical size of the board is a little larger than a stack of credit cards, with all of the components it is about the total size of a mans pocket wallet (about 3”x2”x1/2”). I examined the physical joints on the board and all were machine done (expected) and seemed to be in good order. The first problem I noticed though was that the joints for the HDMI and Audio/Video jacks would not be sufficient to keep them from being broken off the board. Additionally the joints holding the power unit seemed shaky if the unit were plugged in/out too frequently (the book and blogs confirmed that suspicion). The Ethernet port on the board seemed to be in good shape as did the GPIO and Display and Camera Serial Interfaces.

I was pleased to see that there were some status LEDs on-board for simple debugging. Those of us that are used to solving boot problems with status indicators like LEDs or audible tones know that these are important when you just can’t get a board to respond.

I then examined the enclosure case assembly which still had the protective wrapping on it and stunk of cutting fluid. There were no instructions on assembly for that so I set it aside. There seemed to be small parts in that package and I didn’t want to lose them, so I left it sealed.

Setting up Raspbian:
I wanted to validate quickly that there were no problems with the board so I ran through the steps of flashing the SD card with a copy of Raspbian. I actually tried both the dd tool installation under UNIX and the Win32DiskImager to see if there were significant differences in the experience. While the dd process seemed straight-forward the Win32DiskImage was just as easy. I found the documentation here to be the simplest to follow. Some might argue that having a pre-loaded SD card would have been best but I think the point of doing this yourself helps you to better learn the process and get more comfortable with the device.

I then plugged in the HDMI cable to the Pi and dug up a USB mouse and keyboard. Next, I plugged in the USB power supply and SD card. Immediately I made a note to use a powered USB port next time as it would reduce the number of times I would have to torque the onboard USB ports. When I went to plug the HDMI into my monitor I realized that I only had DVI ports and had to scrounge around in my toolbox for a HDMI to DVI converter. (DVI converters are inexpensive and would have been a nice addition to the kit.) I also made a mental note at this point to DX the 1.5m HDMI cable for something longer. I put the board on a non-reactive surface (notebook) so the contacts would not short and then booted the device. I followed all of the default options laid out in the Getting Started book just to make it simple. All-in-all the experience in booting and setting up Raspbian for the first time was satisfying.

Make: Pi Enclosure:
When I first looked at the Pi Enclosure it was pretty easy to see how it was supposed to go together. What I didn’t realize was the amount of swearing it would take to actually get it done. There are only nine parts in the V1 assembly and it should be easy to do, but without instructions it might as well have had a million parts. There is a delicate balance between each of the parts and the tolerance is very low compared to the profile of the board. You also need to torque the enclosure parts to get them to fit together while balancing the assembly in one hand and not drop the Pi. Not at all optimal. In the end I broke a connector slot on the enclosure which required a little superglue to fix. Once I had the board in the enclosure I realized that the opening for the power port was off enough that it would require modification to accept the USB power cord. After taking the enclosure apart I used a project file to widen a couple of the openings (power, GPIO) and tried again, this time adding in the 26 pin ribbon for the Cobbler kit knowing I didn’t want to have to take this apart again just to add that in later. It was even more difficult to put the pieces together with the ribbon cable, but I got it to work. (BTW: Make sure colored ribbon is on pin 1 which is on the same end as the Pi power port.). The how-to for assembling the enclosure here seems to work fine, but doesn’t account for adding the ribbon cable. (I looked over the V2 of this box which uses bolts and nuts to hold together and I see there are problems with how you hold the nuts in place for assembly. I can only imagine the frustration with that version and the number of times nuts are dropped into the box only to have to open it and retrieve them to try again.) Better option: Make your own project box out of LEGOs.

Ada Fruit Cobbler Kit:
Basically the Ada Fruit Cobbler Kit is a simple device to connect the GPIO of the Pi to a breadboard making experimentation a little easier. The kit includes a PCB, socket, 26 pin ribbon and header pins. Assembly was pretty straightforward except for separation of the header pins. My kit came with the header pins in one stick with about 36 pins. You only need 26 (2x13) so breaking this down, while simple, still takes some care. I should have used jewelry pliers or side cutters which would have made sure I didn’t break it into 12, 13 and the balance. Adding back in one header pin is never fun and I should have known better.

Soldering was simple. First I soldered the socket to the PCB so I was working from the inside joints to the outside joints. Turning the assembly upside down worked well for this and my iron was still at a good temperature. I started from one end and worked my way down each set of pins, checked the joints and cleaned up one or two that were messy. Next I placed the 12 and 13 pins into a breadboard, set the PCB on that and worked from the middle pins out and then added the lone pin back in. (2x13 sticks would have made this much easier.) The header pin plastic melted a little because I was being aggressive, but a few tweaks and I was able level the socket with the pins so it didn’t look like my youngest child completed the work. It would have been a better experience if I had a soldering iron with temperature adjustment, smaller soldering tip and smaller diameter solder. My desolder tool helped when I found I had to reset a head pin that I accidentally pushed on with my iron.

I think assembly of the Ada Fruit Cobbler kit will be the most intimidating part of the kit for someone new to electronics. The kit calls out that you will need soldering skills and this is as basic a soldering job as you can get, but still some might shy away from it. I understand that more recent versions actually have the kit pre-assembled for those who don’t want to solder.

Good assembly instructions can be found here.

Working with the OS:
The Raspian OS is Lightweight X11 (LXDE) with Openbox. For non-Linux users this may seem a little scary but there is a whole body of work around this and outside of the scope of this review.

Configuring and setting up the OS on my home network was typical for a Linux install. I wish I had a wireless USB though so I didn’t need to rely on the Ethernet adapter and fear of having a cable pulled and dropping the device. Connectivity completed, I wanted to play with some programming on the device.

I was happy to see Python and IDLE in the install as it made writing a simple program to tinker with the system easy. Additional modules can be downloaded and installed easily. Sample programs are easy to find or write and are typical. At this point I had a working Linux desktop computer, the size of my wallet, connected to my network and a breadboard for experimenting with IO.

I have yet to run this headless but will do so at some point.

Working with IO:
After I completed the assembly items and tinkering, I picked out a project for the breakout board to see if there was something cool that I could show. I worked on the first simple IO example in the book and quickly found that the documentation is really poor for a first-timer.

The first example of GPIO work in the Getting Started book lays out that you should use male-to-female adapters, then promptly tells you that the Pi Cobbler makes it easier to experiment and then continues the experiment with mtf adapters, which aren’t included in the kit. It tries to compensate for this by using a really bad drawing of the GPIO pins that aren’t completely labeled and have caveats about versions of the board. So before wiring the board I had to do a little investigation about the version of the board which you can tell only by booting the device (a nice stamp on the board would have been nice). Fortunately I have a version 2 board making the wiring a little easier to follow. (More information on Pin IO can be found here.) I checked for errata on the book to see if some of it has been sorted out but didn’t see this addressed at the time I was setting the project up.

Note on IO projects: You should really make sure you have your circuits setup and buffered when working with external experiments. It is also important to understand how a breadboard works and which terminals are tied out. Basically if you aren’t careful and paying attention you can accidentally feed power back to your Pi and end up blowing it out. (Mixing the 3V3 and 5V will do that in an instant.) For a $35 board that isn’t too expensive of a lesson, but would probably cause a newbie to be quickly discouraged.

The ‘Hello World’ examples in the Getting Started for IO include lighting an LED and reading from a pushbutton. The setup for these circuits is pretty simple but the author of the experiment doesn’t explain well how the powerbus works on the breadboard which could easily lead to a project discouragement. Additionally, the diagrams are set for mtf jumpers so matching that to the Cobbler kit and making sure you get the correct pins there can be a problem. Reading IO in the samples was easy and was simply a matter of running as su and setting the direction of the pin and then echo or cat the value to set/read its state.

Other sample projects assume you have a PowerSwitch tail relay sitting around, which I don’t, so turning off an external device (table lamp) was out of the question in my first couple of experiments. I would have been nice to see either all of the experiments focused at what was in the kit, or to include all of the items needed for the experiments in the kit.

I tinkered with GPIO and Python to automate some of the work and it was all quite simple to do. Samples in the Getting Started were fine but as with most programming examples, there were some small typos.

I think for someone coming to this the first time the experiments in the book are pretty simple but assume some experience with electronics. For new electronics users I would recommend a copy of Make: Electronics as it does a good job of laying out Electricity 101 in straightforward terms. You will also want to start assembling some other break out tools which can be easily had from lots of sources.

I picked up a copy of Raspberry Pi Users Guide by Upton and Halfacree for more project ideas in the future and look forward to reading and working those projects. I also ended up getting a couple of other books about the Raspberry Pi to see what they have in them and will likely do a book review at some point about their content.

General Observations:
For $35 the Pi is a great buy but the problem is finding the companies who are selling it for that price; Make sells theirs for $50. The added project items needed in this kit seem to be a little pricy, causing the overall price to get it up to the $130 range. Ada Fruit Cobbler kits are running $8, Pi enclosures are running $15, USB chargers run about $7, 4GB cards run about $6, solderless breadboards about $15 and probably $10 for the extra parts in the box, $10 or so for the book. If you are already doing electronics hobby work, I would find a different sourced board and skip the extras here. If you are new and want to give this a try or want to one-stop the parts, then buy the kit.

There is a great deal of an IKEA effect by having you participate in the assembly and feel like you just made something cool. It was largely fun putting the parts together and I am thinking about project applications almost daily. One of our developers belongs to a racing club and we were thinking that these would be a cheap means of tracking and relaying car speed/vitals to a central unit. I am also curious to see if these would be a better solution for tracking car performance for those into hypermiling. In any case, I plan on trying a number of projects and continue to develop with the board.

Lessons Learned:
  • A) Find a project box or assemble one of the nice Lego Pi Enclosures described out on the Internet. The project enclosure in the kit is fragile and difficult to assemble. There is a nice example made by a German Scout named Biz and can be found here. Or, if you are clever, you can make something bigger and better. As there is no heat-sink on board, I would avoid enclosures with a lid so you can vent any thermal from the board.
  • C) Get a powered USB device to control your mouse/keyboard, etc. There are only a couple of open slots on the Pi.
  • D) An HDMI to DVI adapter is helpful.
  • E) Get a longer HDMI cable to make this practical for experimenting.
This discussion has been archived. No new comments can be posted.

Review: Make: Raspberry Pi Starter Kit

Comments Filter:
  • First Post (Score:4, Funny)

    by Anonymous Coward on Monday March 18, 2013 @12:08PM (#43203859)

    Unfortunately my Pi isn't quite quick enough

  • by Gothmolly ( 148874 ) on Monday March 18, 2013 @01:10PM (#43204569)

    No wireless. Less space than a nomad. Lame.

  • Pictures (Score:4, Informative)

    by jones_supa ( 887896 ) on Monday March 18, 2013 @01:29PM (#43204809)
    You could have spiced the article with some photos.
  • Double Standard (Score:5, Interesting)

    by necro81 ( 917438 ) on Monday March 18, 2013 @01:33PM (#43204875) Journal
    Perhaps this is a result of the author's experience, or how the author structured the review and geared it towards the /. audience, but I find a lot of griping and warnings about the electronics and not so much about the software. For instance: Regarding electronics:

    I think assembly of the Ada Fruit Cobbler kit will be the most intimidating part of the kit for someone new to electronics. The kit calls out that you will need soldering skills and this is as basic a soldering job as you can get, but still some might shy away from it.

    In the next paragraph, regarding the Linux install:

    The Raspian OS is Lightweight X11 (LXDE) with Openbox. For non-Linux users this may seem a little scary but there is a whole body of work around this and outside of the scope of this review. Configuring and setting up the OS on my home network was typical for a Linux install.

    To expend two whole paragraphs explaining how he soldered a bunch of header pins, and sum up that it might be intimidating to newbies, and then to basically say "RTFM" about installing and configuring Linux seems to gloss over an awful lot.

    More on the difficulties of hardware:

    You should really make sure you have your circuits setup and buffered when working with external experiments. It is also important to understand how a breadboard works and which terminals are tied out. Basically if you aren’t careful and paying attention you can accidentally feed power back to your Pi and end up blowing it out. (Mixing the 3V3 and 5V will do that in an instant.) For a $35 board that isn’t too expensive of a lesson, but would probably cause a newbie to be quickly discouraged.

    But software is just fine and dandy, and oh so simple

    I was happy to see Python and IDLE in the install as it made writing a simple program to tinker with the system easy. Additional modules can be downloaded and installed easily.

    I can understand that the reviewer is relaying their own personal observations, and perhaps the software really is that easy and straightforward compared to the wiring and breadboarding. Not necessarily true in my experience. The reviewer is assuming, or representing, different levels of experience and comfort between hardware and software.

    • The instructions for raspbian are fairly straightforward. This was a review, and not an introduction, so it seems reasonable to me. If anyone out there is reading this and wants help, please install BerryBoot [] on a decently-sized SD card, say 8GB.

      The hard part to me is selecting an SD card, because many of the fancy ones have poor random read performance... and that is outside of the scope of this comment. Even a slow card will work, though. No card under 1GB is useful and most things need 2GB to be useful.

  • by yog ( 19073 ) * on Monday March 18, 2013 @02:29PM (#43205639) Homepage Journal

    I got one about a month ago from Newark. I got a ($12) case too, and that came much sooner; the Pi took about two weeks to arrive.
    Setting it up was pretty straightforward. I installed the Raspbian image to an 8gb Sd card (about $7 from Amazon), plugged the Pi directly into my router, and powered it up using one of my various microUSB chargers I have lying around.

    Then I was able to get in easily using ssh. I updated the OS, added a few utilities, and started vncserver. From that point, I could access the graphical UI from a window on my Suse desktop. SSH is faster, however; the board isn't that fast.

    I plugged in a spare bluetooth dongle that was not recognized by my Suse desktop, but the Pi recognized it properly and could see other bluetooth devices around the house. Neat!

    I then plugged in a USB wireless dongle that I had lying around, and it came right up. Now it's completely portable around the house, no longer tied to the router. I attached a cheap webcam I had gotten a while back on ebay, and I installed motion, as per a nice how-to, and immediately the Pi became a surveillance system.

    I was going to set it up in front of the house, but then I got the idea I wanted to interface it to my electronic piano in the living room. I got a $6.75 MIDI-to-USB cable and attached the Pi to the piano. Previously I had an identical cable working nicely with a midi keyboard and my Suse desktop. This one did not seem to register as a midi device; I'm going to have to find a driver, or else write some software of my own. My goal is to have a tablet-controlled midi sequencer, so that I can record midi to the Pi and play it back through the piano. A bigger project than I've had time for up to now, but I hope to get to it soon.

    It's a fun little board and I highly recommend it to anyone who enjoys hacking around with Linux and automating things around the house. There's probably fifty other uses for it that I haven't thought of yet.

    • by xaxa ( 988988 )

      Try the MIDI-to-USB cable on your desktop.

      It's possible whatever driver it needs exists in Linux, but hasn't been included in the kernel you're using. (I'm expecting this situation with a touchscreen I bought: [] -- so far it works fine on Ubuntu, but I haven't yet tried it on Raspbian, it's in use for something else.)

      • by yog ( 19073 ) *

        It works on my desktop running OpenSuse. I went ahead and ordered an EMU XMIDI adapter from Amazon for $40. The cheap adapters seem to get overwhelmed very easily especially when sustain is on.

  • My experiences (Score:5, Informative)

    by xonen ( 774419 ) on Monday March 18, 2013 @03:07PM (#43206149) Journal

    A friend got me a PI recently as little present, which was very welcome.

    It's a great little device, though with some very odd design decisions.

    For me personally, the graphics chip is simply not needed. Also, onboard is a DSP that's unfortunately undocumented and hence disfunctional.

    The I/O pins are hardly protected - so if you want to experiment with electronics, best start by a simple circuit to protect them, with some transistors or an optocoupler. Also, the pens are 3.3V and provide no power more than a 10mA... Not really an issue, but also implies that you cannot drive a relais from it directly.

    The biggest issue is in the power. The power supply i had was adequate (1.4A), but, the PI itself is not. Hotplugging the USB with any power hungry device - like a WLAN key, or a webcam, is likely to power-cycle the PI. It is known issue - but can come unexpected. Low power devices like mice and keyboards are likely to be hotplugged but, any sane person only uses those during installation process.

    Software - What works, what not works. Firefox runs. This is really impressive, it actually works. Albeit, that even when idle, the FF process alone will take 60-80% of the CPU power.

    What not works - mono. Well, mono works. But, there are issues - especially regarding floating points, and it typically shows when accessing databases. 'Conversion error in ( or some - i'm not that good with mono).

    Performance - it is said it 'feels' like a pentium 300. I agree, overal the performance is not very sluggish, and much what you'd expect from such device. However, when running benchmarks, things turn out different. For example stockfish, the chess program. With parameter 'bench' it'll perform a single-core benchmark.
    Ubuntu-pc-32: 4900ms
    Ubuntu-pc-32 / optimized build: 4500ms
    Ubuntu-pc-64: 3300ms
    Raspberry pi: 239.000ms
    From this benchmark, the PI more runs like a pentium66. This is a cpu and integer intensive benchmark. I'm sure modern memory access will make up for it. However, it is very clear that the ARM instruction set is very very elegant, but also very inefficient.

    As far as connectors etc go, i agree with the reviewer. It's soldered, but does not look very bullet proof. Best be handled with care, and unplug power by unplugging adapter from mains might be prefered. That being said, apart some installation quircks i did not have to powercycle it often.

    Stability. On idle load, it is very stable. I installed 'motion' - the videocam 'guarding' software, and configured it. However, this software was not stable. I don't know if it's the software, the port, or the PI, but it will not run much longer than a day, when making repeated snapshots (like 1/second).

    The basic distro's seem fine. When adding custom software, the debian package may well be present (very very much kudo's to those distro maintainers!). Compiling software yourself on the PI is going fine in most cases, though may take a while. On larger compiles it may suffer from low memory and break - so, if you want to compile a lot for your PI, best set up a crosscompiler. The biggest issue i had was in unforeseen instabilities, either when putting the PI under load, either when using not-too-well-tested software like mono. That being said, it is very impressive that almost anything in a standard debian distro just works.

    On occasion, i had a process that could not be killed. Here, it shows the architectural differences between i386 and ARM i guess. On a pc, the kernel should be able to kill any process. On the PI arm, this seems not always to be the case. I'm not enough cpu guru to guess details on this, just i guess it has to do with ARM.

    Wifi - i had a nice wifi stick. It works fine. However - again, not perfect stable in my view, it may loose connection. May be my adapter maybe the pi. If you have chance, just use ethernet - it will releive the pi's cpu on the fly, and you may need the cpu power for other things.

    What's missing:
    Audio-in. This is really a

    • by xonen ( 774419 )

      Note about the floating point - before ppl start pointing out - i tried both available debian distrubitions (with hard and soft floating point). While the soft floating point did fix some issues, unfortunately, not all of them (when it came to mono/mysql).

    • by psergiu ( 67614 )

      1) Have you done

      apt-get update
      apt-get dist-upgrade

      (or "raspi-config" and select "update")

      to get the newest (and fastest binaries) from those distros ? With the latest 3.6.11 kernel and optimised libs using the HW floating point and other hardware goodies, the RPi is way faster that when running the default, half-a-month old packages.

      2) Have you tried overclocking ? The UK-made RPis with Samsung RAM have no issues running at 1Ghz (from the default of 700Mhz) and with RAM at 600Mhz (default 400Mhz). The Chine

    • Re:My experiences (Score:5, Informative)

      by xaxa ( 988988 ) on Monday March 18, 2013 @04:31PM (#43207129)

      Note that the processor in the Pi was designed in 2002 (!), so it's probably not a fair reflection of current ARM chips: []

      I've bought a Hardkernel Odroid-U2 [] and plan to replace my webserver. The Pi was almost powerful enough -- it was fine for everything except resizing photographs on demand. The Odroid-U2 has 2GB RAM, and a processor that was released last April ( [] "4 Quad", if I follow the description correctly).

      I will still use the Pi, but more for toy/hobby stuff. At the moment it's monitoring my household electricity use (519W), and drawing a nice graph. Not too taxing:
      20:31:08 up 14 days, 23:09, 1 user, load average: 0.18, 0.08, 0.06

    • Amazon, twenty bucks, Pogoplug. 3xUSB2 that actually work, Marvell ARM chip, if you are careful about selecting the proper model you get 512MB RAM. And the icing, GigE not attached to flaky USB. I think they ones they're making new now have only 128MB RAM or something. There's a second generation device with USB3, but it has a slower processor. Read about them in the arch linux devices section, they detail all of them since Linux runs on all of them. If you don't need the video, this is by far the cheapest

  • I already have a beagle board and a beagle bone, is there anything the Pi can do that the beagle boards can't?
  • Personally, i've never been interested in an rpi, im really very into arm based tech, but at least in australia where i am, the rpi ends up being quite expensive. Its been nice as a project for the general community to work on cause it seems to have focused everyone on a single arm board and so alot of projects have errupted from it. However as a piece of hardware, by the time you could get it in australia there were (and still are) much better options. Ultimately you'll end up spending $50 here, and then t

    • I don't know what you'd pay in Australia, but in the US I can get a Mk802 for around $45. For a media player, it's a better choice. But the R-Pi is still a nifty board from a hacking standpoint, since it has so much more GPIO than other options. But again, you could cheaply add an Arduino knockoff to any cheap device and get plenty of IO.

      The coolest thing I have seen done with a Raspberry Pi is adding Ambilight functionality to XBMC. XBMC runs basically OK on the Pi, though it's a bit gutless for it. Someon

      • by ( 760528 )

        Well, the mk802 is a system on a stick (which isnt what im refering to)... but for the same price you can get an mk802, you should be able to get its dev-board cousins - i.e. what the rpi is (which typically will have all the connectors on the arm chip exposed, gpio included) - and those dev boards have been around as long as the mk802 has.

        As I said in the post above though, i love how the rpi has gotten this ground swell of support following it, and its spawned some very kewl things (all of which work equa

  • by Anonymous Coward

    I've had an RP since Christmas (my children know the right gifts to buy Daddy). It's a nice, but not-that-fast, Linux system with one major problem. Everytime I hot plug anything, the system reboots. This teh suxors when you want to load or save some file. I need to ftp for that. After initial setup using an HDMI-VGA converter, I now work with it using X on the home network. LAMP server works well, but don't try phpmyadmin with the local web browser, it's far too slow for that. Phpmyadmin works well

  • You mean all the /vertisements? That's your own doing. Should've eaten your dogfood first. I mean pie

egrep -n '^[a-z].*\(' $ | sort -t':' +2.0