Bug#290675: Warning message about initrd is out of date

[Andre Tomt]

The hunk that made cramfs initrds work earlier was the invalidate_bdev 
hunk, not the *time hunk. I'm not exactly sure what the *time hunk 
fixes, but it has never been needed here for me.

The debian fix for the initrd boot problem was the invalidate_bdev hunk 
to fd/block_dev.c ; it was dropped from Debian sources around 2.4.26 or 
27 (maybe even .25?) as upstream fixed it differently. I can't find it 
in the debian/changelog now however; i guess it was dropped when 
splitting up the mega-patch.

There is a separate issue however, causing problems for initrds (and 
other things) on sparc32 that may or may not be fixed upstream yet 
though.. Debian kernels have that particular fix 
(095_sparc32_initrd_memcpy.diff).

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]