On Thursday 30 August 2007, Ed W wrote:
> > Apparently its from baselayout:
> >
> > mill2 vanilla # equery belongs /etc/init.d/net.lo
> > [ Searching for file(s) /etc/init.d/net.lo in *... ]
> > sys-apps/baselayout-2.0.0_rc3-r1
> > (/etc/init.d/net.lo -> ../../lib/rcscripts/sh/net.sh)
>
> Hi, it's actually
>
> /etc/init.d/net.vserver
>
> which seems to fix everything in my case.
You don't mean there is naming magic associated with these? Otherwise I guess
you have changed something in udev? Or am I just being dense...?
> I thought this was something I created off my own back to work around
> these issues, but then you pasted in exactly the same file and now I
> doubt myself... Seems coincidental we both came up with the same hack?
Sorry, I was being either cryptic or stupid above. That was just a diffdump
of what was in my tree versus vanilla, including, I see, mostly bugs. But,
somewhere in that mess, there might be something that makes a difference,
i.e.:
diff -ur ./etc/conf.d/rc /etc/conf.d/rc
--- ./etc/conf.d/rc 2007-08-27 20:46:32.000000000 +0000
+++ /etc/conf.d/rc 2007-08-24 16:38:30.000000000 +0000
@@ -26,7 +26,7 @@
# both will be started, but services that depend on 'net' will work if either
# one comes up. With RC_DEPEND_STRICT="yes" we would require them both to
# come up.
-RC_DEPEND_STRICT="yes"
+RC_STRICT_DEPEND="no"
# Do we allow services to be hotplugged? If not, set to RC_HOTPLUG="no"
# NOTE: This does not affect anything hotplug/udev/devd related, just the
-- Which might have enabled my vserver to boot by relaxing some dependency checking in the init system (as you can see, this patch apparently also introduces a bug by renaming RC_DEPEND_STRICT). If you are referring generally to links between net.lo and net.XXX in the /etc/init.d directory, AFAIK that is the Official Gentoo Way (tm) to wedge network interfaces into the init system... so maybe as you originally guessed, you created it manually (while following a guide). -- gmtReceived on Sat Sep 1 19:33:06 2007