Bug#519800: Acknowledgement (FSTYPE=ext3 but only ext2 in ramdisk possible with MODULES=dep)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Mar 15, 2009 at 11:35:55AM +0100, Martin Michlmayr wrote: Actually, how about running fstype when generating the ramdisk to find out which modules you need (either in addition or instead of looking at the output of mount/fstab). I dislike the

Bug#519800: Acknowledgement (FSTYPE=ext3 but only ext2 in ramdisk possible with MODULES=dep)

* Jonas Smedegaard d...@jones.dk [2009-03-19 11:19]: Actually, how about running fstype when generating the ramdisk to find out which modules you need (either in addition or instead of looking at the output of mount/fstab). I dislike the idea of a ramdisk generator deliberately ignoring

Bug#519800: Acknowledgement (FSTYPE=ext3 but only ext2 in ramdisk possible with MODULES=dep)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 19, 2009 at 11:30:40AM +0100, Martin Michlmayr wrote: * Jonas Smedegaard d...@jones.dk [2009-03-19 11:19]: Actually, how about running fstype when generating the ramdisk to find out which modules you need (either in addition or instead

Bug#519800: Acknowledgement (FSTYPE=ext3 but only ext2 in ramdisk possible with MODULES=dep)

Actually, how about running fstype when generating the ramdisk to find out which modules you need (either in addition or instead of looking at the output of mount/fstab). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a