filesystem creates an empty /initrd directory:
[kaboom@skuld BUILD]$ ls -la /initrd
drwxr-xr-x 2 root root 4096 Jun 21 2001 .
drwxr-xr-x 18 root root 4096 Mar 27 17:05 ..
[kaboom@skuld BUILD]$ rpm -qf /initrd
Yes. It's for the initrd.
Shouldn't that go in /boot?
No, it has to be on the root FS.
That seems, to me, to be a violation of the FHS.... If I remember right, it
says that all boot files other than configs must be in /boot, and the kernel
itself (which is what I guess initrd would be classified as) must be in / or /boot.
Oh well... it's required for switching the root FS between the initrd and the
real root filesystem.
Here's what the LSB actually says:
3.5 /boot : Static files of the boot loader
This directory contains everything required for the boot process except
configuration files and the map
installer. Thus /boot stores data that is used before the kernel begins
executing user-mode programs.
This may include saved master boot sectors, sector map files, and other data
that is not directly edited by
3.5.2 Specific Options
The operating system kernel must be located in either / or /boot.3
2. Programs necessary to arrange for the boot loader to be able to boot a
file must be placed in /sbin. Configuration files for
boot loaders must be placed in /etc.
3. On some i386 machines, it may be necessary for /boot to be located on a
separate partition located completely below cylinder
1024 of the boot device due to hardware constraints.
Certain MIPS systems require a /boot partition that is a mounted MS-DOS
filesystem or whatever other filesystem type is
accessible for the firmware. This may result in restrictions with respect to
usable filenames within /boot (only for affected
This would seem to violate that (but then, so does /boot/grub/grub.conf ;-). I
can't imagine that /initrd would cause interoperability problems, though.