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,
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
OK. First, it was someone else who posted. I was one of the responders.
My mistake! Sorry about this.
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
On Fri, Mar 09, 2007 at 11:39:31AM -0500, David Robillard wrote:
OK. First, it was someone else who posted. I was one of the responders.
My mistake! Sorry about this.
That can be a good way of doing it. I have posted a list of steps
for doing essentially that (slightly different
Also see my post to doc about restoring dump files over an http
connection, in case your existing systems' partitions don't have
enough room to temporarily store them.
http://lists.freebsd.org/pipermail/freebsd-doc/2007-February/012190.html
___
to fix this and/or what is the best way to achieve
my goal... which is: install 6.2 on a remote system without hammering
the current system disk?
Thanks,
-mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
this is because the install process has changed a bit
since 4.8.
Is there a way to fix this and/or what is the best way to achieve
my goal... which is: install 6.2 on a remote system without hammering
the current system disk?
Are you using an install CD?
Use that to boot the machine - download the ISO
early in the installation, but after the Commit step.
I figure this is because the install process has changed a bit
since 4.8.
Is there a way to fix this and/or what is the best way to achieve
my goal... which is: install 6.2 on a remote system without hammering
the current
Mark Messier 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
