SUMMARY: V880 question on ethernet interfaces and services
From: Jason McIntosh (jmcintosh_at_mlug.missouri.edu)
To: firstname.lastname@example.org Date: Fri, 25 Apr 2003 09:01:52 -0500
Ok, thanks to all who responded!!! There were more than a few and too
many to list, but here's the general consensus of what I've received:
With regards to the startup scripts, they're the usual /etc/rc*.d
directories. The scripts are also as found on a linux system in
/etc/init.d S##name is a start script, K##name is a stop script.
For which runlevel corresponds to which "action" do a "man init.
Additionally, I was told that /etc/rcS.d is the startup scripts
directory. Further, a combination of rcS.d and rc2.d handle most of
the startup and services. Specifically, S69inet and S72inetsvc for the
network configuration. S30network.sh in /etc/rcS.d handles the network
Another warning - the network scripts in general don't support stop or
restart parameters, as they're "designed to bring up the interfaces,
not to bring them down." (thanks to Darren Dunham for a very specific
set of information on this).
Network interfaces are loaded through files in /etc such as
/etc/hostname.ge0. the ge0 is the interface and the file contains the
hostname. That hostname should be defined in /etc/hosts. This only
counts for currently installed and configured network interfaces.
But, the general network card interfaces for "plumbing" are as follows:
ge# is the Gigabit Ethernet card.
100Mb cards are hme#
Quad-fast-ethernet cards are qfe#
SunBlade 150's (and apparantly the SunFire's) have eri# ports.
To load an interface which hasn't be loaded at boot time, you use
ifconfig with the plumb command. For a dhcp interface, you'd use the
ifconfig eri0 plumb auto-dhcp
The last part of the network config can be found in /etc/defaultrouter
for setting the route information and in /etc/netmasks for setting the
As for the different services running, I was told you can shut off
pretty much anything in /etc/inetd.conf
One person suggested commenting the following out:
talk, finger, rsh, rquota, chargen, cachefs, kcms, bootps, comsat
and anything labeled experimental in /etc/services can be shutdown in
/etc/inetd.conf. If you're not running a dhcp server you can also
comment out the dhcp stuff too. One suggestion was to stop using inetd
and use xinetd instead (xinetd being more secure).
And last, but not least, the SMC requirements. First, it seems no one
has a clear idea of exactly what is required by the SMC (Mike Penny
gave the only real clue) but one thing is the sadmind in
/etc/inetd.conf. Most people apparently aren't using it, primarily
because it's "a pig". But, no one seemed sure of what the SMC
requires, how it's configured, etc.
University of Missouri
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP PUBLIC KEY BLOCK-----
[demime 0.99c.7 removed an attachment of type application/pgp-signature which had a name of PGP.sig]
sunmanagers mailing list