diff options
| author | Jay Lan <jlan@engr.sgi.com> | 2005-06-30 02:59:03 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-30 08:45:12 -0700 |
| commit | f220ab2a5162c35cca6993ea473937cfc962fce4 (patch) | |
| tree | 4d9d1a199625d8b657a69d9afeed17c0dbb02a10 /fs/vfat | |
| parent | 1c71e22e4e4b4e7261f147635518d5634136c226 (diff) | |
| download | linux-3.10-f220ab2a5162c35cca6993ea473937cfc962fce4.tar.gz linux-3.10-f220ab2a5162c35cca6993ea473937cfc962fce4.tar.bz2 linux-3.10-f220ab2a5162c35cca6993ea473937cfc962fce4.zip | |
[PATCH] Improper initrd failure message at boot time
On system boot up, there was an failure reported to boot.msg:
<5>Trying to move old root to /initrd ... failed
According to initrd(4) man page, step #7 of BOOT-UP OPERATION
is described as below:
7. If the normal root file has directory /initrd, device
/dev/ram0 is moved from / to /initrd. Otherwise if
directory /initrd does not exist device /dev/ram0 is
unmounted.
We got service calls from customers concerning about this failure message
at boot time. Many systems do not have /initrd and thus the message can be
changed in the case of non-existing /initrd so that it does not sound like
a failure of the system.
Signed-off-by: Jay Lan <jlan@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/vfat')
0 files changed, 0 insertions, 0 deletions