.comment: A Two-Pound UNIX Workstation On the Cheap - page 2
And A Great Pinball Game, Too
I actually owned a Libretto 70CT, brand new, briefly in early 1998. I'd gotten it after learning on the Toshiba website that OS/2 was supported. The Toshiba website was wrong, as Toshiba finally admitted in taking the machine back.
The problem was the PCMCIA floppy drive, which disappears as soon as the booted kernel takes over from the BIOS. There are probably a couple of ways around this, but they involve dual booting, copying the floppy images to a Windows partition, and editing some files to point to that partition. But the fact is that I can find no record of unqualified success getting OS/2 onto a Libretto.
Linux faces the same problems, but because Linux is Linux they are more readily got around, as I'll explain in due course.
As with OS/2, they have at their heart the PCMCIA floppy drive. The Linux kernel boots and instantly can no longer see the drive whence it booted -- so when it prompts you for the modules floppy and you insert it, it does you no good. (It is said that the Red Hat CD contains a floppy image that includes a kernel with PCMCIA support and the PCMCIA stuff itself, which might allow a network or FTP install; I do not know, because until Red Hat pulls desktops out of /usr, it'll not be a distribution that I willingly use.) There is, kicking around on the Web, a kernel patch that supports the PCMCIA floppy; it works with 2.2.x kernels and, apparently, some early 2.4.x ones, though not the current versions, but this does no good at the install.
When installing to a machine of limited resources, one needs to be circumspect. It is sad that modern Linux distributions tend to be a little sluggish on slower Pentiums with "merely" 64 megs of memory, but that's the situation we're stuck with. Certainly, no one is going to do much compiling on a Libretto. Thus, we have the one situation where Debian's legendary reticence to release anything the same decade that everyone else did -- and therefore its ability to run on low-end machines -- is a definite plus. Debian's package manager blows the whiskers off everything else as well, and this is, as I mentioned, a machine in which software is going to arrive, chiefly, in binary form.
Which has nothing to do with the fact that what's on the machine right now is a combination of SuSE 7.2 and 7.3. It's a combination because the update function of SuSE 7.3 doesn't work very well. And it's on the machine because I already had a notebook drive containing it.
Dropping in the replacement drive, a 4.2-gig IBM, was a piece of cake, though the fit was a little tight. (The 100CT is supposed to accommodate a 9.5-mm-thick drive, but the one that came with it is 8.45mm.) I powered up the machine, and Linux booted.
This was of course just the beginning. XFree86 did surprisingly well first time I started it, because the machine whence the drive came also had a NeoMagic chipset. Problem was, it expected an 800x600 display, so the bottom 120 pixels were not available. These are sometimes important.
SuSE's SaX2 X configurator worked, sort of. It even allowed me to specify a screen resolution of 800x480 -- not that this had any actual effect on the display when I fired up X.
There are lots of XF86Config files for portable machines available on the Web. But most of the ones that involve older hardware are for XFree86-3.3.x, and I wanted to use 4.1. I went through a lot of other people's configurations, trying all kinds of strange modelines, before I found the magic words: Option "override_validate_mode", which is XFree86 language for "I said 800x480 and I meant 800x480, so do it, dammit!" The magic words proved convincing.
KDE looks pretty cool on the little machine, particularly because font anti-aliasing is supported with the NeoMagic chip and XFree86-4.1, but all is not well in some respects. To put it another way, knowledge of the files in ~/.kde/share/config is helpful, because KDE-2.2.2 don' do no steenkin' 800x480 -- the buttons at the bottoms of the configuration screens are all below the screen itself, even though the desktop is well-behaved. (This could be a Qt thing, because I encountered the same problem with Opera. Or it could be that there is a configuration option as yet undiscovered that brings everything into line. And this problem affected only the configuration windows -- everything else, including the KWord-1.1.1 I'm using to write this, fits on the screen.) It helps to have a second machine running KDE, so you can see what the hotkeys are. It was by this method that I discovered that the first page of the Konqueror file manager setup has two settings determined by alt-o. Oops. Because the screen space is fairly limited, it's good to turn off toolbars and status lines and other fripperies that are useful on big screens but expensive luxuries on little ones.
The machine's hardware clock insisted that it was July 18, 2001, which it wasn't. The syntax for the date command was dreamt up by a sadist, and "hwclock --systohw" isn't exactly intuitive, either. It is little details such as this that impart the notion that Linux is not easy to use. And I did not exceed in convincing YaST2 that I have an OPL2-SA3 sound chip instead of the Ensoniq 1688 that resided on the machine where the original install took place, though this could be a function of the terribly broken online update feature in SuSE.
KDE is slow but tolerable on the Libretto except for initial loading, which is deadly. Fortunately, the Libretto's hibernate (suspend-to-disk) function works if it is set up properly. Setting it up means making sure that there's nothing on the last 66 megs of the drive; if there is, it will be overwritten. This space needn't be on a partition. The Libretto doesn't care -- it doesn't consult the partition table when hibernating. (There is potential trouble if you're using a drive greater than 8.4 megs, because the Libretto's bios doesn't support them. People have cooked up all kinds of tricks for sorting out where the hibernate space is, but I've seen nothing that I'd call reliable.) I copied all the stuff from /dev/hda4, the last partition on the drive and the one normally mounted as /home to /dev/hda3, logged out as me and back in as root (this is one of the few cases where SUing root ain't enough), then fired up fdisk, deleted hda4, made a new one a little smaller, formatted it, moved everything back, and had my hibernation space. Now, instead of shutting down, I just close the Libretto's lid. The drive chatters away for a few seconds, then the power lights go off. If I come back in an hour or a week or a year, when I reopen the machine, the contents of the system memory plus video memory are restored to the screen in less than 15 seconds. (One must remove and PCMCIA cards or docking stations before doing this; PCMCIA cards will suck your battery dry and in any case if you yank 'em while the machine is asleep and then, later, start the machine back up, as far as the machine is concerned you have violated Einsteinian physics and it will go berserk.)
All in all, the little Libretto mostly works with SuSE Linux. Which isn't to say that I'm satisfied.
Solid state disks (SSDs) made a splash in consumer technology, and now the technology has its eyes on the enterprise storage market. Download this eBook to see what SSDs can do for your infrastructure and review the pros and cons of this potentially game-changing storage technology.
- 1Linux Top 3: Linus Lashes out, Linux 3.14 Gets PIE and Ubuntu One is Done.
- 2Linux Top 3: Ubuntu 14.04, Debian Gives Squeeze More Life and Red Hat Goes Atomic
- 3Linux Top 3: CoreOS, Oracle Enterprise Linux 7 and Ubuntu 14.10
- 4Linux Top 3: Debian Dumps SPARC, Ubuntu Takes Over Linux 3.13 and the Core Infrastructure Initiative
- 5Linux Top 3: Fedora, Ubuntu and Gluster Lose Community Leaders