| 1 |
G'day, |
| 2 |
|
| 3 |
I've been running baselayout-2 for several months and it's been working |
| 4 |
fine AFAICT. Over the weekend I noticed that my USB thumb drive is no |
| 5 |
longer automounting. |
| 6 |
|
| 7 |
This evening I ran "/etc/init.d/udev status" which reported: |
| 8 |
|
| 9 |
* status: stopped". |
| 10 |
|
| 11 |
Running "/etc/init.d/udev start" reported: |
| 12 |
|
| 13 |
* The udev init-script is written for baselayout-2! |
| 14 |
* Please do not use it with baselayout-1!. |
| 15 |
* ERROR: udev failed to start |
| 16 |
|
| 17 |
The message occurs because /etc/init.d/udev checks for |
| 18 |
/etc/init.d/sysfs, which is not present. |
| 19 |
|
| 20 |
Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I |
| 21 |
have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is |
| 22 |
available, though keyworded ~amd64. Unmasking it and running "emerge |
| 23 |
-p ..." shows that sysvinit is a blocker. |
| 24 |
|
| 25 |
Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely |
| 26 |
to get myself into troubleif I do this? If so, how much and how deep? |
| 27 |
|
| 28 |
Regards, |
| 29 |
|
| 30 |
David |
Archives