Re: Make Release
On Thu, Aug 1, 2013 at 12:40 PM, Amitabh Kant amitabhk...@gmail.com wrote: Devin Teske Rick Miller have a fairly extensive explanation on their blogs on how to create your own modified iso's. Search the archives for links. Hopefully they can chime in with their respective links. Sorry to show up late for the discussion... Devin Teske definitely has more experience and knowledge than I. However, several of my blog posts may have relevant and helpful information on customizing images. There's not really one single answer as it depends largely on what you're looking to do. My customized images use a scripted sysinstall install.cfg that fetches a dynamically generated answer file from Cobbler. The answer file is based on a text template which includes Cheetah calls to Cobbler snippets for various things, including modifying the rc.conf. All lines modifying the rc.conf are placed in the answer file following the installCommit resword. Also understand that we replaced the http media type module with our own permitting direct http installs. In 8.4 or newer, there is a new media type called httpDirect (or similar) that accomplishes this as well. Here are some posts you may find helpful: http://blog.hostileadmin.com/2013/04/11/installing-freebsd-via-cobbler/ http://blog.hostileadmin.com/2012/10/08/building-freebsd-media-with-custom-packages/ http://blog.hostileadmin.com/2012/05/08/using-sysinstall-for-automated-freebsd-8-x-installs/ Bear in mind this applies specifically to FreeBSD 8.x. I will begin attacking 9.x in the coming months and anticipate more blog posts on accomplishing similar tasks within 9.x. -- 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
Make Release
one specific question I have, that I can't find in the handbook... To make a FreeBSD release, that is to build the install images... you build world, and kernel.. then go to /etc/src/release and type make release... after this, the release images show up in /usr/obj/usr/src/release What I WANT to know.. is what shell script or file can I edit, to modify the install image BEFORE its created... for example say I wanted to add a line to /etc/rc.conf on the memstick.img file that gets created I understand that there may be better ways to accomplish this, but editing /etc/rc.conf is ONLY a example, im trying to find a simple way to create a slightly modified install media for my own internal purposes... eg: ssh enabled and the ethernet card set to DHCP, so I can remote install... I am aware of mfsBSD, as well as DruidBSD, however i'm looking for something simple that I can script. any help or thoughts is appreciated -- Sam Fourman Jr. ___ 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: Make Release
On Aug 1, 2013, at 9:14 AM, Sam Fourman Jr. wrote: one specific question I have, that I can't find in the handbook... To make a FreeBSD release, that is to build the install images... you build world, and kernel.. then go to /etc/src/release and type make release... after this, the release images show up in /usr/obj/usr/src/release What I WANT to know.. is what shell script or file can I edit, to modify the install image BEFORE its created... for example say I wanted to add a line to /etc/rc.conf on the memstick.img file that gets created I understand that there may be better ways to accomplish this, but editing /etc/rc.conf is ONLY a example, im trying to find a simple way to create a slightly modified install media for my own internal purposes... eg: ssh enabled and the ethernet card set to DHCP, so I can remote install... I am aware of mfsBSD, as well as DruidBSD, however i'm looking for something simple that I can script. any help or thoughts is appreciated I'm hoping that my very open development documentation on customizing the release(7) process for producing DruidBSD releases can help you out here. I've documented much of the internals of the release(7) process (albeit, relevant to the RELENG_8 release(7) Makefile; in RELENG_9 it's still relevant to /usr/src/release/Makefile.sysinstall ... but I gather that much of the knobs may still exist in HEAD). Have a read through this revision-controlled text file... http://druidbsd.cvs.sf.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/README?revision=1.2view=markup ALSO NOTE: Yes, the file is dated... it talks about cvsup instead of svn. My hope is that the doco can be a good starting point (even if the data is a bit dated). In there, you'll find things like (relevant to RELENG_9): make -f Makefile.sysinstall release \ MAKE=/usr/bin/env CFLAGS=-DDRUID make \ CHROOTDIR=/usr/release EXTSRCDIR=/usr/src KERNELS_BASE= \ NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \ WORLD_FLAGS=-DWITHOUT_OPENSSL PATCH_FLAGS=-N \ LOCAL_PATCHES=/tmp/druid.patches \ LOCAL_SCRIPT=/tmp/local_script.sh | tee release.log Take special note of the LOCAL_SCRIPT= option. Maybe, just maybe, the bsdinstall-specific release(7) process supports LOCAL_SCRIPT too. If it doesn't... why not? -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: Make Release
Devin Teske Rick Miller have a fairly extensive explanation on their blogs on how to create your own modified iso's. Search the archives for links. Hopefully they can chime in with their respective links. I the meantime , the following link has somewhat of my own notes for creating a custom cd; http://www.amitabhkant.com/custom_iso_with_bsdinstall_in_freebsd/ Does not cover all points, but hopefully should give you a starting point. My link is only applicable for bsdinstall (9.0 9.1) based installers. Amitabh Kant On Thu, Aug 1, 2013 at 9:44 PM, Sam Fourman Jr. sfour...@gmail.com wrote: one specific question I have, that I can't find in the handbook... To make a FreeBSD release, that is to build the install images... you build world, and kernel.. then go to /etc/src/release and type make release... after this, the release images show up in /usr/obj/usr/src/release What I WANT to know.. is what shell script or file can I edit, to modify the install image BEFORE its created... for example say I wanted to add a line to /etc/rc.conf on the memstick.img file that gets created I understand that there may be better ways to accomplish this, but editing /etc/rc.conf is ONLY a example, im trying to find a simple way to create a slightly modified install media for my own internal purposes... eg: ssh enabled and the ethernet card set to DHCP, so I can remote install... I am aware of mfsBSD, as well as DruidBSD, however i'm looking for something simple that I can script. any help or thoughts is appreciated -- Sam Fourman Jr. ___ 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: Make Release
On Thu, Aug 1, 2013 at 10:10 PM, Amitabh Kant amitabhk...@gmail.com wrote: Devin Teske Rick Miller have a fairly extensive explanation on their blogs on how to create your own modified iso's. Search the archives for links. Hopefully they can chime in with their respective links. I the meantime , the following link has somewhat of my own notes for creating a custom cd; http://www.amitabhkant.com/custom_iso_with_bsdinstall_in_freebsd/ Does not cover all points, but hopefully should give you a starting point. My link is only applicable for bsdinstall (9.0 9.1) based installers. Amitabh Kant On Thu, Aug 1, 2013 at 9:44 PM, Sam Fourman Jr. sfour...@gmail.comwrote: one specific question I have, that I can't find in the handbook... To make a FreeBSD release, that is to build the install images... you build world, and kernel.. then go to /etc/src/release and type make release... after this, the release images show up in /usr/obj/usr/src/release What I WANT to know.. is what shell script or file can I edit, to modify the install image BEFORE its created... for example say I wanted to add a line to /etc/rc.conf on the memstick.img file that gets created I understand that there may be better ways to accomplish this, but editing /etc/rc.conf is ONLY a example, im trying to find a simple way to create a slightly modified install media for my own internal purposes... eg: ssh enabled and the ethernet card set to DHCP, so I can remote install... I am aware of mfsBSD, as well as DruidBSD, however i'm looking for something simple that I can script. any help or thoughts is appreciated -- Sam Fourman Jr. ___ 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 Sorry for the top posting in my last email. Amitabh ___ 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: Make Release
On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin devin.te...@fisglobal.comwrote: I'm hoping that my very open development documentation on customizing the release(7) process for producing DruidBSD releases can help you out here. I've documented much of the internals of the release(7) process (albeit, relevant to the RELENG_8 release(7) Makefile; in RELENG_9 it's still relevant to /usr/src/release/Makefile.sysinstall ... but I gather that much of the knobs may still exist in HEAD). Have a read through this revision-controlled text file... http://druidbsd.cvs.sf.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/README?revision=1.2view=markup ALSO NOTE: Yes, the file is dated... it talks about cvsup instead of svn. My hope is that the doco can be a good starting point (even if the data is a bit dated). In there, you'll find things like (relevant to RELENG_9): make -f Makefile.sysinstall release \ MAKE=/usr/bin/env CFLAGS=-DDRUID make \ CHROOTDIR=/usr/release EXTSRCDIR=/usr/src KERNELS_BASE= \ NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \ WORLD_FLAGS=-DWITHOUT_OPENSSL PATCH_FLAGS=-N \ LOCAL_PATCHES=/tmp/druid.patches \ LOCAL_SCRIPT=/tmp/local_script.sh | tee release.log Take special note of the LOCAL_SCRIPT= option. Maybe, just maybe, the bsdinstall-specific release(7) process supports LOCAL_SCRIPT too. If it doesn't... why not? -- Devin Devin Do you have any idea if there have an changes to bsdinstall process (on scripting side) in the upcoming 9.2 ? Amitabh ___ 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: Make Release
On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote: On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin devin.te...@fisglobal.com wrote: I'm hoping that my very open development documentation on customizing the release(7) process for producing DruidBSD releases can help you out here. I've documented much of the internals of the release(7) process (albeit, relevant to the RELENG_8 release(7) Makefile; in RELENG_9 it's still relevant to /usr/src/release/Makefile.sysinstall ... but I gather that much of the knobs may still exist in HEAD). Have a read through this revision-controlled text file... http://druidbsd.cvs.sf.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/README?revision=1.2view=markup ALSO NOTE: Yes, the file is dated... it talks about cvsup instead of svn. My hope is that the doco can be a good starting point (even if the data is a bit dated). In there, you'll find things like (relevant to RELENG_9): make -f Makefile.sysinstall release \ MAKE=/usr/bin/env CFLAGS=-DDRUID make \ CHROOTDIR=/usr/release EXTSRCDIR=/usr/src KERNELS_BASE= \ NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \ WORLD_FLAGS=-DWITHOUT_OPENSSL PATCH_FLAGS=-N \ LOCAL_PATCHES=/tmp/druid.patches \ LOCAL_SCRIPT=/tmp/local_script.sh | tee release.log Take special note of the LOCAL_SCRIPT= option. Maybe, just maybe, the bsdinstall-specific release(7) process supports LOCAL_SCRIPT too. If it doesn't... why not? -- Devin Devin Do you have any idea if there have an changes to bsdinstall process (on scripting side) in the upcoming 9.2 ? Yes, the partedit portion of bsdinstall is scriptable in 9.2. Also, many bug fixes. Also, you can now create /etc/installerconf (no `dot' between installer and conf) and it will be picked up and run by bsdinstall. For your bsdinstall scripts, 2 new tools and a new framework to learn... Tools: bsdconfig(8) and sysrc(8) Framework: bsdconfig libraries (advanced scripting) If you're behind on your sysinstall(8) *(yes... sysinstall(8)) scripting abilities, then I suggest you brush up. * bsdconfig(8) is [mostly] backward compatible sysinstall(8) scripts So... in your bsdinstal installerconf, you can: # Example A # ( do bsdinstall stuff ) then... bsdconfig packages # Example B # ( do bsdinstall stuff ) then... sysrc sshd_enable=YES # Example C # ( do bsdinstall stuff ) then... . /usr/share/bsdconfig/script.subr || exit 1 for package in a-1.0 b-2.0 c-3.0; do packageAdd done Here's a full list of items that bsdconfig(8) supports which are documented in sysinstall(8) (to which all you need to do to access is to include /usr/share/bsdconfig/script.subr): loadConfig deviceRescan mediaOpen mediaClose mediaGetType mediaSetCDROM mediaSetDOS mediaSetDirectory mediaSetFloppy mediaSetNFS mediaSetUFS mediaSetUSB optionsEditor tcpMenuSelect mediaSetFTP mediaSetFTPActive mediaSetFTPPassive mediaSetFTPUserPass mediaSetHTTP mediaSetHTTPProxy configPCNFSD configPackages packageAdd packageDelete packageReinstall installVarDefaults dumpVariables But that's only the tip of the iceberg. To get a full idea of what you can do with shell-script ALONE, you have to see the bsdconfig includes, which are in /usr/share/bsdconfig (link to what's released into 9.2 below): http://svnweb.freebsd.org/base/stable/9/usr.sbin/bsdconfig/share/ For example, there is: common.subr -- stuff everybody should use (makes your code cleaner and gives you basic abilities missing in shell, like f_getvar -- partner to setvar) device.subr -- scan for known devices and create structures with device info and type. Also provide routines for quickly scanning the array of structures for pre-probed devices of a specific type. Also contains code for presenting a menu of devices (of given type) to the user to select, returning the user's selection for processing. dialog.subr -- a *monster* of a library (uber documented to boot). Allows clean abstraction of dialog to where either dialog(1) or Xdialog(1) is a simple proposition to interface to. mustberoot.subr -- if your shell script needs to be able to run as non-root but escalate to root as-needed, this provides a clean way to transition to where your users seemlessly elevate. script.subr -- a dummy include that includes all the other includes. strings.subr -- handy string manipulation routines (tuned both for convenience and performance). struct.subr -- hold information in structs (using shell!) sysrc.subr -- manage rc.conf(5)! variable.subr -- variable definitions (boring; unless you code on bsdconfig -- hey, think about writing a module sometime! I encourage it, it's fun!) Beyond that... ( ok that's enough for this e-mail ). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies;
Re: Make Release
On Aug 1, 2013, at 10:58 AM, Teske, Devin wrote: On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote: On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin devin.te...@fisglobal.com wrote: I'm hoping that my very open development documentation on customizing the release(7) process for producing DruidBSD releases can help you out here. I've documented much of the internals of the release(7) process (albeit, relevant to the RELENG_8 release(7) Makefile; in RELENG_9 it's still relevant to /usr/src/release/Makefile.sysinstall ... but I gather that much of the knobs may still exist in HEAD). Have a read through this revision-controlled text file... http://druidbsd.cvs.sf.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/README?revision=1.2view=markup ALSO NOTE: Yes, the file is dated... it talks about cvsup instead of svn. My hope is that the doco can be a good starting point (even if the data is a bit dated). In there, you'll find things like (relevant to RELENG_9): make -f Makefile.sysinstall release \ MAKE=/usr/bin/env CFLAGS=-DDRUID make \ CHROOTDIR=/usr/release EXTSRCDIR=/usr/src KERNELS_BASE= \ NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \ WORLD_FLAGS=-DWITHOUT_OPENSSL PATCH_FLAGS=-N \ LOCAL_PATCHES=/tmp/druid.patches \ LOCAL_SCRIPT=/tmp/local_script.sh | tee release.log Take special note of the LOCAL_SCRIPT= option. Maybe, just maybe, the bsdinstall-specific release(7) process supports LOCAL_SCRIPT too. If it doesn't... why not? -- Devin Devin Do you have any idea if there have an changes to bsdinstall process (on scripting side) in the upcoming 9.2 ? [snip] Beyond that... ( ok that's enough for this e-mail ). More includes (for the advanced scripting -- again, tapping into what /usr/share/bsdconfig/script.subr provides), there are sub-directories in /usr/share/bsdconfig (but again, script.subr brings them all in): media/ -- one file for each type of media (FTP, HTTP, HTTP Proxy, NFS, ... etc.) networking/ -- scripts for getting, setting, and interactively modifying network packages/ -- package management password/ -- root password startup/ -- rc.conf(5) and startup services timezone/ -- like tzsetup usermgmt/ -- user management stuff Each of those includes a lot of low-level functionality but it's all documented very well. That being said... there's one more avenue of scripting. All of the bsdconfig(8) modules that act as front-ends to the above libraries. Those are in /usr/libexec/bsdconfig -- and you can call those from your bsdinstall ``/etc/installerconf'' too. # Example A /usr/libexec/bsdconfig/090.timezone/timezone However, it's far easier to just say: # Example B bsdconfig timezone For a list of keywords to the modules, say either: bsdconfig -h *or* Peruse the diagram (which is generated by bsdconfig dot): http://druidbsd.sourceforge.net/download/bsdconfig/bsdconfig-HEAD-20130506-3i.svg The green parallelograms are the bsdconfig keywords, and the blue rectangles represent the modules (mousing over it will show the /usr/libexec/bsdconfig path in a tooltip). -- Devin -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: make release fails
On 05/23/2013 06:52 AM, Jack Mc Lauren wrote:
Hi
snip
find //usr/obj/usr/src/release/dist/doc -empty -delete
find: -delete: //usr/obj/usr/src/release/dist/doc: relative path potentially
not
safe
*** [distributeworld] Error code 1
snip
What's wrong with this?
Thanks in advance
Huh. Apparently I ran across this myself in the past, since I found a
patch lurking in my source tree.
8
diff --git a/Makefile.inc1 b/Makefile.inc1
index 4567e5d..1830483 100644
--- a/Makefile.inc1
+++ b/Makefile.inc1
@@ -685,7 +685,7 @@ distributeworld installworld: installcheck
${IMAKEENV} rm -rf ${INSTALLTMP}
.if make(distributeworld)
.for dist in ${EXTRA_DISTRIBUTIONS}
- find ${DESTDIR}/${DISTDIR}/${dist} -empty -delete
+ find ${DESTDIR}/${DISTDIR}/${dist} -empty -exec rmdir {} +
.endfor
.endif
8
The reason this occurs is because you and I are building with NODOC,
which leaves dist/doc empty, and the above find construct will refuse to
-delete if the directory specified on the command line is one of the
ones that would have been deleted.
Either patch the makefile as above, tell make to ignore the return code
of this find invocation, or put some non-empty files into
/usr/obj/usr/src/release/dist/doc during the release building process
(like a README pointing to the docs tarball on the mirrors) to make it
not trigger the empty condition.
Hope this helps!
--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
cyber...@cyberleo.net
Furry Peace! - http://www.fur.com/peace/
___
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
make release fails
Hi I'm trying to make my own release ... # cd /usr/src # make buildkernel KERNCONF=MYKERN # make -j4 buildworld # cd release/ # make release NODOC=YES NOPORTS=YES NOSRC=YES and that's the error while making release: find //usr/obj/usr/src/release/dist/doc -empty -delete find: -delete: //usr/obj/usr/src/release/dist/doc: relative path potentially not safe *** [distributeworld] Error code 1 Stop in /usr/src. *** [distributeworld] Error code 1 Stop in /usr/src. *** [base.txz] Error code 1 Stop in /usr/src/release. *** [release] Error code 1 Stop in /usr/src/release These are contents of /etc/src.conf file : WITHOUT_BLUETOOTH=YES WITHOUT_EXAMPLES=YES WITHOUT_FLOPPY=YES WITHOUT_GAMES=YES WITHOUT_MAN=YES WITHOUT_MAN_UTILS=YES WITHOUT_SHAREDOCS=YES WITHOUT_WIRELESS=YES WITHOUT_WIRELESS_SUPPORT=YES WITHOUT_AT=YES WITHOUT_CALENDAR=YES WITHOUT_INFO=YES WITHOUT_LOCALES=YES WITHOUT_ZFS=YES WITHOUT_BSD_CPIO=YES WITHOUT_CTM=YES WITHOUT_DICT=YES WITHOUT_GDB=YES WITHOUT_GNU=YES WITHOUT_GROFF=YES WITHOUT_HTML=YES WITHOU_INFO=YES WITHOUT_LPR=YES WITHOUT_MAIL=YES WITHOUT_PORTSNAP=YES WITHOUT_QUOTAS=YES WITHOUT_RCS=YES WITHOUT_SYSINSTALL=YES WITHOUT_BIND=YES WITHOUT_BIND_XML=YES WITHOUT_BIND_IDN=YES WITHOUT_BIND_SIGCHASE=YES WITHOUT_BIND_LARGE_FILE=YES WITHOUT_FREEBSD_UPDATE=YES WITHOUT_RESCUE=YES What's wrong with this? Thanks in advance ___ 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
make release doesn't correctly include EXTLOCALDIR ?
Hello list, I'm running 8.3-stable r245223 from a mere 2 days ago and am in the process of building a custom release for our internal use as preconfigured firewalls. make release works pretty fine except for a few quirks here and there. First of all, I have set EXTLOCALDIR so that the release contains my existing /usr/local/ , and thus the collection of installed ports. The problem here is that while /release/usr/local/ is correctly populated, the ISO images and ftp install directory have an empty usr/local/ Extracting the ISO's base.?? files doesn't yield the /usr/local/ contents either. The second problem I encounter is with the kernel's build. Apparently make release doesn't pull MODULES_OVERRIDE from /etc/make.conf and decides to build every single module, as opposed to my own restricted list. I'm going to try with with KERNEL_FLAGS=-DMODULES_OVERRIDE module1 module2 in /usr/src/release/Makefile Has anyone else ever experienced the same problem regarding the inclusion of /usr/local/ in their release ? ___ 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
make release and mfsroot
Hi All,
I generate a bootonly ISO and want to add files to the mfsroot.gz
created by the release.8 target. I want sysinstall to load an
install.cfg which makes a call to doconfig.sh. The target destination
for the files is stand/. My question is will the below patch
accomplish this for me provided install.cfg and doconfig.sh exist in
/usr/src/release?
# diff -u Makefile.orig Makefile
--- Makefile.orig 2012-12-11 18:15:29.0 +
+++ Makefile2012-12-11 19:01:46.0 +
@@ -509,6 +509,7 @@
rm foo; \
fi
-test -f install.cfg cp install.cfg ${CHROOTDIR}/usr/src/release
+ -test -f doconfig.sh cp doconfig.sh ${CHROOTDIR}/usr/src/release
echo #!/bin/sh ${_MK}
echo set -ex ${_MK}
echo trap 'umount /dev || true' 0 ${_MK}
@@ -823,7 +824,9 @@
done
.endif
-test -f ${.CURDIR}/install.cfg \
-cp ${.CURDIR}/install.cfg ${RD}/mfsfd
+cp ${.CURDIR}/install.cfg ${RD}/mfsfd/stand
+ -test -f ${.CURDIR}/doconfig.sh \
+cp ${.CURDIR}/doconfig.sh ${RD}/mfsfd/stand
@mkdir -p ${RD}/mfsfd/boot
.if ${TARGET_ARCH} != ia64 ${TARGET_ARCH} != powerpc
@cp ${RD}/trees/base/boot/boot* ${RD}/mfsfd/boot
--
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: make release and mfsroot
Hi Rick,
If you want, you could follow my approach which is to take the completed
mfsroot.gz and use a Makefile to manage the creation of custom mfsroots
(keeping the original unmodified, making it simpler to test different
iterations).
The advantage is that you don't have to re-perform the release(7) process each
time you want to make a change to your mfsroot.
Check it out:
http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/mfsroot/standard/
Basically, you'd grab the Makefile (link below):
http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/mfsroot/standard/Makefile?revision=1.1
Then create a dep directory and src directory:
Next, take the virgin mfsroot.gz produced by the release(7) process and dump it
into the dep directory.
Next, put your install.cfg into the src directory (just like you see that I
did).
Optionally populate more files into the src directory (see the first link
above for an example -- example includes boot/modules/nullfs.ko, etc/fstab,
and etc/group, etc.).
When the src directory represents what you'd like to add to the mfsroot,
you're ready to produce a new copy of the stored original (at
dep/mfsroot.gz), complete with your additions.
Execute:
make from_dep
NOTE: sudo is required
What will happen is that dep/mfsroot.gz will be copied to the current working
directory, the mfsroot is ripped open (requires sudo privileges), the src
directory is layered onto the mfsroot, and finally the mfsroot is packaged back
up (leaving you with a custom ./mfsroot.gz for deployment).
--
Cheers,
Devin
On Dec 11, 2012, at 11:02 AM, Rick Miller wrote:
Hi All,
I generate a bootonly ISO and want to add files to the mfsroot.gz
created by the release.8 target. I want sysinstall to load an
install.cfg which makes a call to doconfig.sh. The target destination
for the files is stand/. My question is will the below patch
accomplish this for me provided install.cfg and doconfig.sh exist in
/usr/src/release?
# diff -u Makefile.orig Makefile
--- Makefile.orig 2012-12-11 18:15:29.0 +
+++ Makefile 2012-12-11 19:01:46.0 +
@@ -509,6 +509,7 @@
rm foo; \
fi
-test -f install.cfg cp install.cfg ${CHROOTDIR}/usr/src/release
+ -test -f doconfig.sh cp doconfig.sh ${CHROOTDIR}/usr/src/release
echo #!/bin/sh ${_MK}
echo set -ex ${_MK}
echo trap 'umount /dev || true' 0 ${_MK}
@@ -823,7 +824,9 @@
done
.endif
-test -f ${.CURDIR}/install.cfg \
- cp ${.CURDIR}/install.cfg ${RD}/mfsfd
+ cp ${.CURDIR}/install.cfg ${RD}/mfsfd/stand
+ -test -f ${.CURDIR}/doconfig.sh \
+ cp ${.CURDIR}/doconfig.sh ${RD}/mfsfd/stand
@mkdir -p ${RD}/mfsfd/boot
.if ${TARGET_ARCH} != ia64 ${TARGET_ARCH} != powerpc
@cp ${RD}/trees/base/boot/boot* ${RD}/mfsfd/boot
--
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
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
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: make release and mfsroot
Hi Devin, On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske devin.te...@fisglobal.com wrote: Hi Rick, If you want, you could follow my approach which is to take the completed mfsroot.gz and use a Makefile to manage the creation of custom mfsroots (keeping the original unmodified, making it simpler to test different iterations). Very interesting approach. I like it and will test it. It looks as though I would need to add code to the Makefile if files copied in later are greater in size than the space available. Would you agree? The advantage is that you don't have to re-perform the release(7) process each time you want to make a change to your mfsroot. This is a very compelling advantage. -- 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: make release and mfsroot
On Dec 11, 2012, at 1:50 PM, Rick Miller wrote: Hi Devin, On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske devin.te...@fisglobal.com wrote: Hi Rick, If you want, you could follow my approach which is to take the completed mfsroot.gz and use a Makefile to manage the creation of custom mfsroots (keeping the original unmodified, making it simpler to test different iterations). Very interesting approach. I like it and will test it. It looks as though I would need to add code to the Makefile if files copied in later are greater in size than the space available. Would you agree? Oh… forgot to mention… The Makefile doesn't adjust the mfsroot's size. What I do to solve that problem is patch the release(7) process to make a bigger mfsroot (and thusly has room for more stuff) -- this allows me to keep the customizations of what goes in at a higher level (separate from release(7)) while not having to write a lot of code for resizing the mfsroot. NOTE: I've actually run into major problems with resizing an mfsroot -- trust me, it's safer to stick with bumping the sectors in the release(7) makefile. If you're working in the 8.x line, take a look at this patch for bumping the mfsroot size: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/freebsd/patches/world_patches/release%3A%3AMakefile.patch?revision=1.1view=markup Meanwhile, for the 9.x line: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/world_patches/release%3A%3AMakefile.sysinstall.patch?revision=1.1view=markup NOTE: For your purposes, you'll only need the first hunk (the second hunk is needed for other reasons -- reasons that are documented in the README one-level-up in the patches directory from the above links). The advantage is that you don't have to re-perform the release(7) process each time you want to make a change to your mfsroot. This is a very compelling advantage. Though, to resize the mfsroot, I still rely on release(7) and the above patches. I've personally never had a need to go beyond 6000 sectors, but I know the guys at Yahoo have gone much further. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: make release and mfsroot
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske devin.te...@fisglobal.com wrote: Though, to resize the mfsroot, I still rely on release(7) and the above patches. Here's another question, have you applied this approach to boot_crunch.conf? I simply replaced the default boot_crunch.conf with my own in the source tree. This is how I discovered MFSSIZE, because the resulting boot_crunch binary was larger than the available space. -- 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: make release and mfsroot
On Dec 11, 2012, at 2:13 PM, Rick Miller wrote: On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske devin.te...@fisglobal.com wrote: Though, to resize the mfsroot, I still rely on release(7) and the above patches. Here's another question, have you applied this approach to boot_crunch.conf? I simply replaced the default boot_crunch.conf with my own in the source tree. This is how I discovered MFSSIZE, because the resulting boot_crunch binary was larger than the available space. I've separated the various additions to mfsroot into two categories: 1. Additions that end up in the boot_crunch binary 2. All other additions I use the release(7) process to produce a custom mfsroot with finely tuned boot_crunch, then I use the previously-shared Makefile to put more files in (things that are separate from the boot_crunch). You can read more about my procedure here (complete recipe for customizing any part of the mfsroot, while spending as little time in the release(7) process as possible): http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/README?revision=1.2view=markup The above is for the 9.x line, for the 8.x line the instructions are *slightly* different: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/freebsd/patches/README?revision=1.1view=markup You can my customizations to boot_crunch: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/patches/local_patches/release%3A%3Ai386%3A%3Aboot_crunch.conf.patch?revision=1.2view=markup and again, slightly different for 8.x: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/freebsd/patches/local_patches/release%3A%3Ai386%3A%3Aboot_crunch.conf.patch?revision=1.1view=markup -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: make release custom kernel conf not found
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer ___ 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: make release custom kernel conf not found
Thanks Rob and Lowell, I will keep this information handy. It was helpful. On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote: On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the right way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer -- 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: make release custom kernel conf not found
Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer rfar...@predatorlabs.net wrote: On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer -- 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: make release custom kernel conf not found
Rick Miller vmil...@hostileadmin.com writes: Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? It works fine; sounds like you just don't understand what a chroot is. Once a process is chroot'd to /app/release/, its idea of /root/kernels is what non-chroot'd processes see as /app/release/kernels. It can't see *any* files that aren't under /app/release. I would tend to recommend adding to your build script a command that copies the kernel file into the chroot before starting the chroot, but I'm sure others have other preferred approaches. - Lowell ___ 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
make release custom kernel conf not found
Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. -- 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: make release custom kernel conf not found
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. Thanks. The kernel is built inside the chroot, so all paths are really /app/release/whatever. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer ___ 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: make release custom kernel conf not found
2012-01-29 18:03, Rick Miller skrev: Hi All, I am performing a `make release` to build a new release with a custom kernel. The `make release` fails with the following error: cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL Shouldn't that be KERNCONF=MYKERNEL DESTDIR=/R/stage/kernels KODIR=/MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I have the kernel config at /root/kernels/MYKERNEL and /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. The applicable environment variables are set in my .profile as follows: BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 CHROOTDIR=/app/release CVSROOT=/home/cvs EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS=GENERIC MYKERNEL MAKE_DVD=YES NODOC=YES NO_FLOPPIES=YES I am unsure how to get `make release` to realize the location of the kernel config. Also, I notice that in the command to make the kernel, DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the location where I want the release to be built) is /app/release. I am wondering if someone knows how I may resolve the issue so I can get the release built. I appreciate any advice and feedback. 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
make release always fails
It looks that I am compiling wrong TAG, somehow. I have RELENG_8 sup file: *default host=cvsup3.ua.FreeBSD.org *default base=/share/freebsd/cvsup *default prefix=/share/freebsd/RELENG_8 *default release=cvs tag=RELENG_8 *default delete use-rel-suffix src-all And CVS supfile: *default host=cvsup6.ua.freebsd.org *default base=/share/freebsd/cvsup *default prefix=/share/freebsd/ncvs *default release=cvs *default delete use-rel-suffix src-all ports-all doc-all cvsroot-all First csup both sup-files. Then make buildworld in /usr/src (which is symlink to /share/freebsd/RELENG_8/src). It always succeeds. Then: cd /usr/src/release make release RELEASETAG=RELENG_8 \ PORTSRELEASETAG=HEAD \ BUILDNAME=8.2-STABLE-$DATE \ CHROOTDIR=/share/freebsd/release \ CVSROOT=/share/freebsd/ncvs This is always fails. Each day with different errors. I want to build nightly snapshots (DVDs) of 8.2-STABLE, what am I doing wrong? ___ 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: How much disk space required for make release?
I want to thank everyone for their suggestions. I ended up creating a larger swap and /tmp and reran make release with much better results. It's not completely finished yet, but has certainly progressed much further than the other day. == Vincent (Rick) Miller Systems Engineer vmil...@verisign.com t: 703-948-4395 21345 Ridgetop Cir Dulles, VA 20166 VerisignInc.com On 8/16/11 5:50 PM, Edwin L. Culp W. edwinlc...@gmail.com wrote: On Tue, Aug 16, 2011 at 1:38 PM, Miller, Vincent (Rick) vmil...@verisign.com wrote: Hello all, I am attempting to 'make release' 8.2-RELEASE. After running for a few hours, it died citing lack of disk space. The filesystem has approximately 80GB available. How much disk space is required when making a release? == Vincent (Rick) Miller Systems Engineer vmil...@verisign.com t: 703-948-4395 21345 Ridgetop Cir Dulles, VA 20166 VerisignInc.com ___ 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 I am not running 8. Only 7, soon to be updated to 9, but I just finished building a release on Current amd64. I doubt that it will help much but . . . # du -s -m release 8693release A little less than 9G. I wouldn't want to have less that 10G free, if I were going to build regularly. Boy am I glad that disks are so much cheaper now. ed ___ 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
How much disk space required for make release?
Hello all, I am attempting to 'make release' 8.2-RELEASE. After running for a few hours, it died citing lack of disk space. The filesystem has approximately 80GB available. How much disk space is required when making a release? == Vincent (Rick) Miller Systems Engineer vmil...@verisign.com t: 703-948-4395 21345 Ridgetop Cir Dulles, VA 20166 VerisignInc.com ___ 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: How much disk space required for make release?
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Miller, Vincent (Rick) Sent: Tuesday, August 16, 2011 11:39 AM To: FreeBSD Subject: How much disk space required for make release? Hello all, I am attempting to 'make release' 8.2-RELEASE. After running for a few hours, it died citing lack of disk space. The filesystem has approximately 80GB available. How much disk space is required when making a release? According to my notes... You will need approximately 600MB of storage space available on the filesystem that `/usr/src' resides on. Meanwhile, you'll need an additional 3GB (approximately) of storage space available on the filesystem that `/usr/release' resides on. And further still, you'll need an additional 600MB of storage space for the `/usr/obj' directory. So if all three directories (`/usr/src', `/usr/obj', and `/usr/release') live on the same filesystem, you'll need approximately 4.2GB of free space to build a FreeBSD release (including the source). Please note however, that this estimate is low because I never compile a release with the default options. I usually use the following: make release CHROOTDIR=/usr/release EXTSRCDIR=/usr/src KERNELS_BASE= \ NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES The above options _significantly_ reduce the size of disk space required to build the release. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ 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: How much disk space required for make release?
Hi, Reference: From: Miller, Vincent (Rick) vmil...@verisign.com Date: Tue, 16 Aug 2011 18:38:31 + Message-id: ca703165.3b97%vmil...@verisign.com Miller, Vincent (Rick) wrote: Hello all, I am attempting to 'make release' 8.2-RELEASE. After running for a few hours, it died citing lack of disk space. The filesystem has approximately 80GB available. How much disk space is required when making a release? A gig or 2 I recall, (each of src/ obj/ I recall is ~ 600M then there's a chroot, so same again, but a few gig should be sufficient. 80G is more than enough, You must have some partiton that overflowed, maybe /tmp or /var. If you cant find what, just run eg touch ~//df.log #!/bin/csh while (1) df ~/df.log sleep 300 end then start release again, the log will show where its getting eaten However I seem to recall some env var that allows piorts/ to be called in too Now ports/distfiles alone is maybe 100 Gig or so ... so avoid ports/ Sorry to be imprecise, I havent rolled a release for months, though I used to do it very frequently. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with ; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: How much disk space required for make release?
On Tue, Aug 16, 2011 at 1:38 PM, Miller, Vincent (Rick) vmil...@verisign.com wrote: Hello all, I am attempting to 'make release' 8.2-RELEASE. After running for a few hours, it died citing lack of disk space. The filesystem has approximately 80GB available. How much disk space is required when making a release? == Vincent (Rick) Miller Systems Engineer vmil...@verisign.com t: 703-948-4395 21345 Ridgetop Cir Dulles, VA 20166 VerisignInc.com ___ 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 I am not running 8. Only 7, soon to be updated to 9, but I just finished building a release on Current amd64. I doubt that it will help much but . . . # du -s -m release 8693release A little less than 9G. I wouldn't want to have less that 10G free, if I were going to build regularly. Boy am I glad that disks are so much cheaper now. ed ___ 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
make release question
Where does make release place the disk images (iso's) by default ___ 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
Fwd: make release question
-- Forwarded message -- From: Aryeh Friedman aryeh.fried...@gmail.com Date: Thu, Jul 21, 2011 at 12:35 PM Subject: Re: make release question To: Nathan Whitehorn nwhiteh...@freebsd.org On Thu, Jul 21, 2011 at 12:33 PM, Aryeh Friedman aryeh.fried...@gmail.com wrote: found them in CHROOT/R and found I needed to do mkisofs on them to get the image oops forgot to ask should I use cdrom/dvd1 or ftp to make a bootable USB drive On Thu, Jul 21, 2011 at 12:31 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 07/21/11 10:42, Aryeh Friedman wrote: Where does make release place the disk images (iso's) by default ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org On -CURRENT, it places them in /usr/obj/usr/src/release. You can use make install DESTDIR=blah to put them somewhere else. On 8.x and earlier it places them in CHROOT/R. -Nathan ___ 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
'make release' on ZFS filesystem fails: chflags: operation not permitted
I followed the steps making a release on FreeBSD 8.0-RC2/AMD64 on my box, the target CHROOTDIR is located on a ZFS volume. I searched the list for a solution, but did not find any. sysctl kern.securelevel shows kern.securelevel: -1 Is there any solution? I guess those with complete ZFS infrastructure will not be able performing a make release, or do they? Thanks in advance, Oliver ___ 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: 'make release' on ZFS filesystem fails: chflags: operation not permitted
O. Hartmann wrote: I followed the steps making a release on FreeBSD 8.0-RC2/AMD64 on my box, the target CHROOTDIR is located on a ZFS volume. I searched the list for a solution, but did not find any. sysctl kern.securelevel shows kern.securelevel: -1 Is there any solution? I guess those with complete ZFS infrastructure will not be able performing a make release, or do they? Odd I though flags were now supported on the newer zfs versions. Try NO_SCHG=yes in /etc/make.conf as a workaround. Vince Thanks in advance, Oliver ___ 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: make release of current
On Wednesday 26 November 2008 22:54:35 Valentin Bud wrote: Hello Beech, Could you be more specific on what documentation to read. thank you and a great day, v On Thu, Nov 27, 2008 at 8:20 AM, Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech A good place to start is man (7) release. Beech -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release of current
Beech Rintoul wrote: On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech Thanks, I've made a release before.. a long while ago in a galaxy far away... I was just wondering if current would work the same. Also, is it possible to make an iso containing a multi release? ie: i386 and amd64? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release of current
On Thursday 27 November 2008 04:44:19 michael wrote: Beech Rintoul wrote: On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech Thanks, I've made a release before.. a long while ago in a galaxy far away... I was just wondering if current would work the same. Also, is it possible to make an iso containing a multi release? ie: i386 and amd64? Technically, but you'd have to burn it to a DVD and figure out how to choose which to boot from. There are people combining all three to a DVD, but I haven't built a release in awhile myself and have never tried making it into a DVD. Burning a -CURRENT release is no problem, just source it from your src tree. It's really no different than burning a regular release. There's no problem burning both iso's the problem will be the boot sector. Beech -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release of current
Beech Rintoul wrote: On Thursday 27 November 2008 04:44:19 michael wrote: Beech Rintoul wrote: On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech Thanks, I've made a release before.. a long while ago in a galaxy far away... I was just wondering if current would work the same. Also, is it possible to make an iso containing a multi release? ie: i386 and amd64? Technically, but you'd have to burn it to a DVD and figure out how to choose which to boot from. There are people combining all three to a DVD, but I haven't built a release in awhile myself and have never tried making it into a DVD. Burning a -CURRENT release is no problem, just source it from your src tree. It's really no different than burning a regular release. There's no problem burning both iso's the problem will be the boot sector. Beech What do you think about using a different loader on the iso, one that will allow selection of a specific architecture? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release of current
will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release of current
On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release of current
Hello Beech, Could you be more specific on what documentation to read. thank you and a great day, v On Thu, Nov 27, 2008 at 8:20 AM, Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 26 November 2008 20:40:21 michael wrote: will make release work for current? i've built a nice working system that i would like to be able to install on several identical machines. Yes, but read all the docs completely there are a number of options you need, like telling it to use your source tree instead of CVS and if you want to build packages etc. Beech ___ 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: make release, src.conf and WITHOUT_SENDMAIL on freebsd 7
On Sat, Aug 30, 2008 at 11:06 AM, Matias Surdi [EMAIL PROTECTED] wrote: The problem arises when I do a make release as, as far as I can see, /etc/src.conf is completly ignored. I think it's an issue with the chroot environment that make release uses. Wich is the correct way to let make release know about src.conf? you can play with release(7) LOCAL_PATCHES variable or copy /etc/src.conf to /usr/src/etc and add it to /usr/src/etc/Makefile. -- regards, Artis Caune . CCNA | ' didii FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release, src.conf and WITHOUT_SENDMAIL on freebsd 7
Hi, I've set up a src.conf so that when I do a make buildworld sendmail is not built. That works great. The problem arises when I do a make release as, as far as I can see, /etc/src.conf is completly ignored. I think it's an issue with the chroot environment that make release uses. Wich is the correct way to let make release know about src.conf? Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release and sysinstall
Sysinstall has a configuration file with wich you can specify several options, see man sysinstall(8) for more details. When making a release you set the sysinstalls configuration file with the LOCAL_PATCHES option to patch it to the chroot environment release build environment. We use it to create a automatic install for a host that we know exactly how the disks will be partitioned, what packages are installed what users etc. Here is an snippet of our patch file, (please note I have changed some of the names to protect the guilty :) ) --- /dev/null Sat Jan 26 17:11:01 2008 +++ release/install.cfg Sat Jan 26 17:17:46 2008 @@ -0,0 +1,31 @@ +debug=yes + +nonInteractive=yes +hostname=a.b.c +domainname=b.c + +mediaSetCDROM + +distSetMinimum + +disk=ar0 etc, etc Hope this helps. PS. You could also look at what nanobsd and I think pfsense does. I think they use a different approach. I have heard sysinstall should have been killed a long time ago but it still works well for us. Riaan On 8/13/08, Matias Surdi [EMAIL PROTECTED] wrote: Hi again, Suppose I build my own FreeBSD based distro, as described in release(7). How can I script sysinstall or replace it with another installer to customize the installation process? Thanks a lot. ___ 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: make release and sysinstall
Hi Riaan, Thanks a lot for your explanation, it's been very usefull to me, really. I've been looking about Freesbie, but it seems abandoned and on their mailing list there is no post since a couple of months. PfSense, which I use here, uses bsdInstaller but it's last new is from Aug 02 2005, so, it seems abandoned also. More of the same with the livecd port... the scripts are not up to date with current FreeBSD releases. I'll give a sigth to nanoBSD., but for the moment it seems that where I can get more support/documentation is with sysinstall and standard FreeBSD tools. Another question: Suppose I create my own install.cfg for sysinstall and then I do a make release.If my sysinstall contains a couple of freeBSD packages (bash, python, etc..) plus a custom package created by me.. How must I instruct make release to include just those packages in the final CDROM? Thanks a lot. Riaan Kruger escribió: Sysinstall has a configuration file with wich you can specify several options, see man sysinstall(8) for more details. When making a release you set the sysinstalls configuration file with the LOCAL_PATCHES option to patch it to the chroot environment release build environment. We use it to create a automatic install for a host that we know exactly how the disks will be partitioned, what packages are installed what users etc. Here is an snippet of our patch file, (please note I have changed some of the names to protect the guilty :) ) --- /dev/null Sat Jan 26 17:11:01 2008 +++ release/install.cfg Sat Jan 26 17:17:46 2008 @@ -0,0 +1,31 @@ +debug=yes + +nonInteractive=yes +hostname=a.b.c +domainname=b.c + +mediaSetCDROM + +distSetMinimum + +disk=ar0 etc, etc Hope this helps. PS. You could also look at what nanobsd and I think pfsense does. I think they use a different approach. I have heard sysinstall should have been killed a long time ago but it still works well for us. Riaan On 8/13/08, Matias Surdi [EMAIL PROTECTED] wrote: Hi again, Suppose I build my own FreeBSD based distro, as described in release(7). How can I script sysinstall or replace it with another installer to customize the installation process? Thanks a lot. ___ 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release and sysinstall
Hi, This should help: http://www.gsoft.com.au/~doconnor/FreeBSD-release.html http://www.gsoft.com.au/~doconnor/release/install.cfg I made my own release with ports on board without additional post-installing. This ports, are configured and ready to work out of box. Best regards, Sebastian Tymkow 2008/8/14 Matias Surdi [EMAIL PROTECTED] Hi Riaan, Thanks a lot for your explanation, it's been very usefull to me, really. I've been looking about Freesbie, but it seems abandoned and on their mailing list there is no post since a couple of months. PfSense, which I use here, uses bsdInstaller but it's last new is from Aug 02 2005, so, it seems abandoned also. More of the same with the livecd port... the scripts are not up to date with current FreeBSD releases. I'll give a sigth to nanoBSD., but for the moment it seems that where I can get more support/documentation is with sysinstall and standard FreeBSD tools. Another question: Suppose I create my own install.cfg for sysinstall and then I do a make release.If my sysinstall contains a couple of freeBSD packages (bash, python, etc..) plus a custom package created by me.. How must I instruct make release to include just those packages in the final CDROM? Thanks a lot. Riaan Kruger escribió: Sysinstall has a configuration file with wich you can specify several options, see man sysinstall(8) for more details. When making a release you set the sysinstalls configuration file with the LOCAL_PATCHES option to patch it to the chroot environment release build environment. We use it to create a automatic install for a host that we know exactly how the disks will be partitioned, what packages are installed what users etc. Here is an snippet of our patch file, (please note I have changed some of the names to protect the guilty :) ) --- /dev/null Sat Jan 26 17:11:01 2008 +++ release/install.cfg Sat Jan 26 17:17:46 2008 @@ -0,0 +1,31 @@ +debug=yes + +nonInteractive=yes +hostname=a.b.c +domainname=b.c + +mediaSetCDROM + +distSetMinimum + +disk=ar0 etc, etc Hope this helps. PS. You could also look at what nanobsd and I think pfsense does. I think they use a different approach. I have heard sysinstall should have been killed a long time ago but it still works well for us. Riaan On 8/13/08, Matias Surdi [EMAIL PROTECTED] wrote: Hi again, Suppose I build my own FreeBSD based distro, as described in release(7). How can I script sysinstall or replace it with another installer to customize the installation process? Thanks a lot. ___ 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] ___ 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: make release and sysinstall
Another question: Suppose I create my own install.cfg for sysinstall and then I do a make release.If my sysinstall contains a couple of freeBSD packages (bash, python, etc..) plus a custom package created by me.. How must I instruct make release to include just those packages in the final CDROM? I have not personally added packages to my distribution CDs but, check out the CD_PACKAGE_TREE option in release(7). It is supposed to be the direcory(s) that contains packages for cd1 and cd2. I am replying to the freebsd-questions mailing list, so that other people can see it too. Maybe they can also help or be helped. It looks like you did not reply to the mailing as well. Remember to reply to the mailing list as well next time :) Riaan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release and sysinstall
Hi again, Suppose I build my own FreeBSD based distro, as described in release(7). How can I script sysinstall or replace it with another installer to customize the installation process? Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Newbie make release question - Rolling a customized release
Hey all, I'm trying to eliminate a headache and I'm hoping you guys
can aim me in the right direction -
I'm trying to roll a custom FreeBSD release - nothing fancy, just a
stock 7-STABLE plus a few ports some stuff under /usr/local - and
I'm a bit confused as to the best way to go about building the release
distributions/CDs with my custom changes.
I *think* what I would like to do is customize the universe that gets
built under the chroot directory and roll a release from that, but I'm
not sure how I go about getting make release (or the mk script?) to
pick up my changes when it re-rolls the base tarball.
I thought this would be as simple as making my changes inside the
chroot, deleting {chroot}/usr/obj/usr/src/release/release.[2-8] and
running the mk script from inside the chroot, but my results were less
than spectacular (the mk script blew up :)
Any pointers would be much appreciated - I'd love to get away from my
12-year-old collection of builder shell scripts and not have to baby-
sit complies/package installations anymore. Collected pointers and
(hopefully) successful results to be turned into a howto for future
clueless dingbats like myself if such a thing doesn't already exist :)
Thanks,
-MG
(PS - I know I can do what I want by rolling a local package with my
changes, but I was hoping for a trained-monkey fire and forget kind of
installation :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
About make release
Hi, All. release can be build by calling commands: make release.1 ... ... make release.7 ... etc. Why need to chroot and build world again ?, may be I do not understand all cobweb of release making process... May be exist any target-name that starts release build stages without chroot? -- With all regards, Victor M. Blood. mailto: [EMAIL PROTECTED] FTN: 2:5024/[EMAIL PROTECTED], ICQ#3567656 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Make Release Customization
What is the best way to add new files into the CHROOT environment when doing a make release? I am trying to create my own distribution using the make release, from release(7), mechanism. The problem is, is that I wish to add files to the CHROOT environment. These files are my own config files that I wish to process with the *LOCAL**_**SCRIPT* script. I know there is a *LOCAL**_**PATCHES *option with which to patch in stuff into the CHROOT environment. However, I wish to avoid the patching mechanism, because of many reasons (which I will explain if you want me to :) ) Riaan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release error for customed x86 platform
[ cc line trimmed a bit... ] On Sun, 2007-08-12 at 08:55 +0800, Put PostgreSQL to Work for Your Business. wrote: Dear all I am building a custom FreeBSD for internal use for the various platforms we used (x86 platform). I am encountering a issue write failed, filesystem is full when creating the boot.floppy on touch release.5, can someone take a look to see what's the reason? following is the screen dump, sorry for any interruptions, thanks in advance. Tony [ Snip ] + mount /dev/md0c /mnt + [ -d /R/stage/image.boot ] + set -e + cd /R/stage/image.boot + find+ cpio . -dump -print /mnt /mnt: write failed, filesystem is full cpio: write error: No space left on device + umount /mnt + mdconfig -d -u md0 *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. I just built the August Monthly Snapshots for amd64 and i386 with no boot floppy issues so I'm guessing whatever it is you're customizing is having some sort of an impact on the boot floppy. Do you actually use the floppies at all? If not I'd suggest you just add NO_FLOPPIES= to the command line when you do the release build so it doesn't even bother trying to create the floppies. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
make release error for customed x86 platform
Dear all I am building a custom FreeBSD for internal use for the various platforms we used (x86 platform). I am encountering a issue write failed, filesystem is full when creating the boot.floppy on touch release.5, can someone take a look to see what's the reason? following is the screen dump, thanks in advance Tony touch release.5 rm -rf /R/stage/dists mkdir -p /R/stage/dists rolling base/base tarball base distribution is finished. rolling catpages/catpages tarball catpages distribution is finished. rolling manpages/manpages tarball manpages distribution is finished. rolling games/games tarball games distribution is finished. rolling proflibs/proflibs tarball proflibs distribution is finished. rolling dict/dict tarball dict distribution is finished. rolling info/info tarball info distribution is finished. rolling doc/doc tarball doc distribution is finished. rolling kernels/generic tarball GENERIC distribution is finished. rolling kernels/smp tarball SMP distribution is finished. # XXX: Inline stripped version of doTARBALL rolling ports/ports tarball ports distribution is finished. touch release.6 rolling src/sbase tarball rolling src/sbin tarball rolling src/scontrib tarball rolling src/scrypto tarball rolling src/setc tarball rolling src/sgames tarball rolling src/sgnu tarball rolling src/sinclude tarball rolling src/skrb5 tarball rolling src/slib tarball rolling src/slibexec tarball rolling src/srelease tarball rolling src/srescue tarball rolling src/ssbin tarball rolling src/ssecure tarball rolling src/sshare tarball rolling src/ssys tarball rolling src/stools tarball rolling src/subin tarball rolling src/susbin tarball (cd /R/stage/dists/src; rm -f CHECKSUM.MD5 CHECKSUM.SHA256; md5 * .CHECKSUM.MD5; sha256 * .CHECKSUM.SHA256; mv .CHECKSUM.MD5 CHECKSUM.MD5; mv .CHECKSUM.SHA256 CHECKSUM.SHA256) src distribution is finished. touch release.7 cp /R/stage/trees/base/etc/disktab /etc rm -rf /R/stage/mfsfd mkdir /R/stage/mfsfd cd /R/stage/mfsfd mkdir -p etc/defaults dev mnt stand/etc/defaults stand/help var/empty ( cd /R/stage/mfsfd for dir in bin sbin ; do ln -sf /stand $dir; done ) cp /R/stage/trees/base/sbin/dhclient-script /R/stage/mfsfd/stand cp /usr/src/release/../etc/usbd.conf /R/stage/mfsfd/etc/usbd.conf cp /usr/src/release/../etc/master.passwd /R/stage/mfsfd/etc/master.passwd cp /R/stage/trees/base/etc/*pwd.db /R/stage/mfsfd/etc/ ( for F in defaults/rc.conf netconfig protocols ; do sed -e '/^#.*$/d' -e 's/[:space:]*#.*$//g' /R/stage/trees/base/etc/$F /R/stage/mfsfd/stand/etc/$F ; done ) grep -E '^(ftp|nameserver|domain|sunrpc|cmd|nfsd)[^-\w]' /R/stage/trees/base/etc/services | sed -e '/^#.*$/d' -e 's/[:space:]*#.*$//g' /R/stage/mfsfd/stand/etc/services grep 'operator' /R/stage/trees/base/etc/group /R/stage/mfsfd/stand/etc/group ln /R/stage/mfsfd/stand/etc/services /R/stage/mfsfd/etc/services ln /R/stage/mfsfd/stand/etc/group /R/stage/mfsfd/etc/group ln /R/stage/mfsfd/stand/etc/netconfig /R/stage/mfsfd/etc/netconfig cp /R/stage/trees/base/COPYRIGHT /R/stage/mfsfd/stand/help/COPYRIGHT.hlp test -f /usr/src/release/install.cfg cp /usr/src/release/install.cfg /R/stage/mfsfd *** Error code 1 (ignored) sh -e /usr/src/release/scripts/doFS.sh bsdlabel /R/stage/mfsroot/mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 + export BLOCKSIZE=512 + DISKLABEL=bsdlabel + shift + MACHINE= + shift + FSIMG=/R/stage/mfsroot/mfsroot + shift + RD=/R/stage + shift + MNT=/mnt + shift + FSSIZE=4320 + shift + FSPROTO=/R/stage/mfsfd + shift + FSINODE=8000 + shift + FSLABEL=minimum3 + shift + [ 4320 -eq 0 -a minimum3 = auto ] + rm -f /R/stage/mfsroot/mfsroot + dd of=/R/stage/mfsroot/mfsroot if=/dev/zero count=4320 bs=1k + uname -r + [ -f /R/stage/trees/base/boot/boot ] + BOOT=-B -b /R/stage/trees/base/boot/boot + dofs_md + [ x != x ] + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot + MDDEVICE=md0 + [ ! -c /dev/md0 ] + trap umount /mnt; mdconfig -d -u md0 EXIT + [ xbsdlabel != x ] + bsdlabel -w -B -b /R/stage/trees/base/boot/boot md0 minimum3 + newfs -O1 -i 8000 -o space -m 0 /dev/md0c fstab: /etc/fstab:0: No such file or directory /dev/md0c: 4.2MB (8640 sectors) block size 4096, fragment size 512 using 4 cylinder groups of 1.06MB, 271 blks, 160 inodes. super-block backups (for fsck -b #) at: 32, 2200, 4368, 6536 + mount /dev/md0c /mnt + [ -d /R/stage/mfsfd ] + set -e + cd /R/stage/mfsfd + find+ cpio . -dump -print /mnt 4764 blocks + df -ki /mnt Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md0c 4175 2411 176458% 54 5848% /mnt + df+ tail -ki -1 /mnt + set /dev/md0c 4175 2411 1764 58% 54 584 8% /mnt + echo *** File system is 4320 K, 1764 left *** File system is 4320 K, 1764 left + echo *** 8000 bytes/inode, 584 left *** 8000 bytes/inode, 584 left + umount /mnt + mdconfig -d -u md0 /R/stage/mfsroot/mfsroot:
make release error for customed x86 platform
Dear all I am building a custom FreeBSD for internal use for the various platforms we used (x86 platform). I am encountering a issue write failed, filesystem is full when creating the boot.floppy on touch release.5, can someone take a look to see what's the reason? following is the screen dump, sorry for any interruptions, thanks in advance. Tony touch release.5 rm -rf /R/stage/dists mkdir -p /R/stage/dists rolling base/base tarball base distribution is finished. rolling catpages/catpages tarball catpages distribution is finished. rolling manpages/manpages tarball manpages distribution is finished. rolling games/games tarball games distribution is finished. rolling proflibs/proflibs tarball proflibs distribution is finished. rolling dict/dict tarball dict distribution is finished. rolling info/info tarball info distribution is finished. rolling doc/doc tarball doc distribution is finished. rolling kernels/generic tarball GENERIC distribution is finished. rolling kernels/smp tarball SMP distribution is finished. # XXX: Inline stripped version of doTARBALL rolling ports/ports tarball ports distribution is finished. touch release.6 rolling src/sbase tarball rolling src/sbin tarball rolling src/scontrib tarball rolling src/scrypto tarball rolling src/setc tarball rolling src/sgames tarball rolling src/sgnu tarball rolling src/sinclude tarball rolling src/skrb5 tarball rolling src/slib tarball rolling src/slibexec tarball rolling src/srelease tarball rolling src/srescue tarball rolling src/ssbin tarball rolling src/ssecure tarball rolling src/sshare tarball rolling src/ssys tarball rolling src/stools tarball rolling src/subin tarball rolling src/susbin tarball (cd /R/stage/dists/src; rm -f CHECKSUM.MD5 CHECKSUM.SHA256; md5 * .CHECKSUM.MD5; sha256 * .CHECKSUM.SHA256; mv .CHECKSUM.MD5 CHECKSUM.MD5; mv .CHECKSUM.SHA256 CHECKSUM.SHA256) src distribution is finished. touch release.7 cp /R/stage/trees/base/etc/disktab /etc rm -rf /R/stage/mfsfd mkdir /R/stage/mfsfd cd /R/stage/mfsfd mkdir -p etc/defaults dev mnt stand/etc/defaults stand/help var/empty ( cd /R/stage/mfsfd for dir in bin sbin ; do ln -sf /stand $dir; done ) cp /R/stage/trees/base/sbin/dhclient-script /R/stage/mfsfd/stand cp /usr/src/release/../etc/usbd.conf /R/stage/mfsfd/etc/usbd.conf cp /usr/src/release/../etc/master.passwd /R/stage/mfsfd/etc/master.passwd cp /R/stage/trees/base/etc/*pwd.db /R/stage/mfsfd/etc/ ( for F in defaults/rc.conf netconfig protocols ; do sed -e '/^#.*$/d' -e 's/[:space:]*#.*$//g' /R/stage/trees/base/etc/$F /R/stage/mfsfd/stand/etc/$F ; done ) grep -E '^(ftp|nameserver|domain|sunrpc|cmd|nfsd)[^-\w]' /R/stage/trees/base/etc/services | sed -e '/^#.*$/d' -e 's/[:space:]*#.*$//g' /R/stage/mfsfd/stand/etc/services grep 'operator' /R/stage/trees/base/etc/group /R/stage/mfsfd/stand/etc/group ln /R/stage/mfsfd/stand/etc/services /R/stage/mfsfd/etc/services ln /R/stage/mfsfd/stand/etc/group /R/stage/mfsfd/etc/group ln /R/stage/mfsfd/stand/etc/netconfig /R/stage/mfsfd/etc/netconfig cp /R/stage/trees/base/COPYRIGHT /R/stage/mfsfd/stand/help/COPYRIGHT.hlp test -f /usr/src/release/install.cfg cp /usr/src/release/install.cfg /R/stage/mfsfd *** Error code 1 (ignored) sh -e /usr/src/release/scripts/doFS.sh bsdlabel /R/stage/mfsroot/mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 + export BLOCKSIZE=512 + DISKLABEL=bsdlabel + shift + MACHINE= + shift + FSIMG=/R/stage/mfsroot/mfsroot + shift + RD=/R/stage + shift + MNT=/mnt + shift + FSSIZE=4320 + shift + FSPROTO=/R/stage/mfsfd + shift + FSINODE=8000 + shift + FSLABEL=minimum3 + shift + [ 4320 -eq 0 -a minimum3 = auto ] + rm -f /R/stage/mfsroot/mfsroot + dd of=/R/stage/mfsroot/mfsroot if=/dev/zero count=4320 bs=1k + uname -r + [ -f /R/stage/trees/base/boot/boot ] + BOOT=-B -b /R/stage/trees/base/boot/boot + dofs_md + [ x != x ] + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot + MDDEVICE=md0 + [ ! -c /dev/md0 ] + trap umount /mnt; mdconfig -d -u md0 EXIT + [ xbsdlabel != x ] + bsdlabel -w -B -b /R/stage/trees/base/boot/boot md0 minimum3 + newfs -O1 -i 8000 -o space -m 0 /dev/md0c fstab: /etc/fstab:0: No such file or directory /dev/md0c: 4.2MB (8640 sectors) block size 4096, fragment size 512 using 4 cylinder groups of 1.06MB, 271 blks, 160 inodes. super-block backups (for fsck -b #) at: 32, 2200, 4368, 6536 + mount /dev/md0c /mnt + [ -d /R/stage/mfsfd ] + set -e + cd /R/stage/mfsfd + find+ cpio . -dump -print /mnt 4764 blocks + df -ki /mnt Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md0c 4175 2411 176458% 54 5848% /mnt + df+ tail -ki -1 /mnt + set /dev/md0c 4175 2411 1764 58% 54 584 8% /mnt + echo *** File system is 4320 K, 1764 left *** File system is 4320 K, 1764 left + echo *** 8000 bytes/inode, 584 left *** 8000 bytes/inode, 584 left + umount /mnt + mdconfig -d -u md0
6.2 make release
I am trying to make a custom release. My goal is to make a custom bsd cd that will install the system to my specification without asking the user any question. My problem is the follwoing: I tried to compile the release without any modifications just to see if it works. I checkout the cvs tree with cvsup and the cvs-supfile in the examples directory. I used the following commands: cd /usr/src make buildworld cd /usr/src/release make release CHROOTDIR=/usr/exile BUILDNAME=EXILE SECURITY \ CVSROOT=/home/ncvs I get the following error error missing kernel configuration file(s) (SMP) ___ 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: make release error
Maxim Vetrov [EMAIL PROTECTED] writes: I'm running 5.4 and trying to make release of 6.0. You do realize the documentation says that's not supported, right? You're kind of on your own there. While making release, I got next error: ... cvs checkout: Updating doc/zh_TW.Big5/share cvs checkout: Updating doc/zh_TW.Big5/share/sgml if [ -d /usr/src/release/../../ports/distfiles/ ]; then cp -rp /usr/src/release/../../ports/distfiles /data/RELEASE_60/bin/usr/ports/distfiles; else mkdir -p /data/RELEASE_60/bin/usr/ports/distfiles; fi make: don't know how to make checksum-recursive. Stop *** Error code 2 Stop in /usr/src/release. *** Error code 1 ... What might cause it? Seems like a mismatch between the 5.4 and 6.0 makefiles. If you try pointing off to the new makefiles, you might be able to get past this particular issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release error
Hi, I'm running 5.4 and trying to make release of 6.0. While making release, I got next error: ... cvs checkout: Updating doc/zh_TW.Big5/share cvs checkout: Updating doc/zh_TW.Big5/share/sgml if [ -d /usr/src/release/../../ports/distfiles/ ]; then cp -rp /usr/src/release/../../ports/distfiles /data/RELEASE_60/bin/usr/ports/distfiles; else mkdir -p /data/RELEASE_60/bin/usr/ports/distfiles; fi make: don't know how to make checksum-recursive. Stop *** Error code 2 Stop in /usr/src/release. *** Error code 1 ... What might cause it? Maxim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release cvsroot directory
Hello all When creating a release using make release is it possible to specify the CVSROOT using pserver or ext? Or will I have to use NFS to mount my CVSROOT directory? -- Antoine W. Solomon Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release
pirat sriyotha [EMAIL PROTECTED] writes: hi sirs, am trying to make my own release by `make release -DNOGAME' at /usr/src/release with 5.4 notebook. i want to have packages that have been built included into disc1.iso too but i get only 198mb of src and ports and some others instead. would you please give me some hints on doing this ? please cc to me since i do not subscripe to the list. thanks in advance for any helps and hints. Have you tried reading any of the documentation? http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-build.html /usr/ports/Tools/scripts/release/README ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release
hi sirs, am trying to make my own release by `make release -DNOGAME' at /usr/src/release with 5.4 notebook. i want to have packages that have been built included into disc1.iso too but i get only 198mb of src and ports and some others instead. would you please give me some hints on doing this ? please cc to me since i do not subscripe to the list. thanks in advance for any helps and hints. -- with best regards, psr http://www.thai-aec.org This message was sent using Inet-Webmail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release problem
I just did a release snapshot and everything worked except the last steps creating the CD iso files. they simply don't exist. All of the supporting files are in place and I can do a mkisofs and create a bootable working disk. Can someone shed some light on how to get the script working? Here is the last part of make release: Setting up FTP distribution area 0 blocks 0 blocks touch ftp.1 Building CDROM live filesystem image 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks Setting up CDROM boot area touch cdrom.1 Building CDROM disc1 filesystem image 0 blocks 0 blocks Building CDROM disc2 filesystem image touch cdrom.2 Building bootonly CDROM filesystem image touch cdrom.3 Release done TIA Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ --- pgpOWpOiyK4fL.pgp Description: PGP signature
Re: make release problem
Beecher Rintoul wrote: I just did a release snapshot and everything worked except the last steps creating the CD iso files. they simply don't exist. All of the supporting files are in place and I can do a mkisofs and create a bootable working disk. Can someone shed some light on how to get the script working? Here is the last part of make release: Setting up FTP distribution area 0 blocks 0 blocks touch ftp.1 Building CDROM live filesystem image 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks Setting up CDROM boot area touch cdrom.1 Building CDROM disc1 filesystem image 0 blocks 0 blocks Building CDROM disc2 filesystem image touch cdrom.2 Building bootonly CDROM filesystem image touch cdrom.3 Release done TIA Beech Did You set MAKE_ISOS like make MAKE_ISOS=YES release? Cheers, Gabor Kovesdan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mdconfig problem on make release of 5_4_0_RELEASE
i'm attempting to make a release and the build of the mfs image is failing (see below). it's mdconfig that's failing: + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device if fact i chroot'ed into the release directory and played around with mdconfig. i cannot get it to function properly. it always responds with 'mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device' i cannot get google to find anything related to this problem. what gives? i'm dumb-founded. please help me! sh -e /usr/src/release/scripts/doFS.sh bsdlabel /R/stage/mfsroot/mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 + export BLOCKSIZE=512 + DISKLABEL=bsdlabel + shift + MACHINE= + shift + FSIMG=/R/stage/mfsroot/mfsroot + shift + RD=/R/stage + shift + MNT=/mnt + shift + FSSIZE=4320 + shift + FSPROTO=/R/stage/mfsfd + shift + FSINODE=8000 + shift + FSLABEL=minimum3 + shift + [ 4320 -eq 0 -a minimum3 = auto ] + rm -f /R/stage/mfsroot/mfsroot + dd of=/R/stage/mfsroot/mfsroot if=/dev/zero count=4320 bs=1k + uname -r + [ -f /R/stage/trees/base/boot/boot ] + BOOT=-B -b /R/stage/trees/base/boot/boot + dofs_md + [ x != x ] + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device + MDDEVICE= *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/w/FreeBSD_20050519/usr/src/release. # uname -a FreeBSD bsdmaster.hcs.tl 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 mdconfig fails in chroot'ed environment: -- Any opinions as lame as the ones expressed above could only belong to me, and are not those of Texas Life Insurance Company. The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering. -- Doctor Who, Face of Evil Those who do not understand Unix are condemned to reinvent it, poorly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdconfig problem on make release of 5_4_0_RELEASE
On Fri, May 20, 2005 at 06:49:44AM -0500, William Richter wrote: i'm attempting to make a release and the build of the mfs image is failing (see below). it's mdconfig that's failing: + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device Do you have md support in your kernel? Kris pgpyMP9M4mgn2.pgp Description: PGP signature
Re: mdconfig problem on make release of 5_4_0_RELEASE
well, it's the kernel that's on disc1 of the 5.4 release iso's. mdconfig works. it just doesn't work when chroot'ed into the build directory. i've just discovered that the /sbin/mdconfig that comes with the distribution works when copied into the release tree (i also had to copy libc.so.5 in the release directory's /lib). but then i was able to complete building the release. i've been building my own releases since 5.2 and never had this issue. On Fri, 20 May 2005 09:49:22 -0700 Kris Kennaway [EMAIL PROTECTED] wrote: On Fri, May 20, 2005 at 06:49:44AM -0500, William Richter wrote: i'm attempting to make a release and the build of the mfs image is failing (see below). it's mdconfig that's failing: + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device Do you have md support in your kernel? Kris -- Any opinions as lame as the ones expressed above could only belong to me, and are not those of Texas Life Insurance Company. The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering. -- Doctor Who, Face of Evil Those who do not understand Unix are condemned to reinvent it, poorly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release
Hello there, I'm about to build a whole FreeBSD system with optimized code for my own purposes. I've read this document: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-build.html According this I should make a CVS mirror and follow the steps that the documention mentions. It would be awful to make a whole CVS mirror, since I would like to build only a 5-STABLE distribution. There is an example, that is highly determined by this approach with cvs mirroring, thus it isn't entirely useful for me, because I'd like to avoid mucking with cvs. If somebody knows how to make full release isos from a simple cvsupped source tree, please let me know. Cheers, Gábor Kövesdán ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems With 'make release'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I cannot get make release to run. I am trying to do RELENG_4 release off of up to date stable sources. After a couple hours of running, I get: cc -O -pipe -mpreferred-stack-boundary=2 -I/usr/src/sys/boot/ficl -I/usr/src/sys/boot/ficl/i386 - -I/usr/src/sys/boot/ficl/../common -DFICL_TRACE -c softcore.c -o softcore.o building static ficl library ranlib libficl.a === sys/boot/i386 === sys/boot/i386/mbr as -o mbr.o /usr/src/sys/boot/i386/mbr/mbr.s ld -N -e start -Ttext 0x600 -o mbr.out mbr.o objcopy -S -O binary mbr.out mbr === sys/boot/i386/boot0 make: don't know how to make boot0.s. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Ideas Anyone? - -- - Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFB2LMFyjgA+Mact+YRAqLTAJ4tnpA1IFrhS1KaTHmp+8DrM8S4lACgzrKJ jAnzbytoFzNbx76v3IQJAJk= =wyJB -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make release question
Hi, I have a FreeBSD 5.2.1-RELEASE-p9 machine. I want to create a release from that system to install FreeBSD on other machines. I have been reading the handbook about how to make a release and I have a question. As far as I understood, the way to create a relese could be: # cd /usr/src # make buildworld # cd release # make release CHROOTDIR=/local3/release BUILDNAME=5.2.1-RELEASE-p9 \ CVSROOT=/usr MAKE_ISOS=YES RELEASETAG=RELENG_5.2 Is that correct? I have doubts about the CVSROOT variable. As far as I understood, that variable points to the cvsrepository where you have the sources you want to use to create the release. In my case in /usr I have the 5.2.1-RELEASE-p9 sources. Well, launching the above commands I get the following error: -- Installing everything.. -- cd /usr/src; make -f Makefile.inc1 install === share/info install -o root -g wheel -m 444 dir-tmpl /local3/release/usr/share/info/dir === include creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. Touch is in /usr/bin which in the root path. Can some want help me with this? Thank you. -David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help w/ make release on 4.9-RELEASE
I'd like to make a custom live CD-2 of a -STABLE release (I want to include the asr-tools on it, so that I can tweak my raid which is normally running 5.2.1) I've been doing this from /usr/src/release sudo make release CHROOTDIR=/opus/release CVSROOT=/home/ncvs BUILDNAME=GH NODOC= It runs for a while and finally dies. The last few things it says are: touch release.1 cd /usr/src/release/../etc make distrib-dirs DESTDIR=/R/stage/trees/base mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p /R/stage/trees/base/ mtree: /R/stage/trees/base/: No such file or directory *** Error code 1 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. I've added the following symlink (thinking it was a missing factoid): (ghost)[1:32pm]releasels -l /R lrwxr-xr-x 1 root wheel 15 Aug 4 07:31 /R - /opus/release/R but still get the same result. Is this supposed to work? Am I missing something obvious? g. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Make release for sparc64 target on i386 system
I seem to be running into brick walls making a 5.2.1-RELEASE-P8 for sparc64 arch on an i386 system. I have tried the following using the latest sources from cvsup: 1)simple make buildworld to populate /usr/obj - make -DMAKE_ISOS -DNOPORTREADMES release \ BUILDNAME=5.2.1-RELEASE-P8-Sparc64 \ CHROOTDIR=/var/release2 \ CVSROOT=/var/ncvs \ RELEASETAG=RELENG_5_2 \ TARGET_ARCH=sparc64 - this works until the time to create the isos at which point the whole thing bails with: sh -e /usr/src/release/scripts/doFS.sh sunlabel /R/stage/mfsroot/mfsroot /R/stage /mnt 4096 /R/stage/mfsfd 8192 auto + export BLOCKSIZE=512 + DISKLABEL=sunlabel + shift + MACHINE= + shift + FSIMG=/R/stage/mfsroot/mfsroot + shift + RD=/R/stage + shift + MNT=/mnt + shift + FSSIZE=4096 + shift + FSPROTO=/R/stage/mfsfd + shift + FSINODE=8192 + shift + FSLABEL=auto + shift + [ 4096 -eq 0 -a auto = auto ] + deadlock=20 + uname -r + [ -f /R/stage/trees/base/boot/boot ] + BOOT=-r + dofs_md + true + rm -f /R/stage/mfsroot/mfsroot + [ x != x ] + dd of=/R/stage/mfsroot/mfsroot if=/dev/zero count=4096 bs=1k + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot + MDDEVICE=md0 + [ ! -c /dev/md0 ] + trap umount /mnt; mdconfig -d -u md0 EXIT + sunlabel -w -r md0 auto Obsolete -r flag ignored + newfs -O1 -i 8192 -o space -m 0 /dev/md0c fstab: /etc/fstab:0: No such file or directory newfs: /dev/md0c: could not find special device + umount /mnt umount: /mnt: not a file system root directory *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. 2) figuring this was because of the wrong world being used to create the release I did: make -j8 buildworld TARGET=sparc64 this created the /usr/obj/sparc64 structure then: - make TARGET_ARCH=sparc64 MAKEOBJDIRPREFIX=/usr/obj/sparc64 \ -DMAKE_ISOS -DNOPORTREADMES release \ BUILDNAME=5.2.1-RELEASE-P8-Sparc64 \ CHROOTDIR=/var/release2 \ CVSROOT=/var/ncvs \ RELEASETAG=RELENG_5_2 resulted in: . . .=== sys === sys/boot === sys/boot/ficl === sys/boot/i386 === sys/boot/i386/mbr install -o root -g wheel -m 444 mbr /var/release2/boot install: mbr: No such file or directory *** Error code 71 Stop in /usr/src/sys/boot/i386/mbr. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. So the question is (two-fold): is it possible to make a sparc64 release with isos on an i386 system and if so, how exactly? Thanks, Sven ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Make release for sparc64 target on i386 system
On Fri, Jun 04, 2004 at 09:41:46AM -0400, Sven Willenberger wrote: I seem to be running into brick walls making a 5.2.1-RELEASE-P8 for sparc64 arch on an i386 system. I have tried the following using the latest sources from cvsup: I don't think you can cross-target releases. For example, the filesystems have a different endianness on sparc64 and i386. Kris pgp985ziMBG7r.pgp Description: PGP signature
Make release problem
Hi All. Please help if know. When i try build my own release i see the problem with floppy image building. Problem looks like this: --- /dev/md0c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 1 cylinder groups of 1.41MB, 360 blks, 32 inodes. super-block backups (for fsck -b #) at: 32 + mount /dev/md0c /mnt + [ -d /R/stage/mfsroot/mfsroot.gz ] + cp -p /R/stage/mfsroot/mfsroot.gz /mnt /mnt: write failed, filesystem is full cp: /mnt/mfsroot.gz: No space left on device + umount /mnt + mdconfig -d -u md0 *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. --- I have found letter from John Baldwin http://docs.freebsd.org/cgi/getmsg.cgi?fetch=605146+0+archive/2004/freebsd-current/20040201.freebsd-current but this is not help, because i try build 4_STABLE based system, and latest /usr/src/release/makefile for this branch dated 2003/11/02 (via cvsup) (John add his fix in January 2004). If somebody has correct Makefile, patch, which works correctly under FreeBSD 4 - please let me know. Any ideas - are welcome. Best regards, Oleg Denisov. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Customizing a 'make release'...
On Thu, Feb 26, 2004 at 09:43:38PM -0800, Peter Losher wrote: (If this question is better served on another list, let me know) I am trying to come up with a custom FreeBSD ISO w/ my personal preferences (no integrated OpenSSH, Heimdal, or Sendmail) I have been working off of http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html, and /usr/bin/time sh -c 'make release CHROOTDIR=/hog0/release NODOC=YES NOPORTS=YES BUILDNAME=5.2-REL-FOO CVSROOT=/hog1/FreeBSD-CVS RELEASETAG=RELENG_5_2_1_RELEASE' | tee /tmp/release.log Now my understanding is that 'make release' honors the variables set in /etc/make.conf, where I have: -=- NO_OPENSSH=true NO_KERBEROS=true NO_SENDMAIL=true -=- After creating the binaries and the ISO image, installing the OS on a new box results in a sendmail-less install, but it still has all the OpenSSH and Heimdal bits included. Do I needed to declare NO_OPENSSH and NO_KERBEROS on the 'make release' command line? It shoudn't be requered. Your guess is a good as mine as to way it still build openssh. Also, is there any way to change the default bits the install process - like the default auto-partition (I prefer to leave the /var partition with the remaining space instead of /usr as it is now), and have it automatically install certain packages instead of asking. Thanks in advance for any advice you can pass along... Yes there is. See man sysinstall for more information on this. -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Customizing a 'make release'...
(If this question is better served on another list, let me know) I am trying to come up with a custom FreeBSD ISO w/ my personal preferences (no integrated OpenSSH, Heimdal, or Sendmail) I have been working off of http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html, and /usr/bin/time sh -c 'make release CHROOTDIR=/hog0/release NODOC=YES NOPORTS=YES BUILDNAME=5.2-REL-FOO CVSROOT=/hog1/FreeBSD-CVS RELEASETAG=RELENG_5_2_1_RELEASE' | tee /tmp/release.log Now my understanding is that 'make release' honors the variables set in /etc/make.conf, where I have: -=- NO_OPENSSH=true NO_KERBEROS=true NO_SENDMAIL=true -=- After creating the binaries and the ISO image, installing the OS on a new box results in a sendmail-less install, but it still has all the OpenSSH and Heimdal bits included. Do I needed to declare NO_OPENSSH and NO_KERBEROS on the 'make release' command line? Also, is there any way to change the default bits the install process - like the default auto-partition (I prefer to leave the /var partition with the remaining space instead of /usr as it is now), and have it automatically install certain packages instead of asking. Thanks in advance for any advice you can pass along... Best Wishes - Peter -- [ http://www.plosh.net/ ] - Earth Halted: Please reboot to continue ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'make release' questions.
Hello - I am planning to cut my own internal 5.2-RELEASE cut w/ all the Heimdal OpenSSH bits removed, and I have come across some questions on how to build such a release (.ISO in this case) I have been following: http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html And I was under the impression that it would honor /etc/make.conf, where I have: -=- NO_OPENSSH=true NO_KERBEROS=true -=- (where in the usual make buildworld sense, it would not build/install Heimdal/SSH bits. But the resulting build and ISO still installs Heimdal OpenSSH. Am I missing something here? (do I need to specify it in the 'make release', etc.) Best Wishes - Peter -- [ http://www.plosh.net/ ] - Earth Halted : Please Reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Make Release with CVSROOT pointing at a CVSup mirror
Hello, everyone. I'm attempting to roll my own -CURRENT release and am having a problem getting the correct syntax for CVSROOT. I have a CVS mirror running on my gateway (-STABLE) system via the cvsup-mirror port and would like to use this to build a release on a remote VMWare -CURRENT system, avoiding me from having to schlep around the multi-gig repository to build releases on my various test boxes. I cannot seem to get the correct syntax to CVSROOT to allow make release to pull from the networked repository and keep getting connection refused error messages. Indeed, all the handbook and other documentation I give refers to a local CVSROOT, so I'm unclear if it is even possible to roll a release against a remote repository. Is this sort of build scenario supported? If so, what would sample syntax be against a cvsup-mirror created repository look like? Thanks for the help! David pgp0.pgp Description: PGP signature
Re: Help with make release from -CURRENT to -STABLE
At 2003-08-05T12:17:07Z, Kirk Strauser [EMAIL PROTECTED] writes: Seriously, noone's made release for an older version before? -- Kirk Strauser pgp0.pgp Description: PGP signature
Help with make release from -CURRENT to -STABLE
I'm trying to make my own floppy release to add support for a wireless NIC that I need to install FreeBSD on a small laptop. My problem is that I'm running 5.1-RELEASE on the build machine, but I want to build a 4.8-RELEASE system for the laptop. I've read through release(7) and I pretty much follow what's going on. However, I don't really understand at which point I'm actually supposed to be building the release. I'm loosely following the example from the man page: cd /usr/src cvs diff -u /path/to/local.patch make buildworld cd release make release CHROOTDIR=/local3/release BUILDNAME=5.0-CURRENT \ CVSROOT=/host/cvs/usr/home/ncvs LOCAL_PATCHES=/path/to/local.patch In my case, I've cvsup'ed the cvs collection to /usr/src, moved /usr/src to /usr/src-5.1 (to get my usual version out of the way), rm -rf'ed /usr/obj, then used export CVSROOT=/usr/cvs cd /usr; cvs co -rRELENG_4_8 src to flesh out the source tree I want to build. After making my edits, I did the cvs diff to make a patch for later use. The next step in the example is to make buildworld, but that (unsurprisingly) fails fairly early into the build. This is where I'm getting confused. Which world am I supposed to be building: the 5.1 that is running on the build machine, or the 4.8 that I'm wanting to use for the release? Thanks, -- Kirk Strauser The Strauser Group Open. Solutions. Simple. http://www.strausergroup.com/ pgp0.pgp Description: PGP signature
Re: make release broken for -STABLE?
If memory serves me right, Igor B. Bykhalo wrote: [kern.flp overflow again] I don't get it: [snip] goshik# ls -l *kern* image.kern: total 1346 drwxr-xr-x 2 root wheel 512 22 ÑÎ× 21:19 boot -r-xr-xr-x 1 root wheel 1344894 22 ÑÎ× 21:19 kernel.gz kernels: total 2864 -r-xr-xr-x 1 root wheel 2909648 22 ÑÎ× 21:19 BOOTMFS.kern Looks like kernel.gz fits to floppy, but for some reason it doesn't... Should i supply more info? Well, kernel.gz will probably fit, but the release needs the entire contents of the image.kern directory to fit on kern.flp. See: freebsd-stable:stage% du image.kern 88 image.kern/boot 1434image.kern This doesn't fit. :-( By my calculation, we have to get rid of about 27K to make it fit, but I could be off. We might be able to move the de, em, or vx drivers to the mfsroot floppy, if there's space. I'll try playing around with this, if I get some time. (Obviously that shouldn't preclude someone else from working on this problem.) Bruce. msg16539/pgp0.pgp Description: PGP signature
Re: make release broken for -STABLE?
I wrote: We might be able to move the de, em, or vx drivers to the mfsroot floppy, if there's space. I'll try playing around with this, if I get some time. (Obviously that shouldn't preclude someone else from working on this problem.) I moved the em driver to mfsroot.flp and was able to build a release successfully (see revision 1.3.2.7 of src/release/i386/drivers.conf). Please update your tree, try the build again, and let me know how this works. Good luck, Bruce. msg16540/pgp0.pgp Description: PGP signature
make release broken for -STABLE?
goshik# uname -a FreeBSD goshik.binep.ac.ru 4.7-STABLE FreeBSD 4.7-STABLE #55: Wed Jan 22 13:20:00 MSK 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GO i386 goshik# make release CVSROOT=/home/ncvs CHROOTDIR=/home/release RELEASETAG=RELENG_4 DOCLANG=en_US.ISO8859-1 MAKE_ISOS=YES [...] touch hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c sh /usr/src/sys/conf/newvers.sh BOOTMFS cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-q ual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -I/usr/src/sys/contrib/ipfilter -D_KERNE L -include opt_global.h -mpreferred-stack-boundary=2 vers.c linking BOOTMFS textdata bss dec hex filename 2669495 207576 209556 3086627 2f1923 BOOTMFS -- Kernel build for BOOTMFS completed on Wed Jan 22 18:19:12 GMT 2003 -- cd /usr/obj/usr/src/sys/BOOTMFS; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac make KERNEL=BOOTMFS reinstall install -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels/BOOTMFS mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy dload=0x20 dsize=0x25000 isize=0x25000 entry=0x20 nsize=0x11afc /R/stage/image.kern/kernel: 53.7% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 8 fd1440 Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn0c:2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. goshik# I don't get it: goshik#cd /home/release/R/stages goshik#ls -l crunch total 3392 -r-xr-xr-x 34 root wheel 2180036 22 ÑÎ× 21:10 boot -rwxr-xr-x 1 root wheel 1233892 22 ÑÎ× 21:11 fixit goshik# ls -l floppies total 2912 -rw-r--r-- 1 root wheel 1474560 22 ÑÎ× 21:19 kern.flp -rw-r--r-- 1 root wheel 1474560 22 ÑÎ× 21:17 mfsroot.flp goshik# ls -l *kern* image.kern: total 1346 drwxr-xr-x 2 root wheel 512 22 ÑÎ× 21:19 boot -r-xr-xr-x 1 root wheel 1344894 22 ÑÎ× 21:19 kernel.gz kernels: total 2864 -r-xr-xr-x 1 root wheel 2909648 22 ÑÎ× 21:19 BOOTMFS.kern Looks like kernel.gz fits to floppy, but for some reason it doesn't... Should i supply more info? TIA, Igor To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Follow-up: Yet Another make release fails on ghostscript-gnu
Michael Dexter [EMAIL PROTECTED] writes: Having complete control over the build of my network OS is simply revolutionary... but I was hoping this revolution would not be so bloody. You can get *that* with one of the supported update options. make release was never intended for anybody but release engineers. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Yet Another make release fails on ghostscript-gnu
Greetings from Latvia, I am very, very excited about FreeBSD's make release ability but like many others I have read about on the various list archives, I my builds are hanging on trivial failures. In this case, the eplaser-3.0.4-651.tgz file is failing its checksum, bringing the build to a halt. I have followed the advice of adding NO_CHECKSUM=yes to no avail. I have tried it both after make and at the end of my string of variables. Which reads: make release CHROOTDIR=/usr/testrelease BUILDNAME=4.7-RELEASE CVSROOT=/usr/ncvs RELEASETAG=RELENG_4_7_0_RELEASE NOPORTS=yes NOPORTREADMES=yes NODOCS=yes TARGET_ARCH=i386 TARGET=i386 (/usr/ncvs is my choice, NO_CHECKSUMS=yes has again gone either after make or at the end) I have also: 1. Downloaded the same file from other /usr/ports/distfiles directories. Though different sizes, they also fail the check. 2. Tried to fetch new versions from /usr/ports/print/ghostscript-gnu/ and place them in either /usr/ports/distfiles and /usr/ports/ghostscript/ AND /usr/ports/ghostscript-gnu/ 3. Not tried DOMINIMALDOCPORTS as this would seem to go through the minimum files I am already having trouble with. Observations: 1. NO_CHECKSUM does not appear to be in any of the Makefiles in /usr/src/release/ or /usr/src/ Where is this check being called? Is there any other way to override it? Does it really exist? 2. The only vague reference to the file I need is in /usr/src/release/Makefile.inc.docports and reportedly the ports. man ports reveals the elusive NO_CHECKSUMS option! I see /usr/src/release/Makefile, doc and scripts but alas my make is not fluent enough to understand who is calling what and when. I would hope I do not need to feed NO_CHECKSUMS into evey invocation of make. 3. NOPORTSATALL=yes seems to be like an unavailable option, given that there will always be minimum documentation, which appear to need ports. 4. Others in need have pointed out that a build-friendly distfiles tar ball would ease this process. Does such a thing exist? Could I strip/re-create it from the official 4.7 release? Note that I have brought my sys, ncvs and ports source trees up to date. Because things are downloaded, I don't see how a fresh, raw, official 4.7 install would help what seems to be the checksum of a single downloaded port that I understand is downloaded on demand. THIS bothers me: make checksum inside of /usr/ports/print/ghostscript-gnu PASSES ALL CHECKSUM TESTS, including eplaser-3.0.4-651.tgz Why would this fail during make release? Any ideas? Many thanks, Michael. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Follow-up: Yet Another make release fails on ghostscript-gnu
Greetings again, Regarding the make release mentioned earlier... After peppering my /usr/ports/distfiles/ tree with very redundant distfiles, i.e. the same files in /usr/ports and /usr/ports/ghostscript and /usr/ports/ghostscript-gnu, things finally worked. (Ending on a vn present failure but I know where to look on that one) Given the time it takes to test each and every variable, I fear I will never be confident that I have an answer, though it was very educational... Early on, I tried stepping through make release.1 and all but this appeared to ignore the flags I sent it. All of the output was sent to the /R directory, rather than my choice of /usr/testrelease/ Can that be changed? Is there indeed a way to step-trough a release build? Having complete control over the build of my network OS is simply revolutionary... but I was hoping this revolution would not be so bloody. Conclusions: As suggested elsewhere, it would be nice to have an official source of buildable release files like the /usr/src on the CD, that would spare one the guesswork of trusting the ports fetch to build the build files prior to making the release. Might a pre-make script based upon the real make script perform all of the downloads and checksum verifications? This could save hours in wasted build time and guesswork, a bit like running cvsup prior to building world, knowing exactly what source will be used. I will look into this but again, my experience with make is only a few hours old. Thanks again, Michael. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
