Can sysinstall be run interactively to install onto a second drive?
Can I run sysinstall on a live system, booted say from ad0 and use it to install a new OS onto a second drive, say ad1? I'm trying to do something like this: sysinstall configFile=install.cfg loadConfig where I have the target drive identified in the sysinstall script, but it doesn't seem to like what I'm trying to do. Basically what I need to do is given a FreeBSD distribution, I want an automated procedure I can run on a system to build a new system with a specific set of packages and other customizations we need. We have this setup now using a PXE boot server, but I'd like something I can run interactively that doesn't require a boot server. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can sysinstall be run interactively to install onto a second drive?
On Fri, Feb 27, 2009 at 09:43:54AM -0800, Peter Steele wrote: Can I run sysinstall on a live system, booted say from ad0 and use it to install a new OS onto a second drive, say ad1? I'm trying to do something like this: sysinstall configFile=install.cfg loadConfig where I have the target drive identified in the sysinstall script, but it doesn't seem to like what I'm trying to do. Basically what I need to do is given a FreeBSD distribution, I want an automated procedure I can run on a system to build a new system with a specific set of packages and other customizations we need. We have this setup now using a PXE boot server, but I'd like something I can run interactively that doesn't require a boot server. If I understand you, I think the answer is yes. You can certainly start sysinstall on a running system. The only thing you can't do is have it write to mounted disk space. I don't think that is your intent, so there should be no problem. Just be careful when you specifiy devices to write to. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can sysinstall be run interactively to install onto a second drive?
On Friday 27 February 2009 08:48:39 Jerry McAllister wrote: On Fri, Feb 27, 2009 at 09:43:54AM -0800, Peter Steele wrote: Can I run sysinstall on a live system, booted say from ad0 and use it to install a new OS onto a second drive, say ad1? I'm trying to do something like this: sysinstall configFile=install.cfg loadConfig where I have the target drive identified in the sysinstall script, but it doesn't seem to like what I'm trying to do. Basically what I need to do is given a FreeBSD distribution, I want an automated procedure I can run on a system to build a new system with a specific set of packages and other customizations we need. We have this setup now using a PXE boot server, but I'd like something I can run interactively that doesn't require a boot server. If I understand you, I think the answer is yes. You can certainly start sysinstall on a running system. Yes for sure. You can partition secondary drives on a running system as long as the drive isn't mounted and your kern.securelevel 2. You will need to define doesn't seem to like what I'm trying to do to get a more constructive answer. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can sysinstall be run interactively to install onto a second drive?
Yes for sure. You can partition secondary drives on a running system as long as the drive isn't mounted and your kern.securelevel 2. It's -1, so I assume that's okay. You will need to define doesn't seem to like what I'm trying to do to get a more constructive answer. Yeah, that wasn't very useful was it? Okay, I'm having a couple of problems, at least. One problem is I don't know how to tell sysinstall where my target root is located. I have something like this in my install.cfg: disk=da0 bootManager=standard partition=all diskPartitionEditor da0s1-1=ufs 0 /newroot diskLabelEditor diskLabelCommit This formats my target drive as I want it (a single full disk partition at this point), but when I do the actual install, there is no way to tell sysinstall where my target root is. So, when the commands dists=base kernels GENERIC manpages distSetCustom installCommit are executed, the files are extracted and installed on my active system, not the system I am building on da0. That's my problem in a nutshell ultimately--how do I tell sysinstall where my target root is? It impacts the whole session, including packageAdd commands. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can sysinstall be run interactively to install onto a second drive?
That's my problem in a nutshell ultimately--how do I tell sysinstall where my target root is? It impacts the whole session, including packageAdd commands. I did a bit of snooping around the distribution and I see that each directory has a simple install script to install base, the kernel, manpages, and do on, and they all use DESTDIR to point to the location where the system is being installed. So I don't need to use sysinstall at all, I'll just call these install scripts directly and that will do exactly what I want... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
