| 1 |
On Tue, 2 Feb 2010 08:08:25 +0200 |
| 2 |
Alan McKinnon wrote: |
| 3 |
|
| 4 |
> On Tuesday 02 February 2010 06:03:10 David Relson wrote: |
| 5 |
> > G'day, |
| 6 |
> > |
| 7 |
> > I've been running baselayout-2 for several months and it's been |
| 8 |
> > working fine AFAICT. Over the weekend I noticed that my USB thumb |
| 9 |
> > drive is no longer automounting. |
| 10 |
> > |
| 11 |
> > This evening I ran "/etc/init.d/udev status" which reported: |
| 12 |
> > |
| 13 |
> > * status: stopped". |
| 14 |
> > |
| 15 |
> > Running "/etc/init.d/udev start" reported: |
| 16 |
> > |
| 17 |
> > * The udev init-script is written for baselayout-2! |
| 18 |
> > * Please do not use it with baselayout-1!. |
| 19 |
> > * ERROR: udev failed to start |
| 20 |
> > |
| 21 |
> > The message occurs because /etc/init.d/udev checks for |
| 22 |
> > /etc/init.d/sysfs, which is not present. |
| 23 |
> > |
| 24 |
> > Googling indicates that /etc/init.d/sysf comes from |
| 25 |
> > sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long |
| 26 |
> > ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. |
| 27 |
> > Unmasking it and running "emerge -p ..." shows that sysvinit is a |
| 28 |
> > blocker. |
| 29 |
> > |
| 30 |
> > Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I |
| 31 |
> > likely to get myself into troubleif I do this? If so, how much and |
| 32 |
> > how deep? |
| 33 |
> |
| 34 |
> very very very very deep trouble if you restart the machine and |
| 35 |
> everything is not complete yet. Do not do that. |
| 36 |
> |
| 37 |
> all version of baselayout-2 are marked unstable and you likely have |
| 38 |
> an old version of sysvinit that is not compatible with the ancient |
| 39 |
> openrc you do have. That openrc is not in portage anymore. |
| 40 |
> |
| 41 |
> You should upgrade to the latest unstable portage (which supports |
| 42 |
> automatically resolving blockers). You need baselayout, openrc and |
| 43 |
> sysvinit as well as /etc/init.d/sysfs. I have none of these in world |
| 44 |
> yet all are present. |
| 45 |
> |
| 46 |
> With the latest portage, try again and let portage figure out for |
| 47 |
> itself what it wants to do. |
| 48 |
|
| 49 |
Hi Alan, |
| 50 |
|
| 51 |
Reply appreciated! |
| 52 |
|
| 53 |
I've been running unstable versions of portage for many months and |
| 54 |
currently have 2.1.7.17, which _is_ the newest non-masked version. |
| 55 |
|
| 56 |
With it, sysvinit is blocking (capital "B") openrc-0.6.0-r1 |
| 57 |
and /etc/init.d/sysfs is not present (which makes /etc/init.d/udev |
| 58 |
unhappy). |
| 59 |
|
| 60 |
Since /etc/init.d/udev only _checks_ for the presence of |
| 61 |
/etc/init.d/sysfs but doesn't run it (or anything), would creating a |
| 62 |
dummy (zero length) sysfs file be workable? |
| 63 |
|
| 64 |
Regards, |
| 65 |
|
| 66 |
David |
Archives