Hello and thanks for all the replies. This list is an excellent resource.
My original message (short form):
When I first brought my system up I gave it a temporary name. I'm using
DEC Unix v4.0A. A few weeks later I renamed it to it's final, production
name using the Network Configuration Application from the SysMan
Configuration Checklist. In particular, I revised the hostname in the
Ethernet Interface dialog box. This seemed to mostly work.
I am about to rebuild the kernel. However, I notice a number of places
under the /sys directory structure where the old name is still being used.
I could rebuild the kernel using the old system name to identify it, but
that is sort of annoying. I'd rather just update the names under /sys to
reflect the new, true name. Here are the places I've identified as needing
to be changed:
[ details removed ]
I'd like to thank the following people for providing help and suggestions:
Eric Sven Ristad <ristad_at_CS.Princeton.EDU>
Becki Kain <beckers_at_josephus.furph.com>
Gerhard Nolte <gnolte_at_gwdg.de>
Andrew Leahy <A.Leahy_at_st.nepean.uws.edu.au>
Based on what these people said, together with a little study of the
doconfig manual page, I did the following:
1. I copied /sys/conf/OLDCONFIG to /sys/conf/NEWCONFIG. This
established a new configuration that was identical to the old one
while at the same time retaining my old configuration as a backup.
2. I edited /sys/conf/NEWCONFIG to change the "ident" field. This
might not really be necessary, but it looks better.
3. I copied /sys/conf/OLDCONFIG.list to
/sys/conf/NEWCONFIG.list. Doing this meant that I wanted my new
configuration to include the same layered products as the old
one. Since I do have a /sys/conf/.product.list file, my impression was
that doconfig would have created a NEWCONFIG.list file from that
automatically. I figured just coping the old one was just as good.
4. I ran
doconfig -c NEWCONFIG
This caused a new symbolic link to be created: /sys/NEWCONFIG and an
entirely new /usr/sys/NEWCONFIG directory to be created and
populated. My existing /usr/sys/OLDCONFIG directory was
unaffected. This is good... I have a back up.
In effect, I now have two distinct kernel configurations on my system,
although they are supposedly identical. It was my intention to boot
the "new" kernel and, if it worked okay, remove the /usr/sys/OLDCONFIG
directory (and /sys/OLDCONFIG link as well as the /sys/conf/OLDCONFIG*
files). However, I ran into a problem during the kernel rebuild that I
don't think has anything to do with the renaming issue. I am going to
post a separate message about that problem in a moment.
*****************************************************************************
Peter
http://twilight.vtc.vsc.edu/~pchapin
pchapin_at_twilight.vtc.vsc.edu Paganism: Ancient beliefs in a modern world
Received on Fri Aug 29 1997 - 23:16:55 NZST