linux-kernel - Re: /dev before the root filesystem is mounted

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Nov 2006 13:26:02 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Ivan Ukhov <uvsoft@...il.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: /dev before the root filesystem is mounted


On Nov 13 2006 15:15, Ivan Ukhov wrote:
> i dont use initrd. the kernel understands argument 'root=/dev/...', so
> /dev should exist, mb not in a real filesystem, but just in ram or
> something. i just want to know what devices are available for being
> the root filesystem for the kernel (displaying all available devices
> will be enough for me).

/dev does not exist. How should it? The root filesystem / is empty, other
people can verify that, or you can verify it yourself with an
initramfs (which, unlike an initrd, is copied to / instead of being
mounted).

Yes, the kernel understands root=/dev/ but that's a hack, a strstr(s,
"/dev/"). Should you want to use, say, root=/devices/hda instead,
that would only succeed when using an initrd/initramfs.

To display the accepted block devices (this is most likely what you
really wanted), check out

ftp://ftp-1.gwdg.de/pub/linux/misc/suser-jengelh/kernel/linux-2.6.18-jen35/show_partitions.diff


Please (a) don't top post (b) don't strip Cc:s.

>
> 2006/11/13, Jan Engelhardt <jengelh@...ux01.gwdg.de>:
>> 
>> > I want the kernel (2.4) to display (just using printk) all available
>> > devices with full path (/dev/...) before the root filesystem is
>> > mounted.
>> 
>> Case 1: You do not use an initrd/initramfs:
>> / is empty, /dev does not exist.
>> 
>> Case 2: You do use an initrd/initramfs
>> You populated /dev during creation of the initrd/initramfs image OR
>> your init script inside the initrd/initramfs mknods the nodes when run.
>> 
>> 
>>        -`J'
>> --
>> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>

	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/