Kernel panic: No init found 1727

the following words to the mbuttes incomp.os.linux.misc...:

I know that, but that is not what I was saying. I am talking of a directory called *-initrd* - i.e. in the root directory of the on-disk root filesystem - which is being used by kernels that make use of aninitrdor aninitramfsfor making thepivotroot.

After thepivot,theinitial-ramdisk-initrd- orinitial-ram-filesystem-initramfs- becomes mounted on *-initrd* and the on-disk root filesystem is mounted on *"-".* Then, theinitrdorinitramfs- both of which are compressed filesystems living in the RAM - are safely unmounted.

As I stated in my previous post, if your kernel doesn't make use of aninitrdor aninitramfs,or - to put it in other words - if your kernel has all the necessary drivers - such as the ones for the filesystem type of the filesystem from which to load other modules - hardcoded in, then there is no need for booting with aninitrdorinitramfsand there will thus also be no need for this directory to exist.

Stock distribution kernels however are highly modular by default and typically only come withext2orext3hardcoded in - which is typically also the filesystem used in theinitrdorinitramfs- and so they are typically set up by the distribution's installer to require aninitrdorinitramfs.

I'm afraid you misinterpreted what I had written... ;-)

P.S.: Please note that my newsreader - and many others - interpret a word delimited by two slashes as beingitalic,- as I understand it, character mode newsreaders such asslrnwill typically show those words in other colors - while a word starting with a single slash is in good UNIX tradition intended to represent a first level directory in the root directory. In other words, I wrote what I wrote, and there was no typo in my technical representation of things.

Your newsreader mileage may vary, of course. ;-)

-- With kind regards,

*Aragorn* (Registered GNU-Linux user #223157)