As for your last question about locations of config files on HP-UX.
As with most other Unices, most of them reside beneath /etc.
But then, this goes especially for many add-on tools and SW packages, they can scatter widely over the whole directory tree,
depending very much on their installation targets.
Just try to run a find as root like
e.g.
# find / -type d -name etc
But there are a few places that a bit predominant.
Like I wrote in my lengthy last posting to this thread, a very important location is
/etc/rc.config.d
for almost every service that can be started or stopped through init.
Thereof especially
/etc/rc.config.d/netconf
for configuring your NICs, static routes, and hostname
/etc/rc.config.d/netdaemons
for daemons like inetd or xntpd
/etc/rc.config.d/nfsconf
for NFS (server and client as well as automounter)
/etc/rc.config.d/nddconf
for tuning your TCP/IP stack
HP-UX has adopted many ndd tunables from Solaris I suppose, so most of them should be familiar to you.
However the online help for each tunable is much better on HP-UX.
"ndd -h" prints you a list of all tunables,
and e.g. "ndd -h ip_ire_gw_probe" extended comment on the very tunable
(you don't find this luxury on Solaris)
Also referring to the NICs settings on Solaris is pretty arcane.
For instance only to check the link speed of NIC /dev/qfe2 you have to do something esoteric like
# ndd -set /dev/qfe instance 2
# ndd -get /dev/qfe instance
2
# ndd -get /dev/qfe link_speed
1
Then you need to know that 1 stands for 100 Mbps.
On HP-UX all that needs to be done to check NIC lan1 is
# lanadmin -x 1
Current Speed = 100 Full-Duplex Auto-Negotiation-ON
/etc/rc.config.d/hp
conf
there you set such parameters for your NICs to make them reboot persistent.
An
# ioscan -knfClan
will show you the driver names your NICs use.
Just have look at all the files in
/etc/rc.config.d
Their names are pretty self-explanatory and designate to which service they belong.
If you want to install your own service, and provide it with an init script you could make use of a template file
/sbin/init.d/template
for that very purpose.
Unlike Solaris there is no subdir
/etc/inet
So most of the Internet config files you would find there on a Solaris box are simply in the parent directory /etc
(but you also have symlinks to /etc on Solaris)
Although as well as on Solaris there exists an /etc/default on HP-UX,
there's much less in that dir, and especially to allow or prevent root logins you need not edit some /etc/default/login
but have to extra provide an /etc/securetty
(so HP is a bit less secure per default in that respect).
Also the inetd has a poor man's tcp wrapper (HP offers an extra tcp wrapper for free download, should you need one) that is pretty concealed, if it exists at all
/var/adm/inetd.sec
NFS configuration deviates significantly from Solaris (although it was a give away from SUN once)
You put your exports (or shares in SUN lingo) in
/etc/exports
(it has an own manpage)
There's no /etc/dfs/dfstab
On Solaris the NFS server wouldn't even start by init until you have a valid entry in this file.
After you have installed a software depot (on HP-UX they are called depots and their file extension is usually .depot) you can browse the list of files by (e.g. MeasureWare Perf Tools) something like this
# swlist -l file B3701AA|grep -E '\.(cf|conf)'
B3701AA.MeasurementInt.ARM: /opt/perf/man/man4/ttd.conf.4
B3701AA.MeasurementInt.ARM: /opt/perf/newconfig/ttd.conf.sample
B3701AA.MeasureWare.MWA: /etc/rc.config.d/mwa
B3701AA.MeasureWare.MWA: /opt/perf/newconfig/etc/rc.config.d/mwa
All in all, probably the best advice to give is to carefully read the excellent manpages from HP-UX OS (that are way better than those from Solaris OS, I wouldn't even hesitate to say one of the best I've seen so far in the Unix world, especially for their example sections).
Pay attention to the FILES sections that usually list all the config files required by the program.
Many ubiquitious config files even provide their own manpages, for format details etc.
Madness, thy name is system administration
