Re: Make Release
On Thu, Aug 1, 2013 at 12:40 PM, Amitabh Kant 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"
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 >> 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.2&view=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
On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote: > On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin > 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.2&view=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 m
Re: Make Release
On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin 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.2&view=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 Thu, Aug 1, 2013 at 10:10 PM, Amitabh Kant 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. 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" >> > > 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
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. 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 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.2&view=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 fails
On 05/23/2013 06:52 AM, Jack Mc Lauren wrote:
> Hi
> 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
> 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
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"
Re: "make deinstall" within /usr/ports/lang - need to recover default language installs
Dear Chaps, Thank you very much for responding so quickly. Curiously the freeBSD 9.0 was installed with the standard answers to a sysinstall session and did contain a version of perl. I now seem to be in the state of discovering which languages I need and then re-installing. Is there a list/database for freeBSD 9.0 standard sysinstalls languages that I can view and use to re-install (via pkg_add -v -r perl etc) ? [there must a config file for sysinstall to use itself] Kind regards, Rob > lang/ contains all languages and so on ruby, lua, python, perl.. Of > course you removed perl since you typed make deinstall in that parent > port tree. > > You can type make install in /usr/ports/lang/perl5.14 to install it > again. You don't need to reinstall FreeBSD, you're not on Windows > here, you can repair everything :) > > Note: there is no perl installed by default, it's in the ports for few > years now. > > Regards, On 19/03/2013 01:19, Matthew Seaman wrote: > On 19/03/2013 07:54, Rob Navarro wrote: >> Hi Chaps, >> >> I typed "make deinstall" within the /usr/ports/lang directory of a >> FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of >> default compiled languages. >> >> How can I get back to the default FreeBSD default installed language >> state (with Perl installed etc)? > Ummm the default state is with just the base system installed: no > extra languages like perl or python and no other additional software > packages. > >> Crossing my fingers that I need not re-install the OS... > Nope. You absolutely do not need to do that -- all you did will have > affected the ports, which on FreeBSD is a distinct entity from the base > system. > > To recover, you simply need to re-install the appropriate ports. If you > know what you want installed, then it's easy: you can just feed a list > of those ports into portmaster(8) or portupgrade(8). > > If you don't know what you need installed in order to support various > end user programs, then there are various ways of checking that the > dependencies of the required ports are installed. For instance, if > you're using pkgng, you could run 'pkg check -da' At worst, and > requiring the least amount of extra software, just try re-installing the > packages in question. This should work, but you might end up doing a > lot of strictly unnecessary recompiling. > > Matthew > > > > ___ > 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 deinstall" within /usr/ports/lang - need to recover default language installs
On 19/03/2013 07:54, Rob Navarro wrote: > Hi Chaps, > > I typed "make deinstall" within the /usr/ports/lang directory of a > FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of > default compiled languages. > > How can I get back to the default FreeBSD default installed language > state (with Perl installed etc)? Ummm the default state is with just the base system installed: no extra languages like perl or python and no other additional software packages. > Crossing my fingers that I need not re-install the OS... Nope. You absolutely do not need to do that -- all you did will have affected the ports, which on FreeBSD is a distinct entity from the base system. To recover, you simply need to re-install the appropriate ports. If you know what you want installed, then it's easy: you can just feed a list of those ports into portmaster(8) or portupgrade(8). If you don't know what you need installed in order to support various end user programs, then there are various ways of checking that the dependencies of the required ports are installed. For instance, if you're using pkgng, you could run 'pkg check -da' At worst, and requiring the least amount of extra software, just try re-installing the packages in question. This should work, but you might end up doing a lot of strictly unnecessary recompiling. Matthew ___ 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 deinstall" within /usr/ports/lang - need to recover default language installs
lang/ contains all languages and so on ruby, lua, python, perl.. Of course you removed perl since you typed make deinstall in that parent port tree. You can type make install in /usr/ports/lang/perl5.14 to install it again. You don't need to reinstall FreeBSD, you're not on Windows here, you can repair everything :) Note: there is no perl installed by default, it's in the ports for few years now. Regards, 2013/3/19 Rob Navarro > Hi Chaps, > > I typed "make deinstall" within the /usr/ports/lang directory of a > FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of > default compiled languages. > > How can I get back to the default FreeBSD default installed language > state (with Perl installed etc)? > > Crossing my fingers that I need not re-install the OS... > > Kind regards, > > Rob > > ___ > 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" > -- Demelier David ___ 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 package" vs "pkg create"
On 24/02/2013 16:33, Joshua Isom wrote:
> I tried making a build jail, not with pourdriere or tinderbox. I just
> went to the ports and ran `make -DBATCH package-recursive clean` to get
> packages created. I ran `pkg add *` in the packages/All directory, but
> all failed because of MANIFEST missing. I'm guessing this is a bug in
> the .mk files, since I do have WITH_PKGNG set. Is this a known problem
> or is there supposed to be a different way to do it? Am I just supposed
> to use pourdriere or the source to keep my ports up to date until all
> the packages are rebuilt on freebsd.org?
'MANIFEST' is pretty fundamental to pkgs -- probably the error you are
seeing is because there are some other sort of files that aren't pkgng
packages present. That's going to upset pkg add. What's the history of
this jail? Did it start out using pkgng, or did it get converted from
pkg_tools? If the latter, did the conversion go smoothly? Can you use
eg. 'pkg info' in your jail to get an accurate listing of the packages
installed there?
If 'WITH_PKGNG' is set in your make.conf, then 'make package' will
certainly use pkgng to generate packages. I do that a lot in testing,
and it works just fine.
If you can clear out the non-pkgng stuff, the recommended way to do what
you intend is to generate a repository catalogue, and then use 'pkg
install'. 'pkg add' really should only be considered for installing
single packages when there is absolutely no alternative.
You should be able to run 'pkg repo /usr/ports/packages' to build a
repository catalogue for all the pkgng packages you've built in your
jail. Then you can either mount the jail's package tree on the machine
where you want to install packages, or make it available through a web
server. Set PACKAGESITE appropriately in ${LOCALBASE}/etc/pkg.conf --
for instance, this is what you'ld set to use a repo made as above and
mounted in the same location:
PACKAGESITE : file:/usr/ports/packages
You can then use 'pkg install' or 'pkg upgrade' in the usual way.
Note: you won't need to install every package in your repo -- many of
them will exist solely in order to facilitate building other packages.
If you choose the packages you specifically want, pkgng will sort out
installing the required dependencies, and moreover will set the
autoremove flags appropriately, so you could later purge things
installed solely as dependencies of packages you no longer want.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: "make package" vs "pkg create"
On Sun, 24 Feb 2013 10:33:45 -0600 Joshua Isom wrote: > I tried making a build jail, not with pourdriere or tinderbox. I just > went to the ports and ran `make -DBATCH package-recursive clean` to get > packages created. I ran `pkg add *` in the packages/All directory, but > all failed because of MANIFEST missing. I'm guessing this is a bug in > the .mk files, since I do have WITH_PKGNG set. No bug, but you will need to run pkg repo to turn the collection of packages you've built into a pkgng repository. > Is this a known problem > or is there supposed to be a different way to do it? Am I just supposed > to use pourdriere or the source to keep my ports up to date until all > the packages are rebuilt on freebsd.org? You don't need to use poudriere but it is very convenient once set up. For example - updating the ports tree and rebuilding the affected ports poudriere ports -u poudriere bulk -f /root/packages -j build build is my build jail, and /root/packages is a file listing the packages I want. -- Steve O'Hara-Smith ___ 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 install package?
On Jan 10, 2013, at 10:21 PM, Fbsd8 wrote: > Gökşin Akdeniz wrote: >> Thu, 10 Jan 2013 14:04:59 -0500 tarihinde >> Fbsd8 yazmış: >>> What is the default path for the packages to be stored in? >>> Is it /usr/packages? >>> >> It is "/usr/ports/packages/All". >>> If that is indeed the default location, how do I get the >>> "make install package" command put it there automatically? >>> >> All packages will be stored >> in /usr/ports/packages/All/relevant/sub/directory. There is no need >> for any any configuration or files. "# make package" is the proper >> command for building packages which are/is installed via ports. > > Is the upcoming pkgng going to have any effect on this? Funny you should ask, I was toying with that just yesterday, as a matter of fact. Works well with pkgng, it lets me create static packages of already installed ports: # pkg create -nao /usr/ports/packages/All Then creating the repo.txz file for use by clients is rather easy" # pkg repo -qf /usr/ports/packages And then, on your client host: # /usr/local/etc/pkg.conf PACKAGESITE : http://195.158.241.101 # pkg stats Local package database: Installed packages: 158 Disk space occupied: 797 MB Remote package database(s): Number of repositories: 1 Packages available: 182 Unique packages: 182 Total size of packages: 648 MB ___ 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 install package?
On 10/01/2013 21:21, Fbsd8 wrote: > Is the upcoming pkgng going to have any effect on this? No. The layout of /usr/ports/packages is controlled at a rather lower level by the Makefiles in /usr/ports/Mk. pkgng doesn't really care about this layout in any case since pkgng repositories don't need anything like it. Instead, they have repository catalogues which can fulfil all your package finding needs. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: make install package?
Gökşin Akdeniz wrote: Thu, 10 Jan 2013 14:04:59 -0500 tarihinde Fbsd8 yazmış: What is the default path for the packages to be stored in? Is it /usr/packages? It is "/usr/ports/packages/All". If that is indeed the default location, how do I get the "make install package" command put it there automatically? All packages will be stored in /usr/ports/packages/All/relevant/sub/directory. There is no need for any any configuration or files. "# make package" is the proper command for building packages which are/is installed via ports. Is the upcoming pkgng going to have any effect on this? ___ 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 install package?
Thu, 10 Jan 2013 14:04:59 -0500 tarihinde Fbsd8 yazmış: > > What is the default path for the packages to be stored in? > Is it /usr/packages? > It is "/usr/ports/packages/All". > > If that is indeed the default location, how do I get the > "make install package" command put it there automatically? > All packages will be stored in /usr/ports/packages/All/relevant/sub/directory. There is no need for any any configuration or files. "# make package" is the proper command for building packages which are/is installed via ports. -- Gökşin Akdeniz pgpJSYQXvYDeE.pgp Description: PGP signature
Re: make install package?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/10/13 2:04 PM, Fbsd8 wrote: > When I do a "make install package" command the package gets stored > in the directory I am in. > > What is the default path for the packages to be stored in? Is it > /usr/packages? > > If that is indeed the default location, how do I get the "make > install package" command put it there automatically? By default, it is /usr/ports/packages. To make sure your packages are stored there, make sure that directory exists. Once it does, cd to your favorite port directory and run this command: make -V PKGFILE The output should indicate that the package will be created in /usr/ports/packages instead of the local directory. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDvExQACgkQ0sRouByUApDaEQCfZazvazW5gHFSf7aj+G6Rjq9z B+oAn32bn6060dXlfgMxht8xO6zyE5Tj =jHKR -END PGP SIGNATURE- ___ 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 do not work in 10-Current
On (12/15/12 11:30), Boris Samorodov wrote:
> (maintainer is CCed)
>
> 15.12.2012 02:24, Eugen Konkov ??:
>
> > # make
> > "Makefile", line 166: Malformed conditional (${PORT_OPTIONS:MFIREBIRD} &&
> > empty(${PORT_OPTIONS:MEXPERIMENTAL})
> > "Makefile", line 168: if-less endif
> > make: fatal errors encountered -- cannot continue
>
Thanks for the report. A fix for this has been committed. Please
update your ports tree and try your build agian.
-r
> Please, try the attached patch (missing ")" at the end of the
> quoted Makefile line).
>
>
> --
> WBR, Boris Samorodov (bsam)
> FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
> Index: /usr/ports/net/freeradius2/Makefile
> ===
> --- /usr/ports/net/freeradius2/Makefile (revision 308706)
> +++ /usr/ports/net/freeradius2/Makefile (working copy)
> @@ -171,7 +171,7 @@
> .endif
>
> # Firebird module is still experimental
> -.if ${PORT_OPTIONS:MFIREBIRD} && empty(${PORT_OPTIONS:MEXPERIMENTAL}
> +.if ${PORT_OPTIONS:MFIREBIRD} && empty(${PORT_OPTIONS:MEXPERIMENTAL})
> EXPM=yes
> .endif
>
--
Ryan Steinmetz
PGP: EF36 D45A 5CA9 28B1 A550 18CD A43C D111 7AD7 FAF2
___
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 do not work in 10-Current
(maintainer is CCed)
15.12.2012 02:24, Eugen Konkov пишет:
> # make
> "Makefile", line 166: Malformed conditional (${PORT_OPTIONS:MFIREBIRD} &&
> empty(${PORT_OPTIONS:MEXPERIMENTAL})
> "Makefile", line 168: if-less endif
> make: fatal errors encountered -- cannot continue
Please, try the attached patch (missing ")" at the end of the
quoted Makefile line).
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Index: /usr/ports/net/freeradius2/Makefile
===
--- /usr/ports/net/freeradius2/Makefile (revision 308706)
+++ /usr/ports/net/freeradius2/Makefile (working copy)
@@ -171,7 +171,7 @@
.endif
# Firebird module is still experimental
-.if ${PORT_OPTIONS:MFIREBIRD} && empty(${PORT_OPTIONS:MEXPERIMENTAL}
+.if ${PORT_OPTIONS:MFIREBIRD} && empty(${PORT_OPTIONS:MEXPERIMENTAL})
EXPM= yes
.endif
___
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 > 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.2&view=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.1&view=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.2&view=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.1&view=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 and mfsroot
On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske 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 1:50 PM, Rick Miller wrote: > Hi Devin, > > On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske > 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.1&view=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.1&view=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
Hi Devin, On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske 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
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 print-index error: Generating INDEX-9 - please wait..perl: not found
On 28/09/2012 21:27, Ed Flecko wrote: > Generating INDEX-9 - please wait..perl: not found > "Makefile", line 31: warning: "perl -V:archname" returned non-zero status > perl: not found > Done. > > O.K., I'm stumped...what's wrong? You need to install perl in order to build an INDEX from scratch. That's true if you use the default 'make index' target or my p5-FreeBSD-Portindex code. Building an INDEX is a fairly time consuming task, and honestly, most people don't need to do it. You can download a pre-built INDEX by 'make fetchindex' which will be perfectly adequate for the vast majority of users. What you don't get by using the pre-built INDEX is the effect of any local customizations or options settings. This means that the INDEX may disagree in detail about exactly what dependencies some ports have. However, the INDEX is not used as part of actually building anything, so those discrepancies are mere annoyances rather than real obstacles. And, indeed, you can build and install ports very happily without any sort of INDEX on your system at all. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: make world error 9.0-RELEASE #0 i386
On Sat, 14 Apr 2012 12:28:52 -0400
Janos Dohanics wrote:
> Hello All,
>
> I'm trying to build world after having csupped, but the build fails
> with:
>
> [...]
> c++ -O2 -pipe
> -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
> -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
> -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
> -I.
> -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
> -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
> -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"i386-unknown-freebsd9.0
> \" -fstack-protector -fno-exceptions -fno-rtti
> -c
> /usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/SemaChecking.cpp
> {standard input}: Assembler messages: {standard input}:57706:
> Warning: end of file not at end of a line; newline inserted {standard
> input}: Assembler messages: {standard input}:71548: Warning: end of
> file not at end of a line; newline inserted {standard input}:71876:
> Error: no such instruction: `su' {standard input}:58857: Error:
> suffix or operands invalid for `mov' c++: Internal error: Killed: 9
> (program cc1plus) Please submit a full bug report. See
> http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1
> c++: Internal error: Killed: 9 (program cc1plus) Please submit a full
> bug report. See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
> [...]
I wanted to note that the error occurred when I used make buildworld
with the -j8 switch. Without the -j8 switch the build completed
without errors.
--
Janos Dohanics
___
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 install fails for /usr/ports/security/sudo after downgrade from 9.0-R to 8-STABLE
On 04/03/2012 04:36, ill...@gmail.com wrote: > Hmm, I would think that merely removing the offending file > and copying the correct one from /usr/obj/usr/src/tmp/usr/include/ > would suffice. I dunno, I don't think so. Why would it not be installed in the downgrade process? Also, the filenames aren't the same but the functionality (as far as I know) is. It might not have been the only thing broken. Downgrading across minor versions is simple and usually painless but there was a heads-up for the change from utmp.h to utmpx.h in -current back in January so I guess it was considered a major, low-level change and the downgrade couldn't work with that. Anyhow, rebuilding to 9-R has fixed everything as far as I can see, so I'm happy ;) -- freebsd at growveg dot net ___ 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 install fails for /usr/ports/security/sudo after downgrade from 9.0-R to 8-STABLE
On 3 March 2012 14:43, FreeBSD Mailing Lists wrote: > On 03/03/12 12:31, ill...@gmail.com wrote: >> >> Stale header files in /usr/include maybe? > > > Hi, > > Yes that's it. It seems got changed to between 8.2 and > 9.0. Fixed by csup of 9.0-R and doing the buildworld buildkernel etc. > Hmm, I would think that merely removing the offending file and copying the correct one from /usr/obj/usr/src/tmp/usr/include/ would suffice. -- -- ___ 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 install fails for /usr/ports/security/sudo after downgrade from 9.0-R to 8-STABLE
On 03/03/12 12:31, ill...@gmail.com wrote: Stale header files in /usr/include maybe? Hi, Yes that's it. It seems got changed to between 8.2 and 9.0. Fixed by csup of 9.0-R and doing the buildworld buildkernel etc. thanks, -- freebsd at growveg dot net ___ 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 install fails for /usr/ports/security/sudo after downgrade from 9.0-R to 8-STABLE
On 2 March 2012 14:44, FreeBSD Mailing Lists wrote: > Hello list, > > I had to downgrade from 9-R to 8-STABLE. To do this, I did the following: > > 1. rm -rf /usr/obj > 2. pkg_delete -a > 3. rm -rf /usr/ports > 4. mkdir -p /usr/ports/distfiles > 5. rm -rf /usr/src > 6. rm -rf /usr/local/* > 6. csup 8-STABLE sources > 7. csup ports > 8. cd /usr/src && make cleandir && make cleandir && make buildworld && > make buildkernel && make installkernel && mergemaster -p > 9. (merged required files) > 10. make installworld && mergemaster > 11. reboot. > > Practically everything in ports actually builds. I've installed X, > icewm, windowmaker, firefox36, thunderbird, gimp and a few others. I > think I've eliminated all the cruft from 9.0. However, I can't build > sudo (or screen) and I can't work out why. Here is the error: > > # make distclean clean install > > ===> Cleaning for sudo-1.8.4 > ===> Deleting distfiles for sudo-1.8.4 > ===> License sudo accepted by the user > ===> Found saved configuration for sudo-1.8.3_2 > => sudo-1.8.4p2.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > => Attempting to fetch http://www.sudo.ws/sudo/dist/sudo-1.8.4p2.tar.gz > ===> License sudo accepted by the user > ===> Found saved configuration for sudo-1.8.3_2 > => sudo-1.8.4p2.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > => Attempting to fetch http://www.sudo.ws/sudo/dist/sudo-1.8.4p2.tar.gz > > [...] > > cc -c -I../include -I.. -I. -I.. -I. -O2 -pipe -march=core2 > -I/usr/local/include -fno-strict-aliasing -D_BSD_SOURCE > -DLOCALEDIR=\"/usr/local/share/locale\" ./ttyname.c > cc -c -I../include -I.. -I. -I.. -I. -O2 -pipe -march=core2 > -I/usr/local/include -fno-strict-aliasing -D_BSD_SOURCE > -DLOCALEDIR=\"/usr/local/share/locale\" ./ttysize.c > cc -c -I../include -I.. -I. -I.. -I. -O2 -pipe -march=core2 > -I/usr/local/include -fno-strict-aliasing -D_BSD_SOURCE > -DLOCALEDIR=\"/usr/local/share/locale\" ./utmp.c > ./utmp.c: In function 'utmp_settime': > ./utmp.c:132: error: dereferencing pointer to incomplete type > ./utmp.c:133: error: dereferencing pointer to incomplete type > ./utmp.c: In function 'utmp_fill': > ./utmp.c:151: error: dereferencing pointer to incomplete type > ./utmp.c:153: error: dereferencing pointer to incomplete type > ./utmp.c:154: error: dereferencing pointer to incomplete type > ./utmp.c:157: error: dereferencing pointer to incomplete type > ./utmp.c:160: error: dereferencing pointer to incomplete type > ./utmp.c:160: error: dereferencing pointer to incomplete type > ./utmp.c:161: error: dereferencing pointer to incomplete type > ./utmp.c:161: error: dereferencing pointer to incomplete type > ./utmp.c:166: error: dereferencing pointer to incomplete type > ./utmp.c:170: error: dereferencing pointer to incomplete type > ./utmp.c: In function 'utmp_login': > ./utmp.c:294: error: storage size of 'utbuf' isn't known > /bin/sh ../libtool --tag=disable-static --mode=compile cc -c > -I../include -I.. -I. -I.. -I. -O2 -pipe -march=core2 > -I/usr/local/include -fno-strict-aliasing -D_BSD_SOURCE > -DLOCALEDIR=\"/usr/local/share/locale\" ./sudo_noexec.c > ./utmp.c: In function 'utmp_logout': > ./utmp.c:343: error: storage size of 'utbuf' isn't known > *** Error code 1 > libtool: compile: cc -c -I../include -I.. -I. -I.. -I. -O2 -pipe > -march=core2 -I/usr/local/include -fno-strict-aliasing -D_BSD_SOURCE > -DLOCALEDIR=\"/usr/local/share/locale\" ./sudo_noexec.c -fPIC -DPIC -o > .libs/sudo_noexec.o > 1 error > *** Error code 2 > 1 error > *** Error code 1 > > Stop in /usr/ports/security/sudo. > *** Error code 1 > > Stop in /usr/ports/security/sudo. > > Can anyone help please? Stale header files in /usr/include maybe? -- -- ___ 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 wrote: > On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller > 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
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller 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
Rick Miller 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"
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 wrote: > On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller 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/. 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
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"
Re: make release custom kernel conf not found
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller 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/. 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 buildworld powers down system
On Fri, 2 Dec 2011, Polytropon wrote: On Fri, 2 Dec 2011 03:28:09 -0500, Mehmet Erol Sanliturk wrote: On Fri, Dec 2, 2011 at 3:05 AM, Polytropon wrote: On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: The screen does go into standby and I am not sure what is controling that, nothing in KDE or Xorg that I set, perhaps a sysctl setting but I did not see one in the acpi section. This might be a dafault option. You can override it in your /etc/X11/xorg.conf by setting Option "DPMS" "false" in the section "Monitor" where you define the values for your monitor. I had a similar experience with an 21" CRT Eizo F980 going to sleep unintendedly. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... Another way may be inserting the following lines into ~/.xinitrc : xset s off xset -dpms Correct, I also have those in my ~/.xinitrc together with the xorg.conf setting above. With both settings, screens shouldn't blank anymore. Alas my problem is/was not with screen blanking. I do have have slightly upgraded 8.2. If I do not have a failing disk, I am left with something that carried across 2 boots. The only change I made was in the BIOS to make the function keys not require the key to be a function key. ___ 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 buildworld powers down system
On Fri, 2 Dec 2011 03:28:09 -0500, Mehmet Erol Sanliturk wrote: > On Fri, Dec 2, 2011 at 3:05 AM, Polytropon wrote: > > > On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: > > > The screen does go into standby and I am not > > > sure what is controling that, nothing in KDE or Xorg that I set, perhaps > > a > > > sysctl setting but I did not see one in the acpi section. > > > > This might be a dafault option. You can override it in > > your /etc/X11/xorg.conf by setting > > > >Option "DPMS" "false" > > > > in the section "Monitor" where you define the values > > for your monitor. I had a similar experience with an > > 21" CRT Eizo F980 going to sleep unintendedly. :-) > > > > -- > > Polytropon > > Magdeburg, Germany > > Happy FreeBSD user since 4.0 > > Andra moi ennepe, Mousa, ... > > > > > > > Another way may be inserting the following lines into ~/.xinitrc : > > xset s off > xset -dpms Correct, I also have those in my ~/.xinitrc together with the xorg.conf setting above. With both settings, screens shouldn't blank anymore. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 buildworld powers down system
On Fri, Dec 2, 2011 at 3:05 AM, Polytropon wrote: > On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: > > The screen does go into standby and I am not > > sure what is controling that, nothing in KDE or Xorg that I set, perhaps > a > > sysctl setting but I did not see one in the acpi section. > > This might be a dafault option. You can override it in > your /etc/X11/xorg.conf by setting > >Option "DPMS" "false" > > in the section "Monitor" where you define the values > for your monitor. I had a similar experience with an > 21" CRT Eizo F980 going to sleep unintendedly. :-) > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > Another way may be inserting the following lines into ~/.xinitrc : xset s off xset -dpms before the statement exec ... desktop_manager such as exec /usr/local/bin/gnome-session etc. OR ( every time when required ) in a terminal window of the desktop manager , enter the above xset commands , which will be effective only up to exit from the X or shutdown of the computer . Thank you very much . Mehmet Erol Sanliturk ___ 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 buildworld powers down system
On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: > The screen does go into standby and I am not > sure what is controling that, nothing in KDE or Xorg that I set, perhaps a > sysctl setting but I did not see one in the acpi section. This might be a dafault option. You can override it in your /etc/X11/xorg.conf by setting Option "DPMS" "false" in the section "Monitor" where you define the values for your monitor. I had a similar experience with an 21" CRT Eizo F980 going to sleep unintendedly. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 buildworld powers down system
On Thu, 1 Dec 2011, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Dec 1 01:16:21 2011 Date: Thu, 1 Dec 2011 02:14:04 -0500 (EST) From: doug To: freebsd-questions@freebsd.org Cc: Subject: make buildworld powers down system Three times in a row. It seems to be repeatable. At the end what should my next debugging step be? I ran the buildworld using script, the last lines in the make: cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncurses -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_beep.c cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncurses -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_bkgd.c cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncurses -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_box.c cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncursesw -I/usr/src/lib/ncurses/ncursesw/../ncurses -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDE^@^@^@^@^@^@^@ this after about 30 minutes of running. There are no errors in the logs First, look for *something* that would cause the machine to sleep/suspend/hibernate/shutdown after a period of "inactivity" It _could_ be a BIOS setting, it could be 'power mangement' software settings. It is also -possible- that this is a *THERMAL* issue -- that the 30+ minutes of heavy CPU utilization is triggering an overtemperature shutdown. Make sure all fans are working properly, and that CPU heat-sinks are dust-free. Thanks for your suggestions. I have ruled out hardware. I did change a BIOS setting to make the function keys be functions without the fn key (this is a Dell laptop). The only other thing I changed was to run a script to record the time and some of the hw.acpi sysctl values. As I now have the upgrade installed I will try the buildworld again. The screen does go into standby and I am not sure what is controling that, nothing in KDE or Xorg that I set, perhaps a sysctl setting but I did not see one in the acpi section. ___ 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 buildworld powers down system
> From owner-freebsd-questi...@freebsd.org Thu Dec 1 01:16:21 2011 > Date: Thu, 1 Dec 2011 02:14:04 -0500 (EST) > From: doug > To: freebsd-questions@freebsd.org > Cc: > Subject: make buildworld powers down system > > Three times in a row. It seems to be repeatable. At the end what should my > next > debugging step be? > > I ran the buildworld using script, the last lines in the make: > > cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. > -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncurses > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall > -DNDEBUG > -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c > /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_beep.c > cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. > -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncurses > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall > -DNDEBUG > -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c > /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_bkgd.c > cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. > -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncurses > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall > -DNDEBUG > -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector -c > /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_box.c > cc -O2 -pipe -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. > -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncursesw > -I/usr/src/lib/ncurses/ncursesw/../ncurses > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include > -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall > -DNDE^@^@^@^@^@^@^@ > > this after about 30 minutes of running. There are no errors in the logs > First, look for *something* that would cause the machine to sleep/suspend/hibernate/shutdown after a period of "inactivity" It _could_ be a BIOS setting, it could be 'power mangement' software settings. It is also -possible- that this is a *THERMAL* issue -- that the 30+ minutes of heavy CPU utilization is triggering an overtemperature shutdown. Make sure all fans are working properly, and that CPU heat-sinks are dust-free. ___ 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 buildworld don't run
From: Michael Powell To: freebsd-questions@freebsd.org Sent: Wednesday, November 2, 2011 4:00 PM Subject: Re: Make buildworld don't run Zantgo wrote: > I write "make buildworld", this is the answer: > > #make buildworld > make: don't know how to make buildworld. Stop Since this works just fine for all those who have learned how to use FreeBSD I can only assume this indicates you do not know what you are doing. > PS: I use FreeBSD 9.0 RC1, and I try to follow current This is a poor choice for anyone new to FreeBSD. There are mainly 3 branches of FreeBSD to consider: -CURRENT is for developers and other contributors working on the next version of FreeBSD, -STABLE is somewhat in the middle in that it will have patches for problems that have been fixed in current and merged back to earlier release versions of code, and RELEASE. There is also a SECURITY branch where only security patches are updated to RELEASE. Since it is obvious you do not know what you are doing the best place for you to begin is RELEASE. Install and begin using a RELEASE version as a learning tool. This means version 8.2! The Handbook may have pieces which are old and could stand updating, but largely it is _THE_ reference you should be working your way through as you proceed to learn FreeBSD. The greatest bulk of what you need to learn is in there. It comes in versions other than English too: http://www.freebsd.org/doc/es_ES.ISO8859-1/books/handbook/index.html If your only exposure to date with computers has been with Windows and you are looking to expand your reach, you will first find that the *Nix world is heavy on reading documentation and trying to figure stuff out for yourself first, before splattering help channels with every little thing that comes along. Once you have made some intial effort you will find that you are in a better position to provide better details on how we can help you. We cannot help you with the effort you need to make in learning the basics, and these basics are all contained in the documentation. I will make no effort to address your error. First of all, you should not be starting in FreeBSD with a release candidate and following -CURRENT. Your error is the result of trying to jump over learning what you need to know. -Mike ___ 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" Is it just me or does someone need to choke this guy. We all had to start somewhere and granted this guy's question was a newbie one, but please get off your soapbox. It's amazing how you make no effort to help this person yet you have the time to make alot of effort to ridicule. Your entire response could have been as simple as: cd /usr/src I work with people all the time who complain that they have no time to help you yet they have all the time in the world to send a lame e-mail complaining about how they have no time to help you. Lighten up ... life is too short, ___ 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 buildworld don't run
Zantgo wrote: > > El 02-11-2011, a las 17:00, Michael Powell > escribió: > >> If your only exposure to date with computers has been with Windows and >> you are looking to expand your reach, you will first find that the *Nix >> world is heavy on reading documentation and trying to figure stuff out >> for yourself first, before splattering help channels with every little >> thing that comes along. Once you have made some intial effort you will >> find that you are in a better position to provide better details on how >> we can help you. We cannot help you with the effort you need to make in >> learning the basics, and these basics are all contained in the >> documentation. >> >> I will make no effort to address your error. First of all, you should not >> be starting in FreeBSD with a release candidate and following -CURRENT. >> Your error is the result of trying to jump over learning what you need to >> know > > Now this worked for me and at one time thought to hold steady, but I > thought that opened many dependencies, and need more current packages so > take care not release Nope. Make buildworld is how you begin a source-based upgrade to the operating system. This is completely different and separate from anything package related. You are completely on the wrong track with this. Study the Handbook some more and this may become apparent. When you refresh your ports tree (which handles dependency tracking whether you are installing from ports or using packages) you will always be looking at the latest ports/packages. This is true no matter which branch of the OS you are using. Install RELEASE, refresh your ports tree, and you will still have all the 'most current packages'. You do *NOT* need to be running - CURRENT in order to have the 'most current packages'! This still reiterates the need for you to read and study the documentation. All of this information is present in the documentation. -Mike ___ 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 buildworld don't run
El 02-11-2011, a las 17:00, Michael Powell escribió: > If your only exposure to date with computers has been with Windows and you > are looking to expand your reach, you will first find that the *Nix world is > heavy on reading documentation and trying to figure stuff out for yourself > first, before splattering help channels with every little thing that comes > along. Once you have made some intial effort you will find that you are in a > better position to provide better details on how we can help you. We cannot > help you with the effort you need to make in learning the basics, and these > basics are all contained in the documentation. > > I will make no effort to address your error. First of all, you should not be > starting in FreeBSD with a release candidate and following -CURRENT. Your > error is the result of trying to jump over learning what you need to know Now this worked for me and at one time thought to hold steady, but I thought that opened many dependencies, and need more current packages so take care not 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"
Re: Make buildworld don't run
Zantgo wrote: > I write "make buildworld", this is the answer: > > #make buildworld > make: don't know how to make buildworld. Stop Since this works just fine for all those who have learned how to use FreeBSD I can only assume this indicates you do not know what you are doing. > PS: I use FreeBSD 9.0 RC1, and I try to follow current This is a poor choice for anyone new to FreeBSD. There are mainly 3 branches of FreeBSD to consider: -CURRENT is for developers and other contributors working on the next version of FreeBSD, -STABLE is somewhat in the middle in that it will have patches for problems that have been fixed in current and merged back to earlier release versions of code, and RELEASE. There is also a SECURITY branch where only security patches are updated to RELEASE. Since it is obvious you do not know what you are doing the best place for you to begin is RELEASE. Install and begin using a RELEASE version as a learning tool. This means version 8.2! The Handbook may have pieces which are old and could stand updating, but largely it is _THE_ reference you should be working your way through as you proceed to learn FreeBSD. The greatest bulk of what you need to learn is in there. It comes in versions other than English too: http://www.freebsd.org/doc/es_ES.ISO8859-1/books/handbook/index.html If your only exposure to date with computers has been with Windows and you are looking to expand your reach, you will first find that the *Nix world is heavy on reading documentation and trying to figure stuff out for yourself first, before splattering help channels with every little thing that comes along. Once you have made some intial effort you will find that you are in a better position to provide better details on how we can help you. We cannot help you with the effort you need to make in learning the basics, and these basics are all contained in the documentation. I will make no effort to address your error. First of all, you should not be starting in FreeBSD with a release candidate and following -CURRENT. Your error is the result of trying to jump over learning what you need to know. -Mike ___ 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 buildworld don't run
El 02-11-2011, a las 16:33, Jerry McAllister escribió: > On Wed, Nov 02, 2011 at 03:45:39PM -0300, Zantgo wrote: > >> I write "make buildworld", this is the answer: >> >> #make buildworld >> make: don't know how to make buildworld. Stop >> >> PS: I use FreeBSD 9.0 RC1, and I try to follow current > > What user/permissions did you have? > Which directory were you in? > > I think you need to be root and in /usr/src > > I could be wrong. > > jerry Yeah!!, I just had to be in / usr / src, thank you very much!. PS: as the directory name that comes after typing "cd" as root or user? > >> >> Zantgo >> ___ >> 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 buildworld don't run
On Wed, Nov 02, 2011 at 03:45:39PM -0300, Zantgo wrote: > I write "make buildworld", this is the answer: > > #make buildworld > make: don't know how to make buildworld. Stop > > PS: I use FreeBSD 9.0 RC1, and I try to follow current What user/permissions did you have? Which directory were you in? I think you need to be root and in /usr/src I could be wrong. jerry > > Zantgo > ___ > 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 buildworld don't run
On Wed, Nov 2, 2011 at 1:45 PM, Zantgo wrote: > I write "make buildworld", this is the answer: > > #make buildworld > make: don't know how to make buildworld. Stop > http://www.freebsd.org/doc/handbook/makeworld.html -- Adam Vande More ___ 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 readmes" no longer builds individual ports' README.html files?
"Conrad J. Sabatier" wrote: > Having been away from FreeBSD for a while, I'm still catching up with > all the changes that took place while I was on hiatus, so bear with me > here. :-) > > Trying to construct the ports' README.html files with: > > cd /usr/ports > make readmes > > Much to my surprise, this only creates README.html at the top level > and within each category, but nothing under the individual ports' > directories. When did this change, and why? Mailing list search has > turned up nothing useful on the subject. > > Or maybe I'm just doing it wrong? :-) It was definitely broken. I've just committed a fix to ports/Tools/make_readmes. Emanuel ___ 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 readmes" no longer builds individual ports' README.html files?
On Mon, 8 Aug 2011 22:35:35 -0500 Conrad J. Sabatier wrote: > Having been away from FreeBSD for a while, I'm still catching up with > all the changes that took place while I was on hiatus, so bear with me > here. :-) > > Trying to construct the ports' README.html files with: > > cd /usr/ports > make readmes > > Much to my surprise, this only creates README.html at the top level > and within each category, but nothing under the individual ports' > directories. When did this change, and why? Mailing list search has > turned up nothing useful on the subject. > > Or maybe I'm just doing it wrong? :-) > > Thanks. > When you "make readmes" from the top level the per port files are created by a perl script I tried running perl /usr/ports/Tools/make_readmes < /usr/ports/INDEX-8 and it didn't work. Since it's quite old I would guess a perl upgrade has probably broken it. [ Since this was cross-posted I've set a reply-to to "ports" where it belongs ] ___ 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 buildworld errors
Hi, Can it be related to an issue from 2009? I have the same problem when compiling with WITHOUT_KVM and WITH_INET6 (implicit as WITHOUT_INET6 is not defined). See the folling links http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013020.html http://lists.freebsd.org/pipermail/freebsd-current/attachments/20091101/4084 8244/ifmcstat.obj Regards, // Mem - On 1st of January 2011 Manolis Kiagias wrote: - Subject: Re: make buildworld errors From: Manolis Kiagias Date: Sat, 01 Jan 2011 00:35:37 -0800 On 01/01/2011 9:54 ?.?., Mike wrote: > > Trying to buildworld but it keeps failing. I finally deleted /usr/src > and recopyed from a cd then cvsup using standard-supfile. Tried > limiting how much ram freebsd uses and only using one stick of ram. > All attempts have failed at the same place. Would using the GENERIC > kernel make a difference? > You shouldn't have any trouble building world using a custom kernel. Try rm -rf /usr/obj/* before starting the build. This usually solves th ___ 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 one partition with two existing ?
On 06/09/2011 10:31 AM, Polytropon wrote: On Thu, 09 Jun 2011 10:21:27 +0200, Frank Bonnet wrote: Hello I have a raid 5 array ( HP hardware managed ) that contains the following partitions -- Filesystem SizeUsed Avail Capacity Mounted on /dev/aacd0s1a1.9G306M1.5G17%/ devfs1.0K1.0K 0B 100%/dev /dev/aacd0s1g 10G7.2M9.3G 0%/tmp /dev/aacd0s1e609G559G1.5G 100%/mnt /dev/aacd0s1d 97G 12G 77G14%/usr /dev/aacd0s1f610G5.3G556G 1%/var What I would like to do is 1 - delete the /mnt partition 2 - extend the /var partition with the free space left by /mnt Is it faisable without destroying the /var data ? Shpuld be possible in few steps. 1. Unmount /var and dump its content, e. g. # umount /var # dump -0a -f /usr/var.dump /dev/aacd0s1f If you can't unmount /var, see "man dump" for the -L option. 2. Delete the /dev/aacd0s1e and /dev/aacd0s1f partition, e. g. using sysinsall. 3. Create a new partition /dev/aacd0s1e with the size of the former /dev/aacd0s1e + /dev/aacd0s1f, e. g. using sysinstall or bsdlabel. 4. Initialize the new partition /dev/aacd0s1e, e. g. # newfs -U /dev/aacd0s1e Use further tunefs commands if required. 5. Mount it and restore from dump. # mount /dev/aacd0s1e /var # cd /var # restore -r -f /usr/var.dump Finally you can remove /usr/var.dump. And make a change to /etc/fstab for the new setting. The whole work is best done in single user mode so there won't be requests for writing things to /var. Thanks a lot ! ___ 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 one partition with two existing ?
On Thu, 09 Jun 2011 10:21:27 +0200, Frank Bonnet wrote: > Hello > > I have a raid 5 array ( HP hardware managed ) that contains the > following partitions > > -- Filesystem SizeUsed Avail Capacity Mounted on > /dev/aacd0s1a1.9G306M1.5G17%/ > devfs1.0K1.0K 0B 100%/dev > /dev/aacd0s1g 10G7.2M9.3G 0%/tmp > /dev/aacd0s1e609G559G1.5G 100%/mnt > /dev/aacd0s1d 97G 12G 77G14%/usr > /dev/aacd0s1f610G5.3G556G 1%/var > > What I would like to do is > > 1 - delete the /mnt partition > 2 - extend the /var partition with the free space left by /mnt > > Is it faisable without destroying the /var data ? Shpuld be possible in few steps. 1. Unmount /var and dump its content, e. g. # umount /var # dump -0a -f /usr/var.dump /dev/aacd0s1f If you can't unmount /var, see "man dump" for the -L option. 2. Delete the /dev/aacd0s1e and /dev/aacd0s1f partition, e. g. using sysinsall. 3. Create a new partition /dev/aacd0s1e with the size of the former /dev/aacd0s1e + /dev/aacd0s1f, e. g. using sysinstall or bsdlabel. 4. Initialize the new partition /dev/aacd0s1e, e. g. # newfs -U /dev/aacd0s1e Use further tunefs commands if required. 5. Mount it and restore from dump. # mount /dev/aacd0s1e /var # cd /var # restore -r -f /usr/var.dump Finally you can remove /usr/var.dump. And make a change to /etc/fstab for the new setting. The whole work is best done in single user mode so there won't be requests for writing things to /var. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 the iso image
On 11/05/2011 18:35, Mage wrote: On 05/11/2011 04:50 AM, Polytropon wrote: On Tue, 10 May 2011 19:24:39 -0700, mohammad abedini wrote: I plan to make the FreeBSD installation with facilities in my state This looks as if you want to create your own installation media. The "make release" operation is intended for that task. However I (not the original sender) would like to create just a LiveDVD from my install, because I upgraded to zpool version and didn't find any official release or snapshot which can mount that. It would be only a rescue DVD, not installer medium. Is there a shorter way than make release? I don't even need a gui on that DVD just some basic tools and zpool v28. (i don't use zfs so not sure if this is feasible) http://www.freebsd.org/doc/handbook/install-advanced.html I used the instuctions here to build a serial install disk which only required some editing of files before regenerating an install iso ( ie not from a running system), maybe this would help you if you could add in the necessary zfs support Paul. Mage ___ 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" -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07534206249 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ 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 the iso image
On 05/11/2011 04:50 AM, Polytropon wrote: > On Tue, 10 May 2011 19:24:39 -0700, mohammad abedini > wrote: >> I plan to make the FreeBSD installation with facilities in my state > This looks as if you want to create your own installation > media. The "make release" operation is intended for that > task. However I (not the original sender) would like to create just a LiveDVD from my install, because I upgraded to zpool version and didn't find any official release or snapshot which can mount that. It would be only a rescue DVD, not installer medium. Is there a shorter way than make release? I don't even need a gui on that DVD just some basic tools and zpool v28. Mage ___ 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 the iso image
On Tue, 10 May 2011 19:21:14 -0700, mohammad abedini wrote: > I like make the release cd image from my installed freebsd . On Tue, 10 May 2011 19:24:39 -0700, mohammad abedini wrote: > I plan to make the FreeBSD installation with facilities in my state This looks as if you want to create your own installation media. The "make release" operation is intended for that task. See /usr/src/Makefile, as well as "man 7 release" for details. I think the manpage explains the process very well. There are targets available for creating the ISO images (and defining what their content should be, e. g. separate media for packages), and anything you then need is to burn the results to the required media (CD or DVD). There is also good documentation that goes into detail, it can be found here: FreeBSD Release Engineering: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/ FreeBSD Release Engineering of Third Party Packages: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/ PS. Plase avoid top-posting; and I'm re-including the list, hope that's okay. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 the iso image
On Tue, 10 May 2011 18:58:47 -0700, mohammad abedini wrote: > Tanks > > I like make iso image from my freeBSD in my hard disk. Do you refer to the "make release" procedure provided in /usr/src/Makefile, do you mean a live system (that can be run from CD or DVD), or do you want to create a backup (dump/restore) from your installed system onto optical media? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 the iso image
Tanks I like make iso image from my freeBSD in my hard disk. BR On Tue, May 10, 2011 at 6:30 AM, Lowell Gilbert < freebsd-questions-lo...@be-well.ilk.org> wrote: > mohammad abedini writes: > > > 1. i install freebsd and make the new kernel, i like make the iso > > install CD in new install FreeBSD how can i do this? > > If you've downloaded the image already and have a CD burner in your > machine, burncd(8) will burn it for you, although installing cdrecord > from the cdrtools port is easier for most people. > > > 2. How can restore FreeBSD in to the first boot time lake sunsolaris > > delete all program and back to the first install > > The fast way is to reinstall, reformatting the disk along the way. > If you want to keep the user data, pkg_delete(1) on all the installed > ports is probably what you want. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: make the iso image
mohammad abedini writes: > 1. i install freebsd and make the new kernel, i like make the iso > install CD in new install FreeBSD how can i do this? If you've downloaded the image already and have a CD burner in your machine, burncd(8) will burn it for you, although installing cdrecord from the cdrtools port is easier for most people. > 2. How can restore FreeBSD in to the first boot time lake sunsolaris > delete all program and back to the first install The fast way is to reinstall, reformatting the disk along the way. If you want to keep the user data, pkg_delete(1) on all the installed ports is probably what you want. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: #>make all vs #/make buildworld
Good Day; Okay, stupid question answered! I found the appropriate section of the Handbook which tells the reasons to use the right build procedure. I then CVSup'd source and ports today. make buildworld seems to be executing as expected. Then... the screen blanked and the mouse and keyboard quit working but, that is a story for another day. I can ssh into the machine from a laptop and see the processes running. I'll wait until the drive light stops indicating activity and ps -A tells me the build process has finished, then do a shutdown -r remotely. Thank You, michael ___ 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 FreeBSD read the slice table and partition table again
On Tue, Feb 1, 2011 at 2:16 PM, Bahman Kahinpour wrote: > Hello > When I destroy the partition table with the following command: > # dd if=/dev/zero of=/dev/ad1 bs=1k count=10 > The entries /dev/ad1s1a, ... still exist in /dev. This means that the > kernel has not found out that the slices and partitions do not exist > anymore. > Um AFAIK, GEOM tastes the provider on closing so that command should have updated the device entries. And it works properly in VM here so I'm unsure the problem you are having. A "true > /dev/ad1" would also cause GEOM to retaste it. -- Adam Vande More ___ 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 buildkernel pre-build too long
On Tue Sep 21 10, David DEMELIER wrote:
> 2010/9/21 Alexander Best :
> > On Fri Sep 17 10, David DEMELIER wrote:
> >> 2010/9/17 Alexander Best :
> >> > On Thu Sep 16 10, David DEMELIER wrote:
> >> >> Hi there,
> >> >>
> >> >> I can't understand why this part of make buildkernel is so long on my
> >> >> amd64 machine (8.1-R)
> >> >>
> >> >> make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E"
> >> >> CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe
> >> >> -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
> >> >> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> >> >> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
> >> >> -fformat-extensions -nostdinc -I. -I/usr/src/sys
> >> >> -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
> >> >> -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
> >> >> -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
> >> >> -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
> >> >> -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
> >> >> -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
> >> >> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
> >> >> -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param
> >> >> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel
> >> >> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
> >> >> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables
> >> >> -ffreestanding -fstack-protector
> >> >>
> >> >> This command takes around 5-6 minutes before continuing, on my i386
> >> >> machine (which is really old) it only takes about 20 seconds. The
> >> >> kernel configs are almost the same for both machines.
> >> >
> >> > are there any differences in /etc/make.conf?
> >> >
> >> > cheers.
> >> > alex
> >> >
> >> >>
> >> >> Do you have any idea?
> >> >>
> >> >> Kind regards,
> >> >>
> >> >> --
> >> >> Demelier David
> >> >
> >> > --
> >> > a13x
> >> >
> >>
> >> No, except the KERNCONF entry it's exactly the same :
> >
> > hmmmstrange. could you post the ouput of `make -VCFLAGS -VCOPTFLAGS` on
> > both your machines, please?
> >
> > cheers.
> > alex
> >
> >>
> >> # General settings.
> >> KERNCONF=Melon
> >> MASTER_SORT?= .fr .uk
> >>
> >> # Portconf.
> >> .if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
> >> _PORTCONF!=/usr/local/libexec/portconf
> >> .for i in ${_PORTCONF:S/|/ /g}
> >> ${i:S/%/ /g}
> >> .endfor
> >> .endif
> >>
> >> # Perl.
> >> PERL_VERSION=5.10.1
> >>
> >> # No need modules.
> >> NO_MODULES=yes
> >>
> >> # Specify other directories.
> >> WRKDIRPREFIX= /usr/obj
> >> DISTDIR= /usr/distfiles
> >>
> >> --
> >> Demelier David
> >
> > --
> > a13x
> >
>
> -O2 -pipe
>
> I think the problem is the amd64 architecture. When I buildkernel
> using TARGET_ARCH=i386 it takes only one minute or even less, it's
> only native target (amd64) which is long.
i finally had the time to measue target buildkernel for amd64 and for i386:
make buildkernel KERNCONF=GENERIC TARGET=i386 248,84s user 47,29s system 101%
cpu 4:52,15 total
vs.
make buildkernel KERNCONF=GENERIC TARGET=amd64 246,36s user 47,08s system 103%
cpu 4:44,62 total
...so no difference in my case. this was tested on a very recent HEAD with
arch=amd64.
cheers.
alex
>
> Kind regards,
>
> --
> Demelier David
--
a13x
___
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 buildworld errors
On 01/01/2011 9:54 ?.?., Mike wrote: > > Trying to buildworld but it keeps failing. I finally deleted /usr/src > and recopyed from a cd then cvsup using standard-supfile. Tried > limiting how much ram freebsd uses and only using one stick of ram. > All attempts have failed at the same place. Would using the GENERIC > kernel make a difference? > You shouldn't have any trouble building world using a custom kernel. Try rm -rf /usr/obj/* before starting the build. This usually solves th ___ 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 gtk widgets use a larger font
in message <20101209114208.c1...@qroenaqrq.6qbyyneqvnyhc.pbz>, wrote
Lars Eighner thusly...
>
> How do I make gtk widgets use larger fonts? I found an old linux
> FAQ on this, but it appears to have nothing to do with the way
> configuration works on FreeBSD.
In ~/.gtkrc-2.0, I have ...
style "default"
{
#font="-adobe-new century
schoolbook-medium-r-normal--14-*-*-*-*-*-iso8859-1"
#font_name="New Century Schoolbook 12"
font_name="Bitstream Vera Sans 10"
}
style "user-tooltip"
{
font_name="Screen 15"
}
# 'gtk-font-name' property is needed for damned Firefox 1.5 as
# 'font_name' property alone didn't work, but does for Gimp 2.2.
# Anti-aliased fonts are used though i would love to use
# non-anti-aliased font in order to get New Century Schoolbook 14
# font.
#gtk-font-name = "Bitstream Vera Serif 12"
#gtk-font-name = "New Century Schoolbook 12"
gtk-font-name = "Bitstream Vera Sans 10"
widget "*" style "default"
widget "*tooltip*" style "user-tooltip"
... and in ~/.gtkrc ...
style "default"
{
font="-adobe-new century schoolbook-medium-r-normal--18-*-*-*-p-*-iso8859-1"
}
style "user-tooltip"
{
font="-sgi-screen-bold-r-normal--16-*-*-*-*-0-iso8859-1"
}
widget "*" style "default"
widget "*tooltip*" style "user-tooltip"
- parv
--
___
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 gtk widgets use a larger font
The fastest solution is probably to install x11/gtk-theme-switch2 and use "switch2" to change the theme and/or font. ___ 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 gtk widgets use a larger font
On Thu, 9 Dec 2010 11:44:01 -0600 (CST), Lars Eighner
wrote:
> How do I make gtk widgets use larger fonts? I found an old linux FAQ on
> this, but it appears to have nothing to do with the way configuration works
> on FreeBSD.
I'm not sure if it will still work, but in the past,
you could create ~/.gtkrc and override settings as
you liked.
style "font_1"
{
font= "-b&h-lucida-medium-r-normal-*-12-*-*-*-p-*-iso8859-15"
}
class "*" style "font_1"
widget "*" style "font_1"
Then replace "iso8859-15" with the font encoding you
need, and of course "12" with any other font size
that fits your needs. In order to construct the font
determination string based on a visual impression and
attribute selection from lists, you can use the
% xfontsel
program.
Attention: Untested.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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 gtk widgets use a larger font
Quoth Lars Eighner on Thursday, 09 December 2010: > How do I make gtk widgets use larger fonts? I found an old linux FAQ on > this, but it appears to have nothing to do with the way configuration works > on FreeBSD. > > -- > Lars Eighner > http://www.larseighner.com/index.html > 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 > > ___ > 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've been looking into this, although my intention was to make the fonts smaller. I have yet to be successful. I think the answer should lie in modifying your gtk theme file (.gtkrc-2.0 for GTK 2). I started by copying a theme that I liked (http://www.cimitan.com/murrine/node/220";>Black Diamondhttp://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp8Wntvr7c4u.pgp Description: PGP signature
Re: make buildkernel pre-build too long
On Tue Sep 21 10, David DEMELIER wrote:
> 2010/9/21 Alexander Best :
> > On Fri Sep 17 10, David DEMELIER wrote:
> >> 2010/9/17 Alexander Best :
> >> > On Thu Sep 16 10, David DEMELIER wrote:
> >> >> Hi there,
> >> >>
> >> >> I can't understand why this part of make buildkernel is so long on my
> >> >> amd64 machine (8.1-R)
> >> >>
> >> >> make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E"
> >> >> CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe
> >> >> -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
> >> >> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> >> >> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
> >> >> -fformat-extensions -nostdinc -I. -I/usr/src/sys
> >> >> -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
> >> >> -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
> >> >> -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
> >> >> -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
> >> >> -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
> >> >> -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
> >> >> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
> >> >> -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param
> >> >> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel
> >> >> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
> >> >> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables
> >> >> -ffreestanding -fstack-protector
> >> >>
> >> >> This command takes around 5-6 minutes before continuing, on my i386
> >> >> machine (which is really old) it only takes about 20 seconds. The
> >> >> kernel configs are almost the same for both machines.
> >> >
> >> > are there any differences in /etc/make.conf?
> >> >
> >> > cheers.
> >> > alex
> >> >
> >> >>
> >> >> Do you have any idea?
> >> >>
> >> >> Kind regards,
> >> >>
> >> >> --
> >> >> Demelier David
> >> >
> >> > --
> >> > a13x
> >> >
> >>
> >> No, except the KERNCONF entry it's exactly the same :
> >
> > hmmmstrange. could you post the ouput of `make -VCFLAGS -VCOPTFLAGS` on
> > both your machines, please?
> >
> > cheers.
> > alex
> >
> >>
> >> # General settings.
> >> KERNCONF=Melon
> >> MASTER_SORT?= .fr .uk
> >>
> >> # Portconf.
> >> .if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
> >> _PORTCONF!=/usr/local/libexec/portconf
> >> .for i in ${_PORTCONF:S/|/ /g}
> >> ${i:S/%/ /g}
> >> .endfor
> >> .endif
> >>
> >> # Perl.
> >> PERL_VERSION=5.10.1
> >>
> >> # No need modules.
> >> NO_MODULES=yes
> >>
> >> # Specify other directories.
> >> WRKDIRPREFIX= /usr/obj
> >> DISTDIR= /usr/distfiles
> >>
> >> --
> >> Demelier David
> >
> > --
> > a13x
> >
>
> -O2 -pipe
>
> I think the problem is the amd64 architecture. When I buildkernel
> using TARGET_ARCH=i386 it takes only one minute or even less, it's
> only native target (amd64) which is long.
i'll try to cross build a kernel for i386 (i686) and see if that shortens the
build time on my pc, too.
you might want to consider aksing this question again on freebsd-current@ or
freebsd-am...@. not too many developers read freebsd-questi...@.
cheers.
alex
>
> Kind regards,
>
> --
> Demelier David
--
a13x
___
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 buildkernel pre-build too long
2010/9/21 Alexander Best :
> On Fri Sep 17 10, David DEMELIER wrote:
>> 2010/9/17 Alexander Best :
>> > On Thu Sep 16 10, David DEMELIER wrote:
>> >> Hi there,
>> >>
>> >> I can't understand why this part of make buildkernel is so long on my
>> >> amd64 machine (8.1-R)
>> >>
>> >> make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E"
>> >> CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe
>> >> -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
>> >> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
>> >> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
>> >> -fformat-extensions -nostdinc -I. -I/usr/src/sys
>> >> -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
>> >> -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
>> >> -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
>> >> -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
>> >> -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
>> >> -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
>> >> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
>> >> -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param
>> >> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel
>> >> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
>> >> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables
>> >> -ffreestanding -fstack-protector
>> >>
>> >> This command takes around 5-6 minutes before continuing, on my i386
>> >> machine (which is really old) it only takes about 20 seconds. The
>> >> kernel configs are almost the same for both machines.
>> >
>> > are there any differences in /etc/make.conf?
>> >
>> > cheers.
>> > alex
>> >
>> >>
>> >> Do you have any idea?
>> >>
>> >> Kind regards,
>> >>
>> >> --
>> >> Demelier David
>> >
>> > --
>> > a13x
>> >
>>
>> No, except the KERNCONF entry it's exactly the same :
>
> hmmmstrange. could you post the ouput of `make -VCFLAGS -VCOPTFLAGS` on
> both your machines, please?
>
> cheers.
> alex
>
>>
>> # General settings.
>> KERNCONF=Melon
>> MASTER_SORT?= .fr .uk
>>
>> # Portconf.
>> .if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
>> _PORTCONF!=/usr/local/libexec/portconf
>> .for i in ${_PORTCONF:S/|/ /g}
>> ${i:S/%/ /g}
>> .endfor
>> .endif
>>
>> # Perl.
>> PERL_VERSION=5.10.1
>>
>> # No need modules.
>> NO_MODULES=yes
>>
>> # Specify other directories.
>> WRKDIRPREFIX= /usr/obj
>> DISTDIR= /usr/distfiles
>>
>> --
>> Demelier David
>
> --
> a13x
>
-O2 -pipe
I think the problem is the amd64 architecture. When I buildkernel
using TARGET_ARCH=i386 it takes only one minute or even less, it's
only native target (amd64) which is long.
Kind regards,
--
Demelier David
___
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 buildkernel pre-build too long
On Fri Sep 17 10, David DEMELIER wrote:
> 2010/9/17 Alexander Best :
> > On Thu Sep 16 10, David DEMELIER wrote:
> >> Hi there,
> >>
> >> I can't understand why this part of make buildkernel is so long on my
> >> amd64 machine (8.1-R)
> >>
> >> make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E"
> >> CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe
> >> -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
> >> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
> >> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
> >> -fformat-extensions -nostdinc -I. -I/usr/src/sys
> >> -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
> >> -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
> >> -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
> >> -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
> >> -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
> >> -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
> >> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
> >> -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param
> >> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel
> >> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
> >> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables
> >> -ffreestanding -fstack-protector
> >>
> >> This command takes around 5-6 minutes before continuing, on my i386
> >> machine (which is really old) it only takes about 20 seconds. The
> >> kernel configs are almost the same for both machines.
> >
> > are there any differences in /etc/make.conf?
> >
> > cheers.
> > alex
> >
> >>
> >> Do you have any idea?
> >>
> >> Kind regards,
> >>
> >> --
> >> Demelier David
> >
> > --
> > a13x
> >
>
> No, except the KERNCONF entry it's exactly the same :
hmmmstrange. could you post the ouput of `make -VCFLAGS -VCOPTFLAGS` on
both your machines, please?
cheers.
alex
>
> # General settings.
> KERNCONF=Melon
> MASTER_SORT?= .fr .uk
>
> # Portconf.
> .if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
> _PORTCONF!=/usr/local/libexec/portconf
> .for i in ${_PORTCONF:S/|/ /g}
> ${i:S/%/ /g}
> .endfor
> .endif
>
> # Perl.
> PERL_VERSION=5.10.1
>
> # No need modules.
> NO_MODULES=yes
>
> # Specify other directories.
> WRKDIRPREFIX= /usr/obj
> DISTDIR=/usr/distfiles
>
> --
> Demelier David
--
a13x
___
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 buildkernel pre-build too long
2010/9/17 Alexander Best :
> On Thu Sep 16 10, David DEMELIER wrote:
>> Hi there,
>>
>> I can't understand why this part of make buildkernel is so long on my
>> amd64 machine (8.1-R)
>>
>> make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E"
>> CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe
>> -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls
>> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
>> -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
>> -fformat-extensions -nostdinc -I. -I/usr/src/sys
>> -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
>> -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
>> -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
>> -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
>> -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
>> -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
>> -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
>> -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel
>> -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
>> -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables
>> -ffreestanding -fstack-protector
>>
>> This command takes around 5-6 minutes before continuing, on my i386
>> machine (which is really old) it only takes about 20 seconds. The
>> kernel configs are almost the same for both machines.
>
> are there any differences in /etc/make.conf?
>
> cheers.
> alex
>
>>
>> Do you have any idea?
>>
>> Kind regards,
>>
>> --
>> Demelier David
>
> --
> a13x
>
No, except the KERNCONF entry it's exactly the same :
# General settings.
KERNCONF=Melon
MASTER_SORT?= .fr .uk
# Portconf.
.if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
_PORTCONF!=/usr/local/libexec/portconf
.for i in ${_PORTCONF:S/|/ /g}
${i:S/%/ /g}
.endfor
.endif
# Perl.
PERL_VERSION=5.10.1
# No need modules.
NO_MODULES=yes
# Specify other directories.
WRKDIRPREFIX= /usr/obj
DISTDIR=/usr/distfiles
--
Demelier David
___
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 buildkernel pre-build too long
On Thu Sep 16 10, David DEMELIER wrote: > Hi there, > > I can't understand why this part of make buildkernel is so long on my > amd64 machine (8.1-R) > > make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" > CC="cc" xargs mkdep -a -f .newdep -O2 -frename-registers -pipe > -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD > -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs > -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb > -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h > -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel > -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables > -ffreestanding -fstack-protector > > This command takes around 5-6 minutes before continuing, on my i386 > machine (which is really old) it only takes about 20 seconds. The > kernel configs are almost the same for both machines. are there any differences in /etc/make.conf? cheers. alex > > Do you have any idea? > > Kind regards, > > -- > Demelier David -- a13x ___ 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 installworld fails
Am Montag, den 02.08.2010, 08:24 -0700 schrieb Caleb Stein: > > On Aug 2, 2010, at 7:34 AM, Lowell Gilbert > > wrote: > > > Caleb Stein writes: > > > >> I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the > >> order I ran the commands in (all as root): > >> > >> cd /usr/src > >> make buildworld > >> make buildkernel > >> shutdown now > >> make installkernel > >> shutdown -r now > >> adjkerntz -i > >> mount -a -t ufs > >> mergemaster -p > >> cd /usr/src > >> make installworld > >> mergemaster > >> reboot > >> > >> But I didn't get to run the last two. When I run make > >> installworld, I > >> get errors telling me that the filesystem is full. Now, I can assure > >> you it is not. Well, basically, what I am asking is why is the > >> filesystem full after installing the new kernel? > > > > The number of kernel modules has been increasing quite quickly, and > > modules are installed with the kernel (by default). This has led to > > installkernel filling up the root filesystem increasingly often. It > > just happened to me yesterday, although in that case snapshots and > > four > > or five old kernels were part of the problem. > > > > Are you *sure* that the filesystem isn't full? > > Can you show df(1) output? > > ___ > > 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 was wrong, the filesystem was full. I did delete the old kernel > modules though, and that fixed the issue. This might not be a good idea since you might need your old kernel to boot from if anything went wrong with the new one. Probably you built your kernel with debugging symbols turned on, which will make it _much_ bigger (and slower!) Put the following line into your /etc/make.conf INSTALL_NODEBUG="yes" and try again. Greetings Peter. > ___ > 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 installworld fails
On Aug 2, 2010, at 7:34 AM, Lowell Gilbert > wrote: Caleb Stein writes: I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the order I ran the commands in (all as root): cd /usr/src make buildworld make buildkernel shutdown now make installkernel shutdown -r now adjkerntz -i mount -a -t ufs mergemaster -p cd /usr/src make installworld mergemaster reboot But I didn't get to run the last two. When I run make installworld, I get errors telling me that the filesystem is full. Now, I can assure you it is not. Well, basically, what I am asking is why is the filesystem full after installing the new kernel? The number of kernel modules has been increasing quite quickly, and modules are installed with the kernel (by default). This has led to installkernel filling up the root filesystem increasingly often. It just happened to me yesterday, although in that case snapshots and four or five old kernels were part of the problem. Are you *sure* that the filesystem isn't full? Can you show df(1) output? ___ 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 was wrong, the filesystem was full. I did delete the old kernel modules though, and that fixed the issue. ___ 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 installworld fails
Caleb Stein writes: > I am trying to update my FreeBSD 8.0 to FreeBSD 8.1. Here is the > order I ran the commands in (all as root): > > cd /usr/src > make buildworld > make buildkernel > shutdown now > make installkernel > shutdown -r now > adjkerntz -i > mount -a -t ufs > mergemaster -p > cd /usr/src > make installworld > mergemaster > reboot > > But I didn't get to run the last two. When I run make installworld, I > get errors telling me that the filesystem is full. Now, I can assure > you it is not. Well, basically, what I am asking is why is the > filesystem full after installing the new kernel? The number of kernel modules has been increasing quite quickly, and modules are installed with the kernel (by default). This has led to installkernel filling up the root filesystem increasingly often. It just happened to me yesterday, although in that case snapshots and four or five old kernels were part of the problem. Are you *sure* that the filesystem isn't full? Can you show df(1) output? ___ 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 installworld fails
--- On Sun, 8/1/10, Caleb Stein wrote: > From: Caleb Stein > Subject: make installworld fails > To: "freebsd-questions@freebsd.org" > Date: Sunday, August 1, 2010, 9:43 PM > I am trying to update my FreeBSD 8.0 > to FreeBSD 8.1. Here is the order I ran the commands > in (all as root): > > cd /usr/src > make buildworld > make buildkernel > shutdown now > make installkernel > shutdown -r now > adjkerntz -i > mount -a -t ufs > mergemaster -p > cd /usr/src > make installworld > mergemaster > reboot > > But I didn't get to run the last two. When I run make > installworld, I get errors telling me that the filesystem is > full. Now, I can assure you it is not. Well, > basically, what I am asking is why is the filesystem full > after installing the new kernel? You are supposed to make installkernel before rebooting to single user. > ___ > 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 recursion error
Hi all: Looks like those packages are mutually dependent: ===> arts-1.5.10_4,1 depends on shared library: jack - not found ===>Verifying install for jack in /usr/ports/audio/jack ===> jackit-0.116.2_4 depends on executable: doxygen - not found ===>Verifying install for doxygen in /usr/ports/devel/doxygen ===> doxygen-1.6.3_1 depends on executable: tmake - found ===> doxygen-1.6.3_1 depends on executable: dot - not found -- how could i untangle this mess? thanks --- On Wed, 4/7/10, gahn wrote: > From: gahn > Subject: make recursion error > To: "freebsd general questions" > Date: Wednesday, April 7, 2010, 5:34 PM > Hi guru: > > trying to compile /usr/ports/graphics/graphviz and running > into problems. the "make" processes kept recycling until > running out of buffer: > > - > > > > make: Max recursion level (500) exceeded.: Resource > temporarily unavailable > *** Error code 2 > Stop in /usr/ports/devel/doxygen. > *** Error code 1 > > Stop in /usr/ports/devel/doxygen. > *** Error code 1 > > Stop in /usr/ports/audio/jack. > *** Error code 1 > > Stop in /usr/ports/audio/arts. > *** Error code 1 > > Stop in /usr/ports/audio/arts. > *** Error code 1 > > Stop in /usr/ports/devel/sdl12. > *** Error code 1 > > Stop in /usr/ports/devel/sdl12. > *** Error code 1 > > Stop in /usr/ports/graphics/devil. > *** Error code 1 > > Stop in /usr/ports/graphics/devil. > *** Error code 1 > > Stop in /usr/ports/graphics/graphviz. > *** Error code 1 > > Stop in /usr/ports/graphics/graphviz. > ... > ... > ... > ... > ... > - > > how could i fix this? > > 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" > ___ 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 delete-old question (removing old binaries)
On Saturday 03 April 2010 11:04:37 Ihsan Junaidi Ibrahim wrote: > Hi folks, > > I've rebuild my world with NO_MAIL (in src.conf) and a few other NO_ > options however I noticed that related binaries are not removed > entirely i.e. mailwrapper when I ran make delete-old / > delete-old-libs. I can see that the old binaries have a timestamp > older than the binaries rebuilt by the make world process. > > [anggerik:/usr/sbin]# ls -l mailwrapper > -r-xr-xr-x 1 root wheel 7808 Nov 21 22:31 mailwrapper > [anggerik:/usr/sbin]# ls -l trac > traceroute* traceroute6* > [anggerik:/usr/sbin]# ls -l traceroute > -r-sr-xr-x 1 root wheel 28240 Apr 3 08:54 traceroute > > Is this simply a cosmetic issue and I can just remove those binaries > manually or if not so, is there a special configs needed to remove > them. > > Apologize if this question has been asked before. You should be using WITHOUT_ versions of the options - see src.conf(5). Files won't be removed unless they're listed in ObsoleteFiles.inc, and it's typically not been kept up-to-date. This is being fixed in -CURRENT but for just now you can remove the binaries manually. -- Bruce Cran ___ 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 buildworld runs out of space
On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman wrote: > I have built two machines with 8.0-STABLE-201002-amd64. When I updated > the sources and ran make buildworld process it would fail claiming > that / was full. > > It seems to be running into the problem when the make installkernel > portion of my script was running. Both machines were built using the > default of 512M for /. I rebuilt the machines with 1G / and all was > well. But one shouldn't have to do this as 512M for / should be > adequate. Yes it's adequate for *one* kernel. But it's often too limited for a couple of kernels (e.g. /boot/kernel.old and /boot/kernel). My /boot has two kernels now, and they are build with debugging symbols so they take a bit more space, but the following is a sample du run: $ du -hsx /boot/kernel* /boot 136M/boot/kernel 136M/boot/kernel.old 273M/boot $ With 273 MB for kernels, there has to be adequate space for the *rest* of the root filesystem files too. With 512 MB you are very close to having "just enough" space, but it's not certain if e.g. your /tmp already contains a few dozen MB of temporary files. As you found out, 1 GB of root filesystem space is ok for now :-) ___ 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 buildworld runs out of space
On Wed, Mar 17, 2010 at 20:08, Polytropon wrote: > On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman > wrote: >> I rebuilt the machines with 1G / and all was well. But one >> shouldn't have to do this as 512M for / should be adequate. > > It's not only the new kernel - a backup of the previous > existing kernel is kept in /boot (and so on /). If you > suppress this, all should be fine, but maybe dangerous > in case your new kernel doesn't boot as intended. > > In this case, the subject "make buildworld runs out of > space" may lead to a misunderstanding; according to what > you stated, "make installkernel" was the operation > causing the out of space problem. > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > 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" > Just a note, the default 512mb is never enough room, especially since hard drive space is negligible these days. I always use 4G for / ___ 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 buildworld runs out of space
On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman wrote: > I rebuilt the machines with 1G / and all was well. But one > shouldn't have to do this as 512M for / should be adequate. It's not only the new kernel - a backup of the previous existing kernel is kept in /boot (and so on /). If you suppress this, all should be fine, but maybe dangerous in case your new kernel doesn't boot as intended. In this case, the subject "make buildworld runs out of space" may lead to a misunderstanding; according to what you stated, "make installkernel" was the operation causing the out of space problem. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 "make install" accept defaults
> "n" == n dhert writes: n> When installing gnome from the ports n> # make install clean n> installs a few hundred packages and displays dozens and dozens times a n> configuration window n> which I always answer by hitting TAB key to move to OK button and then n> . n> Now this installation is already busy for 7 hours (when will it end?) ... n> keeping me locked to my PC ... n> How to specify make install clean .. witj extra options so that is n> will answer a configuration window autoamtically n> to always accept all the defaults so that you can make an Gnome installation n> in an unattended way? I do all the configs ahead of time. There are multiple ways to do that. "make config-recursive" if you're just using the raw Makefiles. "portinstall -c PORTNAME" if you're using Portinstall (my favorite). -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion ___ 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 "make install" accept defaults
You may also want to try "make BATCH=yes install clean" ~Brian Callahan --Original Message-- From: n dhert Sender: owner-freebsd-questi...@freebsd.org To: freebsd-questions@freebsd.org Subject: make "make install" accept defaults Sent: Mar 7, 2010 2:08 PM When installing gnome from the ports # make install clean installs a few hundred packages and displays dozens and dozens times a configuration window which I always answer by hitting TAB key to move to OK button and then . Now this installation is already busy for 7 hours (when will it end?) ... keeping me locked to my PC ... How to specify make install clean .. witj extra options so that is will answer a configuration window autoamtically to always accept all the defaults so that you can make an Gnome installation in an unattended way? ___ 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" Sent from my Verizon Wireless BlackBerry___ 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 "make install" accept defaults
Portmaster (ports-mgmt/portmaster) will help you do that. - Sincerely, Dan Naumov ___ 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 doesn't see changes in /etc/mail/freebsd.mc
On Thu, 28 Jan 2010 16:59:16 +, Anton Shterenlikht wrote: > I've seen this behaviour for years, but never bothered > to ask why. > > Imagine I already have in /etc/mail local .mc and .cf files. Imagine I > then update freebsd.mc. When I run make nothing happens. What I think > should happen is that local .mc should be updated and then .cf > generated. > > Because of this behaviour I have to manually delete local .mc files > and all .cf files before running make. Or merge your local changes *into* the "local.mc" file. For example, I have several dozen lines of local customizations in "HOSTNAME.mc" here: r...@kobe:/etc/mail# diff -u freebsd.mc kobe.mc | diffstat -p1 kobe.mc | 167 1 file changed, 126 insertions(+), 41 deletions(-) I would be very annoyed if updating freebsd.mc clobbered these :-) ___ 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 doesn't see changes in /etc/mail/freebsd.mc
On Jan 28, 2010, at 9:11 AM, Anton Shterenlikht wrote: >> Because your carefully crafted local .mc files shouldn't be clobbered >> whenever freebsd.mc is updated? > > I see.. so you are saying that freebsd.mc shouldn't even be > touched at all, all local chages should be made straight > to local .mc? Please see /etc/mail/Makefile: # # This Makefile uses `.mc' as the default MTA .mc file. This # can be changed by defining SENDMAIL_MC in /etc/make.conf, e.g.: # # SENDMAIL_MC=/etc/mail/myconfig.mc # # If '.mc' does not exist, it is created using 'freebsd.mc' # as a template. Regards, -- -Chuck ___ 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 doesn't see changes in /etc/mail/freebsd.mc
On Thu, Jan 28, 2010 at 05:03:26PM +, Chris Rees wrote: > On 28 January 2010 16:59, Anton Shterenlikht wrote: > > I've seen this behaviour for years, but never bothered > > to ask why. > > > > Imagine I already have in /etc/mail local .mc and .cf > > files. Imagine I then update freebsd.mc. When I run make > > nothing happens. What I think should happen is that > > local .mc should be updated and then .cf generated. > > > > Because of this behaviour I have to manually delete > > local .mc files and all .cf files before running make. > > > > Any comments? > > > > many thanks > > anton > > > > Because your carefully crafted local .mc files shouldn't be clobbered > whenever freebsd.mc is updated? I see.. so you are saying that freebsd.mc shouldn't even be touched at all, all local chages should be made straight to local .mc? thank you -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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 doesn't see changes in /etc/mail/freebsd.mc
On 28 January 2010 16:59, Anton Shterenlikht wrote: > I've seen this behaviour for years, but never bothered > to ask why. > > Imagine I already have in /etc/mail local .mc and .cf > files. Imagine I then update freebsd.mc. When I run make > nothing happens. What I think should happen is that > local .mc should be updated and then .cf generated. > > Because of this behaviour I have to manually delete > local .mc files and all .cf files before running make. > > Any comments? > > many thanks > anton > Because your carefully crafted local .mc files shouldn't be clobbered whenever freebsd.mc is updated? Chris ___ 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 delete-old && make delete-old-libs
Matthew Seaman wrote: >mikel king wrote: >> I had a system that was royally borked after upgrading and completing >> these steps a few years ago. Ever since I have always skipped these >> steps. Has anyone else experienced any issues with these two steps? > What do you mean by "borked"? If you mean that you had to temporarily take it out of service while you rebuilt ports and other software, and adjusted configuration files, well, that is probably to be expected during a major upgrade. >make delete-old-libs can cause you much wailing and gnashing of teeth >if you do it too soon, but usually only when you're doing a major version >upgrade. In those circumstances, unless you're careful, all or large >parts of your software installed from ports will cease to work. Delete >the old libraries only once you've finished reinstalling all of your ported >software. Major >version upgrades are one of the few times when there will >be old shlibs to consider deleting, so this is a rare event. On the whole, I think it is better to remove all of the old files, libraries, and ports first, and only then rebuild in a clean sandbox, rather than run the risk of including an old header or linking to an old base system library that will soon be discarded. In any event, if you must keep old ports around, at least temporarily, in most cases you can still use them if you have the appropriate COMPAT_FREEBSD? options in your kernel, and the corresponding misc/compat?x ports installed. And for other cases you can use libmap.conf(5). So you may as well run make delete-old-libs before rebuilding ports. > >make delete-old can theoretically cause you grief if you overwrite bits >of the base system from ports and set corresponding WITHOUT_FOO flags in >/etc/src.conf. On the whole, having ports overwrite base is something to >be avoided unless you have very good reason to do it. > Indeed. >Whether this will sting you or not is an interesting question: it depends >on developers adding files and directories to the list of old items >conditionally on defining WITHOUT_FOO type flags in /etc/src.conf. While >this has the intuitively attractive behaviour that doing a buildworld cycle >removes the >unwanted programs or libraries, unfortunately it doesn't stop >there. It will remove your carefully installed ported software the following >time you do a buildworld cycle. For this reason, settings in src.conf >do not generally affect the list of old files and directories nowadays. This is wrong: they often do. To see if the files you have may be affected by options in src.conf, look at /usr/src/tools/build/mk/OptionalObsoleteFiles.inc, or run 'make check-old'. And if you are using -CURRENT, be aware that this file is now being updated. In any event, make-delete-old-[libs] is interactive, if you have not defined BATCH_DELETE_OLD_FILES, and you can choose to prevent some files from being removed on the command-line. And of course, you are not obliged to run these targets, but you are probably better off doing so, or cleaning your base system by other means, to avoid pollution. If you've files or links in directories normally reserved for the base system that you want to preserve, you could just write a script to use find(1) to look for files, directories, or links that are older than your freshly-installed files in these directories, ignore those you want to keep, and delete the rest. Some parts of the base system, particularly some header files, are installed with old timestamps, but you can just run make installworld again after running your script, and your base system will be then be clean and up-to-date. b. ___ 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 delete-old && make delete-old-libs
mikel king wrote: I had a system that was royally borked after upgrading and completing these steps a few years ago. Ever since I have always skipped these steps. Has anyone else experienced any issues with these two steps? make delete-old-libs can cause you much wailing and gnashing of teeth if you do it too soon, but usually only when you're doing a major version upgrade. In those circumstances, unless you're careful, all or large parts of your software installed from ports will cease to work. Delete the old libraries only once you've finished reinstalling all of your ported software. Major version upgrades are one of the few times when there will be old shlibs to consider deleting, so this is a rare event. make delete-old can theoretically cause you grief if you overwrite bits of the base system from ports and set corresponding WITHOUT_FOO flags in /etc/src.conf. On the whole, having ports overwrite base is something to be avoided unless you have very good reason to do it. Whether this will sting you or not is an interesting question: it depends on developers adding files and directories to the list of old items conditionally on defining WITHOUT_FOO type flags in /etc/src.conf. While this has the intuitively attractive behaviour that doing a buildworld cycle removes the unwanted programs or libraries, unfortunately it doesn't stop there. It will remove your carefully installed ported software the following time you do a buildworld cycle. For this reason, settings in src.conf do not generally affect the list of old files and directories nowadays. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: make delete-old question
On Thu, Dec 10, 2009 at 08:54:19AM +0100, Rolf G Nielsen wrote: > > Frank Shute wrote: > >Hi, > > > >Successfully upgraded from 7.2 to 8.0 but had my usual problem when > >jumping major versions with the make delete-old target. > > > >The problem being that it asks me to confirm deletion of each lib/file > >with a "y" and a return. I've found that I never say "n" to any > >deletion and it becomes very tedious to hammer at the keyboard for > >hundreds of libs/files. > > > >Is there a way to change the Makefile so that they all get deleted > >with just one "y" and a return? Or possibly use yes(1) to script it? > > > >TIA. > > > >Regards, > > > > yes | make delete-old Thanks Rolf, I hoped it would be something simple. Now I'll update my laptop. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: make delete-old question
> Is there a way to change the Makefile so that they all get deleted > with just one "y" and a return? Or possibly use yes(1) to script it? I often yes | make delete-old Olivier ___ 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 delete-old question
Frank Shute wrote: Hi, Successfully upgraded from 7.2 to 8.0 but had my usual problem when jumping major versions with the make delete-old target. The problem being that it asks me to confirm deletion of each lib/file with a "y" and a return. I've found that I never say "n" to any deletion and it becomes very tedious to hammer at the keyboard for hundreds of libs/files. Is there a way to change the Makefile so that they all get deleted with just one "y" and a return? Or possibly use yes(1) to script it? TIA. Regards, yes | make delete-old ___ 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 installkernel KERNCONF= faults with error
On Wed, 22 Jul 2009 19:11:14 +0300, Anton wrote: > >Hello freebsd-questions, > >It says that there is no libbsm Check that all your sorces are complete and of the same version. The libbsm is part of openbsm - /usr/src/contrib/openbsm/. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 command fails and portupgrade fails
On Fri, Jul 17, 2009 at 12:07 AM, Romeo Paras wrote: > may i know the command or the exact command for this? is it " portupgrade > -fa -k? > On Fri, Jul 17, 2009 at 12:07 AM, Romeo Paras wrote: > may i know the command or the exact command for this? is it " portupgrade > -fa -k? > I suppose that would work. Or, 'portupgrade -fak' (which speaking in terms of internet memes, has 'fail' written all over it). I don't use any automated port building tools. I would try rebuilding the offending port manually, as I had initially suggested. -- Glen Barber ___ 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 command fails and portupgrade fails
may i know the command or the exact command for this? is it " portupgrade -fa -k? On Fri, Jul 17, 2009 at 11:59 AM, Glen Barber wrote: > On Thu, Jul 16, 2009 at 11:16 PM, Romeo Paras wrote: > > Please find the error below when I am trying to update my ports after I > > rebuild my kernel.. please help.// thanks > > > > > > > > > > ===> Installing rc.d startup script(s) > > ===> Compressing manual pages for quagga-0.99.12 > > ===> Running ldconfig > > /sbin/ldconfig -m /usr/local/lib > > ===> Registering installation for quagga-0.99.12 > > ===> SECURITY REPORT: > > This port has installed the following files which may act as network > > servers and may therefore pose a remote security risk to the system. > > /usr/local/lib/libzebra.so.0 > > /usr/local/sbin/zebra > > /usr/local/lib/libospfapiclient.so.0 > > /usr/local/sbin/ripd > > > > This port has installed the following startup scripts which may > cause > > these network services to be started at boot time. > > /usr/local/etc/rc.d/quagga > > /usr/local/etc/rc.d/watchquagga > > > > If there are vulnerabilities in these programs there may be a > security > > risk to the system. FreeBSD makes no guarantee about the security of > > ports included in the Ports Collection. Please type 'make deinstall' > > to deinstall the port if this is a concern. > > > > For more information, and contact details about the security > > status of this software, see the following webpage: > > http://quagga.net/ > > ===> Cleaning for quagga-0.99.12 > > ---> Cleaning out obsolete shared libraries > > [Updating the pkgdb in /var/db/pkg ... - 23 packages > > found (-0 +1) . done] > > ---> Skipping 'ports-mgmt/portupgrade' (portupgrade-2.4.6_2,2) because a > > requisite package 'ruby18-bdb-0.6.5_1' (databases/ruby-bdb) failed > (specify > > -k to force) > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > >! lang/ruby18 (ruby-1.8.7.160_1,1) (unknown build error) > >* databases/ruby-bdb (ruby18-bdb-0.6.5_1) > >* ports-mgmt/portupgrade (portupgrade-2.4.6_2,2) > > Hi, > > Have you tried to manually upgrade databases/ruby-bdb ? Or, as the > error suggests, you can specify '-k' to force it to upgrade the port. > > > > -- > Glen Barber > ___ 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 command fails and portupgrade fails
On Thu, Jul 16, 2009 at 11:16 PM, Romeo Paras wrote: > Please find the error below when I am trying to update my ports after I > rebuild my kernel.. please help.// thanks > > > > > ===> Installing rc.d startup script(s) > ===> Compressing manual pages for quagga-0.99.12 > ===> Running ldconfig > /sbin/ldconfig -m /usr/local/lib > ===> Registering installation for quagga-0.99.12 > ===> SECURITY REPORT: > This port has installed the following files which may act as network > servers and may therefore pose a remote security risk to the system. > /usr/local/lib/libzebra.so.0 > /usr/local/sbin/zebra > /usr/local/lib/libospfapiclient.so.0 > /usr/local/sbin/ripd > > This port has installed the following startup scripts which may cause > these network services to be started at boot time. > /usr/local/etc/rc.d/quagga > /usr/local/etc/rc.d/watchquagga > > If there are vulnerabilities in these programs there may be a security > risk to the system. FreeBSD makes no guarantee about the security of > ports included in the Ports Collection. Please type 'make deinstall' > to deinstall the port if this is a concern. > > For more information, and contact details about the security > status of this software, see the following webpage: > http://quagga.net/ > ===> Cleaning for quagga-0.99.12 > ---> Cleaning out obsolete shared libraries > [Updating the pkgdb in /var/db/pkg ... - 23 packages > found (-0 +1) . done] > ---> Skipping 'ports-mgmt/portupgrade' (portupgrade-2.4.6_2,2) because a > requisite package 'ruby18-bdb-0.6.5_1' (databases/ruby-bdb) failed (specify > -k to force) > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > ! lang/ruby18 (ruby-1.8.7.160_1,1) (unknown build error) > * databases/ruby-bdb (ruby18-bdb-0.6.5_1) > * ports-mgmt/portupgrade (portupgrade-2.4.6_2,2) Hi, Have you tried to manually upgrade databases/ruby-bdb ? Or, as the error suggests, you can specify '-k' to force it to upgrade the port. -- Glen Barber ___ 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"
