| 1 |
On 05/04/2010 00:58, Mark Knecht wrote: |
| 2 |
> One thing about this that still confuses me is where /dev/md3, or |
| 3 |
> whatever, comes from when I boot if the the mknod command is never |
| 4 |
> executed within the chrrot. (As per the install guide.) Not a big deal |
| 5 |
> to proceed and see what happens. Maybe the kernel just creates it |
| 6 |
> based on discovering the RAID? Or it makes it because I explicitly |
| 7 |
> define it at the command line? |
| 8 |
|
| 9 |
Well, it shouldn't matter. The md block device will be initialised by |
| 10 |
the kernel as soon as it loads, whereupon it will be resolved internally |
| 11 |
by its registered major/minor numbers for the purpose of mounting the |
| 12 |
root filesystem (that's the "9, 0" that you referred to earlier in the |
| 13 |
thread). Once the root filesystem is mounted read-only, it proceeds to |
| 14 |
load init. |
| 15 |
|
| 16 |
Later, the device node will need to be present - for instance, when |
| 17 |
fstab is parsed - but udev will have taken care of it by that time. That |
| 18 |
is, udev will manifest the device node in a tmpfs filesystem which is |
| 19 |
mounted at /dev and dynamically populated early on during the boot process. |
| 20 |
|
| 21 |
Cheers, |
| 22 |
|
| 23 |
--Kerin |
Archives