On Monday 17 November 2003 18:59, Svetoslav Slavtchev wrote: > > ... cramfs > > > > > > > > > Should I make it an option in mkinitrd ? > > > > > > > > > > > > I guess yes. But this is compatibility problem. It is not > > > > > > supported on vanilla kernel so you have to detect patched kernel > > > > > > somehow. And how are you going to do it? You will get a flood of > > > > > > "bug reports" from users who compiled their own kernels (vanilla > > > > > > ones or whatever) and cannot load initrd. > > > > > > > > > > just check for /mdk/ and ! /custom/ in uname -r output > > > > > > > > that is still just wild guess :( > > > > > > but it'll work... > > > grep /proc/filesystems else > > > > not working. you can build initrd for 2.6 under 2.4 or other way > > round. or even out of miniroot. > > what about > > grep cramfs /boot/System.map-[KVER] ?
at least make it depend on CONFIG_CRAMFS_INITRD. it is not that crmafs is available but that it is used for initrd. but if it is really read-only, our initrd needs some tweaking indeed > have you got my last mails with the modified mkbuild.pl & co ? yes > have you tried them ? no :)
