On Fri, Mar 09, 2007 at 10:30:44AM -0500, David Robillard wrote: > >I have a remote machine running 4.8-p21. The system has two disks in > >it, but only one is used on a daily basis (the other is filled via dd > >every now and then). > > > >I want to get this remote machine running 6.2, so I figured I'ld > >install the new OS on the second disk, then boot off the second disk, > >leaving the original first disk with all the user data on it (plus as > >a way to back out). > > > >When I try to use /stand/sysinstall for this it seg-faults > >early in the installation, but after the "Commit" step. > > Hi Jerry, > > If you have a 6.2 machine handy, you can create dump files of each > filesystem using dump(8), cpio(1) or pax(1) or whatever you're used > to. > > Ship those dump files to your 4.8 machine via scp(1). Then use > bsdlabel(8) to partition your second hard disk (the one you whish to > install 6.2 on). Create filesystems on those new partitions. Mount > those new filesystems into a chroot, for example /mnt/root, /mnt/usr, > /mnt/var, etc. Then extract your dump files onto those new partitions. > Don't forget to install a boot block on your disk with `bsdlabel -B` > or with boot0cfg(8). That should do it. > > If you need more detailed step-by-step instructions, just say so, I'll > send something on the list.
OK. First, it was someone else who posted. I was one of the responders. That can be a good way of doing it. I have posted a list of steps for doing essentially that (slightly different circumstances) a couple of times in the past. But there is one disadvantage in this particular case. Since the OP is running 4.xx and wants to move to 6.xx, he would probably also want to take advantage of the new UFS2 filesystem improvements. But, if he builds the file system using the 4.xx fdisk and disklabel (before bsdlabel replaced it) then it will use the older file system missing some performance and feature improvements. So, he will want to find a way to fdisk and bsdlabel using a 6.xx system if at all possible. Of course, it is not the end of the world to be stuck with the older file system, but is less than optimal. It would be possible for the person to sort of double up on your suggestion and do a first build with the existing fdisk and bsdlabel and then restore 6.2 dumps. Then build a 6.2 system that can run from memory that includes the essentials such as fdisk, bsdlabel and newfs and tink with booting to boot to that memory system, which would then allow that second disk to remain unmounted or accessed anywhere -- essential for building the file systems. Then use that memory mounted system to build the file systems and finally do the restores from dumps. It should work, but will take some figuring out. The last time I built anything resembling that was back in about FreeBSD 4.9 and I made a file of it and burned it to CD and did the boots from CD. But it should be possible to get it to run from a memory file system. ////jerry > > Have fun, > > David > -- > David Robillard > UNIX systems administrator & Oracle DBA > CISSP, RHCE & Sun Certified Security Administrator > Montreal: +1 514 966 0122 _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"