Re: RFC: OpenRC as Init System for Debian
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Friday 27 April 2012 02:10 AM, Svante Signell wrote:
>> Say you want to mount a network disk during boot. This depend on
>> the
>>> network being configured. This in turn might depend on a DHCP
>>> reply from a DHCP server, and to send the DHCP request the
>>> network card need to be detected. To detect the network card,
>>> the network driver need to be loaded, and the network card need
>>> to be found on the PCI or some other internal bus. And with
>>> the Linux kernel today, there is no way to know when during
>>> boot the network card will be found on the bus.
> This is the whole cause of the problem: You don't know the names of
> your devices ay longer. Blame Linus! What's the point of changing
> names of peripheral devices "dynamically"? I've been struggling
> with eth0 and eth1 for some rime now, never knowing how it will be
> named for every new kernel :-(
>
I think he is talking about when the devices get discovered and in
what order. For naming, linux does have ways to guarantee persistent
device names, both for block and network devices.
- --
Given the large number of mailing lists I follow, I request you to CC me
in replies for quicker response
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCgAGBQJPm6dhAAoJEKY6WKPy4XVpJ4gP/28MSVaq/FcxGzYLZG3U3cog
RvSIv1RcVQfB0N/HuTKSzP19Y0XTPhq7DxJlFwz0c9MgPaUn+W2YngK05XFCGf/S
+zic5zf62pDQymjZ+5M6w+puuzJmbdFYEZdJULBn2e0MzX3b8rZyZulutK5UgMdn
n1W51h2Uq6PpYAE4VQ4WqD/Jo+Bbk3D5f8wy7C38yRPEPSaXNW5seLEU8B2xfQGR
suShUT+06z/BwYLzImKis+vlj8UWYD08h4mLirQt1722w3OU21EMVGDz7+HXIqxe
G4Mggz7wuv7IlxhvxSUitpb3AWHl5Mnnc4vQ+yOKHSHcJsLgOZSfi/ugqHi1YvMm
wTUwqnaEdTPq8cSY78zUJsw+JPmDt7NDmwvL0oWDCvNzwQg5MAxFPFIdLBdznnoT
Wi6Tvse5NheLFgRxUQj+aCtRYAf4FMY6GtVf46IJaeAyrONYPvV7VRA8JOw82wRw
pDirFZjrl/DzXot5LvAbdNpRvOhSFFk6dCoIYVlYvYoBPaNupPC35AvI/waQKseu
eobR/fG7PjwsqQlTr2oiXuh8Oj4ideaNGbdvlVFSh2DBGTEqRZ8EQ0Bkk535d3S2
YkOwHm3lmvAaTD+2SP6A2XHmlvliQC1bDrRvNgFFqRtrVJKk1yQOt3Cu2GZltsOr
dotNNUSr+OST1sBfAZCW
=oGRb
-----END PGP SIGNATURE-----
Reply to: