initrd and fc3
i am testing fc3 by using an old-school initrd. by old-school i mean not the new initramfs/cpio type initrd. the process i use to create the initrd works for all other distributions (suse, mandrake, debian, fc2, 2.2.x, 2.4.x, 2.6.x, etc) but fails with fc3 (2.6.9-1.667).
upon system boot, the kernel executes, checks to see if the initrd is initramfs (it isnt), finds the initrd (ext2), mounts it, and then immediately exits without executing linuxrc.
anyone have any ideas as to why linuxrc is not being executed?
Quoted 9 lines · rich turner
i am testing fc3 by using an old-school initrd. by old-school i mean not the new initramfs/cpio type initrd. the process i use to create the initrd works for all other distributions (suse, mandrake, debian, fc2, 2.2.x, 2.4.x, 2.6.x, etc) but fails with fc3 (2.6.9-1.667).
upon system boot, the kernel executes, checks to see if the initrd is initramfs (it isnt), finds the initrd (ext2), mounts it, and then immediately exits without executing linuxrc.
Quoted 10 lines
anyone have any ideas as to why linuxrc is not being executed?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
You pretty much deduced the bug is in FC3, and not the general kernel...
So why exactly is this on topic on LKML?
Is the bug reproducible on a vanilla kernel.org kernel?
- Mif
Quoted 21 lines · Matan Peled
Quoted 9 lines · rich turner
i am testing fc3 by using an old-school initrd. by old-school i mean not the new initramfs/cpio type initrd. the process i use to create the initrd works for all other distributions (suse, mandrake, debian, fc2, 2.2.x, 2.4.x, 2.6.x, etc) but fails with fc3 (2.6.9-1.667).
upon system boot, the kernel executes, checks to see if the initrd is initramfs (it isnt), finds the initrd (ext2), mounts it, and then immediately exits without executing linuxrc.
Quoted 10 lines
anyone have any ideas as to why linuxrc is not being executed?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines
You pretty much deduced the bug is in FC3, and not the general kernel...
So why exactly is this on topic on LKML?
i agree that this isnt the proper place for this topic if it is only related to fc3.
Quoted 3 lines
Is the bug reproducible on a vanilla kernel.org kernel?
i am doing this now. if this is reproducable in vanilla 2.6.9 then i will let the list know.
Quoted 8 lines
- Mif
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 09 Dec 2004 11:28:01 PST, rich turner said:
(off-list reply)
Quoted 3 lines
upon system boot, the kernel executes, checks to see if the initrd is initramfs (it isnt), finds the initrd (ext2), mounts it, and then immediately exits without executing linuxrc.
Are you *sure* linuxrc isn't run at all?
You might want to run a test 'mkinitrd' and look at what FC3 expects to find in there (yes, it generates a cpio archive, just extract it into a scratch directory), then compare that to your initrd and see if you're missing something (permissions, a directory, etc).
It's possible that the linuxrc is running, not outputting anything to the console, and hitting an error that causes further progress to fail, making it LOOK like it's not running at all.
Quoted 1 line · On Thu, 09 Dec 2004 15:48:05 EST, [email protected] said:
(off-list reply)
Or it would have been, if I had hit "reply" instead of "reply all".
And barring that, it *still* would have been, if I hadn't noticed the cc:, removed it, and then managed to paste it back in again.
Argh. Good thing I'm not trying to write code today. :)