On 7/19/22 01:55, Roberto Sassu wrote: >> Thank you, I have tested that patch but the problem remained. Here is my >> command line, I wonder if there is something wrong. >> >> Kernel command line: rw rootfstype=initramtmpfs root=/dev/ram0 >> initrd=0x500000000 rootwait > > It is just initramtmpfs, without rootfstype=. Whoever wrote that patch really doesn't understand how this stuff works. I can tell from the name. Technically, initramfs is the loader, I.E. "init ramfs". The filesystem instance is called "rootfs" (hence the name in /proc/mounts when the insane special case the kernel added doesn't hide information from people, making all this harder to understand for no obvious reason). ramfs and tmpfs are two different filesystems that COULD be used to implement rootfs. (Last I checked they were the only ram backed filesystems in Linux.) If a system administrator says they're going to install your server's root partition using the "reiserxfs" filesystem, I would not be reassured. > Roberto Rob P.S. Note: there IS another boot option, you can have a pipe backed root filesystem! CONFIG_ROOT_NFS for NFS or CONFIG_CIFS_ROOT for Samba. No, I don't know why the order isn't consistent. P.P.S. If you want to run a command other than /init out of initramfs or initrd, use the rdinit=/run/this option. Note the root= overmount mechanism is completely different code and uses the init=/run/this argument instead, which means nothing to initramfs. Again, specifying root= says we are NOT staying in initramfs.
