Summary: | RC_NET_STRICT_CHECKING='no' not working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jay Phelps <jay.phelps> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jay Phelps
2005-07-20 21:17:30 UTC
you didnt check all the files, it is used in rc services you also missed the comment just below what you quoted ... you have to set it to 'lo' not to 'no' I did check all the files on my system in /etc and that option is not used except in /etc/splash/livecd-2005.0 I'm not sure what 'rc services' file you are refering to but I don't have it in /etc. Is it locate someplace else? I am using the latest stable baselayout 1.11.13. Option 'lo' is what it seems to be doing when I have it set to 'no' which is not correct. If I am reading this correctly 'no' would require either eth0 or ath0 to be up in addition to lo and that's not what's happening. # no - This basically means that at least one net.* service besides net.lo # must be up. This can be used by notebook users that have a wifi and # a static nic, and only wants one up at any given time to have the # 'net' service seen as up. # lo - This is the same as the 'no' option, but net.lo is also counted. # This should be useful to people that do not care about any specific # interface being up at boot. I appologize in advance if I a missing something obvious here. Perhaps I am looking in the wrong place for references to this variable (if it's not in /etc) but, in any event, the behaviour I am experiencing does not match the documented behaviour as specified in /etc/conf.d/rc then your config files werent updated properly re-emerge baselayout with the --noconfmem |