Guus Snijders wrote: > 2007/8/19, Dimitrios Apostolou <[EMAIL PROTECTED]>: >> Roman Kyrylych wrote: >>> 2007/8/18, James Rayner <[EMAIL PROTECTED]>: >>>> On Sat, August 18, 2007 10:21, Dimitrios Apostolou wrote: >>>>> Hello list, >>>>> >>>>> for testing purposes I need to boot my arch system using old versions of >>>>> linux. However, because of udev and libc, I doubt I'll be able to boot >>>>> old enough kernels. > > [...] > >>> Maybe just install another system from 0.7.2 iso where there are >>> 2.6.16.18 and 2.4.32 kernels (if this does not limit your testing >>> procedure). >>> >> Unfortunately I can't reinstall the system. So if I need to go older >> than 2.6.16 I guess I'll try installing a static /dev filesystem. Any >> ideas how to do that, given that udev is permamently mounted on /dev and >> that I have mostly remote access to this system? > > Maybe it's an option to use Qemu (or some other virtualisation package) to > run a 0.7.2 system? > Of course, that would be no option for hardware testing...
Exactly. ;-) Anyway I managed to boot a kernel as old as 2.6.16. I then tried 2.6.13, which is the first to support the uevent subsystem needed by udev. Interestingly the boot process passed the udev step but hanged while mounting (read-write I think) the root filesystem. I got an error telling me about bad superblock of ext3 filesystem, and that I should run fsck (which of course I didn't...). I didn't have enough time to investigate so I rebooted to a good kernel. What is funny is that the root filesystem was mkfs 'd about 2-3 years ago. What could have possibly changed in the latest kernels that makes it unmountable with old ones? Really strange... Thanks, Dimitris _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
