Messages in this thread | | | From | "Bradley D. LaRonde" <> | Subject | Re: [patch] initrd fix 2.3.48 | Date | Wed, 1 Mar 2000 02:17:48 -0500 |
| |
Test results of latest patch:
It seems that it works great for initrd, and for general ramdisk, but only as long as CONFIG_BLK_DEV_INITRD is defined.
However, the file won't even compile if ramdisk is configured without initrd. This is apparently due to initrd_fops being used outside of the #ifdef CONFIG_BLK_DEV_INITRD part.
The fact that RD_LOADER and BUILD_CRAMDISK are always defined at the top of rd.c (except if MODULE is defined) also strikes me as very odd (but that is not due to this particular fix). Maybe the relationship between RD_LOADER and CONFIG_BLK_DEV_INITRD is complicating things?
Regards, Brad
----- Original Message ----- From: "Mike Galbraith" <mikeg@weiden.de> To: "linux-kernel" <linux-kernel@vger.rutgers.edu> Cc: "Linus Torvalds" <torvalds@transmeta.com> Sent: Tuesday, February 29, 2000 11:47 PM Subject: [patch] initrd fix 2.3.48
> Attached, please find version 2 of initrd fix for 2.3.48. > > Changes from version 1: > - Removed explicit initializations. > - Moved invalidate_buffers() avoidance away from generic code. > > Tested with a 15mb initrd, and (light) generic ramdisk usage. > > -Mike > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |