Dave,
I also saw the posting about sys-unconfig, and sent a reply, but it didn't
go to the list, just the OP. So, to repeat myself (yet again (again)):
Except that the support for it doesn't seem to be there.
/usr/sbin/sys-unconfig touches a file named /.unconfigured. The next time
you boot, /etc/rc.sysconfig checks to see if it exists, and if so, is
supposed to invoke a number of system configuration scripts. The problem is
this:
if [ "`/bin/arch`" = "s390" ] ; then
ARCH=".s390"
else
ARCH=""
fi
and these:
if [ -x /usr/bin/passwd$ARCH ]; then
/usr/bin/passwd$ARCH root
fi
if [ -x /usr/sbin/netconfig$ARCH ]; then
/usr/sbin/netconfig$ARCH
fi
When I look, those files (with ".s390" appended to them) don't exist, so
they won't get executed. So for now, at least, /usr/sbin/sys-unconfig is a
"no op" command.
Mark Post
-----Original Message-----
From: Dave Myers [mailto:dave.myers@twcable.com]
Sent: Thursday, January 24, 2002 10:18 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Cloning a RH 7.2 S390 system
> If i want to clone an S390 RH 7.2 system,> what files have been changed
from running> rhsetup?? (i.e. hostname, ip addr > etc).> > And...can I just
go into the newly cloned system> and modify these to new hostname, ip addr
etc.> > Thanks,> > > Dave
> The major ones would be /etc/sysconfig/network, /etc/hosts, and>
/etc/sysconfig/network-scripts/ifcfg-eth0> (if you have > > an eth1 device,
then /etc/sysconfig/network-scripts/ifcfg-eth1> would change as well).
That's all I would expect you to > > > have to change.> It'll definitely do
for basic network connectivity
>see: man 8 sys-unconfigwhich lets the initscripts do the work for you.
>-- Russ Herrold
Russ,
I tried this command expecting the next boot to prompt me for changes.
It did not.
Is it supposed to...or do I have to make changes to config files before next
boot and before
I issue sys-unconfig ????
Thanks,
Dave
--- Begin Message ---
- To: "'Linux on 390 Port'" <LINUX-390@VM.MARIST.EDU>, "'Dave Myers'" <dave.myers@twcable.com>
- Subject: RE: Cloning a RH 7.2 S390 system
- From: "Post, Mark K" <mark.post@eds.com>
- Date: Thu, 24 Jan 2002 10:34:50 -0500
Dave, I also saw the posting about sys-unconfig, and sent a reply, but it didn't go to the list, just the OP. So, to repeat myself (yet again (again)): Except that the support for it doesn't seem to be there. /usr/sbin/sys-unconfig touches a file named /.unconfigured. The next time you boot, /etc/rc.sysconfig checks to see if it exists, and if so, is supposed to invoke a number of system configuration scripts. The problem is this: if [ "`/bin/arch`" = "s390" ] ; then ARCH=".s390" else ARCH="" fi and these: if [ -x /usr/bin/passwd$ARCH ]; then /usr/bin/passwd$ARCH root fi if [ -x /usr/sbin/netconfig$ARCH ]; then /usr/sbin/netconfig$ARCH fi When I look, those files (with ".s390" appended to them) don't exist, so they won't get executed. So for now, at least, /usr/sbin/sys-unconfig is a "no op" command. Mark Post -----Original Message----- From: Dave Myers [mailto:dave.myers@twcable.com] Sent: Thursday, January 24, 2002 10:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Cloning a RH 7.2 S390 system > If i want to clone an S390 RH 7.2 system,> what files have been changed from running> rhsetup?? (i.e. hostname, ip addr > etc).> > And...can I just go into the newly cloned system> and modify these to new hostname, ip addr etc.> > Thanks,> > > Dave > The major ones would be /etc/sysconfig/network, /etc/hosts, and> /etc/sysconfig/network-scripts/ifcfg-eth0> (if you have > > an eth1 device, then /etc/sysconfig/network-scripts/ifcfg-eth1> would change as well). That's all I would expect you to > > > have to change.> It'll definitely do for basic network connectivity >see: man 8 sys-unconfigwhich lets the initscripts do the work for you. >-- Russ Herrold Russ, I tried this command expecting the next boot to prompt me for changes. It did not. Is it supposed to...or do I have to make changes to config files before next boot and before I issue sys-unconfig ???? Thanks, Dave--- End Message ---
