[PATCH] Portsnap - set a good umask, for ports consistancy
Hi, I have a case where some users have different umasks (0077 in some cases). When these users call portsnap (via sudo), it leaves the port- directories permissions in an inconsistent state, and people need to use sudo to list files. I'm not sure honoring "umask" is good from a users-perspective, even if umask is a standard UNIX mechanism of directory and file permissions. I suggest setting a reasonable umask, for the duration of the portsnap program. As far as I know, this should only effect /usr/ports, and if a user wishes to "hide" the contents of this folder, a manual chmod of it should not be overridden, until /usr/ports is completely removed and recreated. If this is a bad suggestion, would it be feasible to make it a config- option? BTW, I really like portsnap - it is a great program. Also I'd like to note that I am very happy with speed from european mirrors these days, which I've been grunting about earlier. Thanks for the effort you put into this! :) Best regards, Daniel Bond. Begin forwarded message: From: Daniel Bond Date: August 25, 2009 10:28:58 AM GMT+02:00 To: d...@danielbond.org Subject: [PATCH] Portsnap - set a good umask, for ports consistancy PGP.sig Description: This is a digitally signed message part
Re: fix ntptrace man page
On Tue, 2009-08-25 at 04:58 +0200, Oliver Pinter wrote: > Hi all! > > It's a small fix to ntpdate man page for freebsd 7-stable. I was looking at this a few days ago. The problem is not that the man page is wrong, it's that the man page documents an entirely different tool. For some reason, FreeBSD provides it's own version of ntptrace which lacks anything but the basic functionality, whereas the man page installed is that of the ntptrace tool as supplied in the ntpd distribution. It would seem much more sensible to use the official ntptrace and retain all the functionality people expoect from ntptrace, although I haven't yet found time to get to the bottom of why this was switched over from the official code in the first place. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PATCH] Portsnap - set a good umask, for ports consistancy
Sorry, seems the patch was not included. when I forwarded mail. I've attached it to this mail. Cheers! portsnap.umask.patch Description: Binary data On Aug 25, 2009, at 10:40 AM, Daniel Bond wrote: Hi, I have a case where some users have different umasks (0077 in some cases). When these users call portsnap (via sudo), it leaves the port-directories permissions in an inconsistent state, and people need to use sudo to list files. I'm not sure honoring "umask" is good from a users-perspective, even if umask is a standard UNIX mechanism of directory and file permissions. I suggest setting a reasonable umask, for the duration of the portsnap program. As far as I know, this should only effect /usr/ ports, and if a user wishes to "hide" the contents of this folder, a manual chmod of it should not be overridden, until /usr/ports is completely removed and recreated. If this is a bad suggestion, would it be feasible to make it a config-option? BTW, I really like portsnap - it is a great program. Also I'd like to note that I am very happy with speed from european mirrors these days, which I've been grunting about earlier. Thanks for the effort you put into this! :) Best regards, Daniel Bond. Begin forwarded message: From: Daniel Bond Date: August 25, 2009 10:28:58 AM GMT+02:00 To: d...@danielbond.org Subject: [PATCH] Portsnap - set a good umask, for ports consistancy PGP.sig Description: This is a digitally signed message part
Re: portmaster not ask for port deletion
On Mon, 24 Aug 2009 12:54:54 -0700 Doug Barton wrote: > Nenhum_de_Nos wrote: > > hail, > > > > portmaster is great, but this is keeping me from using it.I want to fire a > > portmaster -af and let it there until its done. for every package it asks > > this. is ther any way to make it not ask ? delete and go ahead ? > > You really want to read the man page thoroughly before you begin using > portmaster. I've taken a lot of time to try and explain how it works > in the man page, and what your options are. In particular, you > probably do not really want to use the -f option on a regular basis > since that does not do what it does in portupgrade. In portmaster > using '-af' would rebuild all of your ports, not just the ones that > need upgrading. that's just what I was looking for. after the library bumps that happened after BETA2, I'd like to rebuild all :) > It sounds to me like what you're seeing is portmaster asking whether > or not you want to delete the distfiles after an upgrade. The easiest > way to deal with that is to use '-aD' and then when it's done use > either --clean-distfiles or --clean-distfiles-all. Once again, see the > man page for more information on those options. I just want to fire the command and it work alone till is done. > hope this helps, it sure did :) thanks matheus > Doug > > -- > > This .signature sanitized for your protection > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: named stop not stopping
Guy Helmer wrote: Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. Thanks, LB Has named's rc script worked OK before? If not, it might be a config problem like mine. I found that after I added pid-file"/var/run/named/pid"; to the options section of my named.conf file, the rc script was able to stop/restart a running named process. The named script in /etc/rc.d has been working just fine. We think named got wedged and the script could not kill it for some reason. We had to do a kill -9 to make it stop. Then /etc/rc.d/named start worked just fine and the stop has been working fine. LB ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portmaster not ask for port deletion
Nenhum_de_Nos wrote: > that's just what I was looking for. after the library bumps that happened > after BETA2, I'd like to rebuild all :) There is an extensive writeup in the EXAMPLES section of the man page on how to rebuild all of your ports. I don't actually recommend that people use '-af' for that, although in theory it should work. Good luck, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fix ntpd man page
please drop the 20090825051910-ntpd_man_fix.diff patch, and use this: 20090825161558-ntpd_man_debug_fix.diff (attached) this attached patch fixed the documented man options, and runs correct: --8<-- # ntpd - ntpd 4.2.4p5-a Tue Aug 25 16:18:59 CEST 2009 (1) adding new filegen adding new filegen adding new filegen adding new filegen adding new filegen adding new filegen addto_syslog: set_process_priority: Leave priority alone: priority_done is <2> addto_syslog: precision = 0.698 usec create_sockets(123) addto_syslog: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20 addto_syslog: bind() fd 20, family 2, port 123, addr 0.0.0.0, in_classd=0 flags= 0x89 fails: Address already in use addto_syslog: unable to bind to wildcard socket address 0.0.0.0 - another proces s may be running - EXITIN --8<-- On 8/25/09, Oliver Pinter wrote: > Hi all! > > It's one more fix to ntp program set, ntpd man page for freebsd 7-stable. > commit 18001be3bcb3f48f77d87502373f4dbc4683c1dd Author: opv Date: Tue Aug 25 16:15:58 2009 +0200 fix ntpq -d options add -DDEBUG as the header say... #ifdef DEBUG #define VALUE_OPT_DEBUG_LEVEL'd' #endif /* DEBUG */ #ifdef DEBUG #define VALUE_OPT_SET_DEBUG_LEVEL 'D' #endif /* DEBUG */ after this patch, the ntpq running as the man say Signed-off-by : Oliver Pinter diff --git a/usr.sbin/ntp/Makefile.inc b/usr.sbin/ntp/Makefile.inc index f81905a..71e2a57 100644 --- a/usr.sbin/ntp/Makefile.inc +++ b/usr.sbin/ntp/Makefile.inc @@ -2,7 +2,7 @@ .include -DEFS_LOCAL= -DPARSE -DHAVE_CONFIG_H +DEFS_LOCAL= -DPARSE -DHAVE_CONFIG_H -DDEBUG NTPDEFS= -DSYS_FREEBSD # CLOCKDEFS= # -DLOCAL_CLOCK -DPST -DWWVB -DAS2201 -DGOES -DGPSTM -DOMEGA \ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: named stop not stopping
Doug Barton wrote: Lisa Besko wrote: We had an issue with the /etc/rc.d/named script this morning where it looped/hung in the wait_for_pids subroutine. We run a job to restart named which calls the /etc/rc.d/named script with a stop command. For some reason named did not stop properly and the process continued to list PIDs from the wait_for_pids subroutine forever. Has anyone ever encountered this before? We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. First, please verify that you have the latest version of /etc/rc.d/named installed. Second, this could happen if the call in that script to rndc succeeded, but for some reason rndc was not able to actually kill the binary. In that case there should be something in the logs that indicates what the problem is. I'm running a current supported version of bind. It's the one that was included with 7.2 stable and has been patched. The only thing I see in my logs is the icmp unreach message but that does not start until after the named stop command was issued. kernel: Limiting icmp unreach response from 259 to 200 packets/sec Currently we changed the way we run our restart script to do a kill -9 if all else fails. The /etc/rc.d/named script uses a kill -TERM if the original rcnd stop fails. In this case that wasn't enough. Thanks for the input. -- Lisa Besko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fix ntptrace man page
funny, in /usr/src/usr.sbin/ntp/scripts/ntptrace implemented only the -n switch On 8/25/09, Gavin Atkinson wrote: > On Tue, 2009-08-25 at 04:58 +0200, Oliver Pinter wrote: >> Hi all! >> >> It's a small fix to ntpdate man page for freebsd 7-stable. > > I was looking at this a few days ago. The problem is not that the man > page is wrong, it's that the man page documents an entirely different > tool. For some reason, FreeBSD provides it's own version of ntptrace > which lacks anything but the basic functionality, whereas the man page > installed is that of the ntptrace tool as supplied in the ntpd > distribution. It would seem much more sensible to use the official > ntptrace and retain all the functionality people expoect from ntptrace, > although I haven't yet found time to get to the bottom of why this was > switched over from the official code in the first place. > > Gavin > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fix ntptrace man page
On 8/25/09, Oliver Pinter wrote: > funny, in /usr/src/usr.sbin/ntp/scripts/ntptrace implemented only the -n > switch > > > On 8/25/09, Gavin Atkinson wrote: >> On Tue, 2009-08-25 at 04:58 +0200, Oliver Pinter wrote: >>> Hi all! >>> >>> It's a small fix to ntpdate man page for freebsd 7-stable. >> >> I was looking at this a few days ago. The problem is not that the man >> page is wrong, it's that the man page documents an entirely different >> tool. For some reason, FreeBSD provides it's own version of ntptrace >> which lacks anything but the basic functionality, whereas the man page >> installed is that of the ntptrace tool as supplied in the ntpd >> distribution. It would seem much more sensible to use the official >> ntptrace and retain all the functionality people expoect from ntptrace, >> although I haven't yet found time to get to the bottom of why this was >> switched over from the official code in the first place. the ntpd code is under the contrib dir, but the ntptrace script is freebsds own script >> >> Gavin >> > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RESOLVED: Fatal trap 30 w/ latest 8.0-BETA2/amd64
on 23/08/2009 22:50 Jason Harmening said the following: > So after blindly posting to the list, I took some time to figure out > what FreeBSD uses trap code 30 for--turns out some misbehaving PCIe > hardware was firing an MSI to an unassigned vector. Switching it to > legacy interrupts fixed the problem. Sorry for the spam. Jason, could you please share your technique/experience for tracking this down? Thank you! -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fix ntptrace man page
On Tue, Aug 25, 2009 at 04:44:32PM +0200, Oliver Pinter wrote: > On 8/25/09, Oliver Pinter wrote: > > funny, in /usr/src/usr.sbin/ntp/scripts/ntptrace implemented only the -n > > switch > > > > > > On 8/25/09, Gavin Atkinson wrote: > >> On Tue, 2009-08-25 at 04:58 +0200, Oliver Pinter wrote: > >>> Hi all! > >>> > >>> It's a small fix to ntpdate man page for freebsd 7-stable. > >> > >> I was looking at this a few days ago. The problem is not that the man > >> page is wrong, it's that the man page documents an entirely different > >> tool. For some reason, FreeBSD provides it's own version of ntptrace > >> which lacks anything but the basic functionality, whereas the man page > >> installed is that of the ntptrace tool as supplied in the ntpd > >> distribution. It would seem much more sensible to use the official > >> ntptrace and retain all the functionality people expoect from ntptrace, > >> although I haven't yet found time to get to the bottom of why this was > >> switched over from the official code in the first place. > the ntpd code is under the contrib dir, but the ntptrace script is > freebsds own script This is not true. The script comes with ntpd. The old version of ntptrace was replaced (in the ntpd tree) when ipv6 support was added. The reason was that the old version assumed that the refid field was an ip address. This was never part of the spec and was not true in a mixed ipv4/ipv6 setup. (Just because you use ipv4 to get to ntp server A, does not mean that it used ipv4 to sync from its upstream server.) The ntptrace html/man docs was just not updated. John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portmaster not ask for port deletion
Nenhum_de_Nos wrote: > On Mon, 24 Aug 2009 12:54:54 -0700 > Doug Barton wrote: > > > It sounds to me like what you're seeing is portmaster asking whether > > or not you want to delete the distfiles after an upgrade. The easiest > > way to deal with that is to use '-aD' and then when it's done use > > either --clean-distfiles or --clean-distfiles-all. Once again, see the > > man page for more information on those options. > > I just want to fire the command and it work alone till is done. Good luck with unattended runs of portmaster. That's the only real remaining shortfall of portmaster, IMO. It still needs hand-holding to finish its job often times. For example, I just did the big rebuild you're getting ready for. I spent a good 45 minutes updating ports.conf beforehand, fetching a good number of distfiles in advance, and configuring ports before starting the massive build. I also told portmaster to ignore 3 ports (1 broken, 2 would most likely fail to build for one reason or another.) So, I started the build and left. Came back 7 hours later and portmaster had barely run an hour and was stuck waiting for input. What was so important? It wanted to know if it should go ahead an update the 3 ports that I had just explicitly told it not to upgrade 10 minutes before I started it (by using .IGNOREME files). Of course I don't want it to upgrade them anyway. If I wanted them upgraded, I wouldn't have installed IGNOREME files. So, portmaster still needs some hand-holding compared to other tools. But, it still beats portupgrade IMO. -- Skip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RELENG_6 build failures
Hi, I was trying to run a make universe on RELENG_6 and found: 1) alpha doesn't build 2) powerpc LINT fails with: config: Error: device "zs" is unknown 3) sparc64 LINT fails with: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/tmp/usr/include -I/obj/sparc64/RELENG_6.svn/sys/LINT /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c:418:21: ukbdmap.h: No such file or directory At least (3) should be a supported platform but given that universe builds the other two as well I would assume they are as well. amd64, i386, pc98, ia64 were ok, the GENERIC kernels seems to be fine for powerpc and sparc64. alpha as said seems dead. I have no idea why we never saw the errors flying by, so I don't want to rule out a local problem. In case anyone could confirm these findings (or fix them should they exist) that would be great. I had run: make -j8 universe __MAKE_CONF=/dev/null /bz -- Bjoern A. Zeeb What was I talking about and who are you again? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portmaster not ask for port deletion
Skip Ford wrote: > Nenhum_de_Nos wrote: >> On Mon, 24 Aug 2009 12:54:54 -0700 >> Doug Barton wrote: >> >>> It sounds to me like what you're seeing is portmaster asking whether >>> or not you want to delete the distfiles after an upgrade. The easiest >>> way to deal with that is to use '-aD' and then when it's done use >>> either --clean-distfiles or --clean-distfiles-all. Once again, see the >>> man page for more information on those options. >> I just want to fire the command and it work alone till is done. > > Good luck with unattended runs of portmaster. That's the only real > remaining shortfall of portmaster, IMO. It still needs hand-holding > to finish its job often times. Yes, unfortunately it's not omniscient. :) > For example, I just did the big rebuild you're getting ready for. > I spent a good 45 minutes updating ports.conf beforehand, fetching a good > number of distfiles in advance, and configuring ports before starting the > massive build. I also told portmaster to ignore 3 ports (1 broken, 2 > would most likely fail to build for one reason or another.) > > So, I started the build and left. Came back 7 hours later and portmaster > had barely run an hour and was stuck waiting for input. What was so > important? It wanted to know if it should go ahead an update the 3 ports > that I had just explicitly told it not to upgrade 10 minutes before I > started it (by using .IGNOREME files). First, you mean +IGNOREME files, just to be sure no one is confused. Second, without knowing what command line you used I couldn't tell you for sure what happened of course, but assuming you used some combination of '-af' what you saw was expected behavior. There is a conflict (I think a fairly obvious one) between the -f option and +IGNOREME. Since different users would have different ideas of how to resolve that conflict, portmaster takes the safe path and asks you. You only have to answer the question once, during the config phase. Once it starts building things you should not have any more prompts from portmaster. Looking at the man page I see that the dividing line between when to expect interaction and when not to is not as clear as it could be. I'll update that for the next version. In any case, I find it highly unlikely that it ran for a full hour before prompting for the answer. On my system with over 500 ports installed the full run through the config phase takes just a little over 6 minutes. It might take you a little longer than that if you have a lot of OPTIONS dialogs to make choices on, but those would have been pretty obvious. My guess is that you literally started it and walked away. Portmaster does everything it can to get all of the user interaction out of the way in the config phase so that once it starts building there is nothing for the user to do. Of course if there is a problem in the ports infrastructure itself portmaster can't help with that but obviously the goal is to keep those to a minimum. :) hope this helps, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portmaster not ask for port deletion
Doug Barton wrote: > Skip Ford wrote: > > Nenhum_de_Nos wrote: > >> On Mon, 24 Aug 2009 12:54:54 -0700 > >> Doug Barton wrote: > >> > >>> It sounds to me like what you're seeing is portmaster asking whether > >>> or not you want to delete the distfiles after an upgrade. The easiest > >>> way to deal with that is to use '-aD' and then when it's done use > >>> either --clean-distfiles or --clean-distfiles-all. Once again, see the > >>> man page for more information on those options. > >> I just want to fire the command and it work alone till is done. > > > > Good luck with unattended runs of portmaster. That's the only real > > remaining shortfall of portmaster, IMO. It still needs hand-holding > > to finish its job often times. > > Yes, unfortunately it's not omniscient. :) Well, to be honest, it wouldn't need to be. It would just need a flag to know when nobody is present from whom to request input, and then take the default action. But, if all input is requested during config, then that's pointless. > > For example, I just did the big rebuild you're getting ready for. > > I spent a good 45 minutes updating ports.conf beforehand, fetching a good > > number of distfiles in advance, and configuring ports before starting the > > massive build. I also told portmaster to ignore 3 ports (1 broken, 2 > > would most likely fail to build for one reason or another.) > > > > So, I started the build and left. Came back 7 hours later and portmaster > > had barely run an hour and was stuck waiting for input. What was so > > important? It wanted to know if it should go ahead an update the 3 ports > > that I had just explicitly told it not to upgrade 10 minutes before I > > started it (by using .IGNOREME files). > > First, you mean +IGNOREME files, just to be sure no one is confused. > > Second, without knowing what command line you used I couldn't tell you > for sure what happened of course, but assuming you used some > combination of '-af' what you saw was expected behavior. There is a > conflict (I think a fairly obvious one) between the -f option and > +IGNOREME. Since different users would have different ideas of how to > resolve that conflict, portmaster takes the safe path and asks you. Well, it wasn't immediately obvious to me that someone would ever want to mark a port ignore and then want to upgrade it. So, it just seemed like a silly question to me (and still does to be honest, unless that's the behavior of portupgrade you're trying to match.) > You only have to answer the question once, during the config phase. > Once it starts building things you should not have any more prompts > from portmaster. > > Looking at the man page I see that the dividing line between when to > expect interaction and when not to is not as clear as it could be. > I'll update that for the next version. No, that was clear enough. The behavior I saw was documented, I just didn't see the ambiguity in IGNOREME in advance so I didn't read the fine print until I was trying to figure out how my big plan went so wrong. Your code worked as documented. I just expected the presence of an IGNOREME file to always mean, "the port will be ignored for all purposes." > In any case, I find it highly unlikely that it ran for a full hour > before prompting for the answer. On my system with over 500 ports > installed the full run through the config phase takes just a little > over 6 minutes. It might take you a little longer than that if you > have a lot of OPTIONS dialogs to make choices on, but those would have > been pretty obvious. I was just giving a guess at an hour. I wasn't here. :) That "hour" (out of the 7 I was gone) was supposed to mean that it didn't run for very long. > My guess is that you literally started it and walked away. In the end, that has to be what happened. I spent 45 minutes going through several config runs of portmaster and/or configuring ports by hand. Once I knew I had everything configured, I launched it for the final time and left. So, it probably ran for 2 minutes, not an hour. I screwed that up and I also didn't prevent the recursive make config on the final run which sounded after the fact like it would've helped. But, besides that, the upgrade was painless. Everything built, installed, and works. Pretty amazing all things considered. -- Skip ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portmaster not ask for port deletion
On Tue, 25 Aug 2009 07:28:48 -0700 Doug Barton wrote: > Nenhum_de_Nos wrote: > > > that's just what I was looking for. after the library bumps that happened > > after BETA2, I'd like to rebuild all :) > > There is an extensive writeup in the EXAMPLES section of the man page > on how to rebuild all of your ports. I don't actually recommend that > people use '-af' for that, although in theory it should work. yeah, I got bad luck. kBuild won't build in my machine. I had this before and just reinstalling solved. even pkg_delete -a didn't helped :( thanks, matheus > Good luck, > > Doug > > -- > > This .signature sanitized for your protection > -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
