Thanks to all who responded including:
Kevin McDonnell
Bob Harris
Davis Alan
Faidherbe Thierry
Hoai Tran
Haesaerts Corinne
of which I used the option mentioned by Davis as follows:
Use "sysman network" to change network configuration. You can still change
the individual files but sysman is convenient enough now and it helps ensure
that you get everything updated and restarted correctly.
The only problem I've seen is that if you are changing the IP address you
may have to manually remove the old IP using "ifconfig <i/f> -alias <old
IP>". Since network connectivity will likely be unavailable while the
changes are being made you should always reconfigure the network from the
console only.
To make the disk bootable you have to put the right bootblocks on it. When
you disklabel a disk it gets UFS bootblocks by default. To specify AdvFS
bootblocks you would use the "-t advfs" argument to disklabel.
If the label isn't the default layout do this :
disklabel -r dskNN > /tmp/dskNN.label
disklabel -R -r -t advfs dskNN /tmp/dskNN.label
This will save the current label to a file, then re-apply it to the disk
along with the AdvFS bootblocks.
-----Original Message-----
From: jing116_at_263.net
To: tru64-unix-managers_at_ornl.gov
Sent: 10/31/01 4:06 AM
Subject: Clone in Tru64 5.1
Hi managers,
I have two problem:
1. What command can I use to change my network's attribute?
2. After I vdump my disk1 ( all disk for root /) to disk2 ( a backup
disk),I pull out disk1,just want to use disk2 to as boot disk,but it
failed for : cann't open osf_boot,who can tell me why?
I used this command: vdump -0 - / | vrestore -xf - -D /mnt
I just mount disk2 to /mnt
Received on Thu Nov 01 2001 - 01:42:58 NZDT