In message <20011215193848.09C917B55@berkshire.research.att.com>, "Steven M. Be
llovin" writes:
>>I believe it will.  I had trouble getting my 64MB to boot, but I have been
>>able to mount larger cards as additional filesystems.  My boot problems were
>>almost certainly pilot error.

>Tempting.  If I've followed this story correctly, you're booting from 
>CF and mounting /usr via NFS, using a USB Ethernet widget.  Does the 
>sound card work?  What about X?

Sound card:  Mostly.  It's an auvia, and I have had occasional weird skipping
errors; sounds like it's supposed to be playing ABCD and it actually plays
CDAB.  Probably a driver bug.  Other people have reported this on auvia
chipsets, and I'll be comparing with my mom's new laptop shortly.  Amusingly,
my mom's laptop also has the same video chipset, and has one of the same
quirks there - after I leave X, the console's text palette is screwed up, and
normal text is nearly black.  I can't get the IPAQ to do 24-bit color; trying
to do so turns the display off until I reset the unit.  I've got it working
just fine with 16-bit color, though.

Performance is tolerable for a "toy system"; it took about an hour to build
lynx (including gmake, libslang, and libtool), and it got about 8MB into
swap space in the process - but in its defense, I had screen and ssh running
at the time.  If I'd been running on console, it probably would have been
quite a bit faster, especially if I'd been able to hint that gcc should always
do -pipe.  (A lot of time goes into putting temporary files on an NFS-mounted
/tmp.)

When the sound doesn't skip (I can often get through one or two albums of
MP3's, with even a small buffer in mpg123), it's certainly decent; I put
a $30 pair of speakers on it and it's as good as any boom box.

-s