[gentoo-user] Strange messages at boot

[gentoo-user] Strange messages at boot

[Etaoin Shrdlu]

After the recent baselayout update, I see these messages at boot time:

...
Device initiating service: net.eth0
...
...
* net.etho: cannot start until the runlevel boot has completed
...
[rest of boot messages, including entering default runlevel and bringing 
eth0 up]


Nevertheless, networking is fine and everything works.
Before filing a bug, does anyone know what this is about?

Thanks
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Strange messages at boot

[jarry]

Etaoin Shrdlu <shrdlu@unlimitedmail.org>

> After the recent baselayout update, I see these messages at boot time:
> Device initiating service: net.eth0
> * net.etho: cannot start until the runlevel boot has completed

Probably net.eth0 starting has beem somehow moved into boot-runlevel.
AFAIK it should be in defeult-runlevel, so try to move it there:

rc-update del net.eth0 boot
rc-update add net.eth0 default

Jarry

-- 


"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Strange messages at boot

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

On Thu, 29 Jun 2006 12:34:54 +0200, Etaoin Shrdlu wrote:

> After the recent baselayout update, I see these messages at boot time:

What do you mean by "recent"? It greatly depends on whether you are
running stable or testing, arch or ~arch.

> 
> ...
> Device initiating service: net.eth0
> ...
> ...
> * net.etho: cannot start until the runlevel boot has completed
> ...

Adding 'RC_PLUG_SERVICES="!net.eth0"' to /etc/conf.d/rc may fix this.
Read the comments in the file for an explanation.


-- 
Neil Bothwick

There's a fine line between fishing and standing on the shore looking
like an idiot.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Strange messages at boot

[Etaoin Shrdlu]

On Thursday 29 June 2006 13:35, jarry@gmx.net wrote:

> Probably net.eth0 starting has beem somehow moved into boot-runlevel.
> AFAIK it should be in defeult-runlevel, so try to move it there:
>
> rc-update del net.eth0 boot
> rc-update add net.eth0 default

No, it's correctly in default runlevel (spaced for better readability):

[Thu Jun 29 14:59:18 root@mozart ~]# rc-update show
 * Invalid runlevel entry: /etc/runlevels/boot/.keep
 * Invalid runlevel entry: /etc/runlevels/default/.keep
 * Invalid runlevel entry: /etc/runlevels/nonetwork/.keep
 * Invalid runlevel entry: /etc/runlevels/single/.keep
               acpid |      default
            bootmisc | boot
             checkfs | boot
           checkroot | boot
               clock | boot
         consolefont | boot
               cupsd |      default
          domainname |      default
                famd |      default
            hostname | boot
             hotplug | boot
            iptables |      default
             keymaps | boot
               local |      default nonetwork
          localmount | boot
             modules | boot
            net.eth0 |      default
              net.lo | boot
            netmount |      default
           rmnologin | boot
              serial | boot
               spamd |      default
                sshd |      default
            sysklogd |      default
             urandom | boot
          vixie-cron |      default
                 xfs |      default

[Thu Jun 29 14:59:25 root@mozart ~]# ls /etc/runlevels/boot/
bootmisc  checkroot  consolefont  hotplug  localmount  net.lo     serial
checkfs   clock      hostname     keymaps  modules     rmnologin  urandom

[Thu Jun 29 14:59:37 root@mozart ~]# ls -l /etc/runlevels/default
acpid  domainname  iptables  net.eth0  spamd  sysklogd    xfs
cupsd  famd        local     netmount  sshd   vixie-cron



Typing the first command showed also the "Invalid runlevel 
entry: /etc/runlevels/boot/.keep" errors that I did not notice before. 
Seems that the new baselayout has introduced some changes. I'll 
investigate further.

Thanks for the reply.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Strange messages at boot

[Daniel da Veiga]

On 6/29/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 29 Jun 2006 12:34:54 +0200, Etaoin Shrdlu wrote:
>
> > After the recent baselayout update, I see these messages at boot time:
>
> What do you mean by "recent"? It greatly depends on whether you are
> running stable or testing, arch or ~arch.
>
> >
> > ...
> > Device initiating service: net.eth0
> > ...
> > ...
> > * net.etho: cannot start until the runlevel boot has completed
> > ...
>
> Adding 'RC_PLUG_SERVICES="!net.eth0"' to /etc/conf.d/rc may fix this.
> Read the comments in the file for an explanation.
>

Thanks for the info Neil, I also had this problem before, as I was
using wlan0 by the time I simply deleted net.eth0 and it stopped
rising, net.eth0 wasn't in ANY runlevel, not even connected, is this a
new feature?

-- 
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Strange messages at boot

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

On Thu, 29 Jun 2006 13:08:13 -0300, Daniel da Veiga wrote:

> > Adding 'RC_PLUG_SERVICES="!net.eth0"' to /etc/conf.d/rc may fix this.
> > Read the comments in the file for an explanation.

> Thanks for the info Neil, I also had this problem before, as I was
> using wlan0 by the time I simply deleted net.eth0 and it stopped
> rising, net.eth0 wasn't in ANY runlevel, not even connected, is this a
> new feature?

Fairly new, at least for those using stable. Devices can be automatically
configured when they are detected, which for network devices means
running the respective tint.d script.


-- 
Neil Bothwick

Nostalgia isn't what it used to be.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Strange messages at boot

[Mick]

On 29/06/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 29 Jun 2006 13:08:13 -0300, Daniel da Veiga wrote:
>
> > > Adding 'RC_PLUG_SERVICES="!net.eth0"' to /etc/conf.d/rc may fix this.
> > > Read the comments in the file for an explanation.
>
> > Thanks for the info Neil, I also had this problem before, as I was
> > using wlan0 by the time I simply deleted net.eth0 and it stopped
> > rising, net.eth0 wasn't in ANY runlevel, not even connected, is this a
> > new feature?
>
> Fairly new, at least for those using stable. Devices can be automatically
> configured when they are detected, which for network devices means
> running the respective tint.d script.

I thought that this new feature would/should take into account what
net services exist in the rc-update default level and act according to
the settings in /etc/conf.d/rc.  I also do not have net.eth0 in my
default runlevel but still get these boot notices as well as the
errors when I run rc-update -s.

My settings look like this:

RC_PLUG_SERVICES=""
RC_NET_STRICT_CHECKING="lo"

Reading the comments about lo, I thought that if lo comes up it is
counted as an interface and the script stops checking.  Did I get it
all wrong?
-- 
Regards,
Mick
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: Strange messages at boot

[Mick]

On 01/07/06, Mick <michaelkintzios@gmail.com> wrote:

> I thought that this new feature would/should take into account what
> net services exist in the rc-update default level and act according to
> the settings in /etc/conf.d/rc.  I also do not have net.eth0 in my
> default runlevel but still get these boot notices as well as the
> errors when I run rc-update -s.
>
> My settings look like this:
>
> RC_PLUG_SERVICES=""
> RC_NET_STRICT_CHECKING="lo"
>
> Reading the comments about lo, I thought that if lo comes up it is
> counted as an interface and the script stops checking.  Did I get it
> all wrong?

When Knoppix starts up and does not find an iface running, because say
I have not yet switched on the router, it 'backgrounds' the net.eth0
script and carries on with the boot process.  How can I set my Gentoo
up so that it does the same?

I remember reading about it a couple of years back and never got
around to doing it . . .
-- 
Regards,
Mick
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Strange messages at boot

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

On Mon, 3 Jul 2006 22:08:27 +0000, Mick wrote:

> When Knoppix starts up and does not find an iface running, because say
> I have not yet switched on the router, it 'backgrounds' the net.eth0
> script and carries on with the boot process.  How can I set my Gentoo
> up so that it does the same?

emerge ifplugd. that's it, you don't need to configure it or add it to a
runlevel, in fact you should not do so. The Gentoo net scripts detect the
presence of ifplugd and use it to do what you want.


-- 
Neil Bothwick

I am Barney of Borg: I love you. You love me. We're a happy Borg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Re: Strange messages at boot

[Nick Rout]

On Mon, 3 Jul 2006 23:24:19 +0100
Neil Bothwick wrote:

> On Mon, 3 Jul 2006 22:08:27 +0000, Mick wrote:
> 
> > When Knoppix starts up and does not find an iface running, because say
> > I have not yet switched on the router, it 'backgrounds' the net.eth0
> > script and carries on with the boot process.  How can I set my Gentoo
> > up so that it does the same?
> 
> emerge ifplugd. that's it, you don't need to configure it or add it to a
> runlevel, in fact you should not do so. The Gentoo net scripts detect the
> presence of ifplugd and use it to do what you want.

They do? I emerged it a while ago now and then took net.ethx out of all
runlevels and replaced it with ifplugd. Should i undo that?



-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Strange messages at boot

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

On Tue, 04 Jul 2006 14:49:38 +1200, Nick Rout wrote:

> > emerge ifplugd. that's it, you don't need to configure it or add it
> > to a runlevel, in fact you should not do so. The Gentoo net scripts
> > detect the presence of ifplugd and use it to do what you want.
> 
> They do? I emerged it a while ago now and then took net.ethx out of all
> runlevels and replaced it with ifplugd. Should i undo that?

Yes, read /etc/conf.d/net.example.

Doing it this way avoids the problem of init scripts that depend on a net
service complaining because you haven't started any.


-- 
Neil Bothwick

Q. How do you identify a blind man in a nudist colony?
A. It's not hard.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]