edmundo@rano.demon.co.uk writes:
I had it sort of running just now ... [...] I then had no cursor, but a shell, with which I could walk around the file system using pwd, cd and echo *. It reboots as soon as I do anything that involves a fork, such as ls, cat or sh. So I'll worry about configuring X later, right? :-)
I built main and sigma0 myself under Debian 2.1, i.e. gcc 2.7.2.3 and binutils 2.9.1.0.19a, from the sources dated 981207. Everything else was already on grub-ext2fs-floppy from the ftp site. I compile on a 686 machine and run Fiasco on a 486 machine.
I have tried the boot floppy you sent me, and I was able to boot L4Linux into multiuser mode. However, I had to replace "glinux.gz" with my own, self-compiled L4Linux server image because the one on the boot floppy didn't contain drivers for my SCSI card.
One thing you might want to try is booting a newer L4Linux binary (the one one your floppy is pretty old). I'll send you mine under separate cover.
If this also doesn't work, I guess that Fiasco has a problem with 486s. Right now I cannot test this because I currently don't have a working 486, but I probably will get one the week after the next.
Michael
PS: I have uploaded a new grub-ext2fs-floppy.gz which contains the newest version of all binaries, including Fiasco and working configuration files. It's at URL:ftp://ftp.inf.tu-dresden.de/pub/os/L4/devel/grub-ext2fs-floppy.gz.
If this also doesn't work, I guess that Fiasco has a problem with 486s. Right now I cannot test this because I currently don't have a working 486, but I probably will get one the week after the next.
Many thanks for glinux.gz and the new grub-ext2fs-floppy.gz. Unfortunately I got the same result with both of those as I got before: I can boot with init=/bin/sh, but the machine reboots itself as soon as I try anything more difficult than cd, pwd or echo *.
Edmund
l4-hackers@os.inf.tu-dresden.de