summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorMarton Balint <cus@fazekas.hu>2009-01-06 14:40:43 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2009-01-06 15:59:11 -0800
commitbca1033b092a6fab2ed00036e8a7f6e2df5d99a2 (patch)
tree94f2d1124aefe1a383b0cf3d1ca8e983406304e0 /lib
parentb61312d353da1871778711040464b10f5cd904df (diff)
downloadop-kernel-dev-bca1033b092a6fab2ed00036e8a7f6e2df5d99a2.zip
op-kernel-dev-bca1033b092a6fab2ed00036e8a7f6e2df5d99a2.tar.gz
do_mounts: add device info to mount message
In the past, I used the root=... command line parameter to specify the root filesystem to the kernel. Now it seems that specifying it is not necessary. The kernel detects the root filesystem even if the kernel command line is empty. My root fs is on a raid1 device by the way, and I am not using initrd for the boot process. If the kernel detects the root filesystem somehow, I think it should print out the result of this detection, otherwise I will not know which device has the root filesystem. Or is there an easy way to get this information on a running system? I had a quick look at the /proc and /sys filesystems, but haven't found anything useful there. Signed-off-by: Marton Balint <cus@fazekas.hu> Cc: Christoph Hellwig <hch@lst.de> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud