My nephews have an old K6–350 with 64 MB RAM, 2.1 GB HDD, and S3 Trio64 graphics at their grandparent's hou­se. They used it to play about 6 windows games they have installed, until one day when boot files were suddenly gone. Unfortunately (or not?), I already thrown out all Windows 95/98  instalation disks. I also don't posses working floppy drive for few years, so all the floppies are already gone (except for few, but as I found out, those are unreadable anyway). So I went on a quest finding a linux distribution that:

• would run on i586
• would run some desktop environment, while leaving some of the 64MB of RAM unallocated
• would run recent wine
• would run X with GL/DRI, so those games could be run

Well, I've got some bad news – there is no such distribution. Here's why:

Damn Small Linux

DSL installed OK to the harddisk, but it only allowed it's ownmyDSL extensions to be installed. Those doesn't include dosbox or wine >0.9.4×. Switching to apt didn't work on that version, because package statuses were broken, and it would mean downloading and forcing installation of each deb. (Well, I'm writing it after few more days of expermimentation, and it doesn't look like big deal now :), so maybe I'll return to that).

Vector Linux Lite

The LiveCD didn't boot, and installation was too big for 1.8GB partition. Where's the ‚Light‘ part?

Deli Linux

Looks nice in VM, however, there are no packages for it – neither wine or dosbox.

Debian

I installed XFCE environment, but it looks too heavy for the machine space- and memory-wise. Maybe if I started without X and then added JWM and ROX session, and configure it properly… well it would take some time to have it done.

TeenPup 2008

This is a puplet – spinoff of Puppy Linux 2.1. It contains many applications, games, nice icons. But getting packages for puppy linux is a quest itself – searching forums for .pet files, finding passwords for password protected repositories, and fighting incompatible versions of libraries. This distribution helped me getting acquainted with ROX file manager, which is actually quite nice once you understand the philosophy of it. However, wine package didn't work because of incompatible libc. I also managed to lead it to the state where it wouldn't reboot intead it always just restarted X session. So it was time to move further.

PuppyLinux 4.1.2

So after spending few days with TeenPup I understood desktop and bootup process of PuppyLinux, so I picked generic one. Installing wine went smoothly. But DirectX games wouldn't run on Xvesa or Xorg with vesa driver. The solution looked simple – just download full Xorg 7.3 and finally have answer to question, whether the system is actually capable of running those games from Wine. However, there is bug in Xorg 7.3 – xorg-server 1.3.0 doesn't export some of basic symbol properly, so enabling S3 driver results in linking error „Symbol RamDac not found“. So I tried to find a puplet that includes X.org 7.4

LXDE puplet

I found that one, burned the ISO, and found out it's i686 only.

Arch Linux

and arch linux is i686 only as well.

TinyME

This is the last distribution I tried. Looks quite momry heavy (still LXDE is way heavier than ROX/JWM) and still has xserver 1.3.0

Conclusion

There's no out-of-the-box solution. So I will either return to DSL or Debian, or get some bootable CD with win95 bootdisk and just run sys c: (to find out, some other system files are missing :)) – but getting such CD is not easy, who needs win95 anymore?

UUID partition was mystery to me – according to all documentation available they make life easier instantly and you no longer have to worry about your partition letters. Since I'm using LVM on all servers I manage I already stopped worrying. But since this is preferred method now, I wanted to use it (especially after last time udev created /dev/mapper/vg-lv device, but no /dev/vg/lv device after boot and I realized that after my backups were week old and I had to restore corrupted file :().

But here's the problem with UUIDs and LVM: After you create new LV, vol_id and blkid will show their UUID. But as soon as you want to mount that LV via /etc/fstab, it yields Special device UUID=... does not exist. Today I learned this special command:

sudo partprobe

It updates the /dev/disk/by-uuid directory and your uuid mount works like a charm.

I just found clever post with steps to make more space available to your root partition by having /usr compressed with squashfs and overlayed with unionfs. So I'm adding it here as note to self to try it on my Ubuntu on USB disk, where I devoted to much space to NTFS partitions :) It also could be fine for Aspire One, if my wife will start to actually store any files there, not just do the browsing.

http://po-ru.com/…-the-eee-pc/

Oh yes, and according to this comment, Ubuntu 8.10 works nicely on Aspire One, so if I'll be willing to sacrifice nice bootup times of Linpus to more standard way of administration (at least for me), I might give that a try.

I recently got this cutie from Acer. It's purpose is to be my wife's browsing machine. For that I had to modify some things:

1. Install Skype
2. Install Pidgin
3. Upgrade to Firefox 3
4. Instal mscorefonts
5. Video player with subtitle support

   (more…)

Now this was another long night: I was trying to create IPSec tunnel between Cisco PIX and Ubuntu-based router with OpenSwan. At first, I was unable to estabilish ISAKMP communication as PIX always rejected it with SA not acceptable. That was solved with adding

ike=aes-sha1-modp1024

into ipsec.conf configuration file. And once I got though this I came to thegreat showstopper, that is mentioned in the title. Cisco and various forums state, that my pre-shared key was wrong (but it wasn’t), that I should do clear crypto sa on the PIX (but it didn’t help), or that my access list was wrong (but they seemed right). After giving up and getting some sleep instead I decided to change the encryption (I used AES with SHA1). I added new policy for 3DES with MD5 and suddenly the message was gone!

But there was a new one, saying Proxy Identities Not Supported, and finally I found where I should have had 192.168.8.0 instead of 192.168.1.0 – in the ipsec.conf.

And from that time on, the tunnel works perfectly.

One more note:

After you’re happy that your tunnel has been estabilished and you’re re looking forward to trying it out, you may get disappointed that no pings to remote internal network will work, and that ssh will return No route to host.The secret ingredient is to use internal network interface as source, so use

ping remoteinternalhost -I routerinternalinterfaceip

ssh -b routerinternalinterfaceip remoteinternalhost

If you ‚promoted‘ a Samba share to DFS root, a try to access the DFS link right after the change, you may receive rather long and useless error message from explorer, that starts with <location> refers to a location that is unavailable. This is all just a result of your impatience. Log off, log on and try again!