Re: SuperMicro i7 (UP) - very slow performance
On Sep 20, 6:17 am, peterjer...@acm.org (Peter Jeremy) wrote: > On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote: > > >I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and > >it is nowhere near the performance it should be. A buildworld just > >took 22.5 hours! > > That does sound a bit poor. I presume the system was basically unloaded > during the buildworld. > > Can we see the output of: > - vmstat -i interrupt total rate irq1: atkbd0 853 0 irq16: uhci0 mpt0 117706 0 irq17: fwohci0 1 0 irq23: uhci3 ehci122 0 cpu0: timer 1046064200 1979 irq256: em0 1861363 3 irq258: ahci03922875 7 cpu1: timer 1046058992 1979 cpu4: timer 1046056958 1979 cpu3: timer 1046058951 1979 cpu2: timer 1046055416 1979 cpu6: timer 1046057518 1979 cpu5: timer 1046058850 1979 cpu7: timer 1046058744 1979 Total 8374372449 15850 > - zpool status -v pool: data state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/hitachi0 ONLINE 0 0 0 gpt/hitachi1 ONLINE 0 0 0 errors: No known data errors pool: ext1 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM ext1ONLINE 0 0 0 da2 ONLINE 0 0 0 errors: No known data errors pool: storage state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/samsung0 ONLINE 0 0 0 gpt/samsung1 ONLINE 0 0 0 gpt/samsung2 ONLINE 0 0 0 gpt/samsung3 ONLINE 0 0 0 errors: No known data errors pool: system state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM system ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors > - df -k Filesystem 1024-blocks Used Avail Capacity Mounted on system 142091977 611793 141480184 0%/ devfs 1 1 0 100%/dev linprocfs 4 4 0 100%/ compat/linux/proc storage 2729825067 38 2729825028 0%/ storage storage/archive 2959080344 229255316 2729825028 8%/ storage/archive storage/backups 2906677465 176852436 2729825028 6%/ storage/backups data 18178233122487426 1815335886 0%/ storage/data data/Pictures 1912868417 97532531 1815335886 5%/ storage/data/Pictures storage/files 2794105921 64280893 2729825028 2%/ storage/files storage/incoming 3712303044 982478016 272982502826%/ storage/incoming storage/media 2835215837 105390809 2729825028 4%/ storage/media storage/media/Games 2752775684 22950655 2729825028 1%/ storage/media/Games storage/media/Movies 3745007442 1015182414 272982502827%/ storage/media/Movies storage/media/Music 2811591585 81766557 2729825028 3%/ storage/media/Music system/usr 142342976 862792 141480184 1%/usr system/usr/home142105804 625620 141480184 0%/usr/ home system/usr/obj 1432963121816128 141480184 1%/usr/ obj system/usr/ports 142059536 579352 141480184 0%/usr/ ports system/usr/src 141792965 312781 141480184 0%/usr/ src system/var 141715785 235601 141480184 0%/var /dev/md0 19566 12 19554 0%/tmp ext1 1092323986 25 1092323960 0%/mnt ext1/data 10948113902487429 1092323960 0%/mnt/ data ext1/data/Pictures1189727469 97403509 1092323960 8%/mnt/ data/Pictures ext1/storage 1092323987 27 1092323960 0%/mnt/ storage ext1/storage/backups 1269282867 176958906 109232396014%/mnt/ storage/backups ext1/storage/files1156645316 64321355 1092323960 6%/mnt/ storage/files ext1/system 1092935755 611794 1092323960 0%/mnt/ system ext1/system/usr
Re: BIND9 built w/--disable-ipv6 on 8.1-STABLE
On Tue, Sep 21, 2010 at 12:15:17PM -0700, Kevin Oberman wrote: > > Date: Tue, 21 Sep 2010 11:06:43 -0700 > > From: Doug Barton > > Sender: owner-freebsd-sta...@freebsd.org > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > On 9/21/2010 4:43 AM, Mark Kamichoff wrote: > > | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > > |> | Although, that still does beg the question, > > |> > > |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question > > | > > | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > > > > Yes, especially the last bit, "Usage commentators have deemed using the > > term in this way to be incorrect." :) > > Sadly, I must note that Edwin Newman > (http://en.wikipedia.org/wiki/Edwin_Newman) passed away last month. I All I would add is: http://www.qwantz.com/index.php?comic=693 http://languagelog.ldc.upenn.edu/nll/?p=2290 > fear the common, totally illogical use of this phrase is now a lost > cause. I could care less (not sic). It is annoying yes. Language changes underneath us though. > > |> | why don't we want IPv6 enabled by default on new BIND installations? > > |> > > |> It has to do with whether or not IPv6 support is compiled into the > > |> FreeBSD base system which is compiling BIND. If the configure option ... > > If I'm still alive when IPv6 is the norm and IPv4 is the exception, I > > promise to give it another look. :) IPv6 is more prevalent than you think. I can't understand the illogic of turning it off. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: ober...@es.netPhone: +1 510 486-8634 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > ___ > 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" - Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ 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: BIND9 built w/--disable-ipv6 on 8.1-STABLE
On 9/21/2010 12:15 PM, Kevin Oberman wrote: I'd suggest looking at it when IPv6 becomes a standard part of system software and routing . That will happen long before IPv4 becomes an exception. I think you missed the bit where I pointed out that the current configuration works in all modern cases, both common and uncommon. The point I tried to humorously make in my previous post was that the current configuration will continue to work until such time as systems are commonly built without any IPv4 at all. BIND does not even have a configuration knob for "no IPv4" atm, nor should it, since it works perfectly well on IPv6-only systems. In short, there is no reason to make a change now, and long before there is any reason to make such a change the underlying software will have changed sufficiently to make the discussion moot. As always, users with special needs beyond what the base BIND provides are welcome to configure to their heart's content either with the port(s) of BIND, or if that's not enough knobs for you you can always build it yourself. hth, Doug PS, pardon the humorless nature of this reply, as attempting to make my point(s) with humor was apparently not very effective. -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: BIND9 built w/--disable-ipv6 on 8.1-STABLE
> Date: Tue, 21 Sep 2010 11:06:43 -0700 > From: Doug Barton > Sender: owner-freebsd-sta...@freebsd.org > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 9/21/2010 4:43 AM, Mark Kamichoff wrote: > | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > |> | Although, that still does beg the question, > |> > |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question > | > | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > > Yes, especially the last bit, "Usage commentators have deemed using the > term in this way to be incorrect." :) Sadly, I must note that Edwin Newman (http://en.wikipedia.org/wiki/Edwin_Newman) passed away last month. I fear the common, totally illogical use of this phrase is now a lost cause. I could care less (not sic). > |> | why don't we want IPv6 enabled by default on new BIND installations? > |> > |> It has to do with whether or not IPv6 support is compiled into the > |> FreeBSD base system which is compiling BIND. If the configure option > |> is set to enable but there is not the proper support in the base, then > |> Bad Things(TM) happen. However, the way that it is set up now if the > |> binaries are running on a system that has IPv6 support then that is > |> detected, and you can use it if you choose. If the binaries are > |> running on a system without IPv6 support, no harm, no foul. > | > | I see, that makes sense. However, as IPv6 becomes more widely used > | (perhaps quite far in the future, when folks are turning /off/ IPv4), it > | might need revisiting. > > If I'm still alive when IPv6 is the norm and IPv4 is the exception, I > promise to give it another look. :) I'd suggest looking at it when IPv6 becomes a standard part of system software and routing . That will happen long before IPv4 becomes an exception. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On 9/21/2010 6:54 AM, Vadim Goncharov wrote: This thread, to this moment, has one practical statement: calls for volunteers and other major notifications should go to announce@, perhaps to Web site, too ... and since you've made that point, and several people in the project leadership have agreed with you, perhaps it's time to give it a rest? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: BIND9 built w/--disable-ipv6 on 8.1-STABLE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/21/2010 4:43 AM, Mark Kamichoff wrote: | On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: |> | Although, that still does beg the question, |> |> No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question | | http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage Yes, especially the last bit, "Usage commentators have deemed using the term in this way to be incorrect." :) |> | why don't we want IPv6 enabled by default on new BIND installations? |> |> It has to do with whether or not IPv6 support is compiled into the |> FreeBSD base system which is compiling BIND. If the configure option |> is set to enable but there is not the proper support in the base, then |> Bad Things(TM) happen. However, the way that it is set up now if the |> binaries are running on a system that has IPv6 support then that is |> detected, and you can use it if you choose. If the binaries are |> running on a system without IPv6 support, no harm, no foul. | | I see, that makes sense. However, as IPv6 becomes more widely used | (perhaps quite far in the future, when folks are turning /off/ IPv4), it | might need revisiting. If I'm still alive when IPv6 is the norm and IPv4 is the exception, I promise to give it another look. :) Doug - -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBCAAGBQJMmPQzAAoJEFzGhvEaGryEH+cH/1FV/oNnpFR82oQRG9QVV6GJ d1L4uNLcDEDTKsIboFS5oECQaO0H4lZL3OMmfUCXISg3+ZvbIW4tms/HKdXCi+Ks f4sCgRWWCuyOv/yg/FL4asUQXGwA1ESaIv4d34ZthAqbjWdE4cXb0Kwwhkllpcu/ B1ph4xyXZ71apxxSGzC1ZOppwtCTamwj/o0OgEnIrBHkPyiXL2FI7Ozo5vIt2HoN /Q5UDAB1fwd80pVcEY6Rw2wbgNmthgv4fa6HtchqscqA2PgpuqO7+0JbuE7zkik2 Ktf54uaMUQU4eWWGBIFVsZDy/uUSezlaQEsAFwsSM6WUcBkSBEMomwQwANMw+qM= =jN1T -END PGP SIGNATURE- ___ 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: 8.1-PRERELEASE: CPU packages not detected correctly
on 02/09/2010 11:25 Andriy Gapon said the following: > on 01/09/2010 21:26 Jung-uk Kim said the following: >> On Friday 27 August 2010 03:36 pm, Jung-uk Kim wrote: >>> [3] AMD is working on an SMT-capable CPU (code-named Bulldozer) and >>> my patch won't work on them. If anyone has a Bulldozer sample, >>> please look into it. >> >> I checked AMD website today and found out a new CPUID Spec. Rev. 2.34 >> was just released: >> >> http://support.amd.com/us/Embedded_TechDocs/25481.pdf >> >> They have added CPUID 0x801d and 0x801e to detect topology, it >> seems. Also, CPUID 0x8001 %ecx bit 22 (TopologyExtensions) tells >> you whether the above CPUID functions are supported. >> >> Interesting... > > Yeah, I've heard that they are adding SMT capabilities in "Bulldozer" > processors, so I guess they have to change CPU topology detection indicators. The above comment by me is almost nonsense :) I looked at the document with better attention and I think that what the new way does is better/provides proper support for discovering non-uniform topologies based on APIC IDs of the cores. BTW, I am reading that AMD Bulldozer CPU package will consist of modules, which in turn will consist of cores. When a "core" would be something in between current notion of core and current notion of hardware thread (SMT/HTT/whatever). The Bulldozer cores will have independent arithmetic units and L1 caches, but shared FPU, L2, fetch+decode and some other elements; L3 cache is per package (shared by all "modules"). -- 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On 21/09/2010 11:49 PM, Willem Jan Withagen wrote:
On 2010-09-21 15:16, Jeremy Chadwick wrote:
On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote:
On 2010-09-21 13:39, {some mysterious person :-)} wrote:
The Project is ultimately about the users, right? There are early
signs that
some old FreeBSD users get tired from those changes, those
removals, lesser
POLA adherence, marketing-not-technical-stuff for
time-not-feature-based
releases, not so stable -STABLE as it used to be, and so on,
migrating to
other systems. And older users are more valuable to project than
newer ones.
May be it's time to revert to some of thet Old Good Things, if
decade-long
project is mostly ended, while those signs are still early and not
a strong
tendency?.. Given this thread, I've mentioned earlier about 12
messages in
announce@ from 2002 with such public calls for volunteers - there
are several
years already without these.
Andriy wasn't the one who wrote this. In fact, I'm not sure who the
quote actually came from because I never received the Email it came
from, but I'm under the impression it's from Vadim. My mail spool:
My bad for not checking the included reference.
I was also very much under the impression that that quote was Vadim's,
since it was in completeline with his previous complaints/rants/whining.
And yes, your are smart to stay out of the discussion. But this old
fart just had too much urge to react. So now I'll just go back to my
old lurking state.
My thoughts are below - remembering its a volunteer project, people
spend their precious time to make it happen, and
noneofthatwisthandingitsstilldamngood:
a) if you don't like it, fix it.
b) if you can't fix it, pay someone else to fix it
c) if you can't fix it or otherwise be helpful, remain silent
If you can't do a or b or c, and still have no options, below:
d) whinging never helps
e) those that whinge on volunteer projects are subject to the emperors wrath
f) kill the heretic, the witch, the unbeliever. Recover the gene-seed at
all costs.
Cheers
Joe
--WjW
___
freebsd-secur...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to
"freebsd-security-unsubscr...@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: source tree out of sync
On Tuesday 21 September 2010 15:45:54 Gareth de Vaux wrote: > On Tue 2010-09-21 (11:31), Gareth de Vaux wrote: > > I assume I can't do this safely if my /usr/src tree has been > > updated since my last make world? > > Well, doesn't look like it's an issue for me in this instance. > ___ > 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" For the record: It would not be a problem at all, at least in this particular case: You’re only patching and reinstalling bzip2, which hasn’t had a commit for ages except this one security patch. See: http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/bzip2/ You’re not touching any other system component, so the date of your /usr/src checkout is not an issue. You could even csup the most recent version instead of applying the patch manually and then recompile bzip2 only. Cheers, Pascal ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On Tue, Sep 21, 2010 at 3:20 PM, Vadim Goncharov wrote: > I give up. > Thank $DEITY. Cheers Tom ___ 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: Dummynet
On Tue, Sep 21, 2010 at 02:26:41PM +, Vadim Goncharov wrote: > Hi Jon Otterholm! > > On Tue, 21 Sep 2010 16:02:44 +0200; Jon Otterholm wrote about 'SV: Dummynet': > > >> Try to write "buckets 4096" before "mask", though this is unlikely to help, > >> there are some troubles with 8.1's changes in parser. > > Didn't help. > > I've heared about similar bug, but with "queue" after "mask", when it helped. > > >>> Am I missing something here? This worked fine in the 7-branch. > >> > >> The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and > >> 8.1R. > >> There are many new features and, as seen from many PRs, many new bugs. > > OK. I just have to wait then for luigi@ to submit fixes. > > Thanks for the tips and info. > > Should I expect and be prepared for any other flaws from the current > > version of dummynet in 8-STABLE? > > Yes. I think you should better go to > http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=ipfw and > http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=dummynet > and find reports similar to yours. If there no such, create your one - > because: > 1) this is official place for bug reports, they won't get lost, and in >mail lists - they may get lost > 2) luigi@ just may be not knowing about the bug without report I believe this bug was reported and fixed in our internal tree, but did not find the time yet to commit it, due to the 8.1 release cycle and then vacation and other committments. cheers luigi ___ 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: Dummynet
Hi Jon Otterholm! On Tue, 21 Sep 2010 16:02:44 +0200; Jon Otterholm wrote about 'SV: Dummynet': >> Try to write "buckets 4096" before "mask", though this is unlikely to help, >> there are some troubles with 8.1's changes in parser. > Didn't help. I've heared about similar bug, but with "queue" after "mask", when it helped. >>> Am I missing something here? This worked fine in the 7-branch. >> >> The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and >> 8.1R. >> There are many new features and, as seen from many PRs, many new bugs. > OK. I just have to wait then for luigi@ to submit fixes. > Thanks for the tips and info. > Should I expect and be prepared for any other flaws from the current version > of dummynet in 8-STABLE? Yes. I think you should better go to http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=ipfw and http://www.freebsd.org/cgi/query-pr-summary.cgi?&sort=none&text=dummynet and find reports similar to yours. If there no such, create your one - because: 1) this is official place for bug reports, they won't get lost, and in mail lists - they may get lost 2) luigi@ just may be not knowing about the bug without report -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
Hi Andriy Gapon! On Tue, 21 Sep 2010 15:53:56 +0300; Andriy Gapon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': >>> Hmm, it's really simple. >>> If you want to shape the future of the project, then participate in the >>> places >>> where the future is shaped. If you want to know what's coming up in the >>> future, >>> then watch the places where the future is shaped. If you don't do either, >>> you get >>> what you get. Complaining post factum just doesn't work. (Numerous other >>> examples and projects also demonstrate that). >>> "Current", "stable" are not some alien versions of FreeBSD for some other >>> strange >>> people to use. >>> Those are your future releases. >>> Not looking into the future has its benefits - you are not doing anything; >>> but it >>> has costs too - you don't know your future. >>> Looking into the future and shaping it has obvious costs, but the benefits >>> are >>> clear too. >>> Business users and old FreeBSD users should know this best of all. >>> It's strange that you try speak on their behalf but do not seem to realize >>> these >>> simple things. >> >> The essence of your words and your position in other letters is: >> >> "We are an open source project exactly the same kind like many others: >> we have no [moral] responsibility to our users, we are selfish and want only >> your code; give us your code and you will have the right to freedom of >> speech, >> otherwise you're an untermensch". > > Please don't put your words into my mouth. > I've said what I've said. > Your interpretations do not interest me. That's not argument, and my words are logical consequences from your words, and you didn't refute. Still, my statements after, which you skipped (again! you are again skipping the actual truth which discomforts you!), are valid: you say that people who want to know the future or help the Project must go places such as current@, and official FreeBSD docs say that they don't. Thus you are still wrong. But you've failed to hold constructive discussion for 4 RTTs. No logic in reasons, no respect to POVs other than yours -> no hope to prove you something correctly as it is done in science and should be in FreeBSD mail lists. Just accusements. Sad. I give up. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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"
SV: Dummynet
Hi Vadim! > -Ursprungligt meddelande- > Från: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > sta...@freebsd.org] För Vadim Goncharov > Skickat: den 21 september 2010 14:48 > Till: freebsd-stable@freebsd.org > Ämne: Re: Dummynet > > Hi Jon Otterholm! > > On Mon, 20 Sep 2010 10:00:48 +0200; Jon Otterholm wrote about > 'Dummynet': > > > Installed a new router running 8-stable and encounter some problems > > when configuring dummynet pipes: > > > When setting buckets above 1024... > > ipfw pipe 91 config bw 100Mbit/s mask src-ip 0x buckets 4096 > > > ...I get the following error: > > Clamp sched buckets to 1024 (was 4096) > > Try to write "buckets 4096" before "mask", though this is unlikely to help, > there are some troubles with 8.1's changes in parser. Didn't help. > > > # sysctl net.inet.ip.dummynet.hash_size > > net.inet.ip.dummynet.hash_size: 4096 > > Also, make sure you're doing this before any packets actually went to > dummynet (e.g. just after reboot). This is set in /etc/sysctl.conf ... > > > from man ipfw: > > buckets hash-table-size > > Specifies the size of the hash table used for storing the > > various > > queues. Default value is 64 controlled by the sysctl(8) > > variable > > net.inet.ip.dummynet.hash_size, allowed range is 16 to 65536. > > > Am I missing something here? This worked fine in the 7-branch. > > The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and > 8.1R. > There are many new features and, as seen from many PRs, many new bugs. OK. I just have to wait then for luigi@ to submit fixes. Thanks for the tips and info. Should I expect and be prepared for any other flaws from the current version of dummynet in 8-STABLE? //JO ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
Hi Willem Jan Withagen! On Tue, 21 Sep 2010 14:59:46 +0200; Willem Jan Withagen wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': > I'm a FreeBSD user as early as 1993, still have the first 1.0 CD here as > nice remembrance. So I guess that I qualify as one of those "old > FreeBSD" users. > And I completely disagree with you. > If you have been such an old freebsd user,then you should know the > immense effort there has been to move GIANT out of the way. I cann't > even get close to describing what a huge respect I have for the people > that dared to undertake such a humongous effort. With an high > probability of being flamed to death... > But still ever since 5.x I've seen things really improve for the better. > And yes, I was sorry to see ISDN being removed, but as things have > progressed another version has been returned instead. > And sure I have more hardware than you can imagine that is no longer > supported. But it is all old, and worn down, sometimes it is even still > VESA stuff. > And right,there have been variations in the level of what you would like > to call stable. But compared to the "old days" I would say, it has > always been above my expectation. And note that I have and still do run > 24*7 business on this. FreeBSD has never NEVER ever let me down. That's for you. For me. For a lot of people. But when I see, in my circles, some old users - not any Linux newbies we shouldn't care, but old and skilled users - leaving or talking about where to go from FreeBSD, than you shouldn't ignore the facts. You should say that something, um, smells wrong. > So as far as I'm concerned you are barking up the wrong tree here. Even if you, while investigating for a bug, eventually find that it was not a bug, but during the search discover another bug, that is not the reason to fix the latter. This thread, to this moment, has one practical statement: calls for volunteers and other major notifications should go to announce@, perhaps to Web site, too, perhaps clarified how people can help with money or to hire something to work on the code. And that will make the FreeBSD Project better. So, not to flame more, do you disagree with this? -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On 2010-09-21 15:16, Jeremy Chadwick wrote:
On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote:
On 2010-09-21 13:39, {some mysterious person :-)} wrote:
The Project is ultimately about the users, right? There are early signs that
some old FreeBSD users get tired from those changes, those removals, lesser
POLA adherence, marketing-not-technical-stuff for time-not-feature-based
releases, not so stable -STABLE as it used to be, and so on, migrating to
other systems. And older users are more valuable to project than newer ones.
May be it's time to revert to some of thet Old Good Things, if decade-long
project is mostly ended, while those signs are still early and not a strong
tendency?.. Given this thread, I've mentioned earlier about 12 messages in
announce@ from 2002 with such public calls for volunteers - there are several
years already without these.
Andriy wasn't the one who wrote this. In fact, I'm not sure who the
quote actually came from because I never received the Email it came
from, but I'm under the impression it's from Vadim. My mail spool:
My bad for not checking the included reference.
I was also very much under the impression that that quote was Vadim's,
since it was in completeline with his previous complaints/rants/whining.
And yes, your are smart to stay out of the discussion. But this old fart
just had too much urge to react. So now I'll just go back to my old
lurking state.
--WjW
___
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: source tree out of sync
On Tue 2010-09-21 (11:31), Gareth de Vaux wrote: > I assume I can't do this safely if my /usr/src tree has been updated > since my last make world? Well, doesn't look like it's an issue for me in this instance. ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On Tue, Sep 21, 2010 at 02:59:46PM +0200, Willem Jan Withagen wrote:
> On 2010-09-21 13:39, {some mysterious person :-)} wrote:
> >>The Project is ultimately about the users, right? There are early signs that
> >>some old FreeBSD users get tired from those changes, those removals, lesser
> >>POLA adherence, marketing-not-technical-stuff for time-not-feature-based
> >>releases, not so stable -STABLE as it used to be, and so on, migrating to
> >>other systems. And older users are more valuable to project than newer ones.
> >>May be it's time to revert to some of thet Old Good Things, if decade-long
> >>project is mostly ended, while those signs are still early and not a strong
> >>tendency?.. Given this thread, I've mentioned earlier about 12 messages in
> >>announce@ from 2002 with such public calls for volunteers - there are
> >>several
> >>years already without these.
Andriy wasn't the one who wrote this. In fact, I'm not sure who the
quote actually came from because I never received the Email it came
from, but I'm under the impression it's from Vadim. My mail spool:
$ grep "Old Good Things" Mail/freebsd/freebsd-stable
> May be it's time to revert to some of thet Old Good Things, if decade-long
>> May be it's time to revert to some of thet Old Good Things, if decade-long
>>> May be it's time to revert to some of thet Old Good Things, if decade-long
>> May be it's time to revert to some of thet Old Good Things, if decade-long
The first mention of it was in an Email from Andriy, sent to Vadim, with
Andriy quoting someone words (the first paragraph shown above).
Strangely I can't find the mail on the official FreeBSD pipermail lists
either.
I'm staying out of the main discussion, but I'm just wanting to point
out that Andriy did not write the above quote.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On Tue, Sep 21, 2010 at 8:39 AM, Andriy Gapon wrote: [...] > If you want to shape the future of the project, then participate in the places > where the future is shaped. If you want to know what's coming up in the > future, > then watch the places where the future is shaped. If you don't do either, > you get > what you get. Complaining post factum just doesn't work. (Numerous other > examples and projects also demonstrate that). Stop feeding the troll, please. ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
On 2010-09-21 13:39, Andriy Gapon wrote: The Project is ultimately about the users, right? There are early signs that some old FreeBSD users get tired from those changes, those removals, lesser POLA adherence, marketing-not-technical-stuff for time-not-feature-based releases, not so stable -STABLE as it used to be, and so on, migrating to other systems. And older users are more valuable to project than newer ones. May be it's time to revert to some of thet Old Good Things, if decade-long project is mostly ended, while those signs are still early and not a strong tendency?.. Given this thread, I've mentioned earlier about 12 messages in announce@ from 2002 with such public calls for volunteers - there are several years already without these. Well, let me pitch in here a bit, because this discussion has had me on the edge of commenting already for too long. I'm a FreeBSD user as early as 1993, still have the first 1.0 CD here as nice remembrance. So I guess that I qualify as one of those "old FreeBSD" users. And I completely disagree with you. If you have been such an old freebsd user,then you should know the immense effort there has been to move GIANT out of the way. I cann't even get close to describing what a huge respect I have for the people that dared to undertake such a humongous effort. With an high probability of being flamed to death... But still ever since 5.x I've seen things really improve for the better. And yes, I was sorry to see ISDN being removed, but as things have progressed another version has been returned instead. And sure I have more hardware than you can imagine that is no longer supported. But it is all old, and worn down, sometimes it is even still VESA stuff. And right,there have been variations in the level of what you would like to call stable. But compared to the "old days" I would say, it has always been above my expectation. And note that I have and still do run 24*7 business on this. FreeBSD has never NEVER ever let me down. So as far as I'm concerned you are barking up the wrong tree here. --WjW ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
on 21/09/2010 15:36 Vadim Goncharov said the following: > Hi Andriy Gapon! > > On Tue, 21 Sep 2010 14:39:53 +0300; Andriy Gapon wrote about 'Re: HEADS UP: > FreeBSD 6.4 and 8.0 EoLs coming soon': > >>> The Project is ultimately about the users, right? There are early signs that >>> some old FreeBSD users get tired from those changes, those removals, lesser >>> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >>> releases, not so stable -STABLE as it used to be, and so on, migrating to >>> other systems. And older users are more valuable to project than newer ones. >>> May be it's time to revert to some of thet Old Good Things, if decade-long >>> project is mostly ended, while those signs are still early and not a strong >>> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >>> announce@ from 2002 with such public calls for volunteers - there are >>> several >>> years already without these. >> Hmm, it's really simple. >> If you want to shape the future of the project, then participate in the >> places >> where the future is shaped. If you want to know what's coming up in the >> future, >> then watch the places where the future is shaped. If you don't do either, >> you get >> what you get. Complaining post factum just doesn't work. (Numerous other >> examples and projects also demonstrate that). >> "Current", "stable" are not some alien versions of FreeBSD for some other >> strange >> people to use. >> Those are your future releases. >> Not looking into the future has its benefits - you are not doing anything; >> but it >> has costs too - you don't know your future. >> Looking into the future and shaping it has obvious costs, but the benefits >> are >> clear too. >> Business users and old FreeBSD users should know this best of all. >> It's strange that you try speak on their behalf but do not seem to realize >> these >> simple things. > > The essence of your words and your position in other letters is: > > "We are an open source project exactly the same kind like many others: > we have no [moral] responsibility to our users, we are selfish and want only > your code; give us your code and you will have the right to freedom of > speech, > otherwise you're an untermensch". Please don't put your words into my mouth. I've said what I've said. Your interpretations do not interest me. Have a good life. -- 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: Dummynet
Hi Jon Otterholm! On Mon, 20 Sep 2010 10:00:48 +0200; Jon Otterholm wrote about 'Dummynet': > Installed a new router running 8-stable and encounter some problems when > configuring dummynet pipes: > When setting buckets above 1024... > ipfw pipe 91 config bw 100Mbit/s mask src-ip 0x buckets 4096 > ...I get the following error: > Clamp sched buckets to 1024 (was 4096) Try to write "buckets 4096" before "mask", though this is unlikely to help, there are some troubles with 8.1's changes in parser. > # sysctl net.inet.ip.dummynet.hash_size > net.inet.ip.dummynet.hash_size: 4096 Also, make sure you're doing this before any packets actually went to dummynet (e.g. just after reboot). > from man ipfw: > buckets hash-table-size > Specifies the size of the hash table used for storing the > various > queues. Default value is 64 controlled by the sysctl(8) > variable > net.inet.ip.dummynet.hash_size, allowed range is 16 to 65536. > Am I missing something here? This worked fine in the 7-branch. The reason is that luigi@ merged ipfw3 from -CURRENT between 8.0R and 8.1R. There are many new features and, as seen from many PRs, many new bugs. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
Hi Andriy Gapon! On Tue, 21 Sep 2010 14:39:53 +0300; Andriy Gapon wrote about 'Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon': >> The Project is ultimately about the users, right? There are early signs that >> some old FreeBSD users get tired from those changes, those removals, lesser >> POLA adherence, marketing-not-technical-stuff for time-not-feature-based >> releases, not so stable -STABLE as it used to be, and so on, migrating to >> other systems. And older users are more valuable to project than newer ones. >> May be it's time to revert to some of thet Old Good Things, if decade-long >> project is mostly ended, while those signs are still early and not a strong >> tendency?.. Given this thread, I've mentioned earlier about 12 messages in >> announce@ from 2002 with such public calls for volunteers - there are several >> years already without these. > Hmm, it's really simple. > If you want to shape the future of the project, then participate in the places > where the future is shaped. If you want to know what's coming up in the > future, > then watch the places where the future is shaped. If you don't do either, > you get > what you get. Complaining post factum just doesn't work. (Numerous other > examples and projects also demonstrate that). > "Current", "stable" are not some alien versions of FreeBSD for some other > strange > people to use. > Those are your future releases. > Not looking into the future has its benefits - you are not doing anything; > but it > has costs too - you don't know your future. > Looking into the future and shaping it has obvious costs, but the benefits are > clear too. > Business users and old FreeBSD users should know this best of all. > It's strange that you try speak on their behalf but do not seem to realize > these > simple things. The essence of your words and your position in other letters is: "We are an open source project exactly the same kind like many others: we have no [moral] responsibility to our users, we are selfish and want only your code; give us your code and you will have the right to freedom of speech, otherwise you're an untermensch". But FreeBSD Project tries, to the extent possible (of course, volunteers are not paid), be different from those, and provides all those branches, lists, etc. for different people. Business users and old FreeBSD users value FreeBSD for this, and they know that it is official position and documented, e.g.: 12.1 Statement of General Intent The FreeBSD Project targets "production quality commercial off-the-shelf (COTS) workstation, server, and high-end embedded systems". And what they are complaining post factum is that things go _other way than declared_. And they are begin to go the way as you assertions above, which clearly contradicts FreeBSD's official declared goals. Yes, still that an open-source project, there are no liability, etc., etc. But my criticism earlier in the thread was not unconstructive - I've suggested one of the possible ways for those who cannot help us directly by code. Don't reject them just on this criteria (and Project never did before). -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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: Policy for removing working code
Hi Andriy Gapon! On Fri, 17 Sep 2010 15:09:54 +0300; Andriy Gapon wrote about 'Re: Policy for removing working code': >> You either not understanding that this situation is about entire project (not >> ISDN, but policy) or assert that users just running FreeBSD should not care >> about the way things happen, which is wrong. And thus your "stop provoking" >> sounds like ostrich policy, which is even worse. > You either don't understand the situation or are a troll. > People who actively participate(d) in the project/community were very well > aware > of the issue. Following the generalized principle of locality it was not > expected > that much help would come from people who didn't already sufficiently > participate. > This much belated and non-productive thread is a perfect demonstration. No, that is you who actively refuse to understand the main point, while several other people on this list already agreed with me. I've given arguments, valid arguments, but you din't answer them, repeating the same statement reworded. Moreover, you were wrong several times, e.g. at requirement for all users to read stable, while I've found that handbook/eresources.html agrees with me: === freebsd-announce Important events / milestones This is the mailing list for people interested only in occasional announcements of significant FreeBSD events. This includes announcements about snapshots and other releases. It contains announcements of new FreeBSD capabilities. It may contain calls for volunteers etc. This is a low volume, strictly moderated mailing list. === And Project actually did the things as documented, I've counted and wrote in another message 12 such letters in announce@ from 2002, then things stopped to go this way. Why you ignored this argument just as I didn't say anything? After all, your impolite accusements of non-productiveness and trolling. Should I answer the same way and say something about your self-conceit? I'll not come down to this but rather quote committers-guide: === Do not impugn the intentions of someone you disagree with. If they see a different solution to a problem than you, or even a different problem, it is not because they are stupid, because they have questionable parentage, or because they are trying to destroy your hard work, personal image, or FreeBSD, but simply because they have a different outlook on the world. Different is good. Disagree honestly. Argue your position from its merits, be honest about any shortcomings it may have, and be open to seeing their solution, or even their vision of the problem, with an open mind. Accept correction. We are all fallible. When you have made a mistake, apologize and get on with life. Do not beat up yourself, and certainly do not beat up others for your mistake. Do not waste time on embarrassment or recrimination, just fix the problem and move on. Ask for help. Seek out (and give) peer reviews. One of the ways open source software is supposed to excel is in the number of eyeballs applied to it; this does not apply if nobody will review code. === -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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: BIND9 built w/--disable-ipv6 on 8.1-STABLE
On Mon, Sep 20, 2010 at 03:34:05PM -0700, Doug Barton wrote: > | Although, that still does beg the question, > > No, it doesn't. :) See http://en.wikipedia.org/wiki/Beg_the_question http://en.wikipedia.org/wiki/Beg_the_question#Modern_usage > | why don't we want IPv6 enabled by default on new BIND installations? > > It has to do with whether or not IPv6 support is compiled into the > FreeBSD base system which is compiling BIND. If the configure option > is set to enable but there is not the proper support in the base, then > Bad Things(TM) happen. However, the way that it is set up now if the > binaries are running on a system that has IPv6 support then that is > detected, and you can use it if you choose. If the binaries are > running on a system without IPv6 support, no harm, no foul. I see, that makes sense. However, as IPv6 becomes more widely used (perhaps quite far in the future, when folks are turning /off/ IPv4), it might need revisiting. - Mark -- Mark Kamichoff p...@prolixium.com http://www.prolixium.com/ signature.asc Description: Digital signature
Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
> The Project is ultimately about the users, right? There are early signs that > some old FreeBSD users get tired from those changes, those removals, lesser > POLA adherence, marketing-not-technical-stuff for time-not-feature-based > releases, not so stable -STABLE as it used to be, and so on, migrating to > other systems. And older users are more valuable to project than newer ones. > May be it's time to revert to some of thet Old Good Things, if decade-long > project is mostly ended, while those signs are still early and not a strong > tendency?.. Given this thread, I've mentioned earlier about 12 messages in > announce@ from 2002 with such public calls for volunteers - there are several > years already without these. Hmm, it's really simple. If you want to shape the future of the project, then participate in the places where the future is shaped. If you want to know what's coming up in the future, then watch the places where the future is shaped. If you don't do either, you get what you get. Complaining post factum just doesn't work. (Numerous other examples and projects also demonstrate that). "Current", "stable" are not some alien versions of FreeBSD for some other strange people to use. Those are your future releases. Not looking into the future has its benefits - you are not doing anything; but it has costs too - you don't know your future. Looking into the future and shaping it has obvious costs, but the benefits are clear too. Business users and old FreeBSD users should know this best of all. It's strange that you try speak on their behalf but do not seem to realize these simple things. -- 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: Policy for removing working code
Hi Doug Barton! On Fri, 17 Sep 2010 13:27:02 -0700; Doug Barton wrote about 'Re: Policy for removing working code': >> You either not understanding that this situation is about entire project (not >> ISDN, but policy) > I think at this point that you've made your concerns clear. What you > don't seem to be understanding is: > 1) The policy is, and always has been, those who are interested in > keeping code alive work on it. > 2) No one was interested (by the definition above) in keeping the ISDN > code alive. Not quite. There are those who are interested in keeping code alive but can't work on it, i.e., users, not programmers. But they, if notified, could convince another people, programmers, to do the work (such events of volunteer calls are not often), e.g., hire someone. But announcements, may be, should be more clear about this, for the case such people wouldn't _guess_ such possibility exists. BSD tries to be more business-freindly, ain't it? :) > Now you have raised a valid point on how we can do the "volunteers > needed" notifications better in the future, and I think that those will > be taken to heart, and acted on the next time we face this situation. Indeed. Thanks for understanding. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nucli...@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] ___ 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"
source tree out of sync
Hi all, in for example http://security.freebsd.org/advisories/FreeBSD-SA-10:08.bzip2.asc : # cd /usr/src # patch < /path/to/patch # cd /usr/src/lib/libbz2 # make obj && make depend && make && make install I assume I can't do this safely if my /usr/src tree has been updated since my last make world? ___ 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"
