| 1 |
waltdnes@××××××××.org wrote: |
| 2 |
> On Thu, Jun 09, 2016 at 08:16:57AM -0500, Dale wrote |
| 3 |
>> karl@××××××××.se wrote: |
| 4 |
>>> Dale: |
| 5 |
>>> ... |
| 6 |
>>>> Can a system even boot without udev? |
| 7 |
>>> Yes, use sys-fs/static-dev (unless you have some special boot |
| 8 |
>>> requirements). |
| 9 |
>> Well, I was talking about if udev was removed and then a reboot |
| 10 |
>> was done. I would think it would boot to a certain point then when |
| 11 |
>> whatever started and needed devices to be created in /dev, it would |
| 12 |
>> start failing. I suspect this would vary depending on the install |
| 13 |
>> as well. |
| 14 |
> You need *A* device-manager. You can use udev, eudev, static-dev, |
| 15 |
> mdev, whatever, but you need something. Mind you, some software assumes |
| 16 |
> or requires udev/eudev. |
| 17 |
> |
| 18 |
|
| 19 |
|
| 20 |
What I was referring to was if during this switch from udev to eudev, |
| 21 |
someone rebooted without any dev manager at all. In other words, emerge |
| 22 |
-C udev and then reboot before emerging eudev or some other dev |
| 23 |
manager. I suspect that would get interesting pretty quick. |
| 24 |
|
| 25 |
Dale |
| 26 |
|
| 27 |
:-) :-) |
Archives