On Mon, 24 Jan 2005 09:17:05 +0100, Tore Anderson <[EMAIL PROTECTED]> said:
> * Andres Salomon
>> Actually, 2.4 still (last time I checked, circa 2.4.24) needed
>> cramfs fixes in order to work w/ debian kernels. Mainly, some
>> inode stuff wasn't being initialized correctly (iirc).
> If that is so, that's a bug in the kernel, as it's /supposed/ to
> support cramfs initrd. At least, what I based the bug report on is
> the change that was made to init/do_mounts.c that indicates that
> cramfs should work:
Well, if we can get confirmation of the fixed behaviour, I'll
take the warning out. I don't use initrd, and have long since
migrated to 2.6, so it is not easy for me to check this.
>> http://linux.bkbits.net:8080/linux-2.4/diffs/init/[EMAIL
>> PROTECTED]|src/|src/init|hist/init/do_mounts.c>
> I have not tested it myself, though, as I've migrated to 2.6 a
> long time ago and have also burned all bridges going back to 2.4
> (nothing in /dev/, LVM2, etc..)
Same here (well, I don't use udev, but I do use lvm2).
>> Instead, kernel-package should probably check the kernel version
>> being compiled; if it's < 2.6 (or, if 2.4 fixes the cramfs issues,
>> whatever version that happened in), display the initrd warning.
> My impression is that Manoj is loath to include any
> ersion-specific code in make-kpkg, so I assumed it would be futile
> to ask this. :-)
That is correct -- too much of a maintenance nightmare.
manoj
--
One Bell System - it sometimes works.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
