Original Question: Lads, I have an Ultra1 that I need to dump across to a 220R. What command do I use to detect and display the hardware version of the source (Ultra1), I know that Hardware version 5/98 has the required PCI drivers, but prior versions do not. Any help or suggestions would be great. Cian ------------ Answers. There where a couple, but Thorfinn Rasmussen and Casper Dik nailed it. The info I needed was in the /etc/release file. Some said try uname, and man uname, but that gives patch versions, and processor type, but not the info I needed. prtvconf, dmesg and sysdef where also recommended, but did not bear the fruit as I needed the X/XX number of hardware (month / year) I was advised by a someone from Sun, that dumping from an Ultra1 to a 220R may not work, and their official position is not to recommend it. But I like to cheat so oh well :) Thanks to all that answerd, To many to list. Casper made a couple additional points so his mail is attached below. For your information this is how I intend on rebuilding the device tree. Comments are welcome. # cd /mnt/devices ; rm -r * # cd /mnt/dev/dsk ; rm * # cd /mnt/dev/rdsk ; rm * # cd /mnt/dev/rmt ; rm * # rm /mnt/etc/path_to_inst The above destroys the device tree restored from dump # drvconfig -r /mnt/devices -p /mnt/etc/path_to_inst # cd /devices # find . -print | cpio -pdum /mnt/devices # disks -r /mnt # devlinks -r /mnt # ports -r /mnt # tapes -r /mnt Cian cat /etc/release However, be aware that the /dev* trees and /etc/path_to_inst and others do not match and need to be chanegd also. If you need to copy the system over, you can copy the disk image over, nuke /etc/path_to_inst and even possibly parts of /devices (all except pseudo) and then run *upgrade* which will put most things right. CasperReceived on Thu Sep 6 18:42:43 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:32:30 EDT