On Wed, 02 Feb 2005 22:27:45 +0100, Andre Tomt <[EMAIL PROTECTED]> said:
> 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).
Well, I think we still need to have this warning in place,
then. I have toned it down a bit, to make it less frightening, and,
you know, it can be turned off totally of it does annoy you.
manoj
--
You're not drunk if you can lie on the floor without holding on. Dean
Martin
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]
