Hi,
Dave Crane wrote:
because net.lo is not usefull for a system that provides services.
for example running a ssh server for net.lo is kinda silly :)
Maybe we should all remove the localhost line from /etc/hosts if it's silly.
You could, but GNOME won't be happy. Silly, isn't it? ;)
Maybe /etc/fstab should be /etc/conf.d/filesystems?
First off, how is this related to the rest of the discussion?
There is a clear logic to find out what configuration should be set in
/etc/conf.d/ and what should go to /etc in general. I'm sure you will find it
out after thinking a bit over it ;)
(On a side node: /etc/rc.conf still breaks that logic by setting LOGINMANAGER,
although the vast majority of it has been moved to /etc/conf.d/*, which was a
very good thing, IMHO)
Or maybe its should be left to the app. adding RC_NET_STRICT_CHECKING would
have other consequences. One size does not fit all here. If net.lo is the
only thing that satisfies net on a given system and the process doesnt have a
problem attaching to that (as I just verified with both sshd and apache2),
then let it be.
From /etc/conf.d/rc:
# 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 can't see what side effect you are referring to (assuming you set it to 'lo').
If net.lo breaks, net is not provided, and rc-scripts depending on it won't start.
Sorry to go off on this, but things have been changing in the last few months
in ways illogical to me. I've been running gentoo since pre 1.0 days and
this has greatly concerned me lately.
Yes, things have been changing. This mainly causes problems for users that have
installed Gentoo a long time ago, were happy with their installation and leaned
back. I know it is a time-consuming task to follow the development of a
distribution, but it is every administrator's first duty. I remember the nice
GWN article telling how baselayout changed and what you should pay attention to
when upgrading.
Every distro has it's quirks and funny ways of doing things, but the list
seems to be growing with gentoo for no good reason.
I don't think so. From time to time I have the same feelings, but in almost all
cases it turns out that the real issue was me beeing too lazy to read docs.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
[EMAIL PROTECTED]
--
[email protected] mailing list
