Re: Re: sysinstall install.cfg
Wow! Thanks for all the info and the time you spent pulling it together and
writing it out, Devin! There is a lot to digest. Right now, I do have
a "workaround" that I am currently testing out. I will be hanging onto your
email for future reference, certainly.
On Nov 11, 2010 12:19pm, Devin Teske wrote:
On Thu, 2010-11-11 at 12:12 +, vrwmil...@gmail.com wrote:
> Hi all,
>
> Hoping that someone might be able to help me here. I dynamically
generate
> much of the install.cfg by running scripts that send output to files
that
> are, in turn, loaded into install.cfg utilizing loadConfig. The scripts
> that are run are placed into the mfsroot in /stand and /. They send the
> output to /a.
>
> I do this twice before the installCommit and both scripts run and load
the
> resulting configs successfully. I also run another script after the
> InstallComit...it fails citing the script could not be found.
Before distExtractAll is called (called implicitly by installCommit if
not previously called), this is the layout of your environment:
/ -- your mfsroot
/mnt -- your newly formatted disk (empty at this time)
/mnt/dist -- your install media (beit CD/DVD, NFS, etc.)
Meanwhile, _after_ distExtractAll (or installCommit in your case), you
are chroot(2)'ed into /mnt, so this is now your environment:
/ -- your newly formatted disk (populated with FreeBSD now)
/dist -- your install media
> In troubleshooting, I found that sysinstall is removing /stand
That's right:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/install.c.diff?r1=1.360;r2=1.361;f=h
That change was made 5 years, 9 months ago.
> and doing other
> stuff to / and /var. So, I know why the script cannot be found...because
> sysinstall is removing it.
>
> The question I have then is how can I get around this? I attempted
putting
> the script above the installCommit, but the functions being performed
here
> require that the base system already be in place (I'm adding packages).
It
> seems that I have little choice, but to have this after the
installCommit.
> Unfortunately, sysinstall wipes it out.
>
> Any guidance is greatly appreciated.
You essentially have about 5 options (I'll let you choose):
1. You can patch sysinstall to keep `/stand' around.
2. You can use an older mfsroot containing an older build of sysinstall
which doesn't blow away `/stand' (not recommended)
3. You can switch using pc-sysinstall (as mentioned by krad)
4. You can create a "post_install.cfg" in the install media and have
your call loadConfig on `/dist/post_install.cfg' after installCommit
5. You can use an mfsroot already tailored specifically to your needs
available at http://druidbsd.sf.net/
Let's look at each option in detail:
1. If you want to patch sysinstall to keep `/stand' around, here's what
you need to do:
a. cvsup the FreeBSD source tree (beyond the scope of this e-mail)
b. Apply the below patch
--- /usr/src/usr.sbin/sysinstall/install.c 2010-11-11 03:05:53.0
-0800
+++ /usr/src/usr.sbin/sysinstall/install.c.orig 2010-06-13
19:09:06.0 -0700
@@ -906,6 +906,9 @@ installFixupBase(dialogMenuItem *self)
/* BOGON #5: aliases database not built for bin */
vsystem("newaliases");
+ /* BOGON #6: Remove /stand (finally) */
+ vsystem("rm -rf /stand");
+
/* Now run all the mtree stuff to fix things up */
vsystem("mtree -deU -f /etc/mtree/BSD.root.dist -p /");
vsystem("mtree -deU -f /etc/mtree/BSD.var.dist -p /var");
c. Compile a new mfsroot containing your patched sysinstall by:
i. cd /usr/src
ii. make buildworld
iii. cd /usr/src/release
iv. make release CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES
NOTE: If the `make release' fails, it can be resumed...
i. cd /usr/src/release
ii. make rerelease CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \
RELEASENOUPDATE=YES
d. Your mfsroot is at `/usr/release/R/stage/mfsroot/mfsroot.gz'
NOTE: If, after a successful release, you want to change re-build
your mfsroot, you really ought to only re-do the `make release'
step. However, that can be lengthy. If you want to patch only a
single file and rebuild, you need to first copy the modified
files from `/usr/src' to `/usr/release/usr/src' (for example,
copy `/usr/src/usr.sbin/sysinstall/install.c' to
`/usr/release/usr/src/usr.sbin/sysinstall/install.c') and then:
i. rm -f /usr/release/usr/obj/usr/src/releas
Re: sysinstall install.cfg
On Thu, 2010-11-11 at 12:12 +, vrwmil...@gmail.com wrote:
> Hi all,
>
> Hoping that someone might be able to help me here. I dynamically generate
> much of the install.cfg by running scripts that send output to files that
> are, in turn, loaded into install.cfg utilizing loadConfig. The scripts
> that are run are placed into the mfsroot in /stand and /. They send the
> output to /a.
>
> I do this twice before the installCommit and both scripts run and load the
> resulting configs successfully. I also run another script after the
> InstallComit...it fails citing the script could not be found.
Before distExtractAll is called (called implicitly by installCommit if
not previously called), this is the layout of your environment:
/ -- your mfsroot
/mnt -- your newly formatted disk (empty at this time)
/mnt/dist -- your install media (beit CD/DVD, NFS, etc.)
Meanwhile, _after_ distExtractAll (or installCommit in your case), you
are chroot(2)'ed into /mnt, so this is now your environment:
/ -- your newly formatted disk (populated with FreeBSD now)
/dist -- your install media
> In troubleshooting, I found that sysinstall is removing /stand
That's right:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/install.c.diff?r1=1.360;r2=1.361;f=h
That change was made 5 years, 9 months ago.
> and doing other
> stuff to / and /var. So, I know why the script cannot be found...because
> sysinstall is removing it.
>
> The question I have then is how can I get around this? I attempted putting
> the script above the installCommit, but the functions being performed here
> require that the base system already be in place (I'm adding packages). It
> seems that I have little choice, but to have this after the installCommit.
> Unfortunately, sysinstall wipes it out.
>
> Any guidance is greatly appreciated.
You essentially have about 5 options (I'll let you choose):
1. You can patch sysinstall to keep `/stand' around.
2. You can use an older mfsroot containing an older build of sysinstall
which doesn't blow away `/stand' (not recommended)
3. You can switch using pc-sysinstall (as mentioned by krad)
4. You can create a "post_install.cfg" in the install media and have
your call loadConfig on `/dist/post_install.cfg' after installCommit
5. You can use an mfsroot already tailored specifically to your needs
available at http://druidbsd.sf.net/
Let's look at each option in detail:
1. If you want to patch sysinstall to keep `/stand' around, here's what
you need to do:
a. cvsup the FreeBSD source tree (beyond the scope of this e-mail)
b. Apply the below patch
--- /usr/src/usr.sbin/sysinstall/install.c 2010-11-11 03:05:53.0
-0800
+++ /usr/src/usr.sbin/sysinstall/install.c.orig 2010-06-13 19:09:06.0
-0700
@@ -906,6 +906,9 @@ installFixupBase(dialogMenuItem *self)
/* BOGON #5: aliases database not built for bin */
vsystem("newaliases");
+ /* BOGON #6: Remove /stand (finally) */
+ vsystem("rm -rf /stand");
+
/* Now run all the mtree stuff to fix things up */
vsystem("mtree -deU -f /etc/mtree/BSD.root.dist -p /");
vsystem("mtree -deU -f /etc/mtree/BSD.var.dist -p /var");
c. Compile a new mfsroot containing your patched sysinstall by:
i. cd /usr/src
ii. make buildworld
iii. cd /usr/src/release
iv. make release CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES
NOTE: If the `make release' fails, it can be resumed...
i. cd /usr/src/release
ii. make rerelease CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \
RELEASENOUPDATE=YES
d. Your mfsroot is at `/usr/release/R/stage/mfsroot/mfsroot.gz'
NOTE: If, after a successful release, you want to change re-build
your mfsroot, you really ought to only re-do the `make release'
step. However, that can be lengthy. If you want to patch only a
single file and rebuild, you need to first copy the modified
files from `/usr/src' to `/usr/release/usr/src' (for example,
copy `/usr/src/usr.sbin/sysinstall/install.c' to
`/usr/release/usr/src/usr.sbin/sysinstall/install.c') and then:
i. rm -f /usr/release/usr/obj/usr/src/release/release.4
ii. rm -f /usr/release/usr/obj/usr/src/release/release.8
iii. cd /usr/src/release
iv. make rerelease CHROOTDIR=/usr/release \
EXTSRCDIR=/usr/src NODOC=YES NO_FLOPPIES=YES \
NOCDROM=YES NOPORTS=YES RELEASENOUPDATE=YES
NOTE: If it looks like you're going to go this route, pl
Re: sysinstall install.cfg
On Thu, Nov 11, 2010 at 10:34 AM, Ross wrote: > vgc> I do this twice before the installCommit and both scripts run and load > the > vgc> resulting configs successfully. I also run another script after the > vgc> InstallComit...it fails citing the script could not be found. In > vgc> troubleshooting, I found that sysinstall is removing /stand and doing > other > vgc> stuff to / and /var. So, I know why the script cannot be found...because > vgc> sysinstall is removing it. > > sysinstall basically does a chroot into the newly installed root after > doing the installcommit, and then remounts the installation source as > /dist (not quite true, you can mount other sources at this time, but > always to /dist). > > After the installcommit, you basically are now at a normal freebsd > installation (ie: /usr/bin and the like are available). You lose > access to your original mfsroot distribution at this point. Thank you, Ross. Your explanation of what was happening lead me to combine the 2nd of the 2 scripts prior to the installCommit and the 3rd script that I was running after the installCommit. The result of the code in the scripts plus the lines in the install.cfg were echoed out to a file and subsequently loaded via loadConfig. This produced the desired result. -- Take care Rick Miller ___ 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: sysinstall install.cfg
vgc> I do this twice before the installCommit and both scripts run and load the vgc> resulting configs successfully. I also run another script after the vgc> InstallComit...it fails citing the script could not be found. In vgc> troubleshooting, I found that sysinstall is removing /stand and doing other vgc> stuff to / and /var. So, I know why the script cannot be found...because vgc> sysinstall is removing it. sysinstall basically does a chroot into the newly installed root after doing the installcommit, and then remounts the installation source as /dist (not quite true, you can mount other sources at this time, but always to /dist). After the installcommit, you basically are now at a normal freebsd installation (ie: /usr/bin and the like are available). You lose access to your original mfsroot distribution at this point. R. -- ___ 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: sysinstall install.cfg
On 11 November 2010 12:12, wrote: > Hi all, > > Hoping that someone might be able to help me here. I dynamically generate > much of the install.cfg by running scripts that send output to files that > are, in turn, loaded into install.cfg utilizing loadConfig. The scripts that > are run are placed into the mfsroot in /stand and /. They send the output to > /a. > > I do this twice before the installCommit and both scripts run and load the > resulting configs successfully. I also run another script after the > InstallComit...it fails citing the script could not be found. In > troubleshooting, I found that sysinstall is removing /stand and doing other > stuff to / and /var. So, I know why the script cannot be found...because > sysinstall is removing it. > > The question I have then is how can I get around this? I attempted putting > the script above the installCommit, but the functions being performed here > require that the base system already be in place (I'm adding packages). It > seems that I have little choice, but to have this after the installCommit. > Unfortunately, sysinstall wipes it out. > > Any guidance is greatly appreciated. > ___ > 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" > have a look at the pc-bsd installer as it will let you do far more advanced installations, and probably easier. Its been commited to head as it looks like it going to become the standard bsd installer in the future. ___ 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"
sysinstall install.cfg
Hi all, Hoping that someone might be able to help me here. I dynamically generate much of the install.cfg by running scripts that send output to files that are, in turn, loaded into install.cfg utilizing loadConfig. The scripts that are run are placed into the mfsroot in /stand and /. They send the output to /a. I do this twice before the installCommit and both scripts run and load the resulting configs successfully. I also run another script after the InstallComit...it fails citing the script could not be found. In troubleshooting, I found that sysinstall is removing /stand and doing other stuff to / and /var. So, I know why the script cannot be found...because sysinstall is removing it. The question I have then is how can I get around this? I attempted putting the script above the installCommit, but the functions being performed here require that the base system already be in place (I'm adding packages). It seems that I have little choice, but to have this after the installCommit. Unfortunately, sysinstall wipes it out. Any guidance is greatly appreciated. ___ 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"
dynamically generating install.cfg
Hello all, I would like to dynamically generate various settings that will be placed into the install.cfg file before sysinstall executes. I am PXE booting and have a mfsroot that contains a install.cfg with variables that will be applicable to all installs. Inside the mfsroot is a script that is supposed to download, via anon-ftp, a file that contains other variables which are set on per host basis. Inside the script, I run ifconfig to setup the interface then immediately run ftp to download the file from the PXE server. As soon as it gets the file, ifconfig runs and takes the interface down. During the install, the debug screen shows no errors when running ifconfig, yet when the script attempts to ftp to the PXE server, it gets a 'network unreachable'. As a result of this, I tried setting up the route as well, using route add default $gateway and get the same error. Running tcpdump on the PXE server confirms that there is not ftp attempt from the client. I am wondering if anyone has tried anything similar and had luck with it or if anyone might be able to provide direction in how I can troubleshoot. I'm not even sure if the interface is being setup properly. At the point where this fails, there is no holographic shell for me to get into and poke around. Thoughts? Ideas? -- Take care Rick Miller ___ 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: Automated sysinstall install.cfg
On 2 July 2010 15:48, Ross wrote: > TT> is there a person who can help me to solve some problems with > TT> sysinstall and its install.cfg. > > TT> How can i manage that my mfsroot executes custom commands ? > > Before the "installCommit" command you generally only have access to > statically compiled commands (generally in the /stand directory) from > the mfsroot image used. > > -= example lines in install.cfg > # Sleep for 15 seconds to stabilize things. > command=/stand/sleep 15 > system > -= > > After the "installCommit" command, a chroot will have occurred to the > installation mount point, and you must then use your installed binaries > to do work. Specify full paths for everything and note that there are > other oddities since not all things are online/configured, so try and > keep it as simple as possible. > > -- > > ___ > 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" > Alternatively you could look at the pc-bsd installer. It will do advanced setups very easily, most of which are not possible with sysinstall (geom stuff, zfs etc). It will install standard freebsd, from a variety of formats. With a little tinkering you should be able to detach the installer program from the standard pcbsd image and use your own custom live os on a usb stick. You would then have a lot of power. ___ 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: Automated sysinstall install.cfg
TT> is there a person who can help me to solve some problems with TT> sysinstall and its install.cfg. TT> How can i manage that my mfsroot executes custom commands ? Before the "installCommit" command you generally only have access to statically compiled commands (generally in the /stand directory) from the mfsroot image used. -= example lines in install.cfg # Sleep for 15 seconds to stabilize things. command=/stand/sleep 15 system -= After the "installCommit" command, a chroot will have occurred to the installation mount point, and you must then use your installed binaries to do work. Specify full paths for everything and note that there are other oddities since not all things are online/configured, so try and keep it as simple as possible. -- ___ 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"
Automated sysinstall install.cfg
Hello, is there a person who can help me to solve some problems with sysinstall and its install.cfg. How can i manage that my mfsroot executes custom commands ? -- Viele Grüsse aus Menden Thomas Toka Webmaster, Administrator, Webhoster, Gameserverhoster Serverman Webhosting Thomas Toka Droste-Hülshoff-Str. 11 58708 Menden Office: +49 (0) 2373 389140 (Festnetz) Mobil: +49 (0) 171 2772896 (D1) Fax: +49 (0) 2373 389142 (Festnetz) Internet: http://www.serverman.de Steuer-Nummer: DE240010739 Inhaber: Thomas Toka Serverstandort: Newcolo GmbH. Mainzer Landstrasse 351-353, 60326 Frankfurt am Main Die in dieser eMail enthaltenen Informationen sind vertraulich und können von rechtlicher Relevanz sein. Diese Mail ist ausschliesslich für den im Quelltext genannten Empfänger bestimmt und jeglicher Zugriff durch andere Personen ist nicht authorisiert. Falls Sie nicht der rechtmäßige Empfänger sind, ist jegliche Veröffentlichung, Vervielfältigung, Verteilung oder sonstige in diesem Zusammenhang stehende Handlung untersagt und unter Umständen strafbar. Sollten Sie diese Mail irrtümlich erhalten haben, leiten Sie diese bitte an webmas...@serverman.de weiter und löschen Ihre Kopien dieser Mail unverzüglich. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee and access to the e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this e-mail in error please forward to webmas...@serverman.de and delete all local copies of this mail. ___ 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: PXE + sysinstall(8) install.cfg: DHCP Attribute to map install config/policy to system MAC?
On 21/04/10 21:59, Brian A. Seklecki (CFI NOC) wrote: All: The install.cfg mechanism is pretty wicked. Unfortunately, there doesn't seem to be a really efficient way to provide new clients (or class of clients) an install.cfg without rebuilding an MFSROOT image. Possibly a TFTP or NFS URL passed from the DHCP server -> boot loader -> kernel sysctl -> sysinstall(8). Thoughts or other ideas? You can configure sysinstall in your install.cfg to execute shell commands, including any fetch-like command. Some scripting should be possible to do what you require. I wrote about it here: http://www.locolomo.org/howto/pxeboot/automatic-installation.html However, I never really went on and tested this, let me know if this works. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.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"
PXE + sysinstall(8) install.cfg: DHCP Attribute to map install config/policy to system MAC?
All:
The install.cfg mechanism is pretty wicked.
Unfortunately, there doesn't seem to be a really efficient way
to provide new clients (or class of clients) an install.cfg
without rebuilding an MFSROOT image.
At least with pxeboot(8), in TFTP-only-mode, using
dhcpd.conf(5) client{} entries, there isn't a way
to differentiate policies.
It's just going to go looking for /boot/loader.rc
and /boot/loader.conf from wherever DHCP told PXE
to fetch pxeboot(8) from.
From there, you need to custom compile a 5 meg
mfsroot image for each [class of] client.
With an NFS stage-2 boot, I suppose you could set:
option root-path "/export/${client}Root" etc.,
but then your 5 meg mfsroot is just extracted
1-per-client.
Still seems a bit ugly. It seems like we could teach
sysinstall(8) to fetch install.cfg by some standard
mechanism.
Possibly a TFTP or NFS URL passed from the DHCP server
-> boot loader -> kernel sysctl -> sysinstall(8).
For example, the Sun SPARC4s would TFTP fetch their
stage 1 boot loader via TFTP with a filename req
of their MAC address in HEX format, so one could
just put symlinks in place.
Thoughts or other ideas?
~BAS
PS: our in-tree tftpd(8) is an unending source of sorrow and misery and
clinical despair. ports/net/freebsd-tftp is a lifesaver (it actually
has debugging)
___
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: install.cfg for Documentation Installation Menu on 8.0-RELEASE
thank you, thenk you, thank you :) On Thu, Mar 4, 2010 at 4:41 PM, Ross wrote: > > dJ> What come up with 8.0-RELEASE is the new FreeBSD > dJ> Documentation Installation Menu in sysinstall. I would like to know > dJ> what command for install.cfg to configure my installation with, say, > dJ> English Documentation. > > It's undocumented (and breaks non-interactive installs) so I ended up > going through the source to find the answer for myself a while ago. > > The option you want is: > > distDoc= > > Where the is a bitfield for which versions of the doc packages > you want installed. Also the bitfield must be in _decimal_, not 0x## > format, or it won't correctly select what you want. You need to view > version 1.75 or higher of dist.h (from sysinstall's source) to get the > full listing. URL: > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/dist.h?rev=1.75.2.1.2.1;content-type=text%2Fplain > > 0 (zero) disables installation. 16 is english. > > *** WARNING/RANT: If you use any of the "distSetxx" (eg: > distSetKernDeveloper) options to select what to install, it doesn't > matter what you've selected above - you _will_ be prompted with a menu > to select a doc package upon running sysinstall. (Those options reset > distDoc option above). > > Non-interactive sysinstall is effectively broken in FreeBSD 8.0 > distribution disks. (There is a way around it, but it's a pain in the > butt) > > That being said: sysinstall has been patched in source last month (Feb > 2010), so should be good for 8.1, with the default of no docs > installed if "nonInteractive=yes" is set in your sysinstall.cfg file. > > > R. > > -- > > > ___ 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: install.cfg for Documentation Installation Menu on 8.0-RELEASE
dJ> What come up with 8.0-RELEASE is the new FreeBSD dJ> Documentation Installation Menu in sysinstall. I would like to know dJ> what command for install.cfg to configure my installation with, say, dJ> English Documentation. It's undocumented (and breaks non-interactive installs) so I ended up going through the source to find the answer for myself a while ago. The option you want is: distDoc= Where the is a bitfield for which versions of the doc packages you want installed. Also the bitfield must be in _decimal_, not 0x## format, or it won't correctly select what you want. You need to view version 1.75 or higher of dist.h (from sysinstall's source) to get the full listing. URL: http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/dist.h?rev=1.75.2.1.2.1;content-type=text%2Fplain 0 (zero) disables installation. 16 is english. *** WARNING/RANT: If you use any of the "distSetxx" (eg: distSetKernDeveloper) options to select what to install, it doesn't matter what you've selected above - you _will_ be prompted with a menu to select a doc package upon running sysinstall. (Those options reset distDoc option above). Non-interactive sysinstall is effectively broken in FreeBSD 8.0 distribution disks. (There is a way around it, but it's a pain in the butt) That being said: sysinstall has been patched in source last month (Feb 2010), so should be good for 8.1, with the default of no docs installed if "nonInteractive=yes" is set in your sysinstall.cfg file. R. -- ___ 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: install.cfg for Documentation Installation Menu on 8.0-RELEASE
On Wed, Feb 24, 2010 at 3:51 PM, don Juan wrote: > Hi, > > What come up with 8.0-RELEASE is the new FreeBSD > Documentation Installation Menu in sysinstall. I would like to know > what command for install.cfg to configure my installation with, say, > English Documentation. > > i've found this question already posted to this forum but it's still > unanswered. > > Thanks! > Please? ___ 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"
install.cfg for Documentation Installation Menu on 8.0-RELEASE
Hi, What come up with 8.0-RELEASE is the new FreeBSD Documentation Installation Menu in sysinstall. I would like to know what command for install.cfg to configure my installation with, say, English Documentation. i've found this question already posted to this forum but it's still unanswered. Thanks! ___ 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"
install.cfg for Documentation Installation Menu on 8.0-RELEASE
Hi all, I want to try FreeBSD 8.0-RELEASE unattended installation with PXE boot using install.cfg. Currently after following some clues from FreeBSD Handbook and some websites like http://high5.net/index_files/freebsd_pxe_install_server.html, I tried to do that and come with success with some changes in /dev/md0c to /dev/md0. The only thing that come up with 8.0-RELEASE is the new FreeBSD Documentation Installation Menu in sysinstall. I would like to know what command for install.cfg to configure my installation with, say, English Documentation. I tried to look for in sysinstall (7) man pages and come with no result. Sample install.cfg doesn't give me any clue either. So I would like to ask for anybody's help for this matter. Thanks! -affan ___ 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: install.cfg scripting issue
On Fri, Nov 06, 2009 at 11:31:39AM -0800, Jason wrote: > > Hi, > > I am having a heck of a time getting an automated installation to get a > couple of commands done, and was wondering if anyone would be able to offer > any assistance. > > Everything works, but post does not. I know we will more than likely move to > a post pkg for configuration, but due to the time-frame to deliver, what > follows below will suit needs just fine. > > command='echo sshd_enable="YES" >> /etc/rc.conf.local' > system > command=cp /usr/share/zoneinfo/America/Los_Angeles /etc/localtime > system > command=/sbin/reboot > system > > I've tried the first command, and it fails, with a "command not found," and > I have yet to get past those command to the last commands. I have been using > single ticks, and double-quotes, but nothing is seeming to work. In > addition to this, I have also escaped the quotes. > > Any help is much appreciated. > > Thanks, > Jason I'm not familiar with install.cfg but have you tried using the full path for your command? E.g: command='/bin/echo sshd_enable=\"YES\" >> /etc/rc.conf.local' Ditto with your other commands. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: Sysinstall with install.cfg
On Wed, 1 Apr 2009 23:25:16 +0200, Andreas Nilsson wrote: AN> AN> # Now set the parameters for the partition editor on da0. AN> disk=da0 AN> partition=all AN> bootManager=none try bootManager=standard AN> diskPartitionEditor AN> diskPartitionWrite try to remove diskPartitionWrite -- Anton Yuzhaninov ___ 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"
Sysinstall with install.cfg
Hello, I've been tasked with building a modified FreeBSD release, which among other things should have a scripted sysinstall. However when I try to use a basic one I get an error saying something like: "No such device /dev/da0s1b", but in the debug output I see that it was created. The install.cfg I'm using is: debug=yes # Which installation device to use mediaSetCDROM # Select which distributions we want. #dists= #distSetCustom distSetDeveloper # Now set the parameters for the partition editor on da0. disk=da0 partition=all bootManager=none diskPartitionEditor diskPartitionWrite da0s1-1=ufs 62914569 / da0s1-2=swap 16777216 none da0s1-4=ufs 0 /usr diskLabelEditor installCommit What am I missing? Best regards Andreas Nilsson ___ 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"
install.cfg sysinstall error
Hi list members,
while trying to create an unattended installation 'thing' for FreeBSD
7.1-RELEASE sysinstall brings me the following error when parsing
install.cfg:
'EBUG: dispatch: calling resword 'mediaSetFTP
''BUG: Notify: Warning: No such command ''MediaSetFTP
I boot using PXE and a custombuild mfsroot gets loaded. This included
the 'fetch' cmd so i can fetch the install.cfg from a remote location.
The actual /install.cfg looks like this:
command=/stand/pre.sh
system
configFile=/stand/install.cfg
loadConfig
pre.sh is executed ok since the /stand/install.cfg is downloaded ok. I
suspect there is an error in character encoding perhaps? Though i did
specify header("content-type: text/plain") just before sending out the
install.cfg (generated using php).
Please put me in the CC since i am not a list member.
regards,
- Harm
___
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"
flexible install.cfg url from kernel parameters
Hi all, in an effort to create a jumpstart/kickstart-like environment for easy OS deployment i, ofcourse, ran into install.cfg for FreeBSD. It works great, but since it requires a modified image (with an inserted install.cfg file) it's not a great option. It even needs a BSD box or CentOS with plus kernel to access the ufs filesystem inside the image... Is there any effort beeing done to allow for a more convenient way to load the install.cfg? Say, like linux does with kickstart/preseed files? Just fill in some weblocation as kernel parameter and you're done :) I would suspect this beeing coded in sysinstall somewhere, or perhaps init? Any suggestions/help is appreciated. Regards Harm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall install.cfg question
Hi, I'm trying to figure out how could I tell sysinstall to let the user choose the disk he want to install into and then, based on that response, create automatically without any other question the partitions/labels that are required. I've seen several examples but I can't find the way to do it.I've also noticed that the manpage isn't complete, as there are many variables defined in sysinstall.h that are not documented there. Thanks for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg and command
http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/040502.htmlit states that I can run commands while installing server like: command="echo keyrate="fast" >> /etc/rc.conf" command="echo keyrate=\"fast\" >>/etc/rc.conf" system But when I use that I get error I can't issue that command. Is there a speacial way to execute commands like that in install.cfg ( echo " " >> file_on_disk_not_in_memory_filesystem ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
install.cfg and command
Hi, At http://lists.freebsd.org/pipermail/freebsd-questions/2004-March/040502.htmlit states that I can run commands while installing server like: command="echo keyrate="fast" >> /etc/rc.conf" system But when I use that I get error I can't issue that command. Is there a speacial way to execute commands like that in install.cfg ( echo " " >> file_on_disk_not_in_memory_filesystem ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fetching install.cfg from a remote machine
Philippe LAQUET wrote: > I would like to know if someone has published some patch or found a > solution to perform a automatic installation via sysinstall but with a > remote (ftp/http/nfs) install.cfg file? I found some solutions using a > PXE boot disk and mount via NFS but don't want to put NFS shares and > DHCP "specific" server to do only that task. You don't need to setup nfs, install.cfg can be fetched with ftp. You can setup a PXEBoot jumpstart server that runs only tftp and dhcp, then in the install.cfg define a remote ftp server and the release you want. check this www.daemonsecurity.com/pub/pxeboot/ Alternatively, you can create a custom "boot-only" type iso which fetches the install.cfg, but in all cases, if you don't want to redo a lot of your work every time a new release comes out, you need to install using ftp. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 smime.p7s Description: S/MIME Cryptographic Signature
Fetching install.cfg from a remote machine
EHLO I would like to know if someone has published some patch or found a solution to perform a automatic installation via sysinstall but with a remote (ftp/http/nfs) install.cfg file? I found some solutions using a PXE boot disk and mount via NFS but don't want to put NFS shares and DHCP "specific" server to do only that task. Do the rebuild of the ISO image itself with the "install.cfg" on the CD is also an alternate option but we will have to rebuild the ISO, re-burn images every time we change an option - Use a new release and so on... Thanks in advance Philippe LAQUET ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fetching install.cfg from a remote machine
Hi! I would like to know if someone has published some patch or found a solution to perform a automatic installation via sysinstall but with a remote (ftp/http/nfs) install.cfg file? I found some solutions using a PXE boot disk and mount via NFS but don't want to put NFS shares and DHCP "specific" server to do only that task. Do the rebuild of the ISO image itself with the "install.cfg" on the CD is also an alternate option but we will have to rebuild the ISO, re-burn images every time we change an option - Use a new release and so on... Thanks for your help :P ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mac address in install.cfg
Hi, I am doing network installs of FreeBSD 6.0 and I want to place the install files in a directory that depends on the mac address of the server being installed. In install.cfg I want to specify something like nfs=10.0.0.1:/var/net_install/files/$MAC_ADDRESS mediaSetNFS package=db42-4.2.52_4 packageAdd Where the target server substitutes $MAC_ADDRESS at install time. Can anyone think of a way of doing this? Thanks John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make release / automated install / install.cfg woes
Is there some extra magic to making install.cfg work when rolling a release? I spent a fair amount of time this weekend preparing a custom release based off releng_6_0, and it works great but for one tiny detail.. After the installation is 'finished' and I reboot the system without the CD, it hangs with the bios complaining that it can't find anything to boot, which sounds suspiciously like the MBR wasn't written out correctly. The disk part of my install.cfg says: = disk=da0 bootManager=boot partition=all diskPartitionEditor da0s1-1=ufs 524288 / da0s1-2=swap 2097152 none da0s1-3=ufs 524288 /var da0s1-4=ufs 524288 /tmp da0s1-5=ufs 0 /usr 1 diskLabelEditor = The disk itself is setup absolutely correctly, the partitions are made, and the instally goes according to task up to and including the package installation... it just doesn't appear to Do The Right Thing when it comes to actually making the hdd bootable. Does this look like it should work? I've fiddled with various changes to the "bootManager" and "partition" lines, so far to no avail. Am I missing something here or should I start trying to figure out if the test system will boot off *any* hard drive? On a related note, when I make a change to this file, can I get away with something less than a new full "make release?" Is make rerelase or something else suitable when everything else is done and I'm just fiddling with this file? Thanks for any pointers. When I'm done with this I think I'm going to submit a doc patch for the 'make release' instructions. They are woefully inadequate for doing anything other than making a copy of your own release (unautomated) installations, and the example install.cfg still dates back to 4.x and jkh's laptop.. heh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysinstall install.cfg questions
Thank you! Excellent, exactly what I needed. The plan is to use disc1 of the release and modify it with a few packages and config changes to make an easily installable version of our modified desktop (Waimea/ROX/Webmin). I was going to use the BSD installer (bsdinstaller.org) but this way seems to make more sense in the long run, and leads into creating a port of the desktop as well (which is planned). Most likely we'll eventually make our own releases with a Live CD and a separate Install CD, so your reply was about as perfect as I could of ever hoped for. Progress is slow as it's not a top priority, but a preview of the project is available here: http://live.webpath.net I hope to get some screen shots up with in the next week or two. files to the Antony Mawer wrote: On 4/11/2005 6:52 AM, Todd wrote: I'm trying to figure out how to use the sysinstall using a install.cfg script to install on multiple machines without floppies, and without needing any interaction other than putting in the CD. I can create the script but don't know where to put it on the modified installation CD, or how to initiate sysinstall during the boot process to use it? Any help will be greatly appreciated! Todd Are you creating your own CDs using a 'make release' (see release(7)) process? If so, I've generally followed an approach similar to the following: 1. Create your install.cfg file in the /usr/src/release/ directory. 2. Create a patch file that will add your install.cfg to a standard /usr/src tree: cd /usr/src diff -u /dev/null src/release/install.cfg > ~/local.patch 3. Make the release with the appropriate LOCAL_PATCH parameter: make release \ CHROOTDIR=/some/dir \ BUILDNAME=6.0-MYRELEASE \ CVSROOT=/usr/home/ncvs \ RELEASETAG=RELENG_6_0 \ LOCAL_PATCHES=/path/to/local.path That would build a 6.0 security branch build with your install.cfg in /usr/src/release/ of the chroot. The make release process then takes care of placing the install.cfg in the appropriate location on the CD. If you're attempting to patch an existing CD image, reading /usr/src/release/Makefile suggests you'll need to: - Extract the contents of the ISO - Un-gzip and then mount the decompressed /boot/mfsroot.gz file - Place your install.cfg in the root of the mounted mfsroot fs - Unmount the mfsroot filesystem - Re-gzip the mfsroot file to /boot/mfsroot.gz - Run mkisofs to re-create the CD Hopefully this points you in the right general direction! Cheers Antony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysinstall install.cfg questions
On 4/11/2005 6:52 AM, Todd wrote: I'm trying to figure out how to use the sysinstall using a install.cfg script to install on multiple machines without floppies, and without needing any interaction other than putting in the CD. I can create the script but don't know where to put it on the modified installation CD, or how to initiate sysinstall during the boot process to use it? Any help will be greatly appreciated! Todd Are you creating your own CDs using a 'make release' (see release(7)) process? If so, I've generally followed an approach similar to the following: 1. Create your install.cfg file in the /usr/src/release/ directory. 2. Create a patch file that will add your install.cfg to a standard /usr/src tree: cd /usr/src diff -u /dev/null src/release/install.cfg > ~/local.patch 3. Make the release with the appropriate LOCAL_PATCH parameter: make release \ CHROOTDIR=/some/dir \ BUILDNAME=6.0-MYRELEASE \ CVSROOT=/usr/home/ncvs \ RELEASETAG=RELENG_6_0 \ LOCAL_PATCHES=/path/to/local.path That would build a 6.0 security branch build with your install.cfg in /usr/src/release/ of the chroot. The make release process then takes care of placing the install.cfg in the appropriate location on the CD. If you're attempting to patch an existing CD image, reading /usr/src/release/Makefile suggests you'll need to: - Extract the contents of the ISO - Un-gzip and then mount the decompressed /boot/mfsroot.gz file - Place your install.cfg in the root of the mounted mfsroot fs - Unmount the mfsroot filesystem - Re-gzip the mfsroot file to /boot/mfsroot.gz - Run mkisofs to re-create the CD Hopefully this points you in the right general direction! Cheers Antony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall install.cfg questions
I'm trying to figure out how to use the sysinstall using a install.cfg script to install on multiple machines without floppies, and without needing any interaction other than putting in the CD. I can create the script but don't know where to put it on the modified installation CD, or how to initiate sysinstall during the boot process to use it? Any help will be greatly appreciated! Todd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Autoinstall - install.cfg - scripting with system command
Hi Im having some trouble with the system command in the install.cfg file for autoinstalls. THe man page says the "system " command can be used at the end of the cfg file but I cant get it to work. I've tried. system "/full/path/to/prog \"escsomequotes\" " system "/full/path /full/path" system "/mnt/script" system /mnt/script system /full/path /full/path system "/full/path/to/prog" Sysinstall will just say that 'system /sbin/ping blah' failed - rest of script aborted ALT-F2 Reports the same DEBUG: Notify : warning : NO such command ping blah ..nothing seems to work. Can someone throw me an example or a hint on how to get some commands or scripting going at the end of install.cfg? I'm on FreeBSD5.4 on Intel. Thanks --CH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg (was RE: & No Subject)
Mike, Thanks alot for your suggestion, I'll try to put these lines to a shell script and try to make install.cfg run them. I'll post results soon. John Meing On Apr 8, 2005 5:55 PM, wizlayer <[EMAIL PROTECTED]> wrote: > On Friday 08 April 2005 02:31 am, John Meing wrote: > > Mike I also tried to use only following line in install.cfg > > (without the rc.conf lines) > > > > command="passwd root" system > > > > which should not has mismatching quote errors (and I tested > > with /stand/sysinstalld and it worked) but it didn't work when > > i put it in install.cfg :(( > > > > John Meing > > > [snip] > > > Okay, but that still doesn't work for the syntax... Going > > > back to > > > > > > your original post: > > > > command="echo sendmail_enable="NONE" >> /etc/rc.conf" > > > > system > > > > > > would at best cause mismatching quote errors (which is what > > > I'm assuming you're getting?) > > > > > > Mike > > hmmm... I googled this list and found the following link (which > may wrap in email): > > http://lists.freebsd.org/pipermail/freebsd-questions/2004-January/031620.html > > I'm thinking perhaps this function through sysinstall isn't > completely implemented yet or I've just noticed there's > no mention of a shell (h)... > > Maybe something like: > > # /stand/sysinstall command="sh passwd root" system > > Even though it doesn't seem to work from the command line, I > wonder if the problem isn't something along these lines? Perhaps > putting these commands into a script and then having install.cfg > run the script instead would clear it up. > > (I'm shooting in the dark here, I know... But now I'm curious...) > > Mike > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg (was RE: & No Subject)
On Friday 08 April 2005 02:31 am, John Meing wrote: > Mike I also tried to use only following line in install.cfg > (without the rc.conf lines) > > command="passwd root" system > > which should not has mismatching quote errors (and I tested > with /stand/sysinstalld and it worked) but it didn't work when > i put it in install.cfg :(( > > John Meing > [snip] > > Okay, but that still doesn't work for the syntax... Going > > back to > > > > your original post: > > > command="echo sendmail_enable="NONE" >> /etc/rc.conf" > > > system > > > > would at best cause mismatching quote errors (which is what > > I'm assuming you're getting?) > > > > Mike hmmm... I googled this list and found the following link (which may wrap in email): http://lists.freebsd.org/pipermail/freebsd-questions/2004-January/031620.html I'm thinking perhaps this function through sysinstall isn't completely implemented yet or I've just noticed there's no mention of a shell (h)... Maybe something like: # /stand/sysinstall command="sh passwd root" system Even though it doesn't seem to work from the command line, I wonder if the problem isn't something along these lines? Perhaps putting these commands into a script and then having install.cfg run the script instead would clear it up. (I'm shooting in the dark here, I know... But now I'm curious...) Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg (was RE: & No Subject)
Mike I also tried to use only following line in install.cfg (without the rc.conf lines) command="passwd root" system which should not has mismatching quote errors (and I tested with /stand/sysinstalld and it worked) but it didn't work when i put it in install.cfg :(( John Meing On Apr 7, 2005 7:05 PM, wizlayer <[EMAIL PROTECTED]> wrote: > On Thursday 07 April 2005 07:38 am, John Meing wrote: > > Dear Mike > > > > Here are few guides i used to create this install.cfg. > > > > http://mypage.bluewin.ch/dazdaz/freebsd_sysinstall.html > > http://www.freebsd.org/cgi/man.cgi?query=sysinstall&apropos=0&s > >ektion=0&manpath=FreeBSD+4.11-RELEASE&format=html > > > > I also try command line version of sysinstall like > > # /stand/sysinstall command="passwd root" system > > > > and it was works, but I don't know why it doesn't work with > > install.cfg > > > > John Meing > > Open mouth, insert foot... There is a command! :) > > Okay, but that still doesn't work for the syntax... Going back to > your original post: > > > command="echo sendmail_enable="NONE" >> /etc/rc.conf" system > > would at best cause mismatching quote errors (which is what I'm > assuming you're getting?) > > Mike > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg (was RE: & No Subject)
On Thursday 07 April 2005 08:05 am, wizlayer wrote: > > Okay, but that still doesn't work for the syntax... Going back > to > > your original post: > > command="echo sendmail_enable="NONE" >> /etc/rc.conf" system > > would at best cause mismatching quote errors (which is what I'm > assuming you're getting?) > > Mike I meant to ps before I sent this... Why not just create the rc.conf you want and introduce it after the install? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg (was RE: & No Subject)
On Thursday 07 April 2005 07:38 am, John Meing wrote: > Dear Mike > > Here are few guides i used to create this install.cfg. > > http://mypage.bluewin.ch/dazdaz/freebsd_sysinstall.html > http://www.freebsd.org/cgi/man.cgi?query=sysinstall&apropos=0&s >ektion=0&manpath=FreeBSD+4.11-RELEASE&format=html > > I also try command line version of sysinstall like > # /stand/sysinstall command="passwd root" system > > and it was works, but I don't know why it doesn't work with > install.cfg > > John Meing Open mouth, insert foot... There is a command! :) Okay, but that still doesn't work for the syntax... Going back to your original post: > command="echo sendmail_enable="NONE" >> /etc/rc.conf" system would at best cause mismatching quote errors (which is what I'm assuming you're getting?) Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg disklabel customization question
Good suggestion on using bsdlabel. Unfortunately I am required to use FreeBSD 4.6.2 which does not contain this utility and disklabel requires one to invoke an editor to define the new label. What I resorted to doing was having netboot create /usr100 and then later overwrite the /etc/fstab via an installation package that sets noauto for the label. Curtis On Wed, 05 Jan 2005 10:38:19 +, Matthew Seaman <[EMAIL PROTECTED]> wrote: > Curtis Almond wrote: > > > Anyone know how to make /usr100 not mounted at boot time? > > Edit /etc/fstab and add the 'noauto' flag to the appropriate line. > Something like this: > > /dev/ad0s2f /usr100 ufs rw,noauto 2 2 > > > Or even better > > How can I create the ad0s2-4 (ad0s2f after boot) label but have > > sysinstall not newfs it during netboot? > > You shouldn't need to recreate the disk or partition labels every time > you reboot, unless you are wiping and re-installing most of the disk > each time. > > If you're using sysinstall(8) to do an automatic install as part of your > netboot process, then as far as I can tell, there's no way using the > scripted interface to tell it to create a UFS partition but not newfs or > mount it -- although that's easy enough using sysinstall interactively. > > I'd be thinking more along the lines of ditching sysinstall(8) entirely > for that purpose and using fdisk(8), bsdlabel(8) and newfs(8) directly. > >Cheers, > >Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor > School Rd > PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone > Tel: +44 1304 617253 Kent, CT14 0JL UK > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg disklabel customization question
On Tue, 4 Jan 2005 17:23:05 -0600, Curtis Almond <[EMAIL PROTECTED]> wrote: > I would like to be able to do the following > > 1. Create a / partition of x size > 2. Create a swap partition of x size > 3. Create a /usr partition of x size > 4. Create a ufs partition of the rest of the disk but it is not mounted at > boot. > > What I have thus far is: > # label disk 1 > # IDE > ad0s2-1=ufs 3969000 / > ad0s2-2=swap 3969000 none > ad0s2-3=ufs 3969000 /usr > ad0s2-4=ufs 0 /usr100 > > Anyone know how to make /usr100 not mounted at boot time? Don't put it in /etc/fstab. Then you can use mount(8) to mount it when you need to. -- Joshua Lokken Open Source Advocate ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg disklabel customization question
Curtis Almond wrote: Anyone know how to make /usr100 not mounted at boot time? Edit /etc/fstab and add the 'noauto' flag to the appropriate line. Something like this: /dev/ad0s2f /usr100 ufs rw,noauto 2 2 Or even better How can I create the ad0s2-4 (ad0s2f after boot) label but have sysinstall not newfs it during netboot? You shouldn't need to recreate the disk or partition labels every time you reboot, unless you are wiping and re-installing most of the disk each time. If you're using sysinstall(8) to do an automatic install as part of your netboot process, then as far as I can tell, there's no way using the scripted interface to tell it to create a UFS partition but not newfs or mount it -- although that's easy enough using sysinstall interactively. I'd be thinking more along the lines of ditching sysinstall(8) entirely for that purpose and using fdisk(8), bsdlabel(8) and newfs(8) directly. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor School Rd PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone Tel: +44 1304 617253 Kent, CT14 0JL UK signature.asc Description: OpenPGP digital signature
install.cfg disklabel customization question
I would like to be able to do the following 1. Create a / partition of x size 2. Create a swap partition of x size 3. Create a /usr partition of x size 4. Create a ufs partition of the rest of the disk but it is not mounted at boot. What I have thus far is: # label disk 1 # IDE ad0s2-1=ufs 3969000 / ad0s2-2=swap 3969000 none ad0s2-3=ufs 3969000 /usr ad0s2-4=ufs 0 /usr100 Anyone know how to make /usr100 not mounted at boot time? Or even better How can I create the ad0s2-4 (ad0s2f after boot) label but have sysinstall not newfs it during netboot? Any ideas would be great.. Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2.1-RELEASE and install.cfg unable to find ad0s1b dev node
On Tuesday 14 September 2004 02:12, Ivan Fetch wrote: > Hello, > > I've searched the mailing lists and found others with this issue, but > haven't found a solution yet - can someone point me in the right direction > please? > > When using an install.cfg file with 5.2.1-RELEASE, I get: > Unable to find device node for /dev/ad0s1b in /dev! > The creation of filesystems will be aborted. [...] > debug=yes > # Networking Options > hostname=geo > domainname=domain.com > nameserver=192.168.0.254 > defaultrouter=192.168.0.254 > ipaddr=192.168.0.201 > netmask=255.255.255.0 > netDev=fxp0 > # Install Media Options > mediaSetCDROM > # Distribution Selection > distSetKernDeveloper > # Partitioning > disk=ad0 > partition=all > bootManager=boot > diskPartitionEditor > diskPartitionWrite > ad0s1-1=ufs 524288 / > ad0s1-2=swap 131072 none > ad0s1-3=ufs 524288 /var > ad0s1-4=ufs 0 /usr > # Even commenting out the above and uncomminting the below, install still > fails. > #diskInteractive=yes > diskLabelEditor > diskLabelCommit > installCommit I think you should remove the functions "diskPartitionWrite" and "diskLabelCommit", try this instead: debug=yes # Networking Options hostname=geo domainname=domain.com nameserver=192.168.0.254 defaultrouter=192.168.0.254 ipaddr=192.168.0.201 netmask=255.255.255.0 netDev=fxp0 # Partitioning disk=ad0 partition=all bootManager=boot diskPartitionEditor # disklabel ad0s1-1=ufs 524288 / ad0s1-2=swap 131072 none ad0s1-3=ufs 524288 /var ad0s1-4=ufs 0 /usr diskLabelEditor # install sys mediaSetCDROM distSetKernDeveloper installCommit Cheers, ch -- Christian Hiris <[EMAIL PROTECTED]> | OpenPGP KeyID 0x3BCA53BE OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.2.1-RELEASE and install.cfg unable to find ad0s1b dev node
Hello, I've searched the mailing lists and found others with this issue, but haven't found a solution yet - can someone point me in the right direction please? When using an install.cfg file with 5.2.1-RELEASE, I get: Unable to find device node for /dev/ad0s1b in /dev! The creation of filesystems will be aborted. Even if I set the DiskInteractive variable before running the DiskLabel editor, the above error still appears. Here is my install.cfg file: installVarDefaults debug=yes # Networking Options hostname=geo domainname=domain.com nameserver=192.168.0.254 defaultrouter=192.168.0.254 ipaddr=192.168.0.201 netmask=255.255.255.0 netDev=fxp0 # Install Media Options mediaSetCDROM # Distribution Selection distSetKernDeveloper # Partitioning disk=ad0 partition=all bootManager=boot diskPartitionEditor diskPartitionWrite ad0s1-1=ufs 524288 / ad0s1-2=swap 131072 none ad0s1-3=ufs 524288 /var ad0s1-4=ufs 0 /usr # Even commenting out the above and uncomminting the below, install still fails. #diskInteractive=yes diskLabelEditor diskLabelCommit installCommit Thanks in advance for your help, Ivan Fetch. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall install.cfg disk unmount failure
I've scripted sysinstall to do a complete system installation, compiled a custom PXE kernel and mfsroot image, and gotten almost all of my disk issues straightened out. My last issue is this: After the system installation completes and the system reboots, I get errors about the file systems not being unmounted cleanly. If I remove "shutdown" from the end of my install.cfg script and replace it with "command=/sbin/reboot \ system" then I get an error in sysinstall about system command failing but the system reboots and the file systems are clean. Does anyone have any ideas where I might be screwing up this time? -Don ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
install.cfg disklabel failure when PXE booting
I am attempting to set up network installs of FreeBSD 5.2.1 for a project I am working on. I can boot kern.flp and mfsroot.flp over the network with no problems and do a manual install. I can configure install.cfg to automatically set the distribution, network card, install method and so on. What I can not get working right is automatic disk partitioning. No matter what I have set up, the installer just will not set up partitions for me. install.cfg looks like: # Now set the parameters for the partition editor on ad0 disk=ad0 partition=all bootManager=standard diskPartitionEditor #diskPartitionWrite # All sizes are expressed in 512 byte blocks! ad0s1-1=ufs 199 / ad0s1-2=swap 6485760 none ad0s1-3=ufs 2097152 /var ad0s1-4=ufs 0 /usr # Let's do it! diskLabelEditor #diskLabelCommit Can anyone tell me where I am screwing up? I have tried several variations on the above config file all without success. There is also the somewhat related problem of sysinstall refusing to accept the BIOS definition of the drive geometry but I believe I was able to get beyond that problem. Thanks in advance, -Don ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sysinstall, install.cfg, unable to find device node
Hello all, I am trying to make an automatic install procedure of a FreeBSD 5.2.1. I'm booting from the 5.2.1-miniiso and then I insert a floppy containing my install.cfg. Then I select the "Load config" menuitem from sysinstall and run the install.cfg. It then perform some network operations but halts shortly after with the following error message: "Unable to find device node for /dev/aacd0s2b in /dev!" The Debug console is telling me this: ... DEBUG: Scanning disk aacd0 for swap partitions DEBUG: Found swapdev at aacd0s2b! I've noticed that the slice created by my install.cfg get a partition subtype 3 and not 165 as one would expect. If I examine the labels through the sysinstall menu it seems as if they're created. If I try to manually delete the created labels and manually creates some new ones I get the same error. But if I delete the created slice and afterwards creates the labels things seems to be alright. Any suggestions as to what might be wrong? My install.cfg is as follows (some of the comments have been wrapped but are as they should be in the original file): # # FreeBSD Unattended Install Sample install.cfg # Provided by http://bsdhound.com # # Turn on extra debugging. debug=YES # Initialize all variables to their defaults, overriding any previous settings. installVarDefaults # # Networking Information # hostname=goodman domainname=interflow.dk # DHCP Server Should take care of below nameserver=192.168.1.1 defaultrouter=192.168.1.1 ipaddr=192.168.1.115 netmask=255.255.255.0 #ntpdate_flags=-b ntp.lth.se #configNTP # # Which installation method to use # # FTP _ftpPath=ftp://ftp.dk.freebsd.org/pub/FreeBSD/ netDev=em0 mediaSetFTP # NFS #mediaSetNFS #nfs=MyNfsServer:/export/ari_scratch2/gallatin/freebsd-dist # # Select which distributions we want. # dists= bin doc catpages dict info crypto ports #THE INFORMATION ABOVE HERE SHOULD BE ON 1 LINE. distSetCustom # # Set the parameters for the partition editor # # ad = IDE, da = SCSI disk=aacd0 # Enable this for interactive fdisk # If you plan on using this on various other machies # it might be wise to enable the interactive fdisk and # disklabel #diskInteractive # Change this to "all" if this is a server, we don't want any multi-booting rubbish on our servers partition=free bootManager=boot diskPartitionEditor # # - All sizes are expressed in 512 byte blocks! # - "Size in MB" = sectors * 512 / 1024 / 1024 # - "Number of blocks" = xsize in mb * 1024 * 1024 / 512 # The non-zero value after the mountpoint means enable soft updates # # 256MB UFS root aacd0s2-1=ufs 524288 / # 1024MB SWAP aacd0s2b aacd0s2-2=swap 2097152 none # 256MB UFS aacd0s2e aacd0s2-3=ufs 524288 /var 1 # 256MB UFS aacd0s2f aacd0s2-4=ufs 524288 /tmp 1 # Rest of FreeBSD partition aacd0s2g aacd0s2-5=ufs 0 /usr 1 diskLabelEditor # OK, everything is set. Do it! installCommit # # Install some packages at the end. # #package=BitchX-1.0c19_3 #packageAdd # # this last package is special. It is used to configure the machine. # it installs several files (like /root/.rhosts) an its installation # script tweaks several options in /etc/rc.conf # #package=ari-0.0 #packageAdd # In case of any problem with the script we enable remote access now and set a temporary root password command="echo rc_conf_files="/etc/rc.conf /etc/rc.conf.local" >> /etc/rc.conf" system command="echo keymap="danish.iso" >> /etc/rc.conf" system command="echo keyrate="fast" >> /etc/rc.conf" system command="echo sshd_enable="YES" >> /etc/rc.conf" system command="echo 'devilinside' | /usr/sbin/pw usermod -u root -h 0" system command=/sbin/reboot system -- Cheers, Jacob Atzen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Set Fragment Size via sysinstall/install.cfg
On Wed, 4 Feb 2004 15:20:37 -0800 Michael Barrett <[EMAIL PROTECTED]> wrote: > I have a PXE boot build system that works great. I am about to > make a database that will grow very large, so I thought it might > be a good idea to create a partition for that database that has a > large fragment & block size (to save time on fsck's and the like). > Does anyone know how to do this via install.cfg for sysinstall? > Is it even possible? The documentation doesn't mention it. > > Thanks. Please wrap. Custom newfs options in the Label screen taken from man newfs ? -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Set Fragment Size via sysinstall/install.cfg
I have a PXE boot build system that works great. I am about to make a database that will grow very large, so I thought it might be a good idea to create a partition for that database that has a large fragment & block size (to save time on fsck's and the like). Does anyone know how to do this via install.cfg for sysinstall? Is it even possible? The documentation doesn't mention it. Thanks. -- Mike Barrett | "We have veggie bacon, why don't we have [EMAIL PROTECTED] | meat fruit?" www.daboyz.org |-- My ex-coworker, Ben +--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install.cfg
Vahric MUHTARYAN asked on Saturday January 10, 2004: > Hi , > > You can see my install.cfg output below. I can't set hostname , ip address > I'dont understand why ? and I red sysinstall but it's funny I cant find any > variable for hostname and ip address . They are only available for > mediaSetNFS . Do I have to use install media NFS ? > > Thanks, > Vahric I'm guessing that you've already looked at /usr/src/release/sysinstall/install.cfg - that's a good starting point. You only configure the network in install.cfg if you're doing a network install. These values (as far as I know) do not persist after the installation. Why not put /etc/rc.conf and so forth onto a floppy, and add them to the system after installation? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
install.cfg
Hi , You can see my install.cfg output below. I can't set hostname , ip address I'dont understand why ? and I red sysinstall but it's funny I cant find any variable for hostname and ip address . They are only available for mediaSetNFS . Do I have to use install media NFS ? Thanks, Vahric # # This is my install.cfg for FreeBSD 4.8-RELEASE. You must save this in UNIX and not PC format! # This is a typical config that most people will want to use, modify as necessary. # # From the sysinstall manpage : # "sysinstall is currently at the end of its life cycle and will eventually be replaced." # # [EMAIL PROTECTED] # # *** WARNING *** DO NOT USE THIS CONFIG YOU'VE READ IT CAREFULLY AS IT WILL OVERWRITE YOUR DISK # # Use Alt F2 to see the debug output #installVarDefaults #nonInteractive=NO #tryDHCP=NO #noWarn=NO # router solicitation, turns off IPv6 #tryRTSOL=NO debug=yes # # Installed host's configuration hostname=freebsd.try.net.tr domainname=try.net.tr nameserver=10.10.10.2 defaultrouter=10.10.10.1 ipaddr=10.10.10.102 netmask=255.255.255.0 # # Which installation method to use # This is where the system will go - ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/i386/packages-4.8-release/All/ # If you use a different kernel, such as upgrading to 4.8-STABLE then you won't be able to ftp packages because # sysinstall does'nt allow it. #_ftpPath=ftp://ftp.uk.freebsd.org/pub/FreeBSD/ #netDev=xl0 #mediaSetFTP #mediaSetNFS #nfs=MyNfsServer:/export/ari_scratch2/gallatin/freebsd-dist mediaSetCDROM # # Select which distributions we want. #dists=bin doc manpages dict info crypto compat3x compat4x ports ssecure sbase scontrib sgnu setc sinclude slib slibexec srelease sb in ssbin sshare ssys subin susbin ssmailcf Xbin Xcfg Xdoc Xhtml Xlib Xlk98 Xlkit Xman Xprog Xps Xset Servers/XSVGA Servers/XVG16 Ser vers/Xnest Servers/Xvfb Xfnts Xf100 Xfcyr Xfscl Xfnon Xfsrv #distSetCustom distSetEverything # # Set the parameters for the partition editor # ad = IDE, da = SCSI disk=da0 # Enable this for interactive fdisk #diskInteractive # Change this to "all" if this is a server, we don't want any multi-booting rubbish on our servers #partition=existing #partition=all partition=exclusive bootManager=boot diskPartitionEditor # # - All sizes are expressed in 512 byte blocks! # - "Size in MB" = sectors * 512 / 1024 / 1024 # - "Number of blocks" = xsize in mb * 1024 * 1024 / 512 # The non-zero value after the mountpoint means enable soft updates da0s1-1=ufs 2031616 / da0s1-2=swap 1015808 none da0s1-3=ufs 2031616 /var 56 da0s1-4=ufs 1015808 /tmp da0s1-5=ufs 0 /usr diskLabelEditor # runs diskLabelCommit diskPartitionWrite #configPackages #package=bash-2.05b.007 #packageAdd #package=cvsup-16.1h #packageAdd #package=vim-lite-6.2.72 #packageAdd installCommit package=bash-2.05b.007 packageAdd package=cvsup-16.1h packageAdd package=vim-lite-6.2.72 packageAdd # If you use execute a system command with parameters, then you must use double quotes, else it won't work # and will terminate the script. # I recommend that you execute as few commands here as possible because if they fail the subsequent commands # will not be executed, and so the entire installation may be unusable depending on the subsequent commands. # Remember to use the full path to the system command # WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING # These still don't work properly, i'm fed up with sysinstall!!! Just execute the script, that works. # WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING # In case of any problem with the script we enable remote access now and set a temporary root password #command="echo rc_conf_files="/etc/rc.conf /etc/rc.conf.local" >> /etc/rc.conf" #system #command="echo sshd_enable="YES" >> /etc/rc.conf" #system #command="echo 'abc123' | /usr/sbin/pw usermod -u root -h 0" #system # We write a script to make system changes as opposed to using a package as this way we have much more control # PATH is not set so also be careful to explicitly tell system where the script is #command=/stand/post-install.sh #system #command=/sbin/reboot #system shutdown # End of install.cfg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[5.1] custom FDISK with sysinstall + install.cfg
Suppose I want to get something like: 0 63 62- 12 unused0 63 20466747 20466809da0s1 8freebsd 165 20466810 15085035 35551844da0s2 8freebsd 165 35551845 14633 35566477- 12 unused0 with sysinstall + Local Config + install.cfg. The only thing I found in sysinstall(8) manpage is: partition=free partition=all partition=existing partition=exclusive partition=aNumber <--- this supposes an empty available space Is there any syntax available? -- Jacques Beigbeder| [EMAIL PROTECTED] Service de Prestations Informatiques | http://www.spi.ens.fr Ecole normale supérieure | 45 rue d'Ulm |Tel : (+33 1)1 44 32 37 96 F75230 Paris cedex 05|Fax : (+33 1)1 44 32 20 75 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
install.cfg & newfs
I have done some experimenting with install.cfg and missed newfs with that. I noticed that it was availble when you do with this config file. I read (in the source) something about a argument like newfsArgs but it was not clear on how to use this. I appricate any pointers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
