Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4406 - /initrd directory
Attached to Project:
Arch Linux
Opened by Andrew Simmons (Wolfman) - Saturday, 08 April 2006, 00:55 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 08 April 2006, 09:56 GMT
Opened by Andrew Simmons (Wolfman) - Saturday, 08 April 2006, 00:55 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 08 April 2006, 09:56 GMT
|
DetailsA few weeks ago I noticed that I had a new directory: /initrd. And since I have been digging around my initrd images, I now know why it's there. I have two qualms regarding this setup. It's under the root directory, and the linuxrc script does not check for its existence and create it if absent.
I really do not like having yet another directory in the root of my file system, and this directory is particularly noxious because it is empty by the time the system has finished starting. To most users /initrd looks like an empty and useless directory, which some users might unwittingly delete (I did). Also the FHS doesn't include such a directory. Ideally, I'd like to see /initrd moved somewhere else. /tmp/initrd would be good, since the tempfs would mount over /tmp and /tmp/initrd would disappear. Someplace in the /var hierarchy would be fine: /var/initrd or /var/tmp/initrd. Even the /mnt directory would be good. It might also be nice to include a small text file in the directory to tell users why this directory is present and not delete it. Finally, I'd like to know why the linuxrc script does not check to the existence of /initrd before it calls pivot_root, this will definitely keep your system from starting. If the root fs is still mounted read-only, then you can not create the directory that you want, but something more graceful should be done. |
This task depends upon
Closed by James Rayner (iphitus)
Sunday, 15 October 2006, 10:30 GMT
Reason for closing: Won't fix
Additional comments about closing: mkinitrd is obsolete, please use mkinitcpio.
Sunday, 15 October 2006, 10:30 GMT
Reason for closing: Won't fix
Additional comments about closing: mkinitrd is obsolete, please use mkinitcpio.
/initrd/ is owned by mkinitrd 1.01-29
hmm before you start deleting stuff on your own, perhaps do a pacman -Qo on the file next time