Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Preventing eth1 from starting during boot?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
bjorntj
Guru
Guru


Joined: 01 Jun 2005
Posts: 402

PostPosted: Wed Apr 12, 2006 1:34 pm    Post subject: Preventing eth1 from starting during boot? Reply with quote

After updating my system lately, the system tries to start all my network intefaces automatically.
Is there a way to prevent it from doing this?


Regards,

BTJ
_________________
Someone wrote:
"I understand that if you play a Windows CD backwards you hear strange Satanic messages"
To which someone replied:
"It's even worse than that; play it forwards and it installs Windows"
Back to top
View user's profile Send private message
!equilibrium
Bodhisattva
Bodhisattva


Joined: 06 Jun 2004
Posts: 2109
Location: MI/BG/LC

PostPosted: Wed Apr 12, 2006 1:44 pm    Post subject: Reply with quote

yes, erasing /etc/conf,d/net the network is no more started automatically with the new baselayout
_________________
Arch Tester for Gentoo/FreeBSD
Equilibrium's Universe

all my contents are released under the Creative Commons Licence by-nc-nd 2.5
Back to top
View user's profile Send private message
bjorntj
Guru
Guru


Joined: 01 Jun 2005
Posts: 402

PostPosted: Wed Apr 12, 2006 1:45 pm    Post subject: Reply with quote

So where do I configure my network interface then?


BTJ
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Wed Apr 12, 2006 3:16 pm    Post subject: Reply with quote

rc-update del net.eth1 default


removes the ability to start the card during boot.
Phil.
Back to top
View user's profile Send private message
diogot
Tux's lil' helper
Tux's lil' helper


Joined: 25 Mar 2006
Posts: 114
Location: Brasil

PostPosted: Wed Apr 12, 2006 3:17 pm    Post subject: Reply with quote

Did you try the rc-update?
Back to top
View user's profile Send private message
bjorntj
Guru
Guru


Joined: 01 Jun 2005
Posts: 402

PostPosted: Wed Apr 12, 2006 5:10 pm    Post subject: Reply with quote

net.eth1 is not enabled in the default runlevel or boot...
That's why I asked my question about starting by itself....


BTJ
Back to top
View user's profile Send private message
diogot
Tux's lil' helper
Tux's lil' helper


Joined: 25 Mar 2006
Posts: 114
Location: Brasil

PostPosted: Wed Apr 12, 2006 5:19 pm    Post subject: Reply with quote

weird!
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Wed Apr 12, 2006 5:38 pm    Post subject: Reply with quote

Very.
I have no idea, sorry...
Back to top
View user's profile Send private message
!equilibrium
Bodhisattva
Bodhisattva


Joined: 06 Jun 2004
Posts: 2109
Location: MI/BG/LC

PostPosted: Thu Apr 13, 2006 6:06 pm    Post subject: Reply with quote

phil_r wrote:
Very.
I have no idea, sorry...


you need to remove 'netmount' from the runlevel with rc-update command.
_________________
Arch Tester for Gentoo/FreeBSD
Equilibrium's Universe

all my contents are released under the Creative Commons Licence by-nc-nd 2.5
Back to top
View user's profile Send private message
Tlaloc
Guru
Guru


Joined: 21 Feb 2005
Posts: 451
Location: Europe - Alps - Tyrol

PostPosted: Tue Apr 18, 2006 8:37 am    Post subject: Reply with quote

Removed netmont from any runlevel but net.eth1 and net.eth0 still autostart. This is the output of rc-update show:
Code:

alsasound |      default
            bootmisc | boot
             checkfs | boot
           checkroot | boot
               clock | boot
            coldplug |      default
         consolefont | boot
                dbus |      default
                hald |      default
            hostname | boot
             hotplug |      default
             keymaps | boot
         laptop_mode |      default
               local |      default nonetwork
          localmount | boot
             modules | boot
              net.lo | boot
              pcmcia |      default
          powersaved |      default
           rmnologin | boot
              serial | boot
           syslog-ng |      default
             urandom | boot
          vixie-cron |      default
                 xdm |      default

baselayout version is
sys-apps/baselayout-1.12.0_pre17-r2
and this is the content of /etc/init.d/:
Code:
-rwxr-xr-x  1 root root   785 Feb 15 10:58 acpid
-rwxr-xr-x  1 root root  7183 Mar 12 19:45 alsasound
-rwxr-xr-x  1 root root  3411 Feb 14 12:38 bluetooth
-rwxr-xr-x  1 root root  3490 Apr 13 21:45 bootmisc
-rwxr-xr-x  1 root root  1056 Apr 13 22:31 checkfs
-rwxr-xr-x  1 root root  3161 Apr 13 21:45 checkroot
-rwxr-xr-x  1 root root  2033 Apr  8 23:05 clamd
-rwxr-xr-x  1 root root  2656 Apr 13 21:45 clock
-rwxr-xr-x  1 root root   889 Jan 12 23:03 coldplug
-rwxr-xr-x  1 root root  1429 Apr 13 21:45 consolefont
-rwxr-xr-x  1 root root   919 Jan 13 17:39 cpufreqd
-rwxr-xr-x  1 root root   498 Jan 24 17:02 cpufrequtils
-rwxr-xr-x  1 root root  1625 Apr 12 10:15 crypto-loop
-rwxr-xr-x  1 root root   515 Apr  5 10:19 cupsd
-rwxr-xr-x  1 root root  1346 Apr  5 21:29 dbus
lrwxrwxrwx  1 root root    21 Apr 13 21:45 depscan.sh -> ../../sbin/depscan.sh
-rwxr-xr-x  1 root root  1530 Feb 24 18:04 dhcp
-rwxr-xr-x  1 root root   748 Feb 24 17:51 dhcrelay
-rwxr-xr-x  1 root root   490 Mar  2 09:44 famd
lrwxrwxrwx  1 root root    23 Apr 13 21:45 functions.sh -> ../../sbin/functions.sh
-rwxr-xr-x  1 root root   660 Jan 12 22:58 hald
-rwxr-xr-x  1 root root  5580 Apr 13 22:31 halt.sh
-rwxr-xr-x  1 root root  2724 Mar 11 19:42 hdparm
-rwxr-xr-x  1 root root  2064 Apr 13 22:29 hibernate-cleanup
-rwxr-xr-x  1 root root   433 Apr 13 21:45 hostname
-rwxr-xr-x  1 root root  1076 Jan 12 23:02 hotplug
-rwxr-xr-x  1 root root  4237 Apr  8 23:21 ifplugd
-rwxr-xr-x  1 root root  1874 Apr 13 21:45 keymaps
-rwxr-xr-x  1 root root   860 Mar 25 11:47 laptop_mode
-rwxr-xr-x  1 root root   620 Apr 13 21:45 local
-rwxr-xr-x  1 root root  1332 Apr 13 22:31 localmount
-rwxr-xr-x  1 root root  3063 Mar  5 12:48 mldonkey
-rwxr-xr-x  1 root root  2947 Apr 13 21:45 modules
-rwxr-xr-x  1 root root 10482 Apr 12 20:29 mysql
-rwxr-xr-x  1 root root   569 Mar  9 19:08 nas
lrwxrwxrwx  1 root root     6 Apr 13 21:45 net.eth0 -> net.lo
lrwxrwxrwx  1 root root    18 Feb  5 21:09 net.eth1 -> /etc/init.d/net.lo
lrwxrwxrwx  1 root root    20 Mar 16 11:18 net.eth2 -> /etc/init.d/net.eth0
-rwxr-xr-x  1 root root 29697 Apr 13 21:45 net.lo
-rwxr-xr-x  1 root root  3038 Apr 13 21:45 netmount
-rwxr-xr-x  1 root root  1339 Jan 13 10:26 nscd
-rwxr-xr-x  1 root root   670 Apr 13 21:45 numlock
-rwxr-xr-x  1 root root  2244 Mar  9 19:10 pcmcia
-rwxr-xr-x  1 root root  1132 Jan 13 10:20 portmap
-rwxr-xr-x  1 root root   512 Apr 12 23:00 powersaved
-rwxr-xr-x  1 root root   540 Apr 12 10:30 pwcheck
-rwxr-xr-x  1 root root   221 Apr 13 21:45 reboot.sh
-rwxr-xr-x  1 root root   276 Apr 13 21:45 rmnologin
-rwxr-xr-x  1 root root   438 Jan 13 10:24 rsyncd
lrwxrwxrwx  1 root root    23 Apr 13 21:45 runscript.sh -> ../../sbin/runscript.sh
-rwxr-xr-x  1 root root  1109 Apr  9 20:51 samba
-rwxr-xr-x  1 root root   527 Apr 12 10:30 saslauthd
-rwxr-xr-x  1 root root  1104 Jan 13 10:23 serial
-rwxr-xr-x  1 root root   287 Apr 13 21:45 shutdown.sh
-rwxr-xr-x  1 root root   584 Apr  5 20:35 slapd
-rwxr-xr-x  1 root root   495 Apr  5 20:35 slurpd
-rwxr-xr-x  1 root root  1452 Feb 14 12:39 sshd
-rwxr-xr-x  1 root root   817 Jan 13 10:25 svnserve
-rwxr-xr-x  1 root root   446 Mar  3 19:08 syndaemon
-rwxr-xr-x  1 root root  1527 Jan 23 15:51 syslog-ng
-rwxr-xr-x  1 root root   915 Apr 13 21:45 urandom
-rwxr-xr-x  1 root root   530 Jan 12 23:18 vixie-cron
-rwxr-xr-x  1 root root  3418 Apr  5 12:11 xdm


If it wouldn't have any effect there would be no problem, but my linksys router/adsl gateway somehow gets confused after a while and cannot resolve hostnames anymore.
Thanks for any hints, Valentin.
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3793

PostPosted: Tue Apr 18, 2006 11:26 am    Post subject: Reply with quote

set interfaceX_hotplug="no" in /etc/conf.d/net.
This will not work with latest (unstable) baselayout and should be done directly with udev instead.

cheers
Back to top
View user's profile Send private message
aguyfromearth
n00b
n00b


Joined: 18 Apr 2006
Posts: 53
Location: /earth/europe/...

PostPosted: Tue Apr 18, 2006 3:21 pm    Post subject: Re: Preventing eth1 from starting during boot? Reply with quote

bjorntj wrote:
After updating my system lately, the system tries to start all my network intefaces automatically.
Is there a way to prevent it from doing this?


Regards,

BTJ


after i installed a new baselayout 1.12.0_pre17-r2 same problem occured.

change in /etc/conf.d/rc

RC_COLDPLUG="no" # yes is the default answer

maybe it work too, when u change

RC_NET_STRICT_CHECKING="no" to RC_NET_STRICT_CHECKING="lo" then only the loopback will start

hope it helps
Back to top
View user's profile Send private message
Tlaloc
Guru
Guru


Joined: 21 Feb 2005
Posts: 451
Location: Europe - Alps - Tyrol

PostPosted: Tue Apr 18, 2006 5:13 pm    Post subject: Re: Preventing eth1 from starting during boot? Reply with quote

aguyfromearth wrote:
bjorntj wrote:
After updating my system lately, the system tries to start all my network intefaces automatically.
Is there a way to prevent it from doing this?


Regards,

BTJ


after i installed a new baselayout 1.12.0_pre17-r2 same problem occured.

change in /etc/conf.d/rc

RC_COLDPLUG="no" # yes is the default answer

maybe it work too, when u change

RC_NET_STRICT_CHECKING="no" to RC_NET_STRICT_CHECKING="lo" then only the loopback will start

hope it helps


Thanks for pointing out in which config file to set these things.
I didn't directly follow your advice and followed the example that was directly given in the rc file. So the corresponding line now looks like this:
Code:
# Dynamic /dev managers can trigger coldplug events which cause services to
# start before we are ready for them. If this happens, we can defer these
# services to start in the boot runlevel. If you don't want this then set
# RC_COLDPLUG to no.
# For more fine grained control you can list full service names to allow
# them to coldplug and prefix them with ! so they don't coldplug.
# Example - RC_COLDLUG="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to coldplug.

RC_COLDPLUG="net.lo !net.*"

#RC_COLDPLUG="yes"


I rebooted once now and the network interfaces didn't come up automatically as wanted, it seems to work.

Bye, Val.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum