Re: Missing libpthread.so.*
On Fri, 9 Dec 2005 [EMAIL PROTECTED] wrote: > Geez, it was that simple!!! I've searched everywhere for libpthread, but > didn't bother to see doc on libkse. My bad... Stop using libkse. In 5.0 it's an experimental library. If you want libpthread, you need to upgrade to 5-stable. Like I've said before, you've either hosed your system or are using an improper (for 5.0) /etc/libmap.conf. There should be no references to libpthread.so in 5.0. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Missing libpthread.so.*
Geez, it was that simple!!! I've searched everywhere for libpthread, but didn't bother to see doc on libkse. My bad... Thanks... > On 12/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> FBSD 5.0 >> >> I'm getting missing libpthread.so.* error, so I copied it from another >> FBSD box, and now getting: >> Undefined symbol "__malloc_lock" >> >> So I went into /usr/src/lib/libpthread and did make/install. I noticed >> that it installed libkse.so.* but not libpthread.so.*. >> > What you need to do is create a link between libpthread.so.* and > libkse.so.*: > > cd /usr/lib > ln libkse.so... libpthread.so > > Also see this cvs entry about libkse on FreeBSD 5.0: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libpthread/Makefile?rev=1.35&content-type=text/x-cvsweb-markup > > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > > ** Computer problems? ... ..http://www.multibyte.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Automatic installation problem
On Sat, 10 Dec 2005 01:34 am, Tarasov Alexey wrote: > Hello! > > I'm trying to make full automatical FreeBSD installation. I have the > > following lines in my install.cfg: > > command="echo sshd_enable="YES" >> /etc/rc.conf" > > system > > command="echo 'pass' | /usr/sbin/pw useradd -u user -h 0 -G wheel" > > system > > But during installation I get some error messages: > > DEBUG: dispatch: calling resword 'system' > > echo sshd_enable=YES >> /etc/rc.conf: not found > > I am using FreeBSD 6.0-RELEASE. Yep, something changed around 4.x in sysinstall where rc.conf is not created until near when it finishes. If you write to rc.conf during an scripted sysinstall, then it will be over written. You can write your stuff to /etc/rc.conf.local. It gets sourced in /etc/defaults/rc.conf. $ grep rc.conf /etc/defaults/rc.conf rc_conf_files="/etc/rc.conf /etc/rc.conf.local" After boot time, we have a post boot script which merges our stuff from rc.conf.local into rc.conf, just to keep it clean. Just to be safe, we quote everything in install.cfg. As in echo 'sshd_enable=YES' >> /etc/rc.conf.local Paul. -- Paul Koch CTO Statseeker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
On Fri, Dec 09, 2005 at 05:38:43PM +0100, Thomas E. Zander wrote: > On Fri, 09. Dec 2005, at 16:00 +, David Malone wrote > according to [Re: Boot manager beep]: > > On Fri, Dec 09, 2005 at 08:43:14AM -0700, Scott Long wrote: > > > > > It is highly irritating for everyone else, though. > > > > Not quite everyone - if I'm working on a few machines I find it > > useful to know when a particular machine has reached the boot stage, > > so I can tell it to go into single user mode. It is particularly > > useful on machines where the BIOS tages ages to do its stuff. > > Probably it isn't even a real problem on most boxes. Usually standard > desktops and servers (maybe) have their pc speaker which is set to a > reasonable volume at boot time. I never found this beep annoying in my > servers. Just came across it when I had to reinstall my notebook > because of a hard drive crash and 6.0 installed this beeping boot > loader. So probably as Scott pointed out, it might be best to let the > user choose a quiet loader as an option. > Naturally, boot0 is a tiny program, it shouldn't be a problem to build > a boot0nobeep as well and install one of them depending on settings, > maybe even early during sysinstall ?! yes, that sounds reasonable to me .. i'm one of those sightless ones who caused the irritation for mr long. may i suggest that the default situation be set to beep: ON and if teh enduser requires or need the beep: OFF version then they are left to make the adjustments as thier own exercise. i like the idea about setting a bit in the /dev/conf file, ummm something like that my memory isnt that good this morning. it is most difficult trying to work out how and where to make changes when being able to see teh scree becomes a personal issue .. every bit helps. sorry for the intrusion . this be one of those items that needs some vocalisation from those it genuinely affects and for whom it is not a meer cosmetic annoyance. regards and apologies jonathan -- powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system === appropriate solution in an inappropriate world === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nve(4) patch - please test!
Hi, everyone out there who had only seen timeouts like nve0: device timeout (4) on nve and __never got it working at all__ please try this patch[1] which made my nve working from 0 to 99. I still can get timeouts by for example flood pinging another machine on the local LAN but it all recovers on it's own and I can work on that machine and do things like find / over ssh without losing connectivity. Fixing the timeouts will be another problem that needs to be addressed later. Greetings Bjoern A. Zeeb [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff Index: if_nve.c === RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/nve/if_nve.c,v retrieving revision 1.19 diff -u -p -r1.19 if_nve.c --- if_nve.c7 Dec 2005 17:38:03 - 1.19 +++ if_nve.c9 Dec 2005 17:50:32 - @@ -643,6 +643,10 @@ nve_init_locked(struct nve_softc *sc) nve_stop(sc); DEBUGOUT(NVE_DEBUG_INIT, "nve: do pfnInit\n"); + /* Setup multicast filter */ + nve_setmulti(sc); + nve_ifmedia_upd_locked(ifp); + /* Setup Hardware interface and allocate memory structures */ error = sc->hwapi->pfnInit(sc->hwapi->pADCX, 0, /* force speed */ @@ -661,10 +665,6 @@ nve_init_locked(struct nve_softc *sc) sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); sc->hwapi->pfnStart(sc->hwapi->pADCX); - /* Setup multicast filter */ - nve_setmulti(sc); - nve_ifmedia_upd_locked(ifp); - /* Update interface parameters */ ifp->if_drv_flags |= IFF_DRV_RUNNING; ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
> > > One last point, either remove me from the reply to list or place the > > > maillist > > > back on it, thank you. > > > > I think you owe me an apology - but I doubt I will get it. > > Your correct, you won't. I think you mean "you are" ? It is a writer's credibility that is at stake if they choose to argue ad personam, or make patently incorrect and illogical statements and then do not apologize afterwards. Your loss - not mine Take care david ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
On Friday 09 December 2005 11:31, vizion wrote: > > -Original Message- > > From: Michael C. Shultz [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 09, 2005 10:32 AM > > To: vizion > > Cc: 'Peter Jeremy'; 'Doug Barton' > > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic > > > > On Friday 09 December 2005 09:39, vizion wrote: > > > > Vison, you are much better at writting florid prose on how and why > > > > FreeBSD is > > > > such an awful OS run by a team of Techies who care nothing about end > > > > users needs than you are at reading and comprehending simple > > > > instructions. > > > > > > > > What you write is almost believable, your writing skill is very good > > > > and > > > > > > convincing, only in this particualr case I know you are completely > > > > wrong > > > > > > and > > > > your failure to follow the simplest advice is why your machine is now > > > > non > > > > > > operational. Quit crying about non relevent issues and concentrate > > > > on solving your real problem - getting that darn machine to boot up. > > > > > > > > One last thought, name one OS that has better documentation than > > > > FreeBSD > > > > > > please, comercial or otherwise. Maybe there is such a beast, if so I > > > > am > > > > > > very > > > > curious to know what it is called. > > > > > > Mike > > > > > > Rather than replying to the list I am emailing you direct and cc onl;y > > > > the > > > > > individuals to whom you cc'd your original. > > > > > > Frankly I never ceased to be amazed at diversionary personalized > > > attacks that seem to be a regular occurrence on freebsd lists whenever > > > someone makes friendly but critical observations about freebsd. There > > > is a touchyness there which is a big deterrent to the engagement of > > > others > > > > and a > > > > > tendency to paternalize which, on rare occasions, is an unspeakably > > > ugly aspect of some freebsd interactions. > > > > > > I do not know the root cause of such over-defensiveness I am constantly > > > amazed when old timers do not recognize it. It is time to grow up and I > > > hope something will happen to discourage people from arguing ad > > > > personam. > > > > > Your remarks seem to have been written with the deliberate intention of > > > attacking the messenger rather than discussing the message. You did not > > > even aspire to achieving accuracy. > > > > > > The fact the my system did upgrade successfully from 5.3 to 5.4 by > > > following your advice does not give you the right to make false > > > > assumptions > > > > > about a failed upgrade from 5.4 to 6.0 that is due to a combination of > > > events that have nothing whatsoever to do with the topic under > > > > discussion, > > > > > advice that has been given or even freebsd or its documentation. It > > > > turns > > > > > out that a motherboard hardware failure was the casue of the upgrade > > > failure.. hence I have to do a total rebuild because the motherboard is > > > > no > > > > > longer available. > > > > And this is your excuse for attacking the FreeBSD organization? > > No and I have nott attacked "the organization". The c ritic of the way in > which documentation is not integrated ionto the freebsd development cycle > was made long before there was any motherboard failure. I do wish you > would stick to the facts. > > > > I'm sure > > > everyone feels bad for you that you have to get a new motherboard. I am > > confused as to how better coordination between developers and technical > > writers could have prevented it from failing though. > > I have not made that suggestion - only you have put forward that notion -- > come on laugh a bit - you are really being a bit wild and cranky over this > . The motherboard failure occurred after the discussion on > documentation not before you really are missing the point here. > > > > As for the use of perjorative terminology (florid prose) and false > > > accusations - I am really personally very disappointed in your > > > > reactions. > > > > > What you seemed to be saying was that you were unable to counter my > > > suggestions which were so unwelcome to you that you chose to attack me > > > personally. > > > > Your suggestions were irrelevent to the problem at hand. > > My suggestions are very relevant to the documentary errors, omissions and > lack of documentary integration that waste much of the time of many end > users. > > > My suggestions were, it is true, were off the original topic and came about > as a response to someone else who complained about freebsd documentation > and I responded to him. > > He was strongly critical because the documentation stated that direct > upgrade from 5.3 to 6.00 was possible when, as you pointed out, it was not. I never said this, must have been someone else. > > I suggest you reread the whole thread with care and look at the sequence of > events instead of massaging a false interpretation events to satisfy a > desire to argue add pers
Freebsd Stable documentation
Thiis was originally Upgrading 5.3 > 6.0 buildworld failure now in libmagic And on Mike Shultz recommendation I have relabeled the topic > On Thursday 08 December 2005 08:57, [EMAIL PROTECTED] wrote: > > > From: Peter Jeremy <[EMAIL PROTECTED]> > > > Date: 2005/12/08 Thu AM 01:34:42 PST > > > To: Vizion <[EMAIL PROTECTED]> > > > CC: Doug Barton <[EMAIL PROTECTED]>, freebsd-stable@freebsd.org > > > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic > > > > > > On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: > > > >Well having run many very large scale projects myself I find it > > > > difficult to accept either implication of this perspective. > > > > > > There's a massive difference between running a large commercial > project > > > and running a large open source project using volunteers. > > > > Not really I have done both and found that shared values and community > > collaboration work the same. > > > > >On a commercial > > > project, you can direct someone to do something and they have a choice > of > > > either doing it or finding another job. > > > > Well that kind of development environment (rule by dictat) does not work > > very well. Developers are people who are engaged in a collaborative > > process. If you encourage them to think like prima donas then they will > > behave like prima donas rather than as part of an integrated team. > > > > >On a volunteer project, there's > > > a limit to how far you can push someone to do something they don't > enjoy > > > before they just leave. > > > > Push has it limitations everywhere.. goals and communal rewards are > better > > in both volunteer and commercial projects. > > > > > > The first implication is that > > > >we should be complacent about it and not seek to find a method to > > > > improve the process. > > > > > > I don't think anyone is suggesting this. In my experience, the > FreeBSD > > > project is always open to process improvements - this is especially > > > obvious in the documentation and release engineering areas. > > > > The question is about the degree of committment to process change not > > whwther it is absent or present. The critique is there is tooo little > > comitment to process change and too much resistance to greater > > concentration on the quality of user docuimentation and the significance > of > > that work in the developmenmt cycle. > > > > > >>Most of our really top > > > >>notch developers are actually very bad at documenting their work (I > > > >> don't mean bad at being timely with it, I mean that they are bad at > > > >> DOING it), and frankly their time is better spent elsewhere. > > > > > > > >That is a judgment call - franky my experience has been that > developers > > > > who are bad at ensuring their work is well documentated are second > rate > > > > rather than top rate developers. > > > > > > Software developers are notoriously poor at writing documentation for > > > non-technical people. There are probably very few developers who > > > enjoy writing end-user documentation (and can write). In my > > > experience, especially on large projects, it's rare for developers to > > > write the end-user documentation. > > > > NOTE I said" > > F:ranky my experience has been that developers who are bad at > > ENSURING > > their work is well documentated are second rate rather than top rate > > developers. The work of the technical writer needs to influence > development > > at the design stage! It does not matter whether the developer does or > does > > not write the the documentation but it does matter whether the developer > is > > COMIITED to both ensuring that there is proper documentation AND that > the > > documentation process is an integral part of the development process > that > > influences its outcome. > > > > >They may write a rough outline but > > > it's the technical writers who actually do the documentation. > > > > The outline for user documentation needs to be structured BEFORE > > development begins NOT as an afterthought. In a well structured > > development environment documentation is part of DESIGN not post design > > implementation . That is because thinking about end user at the design > > stage is necessary if the outcome of the process is going to be user > > centric. > > > > >The > > > problem is finding people with technical writing skills who are > > > interested in helping with FreeBSD. > > > > Freebsd needs to reorganize the way it develops if it is going to > interest > > techn ical writers. No technical writer wants to be associated with > writing > > documnets for developments that have been poorly designed for the end > user. > > Clearing up someone else's mess is no fun. If you treat technical > writers > > as people who come along afterwards and pick up yopur trash OF COURSE > you > > will not get them involved. You need to ask WHY it is difficult to get > > them. It is because freebsd does not produce software with a focus on > end > > user sati
RE: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
> -Original Message- > From: Michael C. Shultz [mailto:[EMAIL PROTECTED] > Sent: Friday, December 09, 2005 10:32 AM > To: vizion > Cc: 'Peter Jeremy'; 'Doug Barton' > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic > > On Friday 09 December 2005 09:39, vizion wrote: > > > Vison, you are much better at writting florid prose on how and why > > > FreeBSD is > > > such an awful OS run by a team of Techies who care nothing about end > > > users needs than you are at reading and comprehending simple > > > instructions. > > > > > > What you write is almost believable, your writing skill is very good > and > > > convincing, only in this particualr case I know you are completely > wrong > > > and > > > your failure to follow the simplest advice is why your machine is now > non > > > operational. Quit crying about non relevent issues and concentrate on > > > solving your real problem - getting that darn machine to boot up. > > > > > > One last thought, name one OS that has better documentation than > FreeBSD > > > please, comercial or otherwise. Maybe there is such a beast, if so I > am > > > very > > > curious to know what it is called. > > > > Mike > > > > Rather than replying to the list I am emailing you direct and cc onl;y > the > > individuals to whom you cc'd your original. > > > > Frankly I never ceased to be amazed at diversionary personalized attacks > > that seem to be a regular occurrence on freebsd lists whenever someone > > makes friendly but critical observations about freebsd. There is a > > touchyness there which is a big deterrent to the engagement of others > and a > > tendency to paternalize which, on rare occasions, is an unspeakably ugly > > aspect of some freebsd interactions. > > > > I do not know the root cause of such over-defensiveness I am constantly > > amazed when old timers do not recognize it. It is time to grow up and I > > hope something will happen to discourage people from arguing ad > personam. > > > > Your remarks seem to have been written with the deliberate intention of > > attacking the messenger rather than discussing the message. You did not > > even aspire to achieving accuracy. > > > > The fact the my system did upgrade successfully from 5.3 to 5.4 by > > following your advice does not give you the right to make false > assumptions > > about a failed upgrade from 5.4 to 6.0 that is due to a combination of > > events that have nothing whatsoever to do with the topic under > discussion, > > advice that has been given or even freebsd or its documentation. It > turns > > out that a motherboard hardware failure was the casue of the upgrade > > failure.. hence I have to do a total rebuild because the motherboard is > no > > longer available. > > > And this is your excuse for attacking the FreeBSD organization? No and I have nott attacked "the organization". The c ritic of the way in which documentation is not integrated ionto the freebsd development cycle was made long before there was any motherboard failure. I do wish you would stick to the facts. I'm sure > everyone feels bad for you that you have to get a new motherboard. I am > confused as to how better coordination between developers and technical > writers could have prevented it from failing though. I have not made that suggestion - only you have put forward that notion -- come on laugh a bit - you are really being a bit wild and cranky over this . The motherboard failure occurred after the discussion on documentation not before you really are missing the point here. > > > > As for the use of perjorative terminology (florid prose) and false > > accusations - I am really personally very disappointed in your > reactions. > > > > What you seemed to be saying was that you were unable to counter my > > suggestions which were so unwelcome to you that you chose to attack me > > personally. > > Your suggestions were irrelevent to the problem at hand. My suggestions are very relevant to the documentary errors, omissions and lack of documentary integration that waste much of the time of many end users. My suggestions were, it is true, were off the original topic and came about as a response to someone else who complained about freebsd documentation and I responded to him. He was strongly critical because the documentation stated that direct upgrade from 5.3 to 6.00 was possible when, as you pointed out, it was not. I suggest you reread the whole thread with care and look at the sequence of events instead of massaging a false interpretation events to satisfy a desire to argue add personam.. > tecnical > help that is one thing, if you want to improve documentaion that is > another > topic with it's own mail list. I see this as more diversionary BS you could have said: "Hey david -- sorry I should not have jumped to conclusions" > > > > I am disappointed that you react that way to me and even more concerned > > that those who have been around far less years than I wi
Re: Missing libpthread.so.*
On Fri, 9 Dec 2005, Scot Hetzel wrote: > On 12/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > FBSD 5.0 > > > > I'm getting missing libpthread.so.* error, so I copied it from another > > FBSD box, and now getting: > > Undefined symbol "__malloc_lock" > > > > So I went into /usr/src/lib/libpthread and did make/install. I noticed > > that it installed libkse.so.* but not libpthread.so.*. > > > What you need to do is create a link between libpthread.so.* and libkse.so.*: No, he's hosed his system. There is no libpthread in 5.0. Somehow you've brought in binaries from somewhere else that are linked to libpthread because they were linked on a more recent version of FreeBSD. Either that, or you have a /etc/libmap.conf that is trying to use libpthread. -- DE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0 as storage server with raid5?
Stijn Hoop wrote this message on Fri, Dec 09, 2005 at 10:30 +0100: > Besides, I've seen a few hardware RAID controllers having issues > themselves (and they weren't the cheapest ones available either). Yep, and because of failure to get proper vender support, software raid is looking more attractive to the company I work at... Delaying upgrades of the OS due to hardware raid issues, and then finding out that the ICP aka Adaptec no longer supports iir beyond 5.2-R (no 5.4-R or any 6.x and beyond) makes it harder for us to justify spending money on hardware raid. (who knows that the next brand of hardware raid isn't going to have the another issue, and decide to not provide support)... At least they finally released a new patch against 5.4-R, but we can barely get them to support us on 4.7-R (which has the same driver as 4.11-R), let alone when we had issues on 5.4-R... So, even though software raid may not be as reliable among other things, at least you have the source and can fix it, and don't have to wait many months just to wait longer for the vendor to fix the issue... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Missing libpthread.so.*
On 12/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > FBSD 5.0 > > I'm getting missing libpthread.so.* error, so I copied it from another > FBSD box, and now getting: > Undefined symbol "__malloc_lock" > > So I went into /usr/src/lib/libpthread and did make/install. I noticed > that it installed libkse.so.* but not libpthread.so.*. > What you need to do is create a link between libpthread.so.* and libkse.so.*: cd /usr/lib ln libkse.so... libpthread.so Also see this cvs entry about libkse on FreeBSD 5.0: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libpthread/Makefile?rev=1.35&content-type=text/x-cvsweb-markup -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
QUARANTINED: Returned mail: see transcript for details
The message "Returned mail: see transcript for details" from Post Office, sent on 12/9/2005 19:30 was quarantined because it contained either an executable file, a batch file or a screen saver file. All of these types of attachments are considered security risks. Please consult your mail administrator who can release the message. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Missing libpthread.so.*
FBSD 5.0 I'm getting missing libpthread.so.* error, so I copied it from another FBSD box, and now getting: Undefined symbol "__malloc_lock" So I went into /usr/src/lib/libpthread and did make/install. I noticed that it installed libkse.so.* but not libpthread.so.*. Help... ** Computer problems? ... ..http://www.multibyte.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
On Fri, Dec 09, 2005 at 08:43:14AM -0700, Scott Long wrote.. > Wilko Bulte wrote: > >On Fri, Dec 09, 2005 at 07:49:33AM -0700, Scott Long wrote.. > > > >>Thomas E. Zander wrote: > >> > >>>Hi, > >>> > >>>just installed a fresh 6.0 on a laptop, using the standard boot > >>>manager. The problem is: The default volume of pcspeaker can't be tuned > >>>in bios or anywhere else before loading a sound driver (in this case > >>>snd_ich). This especially means the pc speaker volume is always set to > >>>100% at every boot which results in a horribly loud beep which I am > >>>afraid the built-in "speakers" can't do very often :-) > >>> > >>>So what about this one: > >>> > >>>--- /usr/src/sys/boot/i386/boot0/boot0.S > >>>+++ boot0.S > >>>@@ -201,9 +201,7 @@ > >>>/* > >>>* Start of input loop. Beep and take note of time > >>>*/ > >>>-main.10: movb $ASCII_BEL,%al # Signal > >>>- callw putchr# beep! > >>>- xorb %ah,%ah# BIOS: Get > >>>+main.10: xorb %ah,%ah# BIOS: Get > >>> int $0x1a # system time > >>> movw %dx,%di# Ticks when > >>> addw _TICKS(%bp),%di# timeout > >>> > >>>This might be an issue on other architectures (amd64?) as well, I > >>>haven't checked that right now. > >>> > >>>TIA, > >>>Riggs > >>> > >> > >>The beep is useful for some people who run headless systems, but it > >>is indeed annoying for others, especially with laptops in quiet places. > >>We should probably conditionalize this on a variable that can go into > >>/etc/make.conf. Note that amd64 uses the i386 bits here. > > > > > >Originally it was introduced (IIRC) to accomodate visually impaired users > >of FreeBSD. So the install CDs etc better keep it enabled. > > It is highly irritating for everyone else, though. So, creating an option to disable it would help them. And still allow the others the benefit of the 'beep'. There is enough unusable (for visually imparred people) crud in this world, like all these silly Flash-websites etc. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
On Fri, 09. Dec 2005, at 16:00 +, David Malone wrote according to [Re: Boot manager beep]: > On Fri, Dec 09, 2005 at 08:43:14AM -0700, Scott Long wrote: > > > It is highly irritating for everyone else, though. > > Not quite everyone - if I'm working on a few machines I find it > useful to know when a particular machine has reached the boot stage, > so I can tell it to go into single user mode. It is particularly > useful on machines where the BIOS tages ages to do its stuff. Probably it isn't even a real problem on most boxes. Usually standard desktops and servers (maybe) have their pc speaker which is set to a reasonable volume at boot time. I never found this beep annoying in my servers. Just came across it when I had to reinstall my notebook because of a hard drive crash and 6.0 installed this beeping boot loader. So probably as Scott pointed out, it might be best to let the user choose a quiet loader as an option. Naturally, boot0 is a tiny program, it shouldn't be a problem to build a boot0nobeep as well and install one of them depending on settings, maybe even early during sysinstall ?! Riggs -- - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. "It committed suicide." said Marvin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
On Fri, Dec 09, 2005 at 08:43:14AM -0700, Scott Long wrote: > >Originally it was introduced (IIRC) to accomodate visually impaired users > >of FreeBSD. So the install CDs etc better keep it enabled. > It is highly irritating for everyone else, though. Not quite everyone - if I'm working on a few machines I find it useful to know when a particular machine has reached the boot stage, so I can tell it to go into single user mode. It is particularly useful on machines where the BIOS tages ages to do its stuff. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD 6.0-RELEASE] Incorrect geometry for VIA RAID0 array
Yes, the array is being recognized properly. The problem seems to be in the via_read_meta() function in sys/dev/ata/ata_raid.c. Essentially, the problem is that in the case of a striped array, the function overwrites the total sector count of the top-level raid descriptor with the sector count of each enumerated disk, rather than adding to the sector count. Last night I installed FreeBSD on the first half of the array, and then built a custom kernel with a modification to fix this issue. The full 148G capacity of the array is now recognized, and I've been able to expand my slice with fdisk and bsdlabel/newfs a new partition in the added space. So far I've written about a gig of data to the new partition, and everything is working fine. Note that even if you had a striped array, you wouldn't see this issue because in your case the OS would use the promise_read_meta() routine, which doesn't have this bug. On 12/8/05, greg byshenk <[EMAIL PROTECTED]> wrote: > > On freebsd-stable, [EMAIL PROTECTED] (Jason Harmening) wrote: > > > Here's the dmesg output from the installer: > > > ad4: 70911MB at ata2-master SATA150 > > ad6: 70911MB at ata3-master SATA150 > > ar0: 70911MB status: READY > > ar0: disk0 READY using ad4 at ata2-master > > ar0: disk1 READY using ad6 at ata3-master > > Are you _sure_ that the array is being recognized properly? > > Based on the dmesg output, it looks like the controller is being read > as a 74G drive. > > FWIW, this is the section of my dmesg output, for a _mirror_: > > ad4: 78167MB at ata2-master UDMA133 > ad6: 78167MB at ata3-master UDMA133 > ar0: 77247MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master > > > > On 12/7/05, Jason Harmening <[EMAIL PROTECTED]> wrote: > > > > I'm trying to install FreeBSD 6.0-RELEASE on a RAID0 array attached to > the > > > VIA 8237 controller on my Asus A8V Deluxe motherboard. The array > consists > > > of two 74G drives. The installer recognizes the array as ar0, but > when I > > > enter FDISK to set up my partition, the size of the array is only > recognized > > > as 74G, rather than the true 148G. I've double-checked all my BIOS > > > settings, and nothing seems out of order. Please help! > > > -- > greg byshenk - [EMAIL PROTECTED] - Leiden, NL > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
Wilko Bulte wrote: On Fri, Dec 09, 2005 at 07:49:33AM -0700, Scott Long wrote.. Thomas E. Zander wrote: Hi, just installed a fresh 6.0 on a laptop, using the standard boot manager. The problem is: The default volume of pcspeaker can't be tuned in bios or anywhere else before loading a sound driver (in this case snd_ich). This especially means the pc speaker volume is always set to 100% at every boot which results in a horribly loud beep which I am afraid the built-in "speakers" can't do very often :-) So what about this one: --- /usr/src/sys/boot/i386/boot0/boot0.S +++ boot0.S @@ -201,9 +201,7 @@ /* * Start of input loop. Beep and take note of time */ -main.10: movb $ASCII_BEL,%al # Signal - callw putchr# beep! - xorb %ah,%ah# BIOS: Get +main.10: xorb %ah,%ah# BIOS: Get int $0x1a # system time movw %dx,%di# Ticks when addw _TICKS(%bp),%di# timeout This might be an issue on other architectures (amd64?) as well, I haven't checked that right now. TIA, Riggs The beep is useful for some people who run headless systems, but it is indeed annoying for others, especially with laptops in quiet places. We should probably conditionalize this on a variable that can go into /etc/make.conf. Note that amd64 uses the i386 bits here. Originally it was introduced (IIRC) to accomodate visually impaired users of FreeBSD. So the install CDs etc better keep it enabled. It is highly irritating for everyone else, though. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
On Fri, Dec 09, 2005 at 07:49:33AM -0700, Scott Long wrote.. > Thomas E. Zander wrote: > >Hi, > > > >just installed a fresh 6.0 on a laptop, using the standard boot > >manager. The problem is: The default volume of pcspeaker can't be tuned > >in bios or anywhere else before loading a sound driver (in this case > >snd_ich). This especially means the pc speaker volume is always set to > >100% at every boot which results in a horribly loud beep which I am > >afraid the built-in "speakers" can't do very often :-) > > > >So what about this one: > > > >--- /usr/src/sys/boot/i386/boot0/boot0.S > >+++ boot0.S > >@@ -201,9 +201,7 @@ > > /* > > * Start of input loop. Beep and take note of time > > */ > >-main.10:movb $ASCII_BEL,%al # Signal > >-callw putchr# beep! > >-xorb %ah,%ah# BIOS: Get > >+main.10:xorb %ah,%ah# BIOS: Get > > int $0x1a # system time > > movw %dx,%di# Ticks when > > addw _TICKS(%bp),%di# timeout > > > >This might be an issue on other architectures (amd64?) as well, I > >haven't checked that right now. > > > >TIA, > >Riggs > > > > The beep is useful for some people who run headless systems, but it > is indeed annoying for others, especially with laptops in quiet places. > We should probably conditionalize this on a variable that can go into > /etc/make.conf. Note that amd64 uses the i386 bits here. Originally it was introduced (IIRC) to accomodate visually impaired users of FreeBSD. So the install CDs etc better keep it enabled. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Automatic installation problem
Hello! I'm trying to make full automatical FreeBSD installation. I have the following lines in my install.cfg: command="echo sshd_enable="YES" >> /etc/rc.conf" system command="echo 'pass' | /usr/sbin/pw useradd -u user -h 0 -G wheel" system But during installation I get some error messages: > DEBUG: dispatch: calling resword 'system' > echo sshd_enable=YES >> /etc/rc.conf: not found I am using FreeBSD 6.0-RELEASE. -- Best regards, Tarasov Alexey. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager beep
Thomas E. Zander wrote: Hi, just installed a fresh 6.0 on a laptop, using the standard boot manager. The problem is: The default volume of pcspeaker can't be tuned in bios or anywhere else before loading a sound driver (in this case snd_ich). This especially means the pc speaker volume is always set to 100% at every boot which results in a horribly loud beep which I am afraid the built-in "speakers" can't do very often :-) So what about this one: --- /usr/src/sys/boot/i386/boot0/boot0.S +++ boot0.S @@ -201,9 +201,7 @@ /* * Start of input loop. Beep and take note of time */ -main.10: movb $ASCII_BEL,%al # Signal - callw putchr# beep! - xorb %ah,%ah# BIOS: Get +main.10: xorb %ah,%ah# BIOS: Get int $0x1a # system time movw %dx,%di# Ticks when addw _TICKS(%bp),%di# timeout This might be an issue on other architectures (amd64?) as well, I haven't checked that right now. TIA, Riggs The beep is useful for some people who run headless systems, but it is indeed annoying for others, especially with laptops in quiet places. We should probably conditionalize this on a variable that can go into /etc/make.conf. Note that amd64 uses the i386 bits here. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Questions about geom-gate and RAID1/10 and CARP
Michael Schuh wrote: i have searched informations about geom-gate and RAID1 or Raid10 over TCP/IP. But nothing relevant found, so that i write the questions here. Actually, there has been some discussion about this, but you probably won't like the result... Has anyone any experiences with geom-gate and doing RAID1 or RAID10 over TCP/IP? And has anyone a good solution in Production use? Theoretically, yes - it can be done this way. You could use any GEOM-aware RAID solution, and throw ggate in the mix. When I tried it (back in early 5-stable days) I could create the setup just fine, but could not stabilise it - gmirror kept loosing the ggate component(s), possibly(?) due to timeouts from network latency. IIRC, just around the time 6-stable was branched there was a similar report from somebody else. BUT, ggate has had several changes since then that should address performace, so maybe it's time to try again. There's another problem: if you do get the over-the-network mirroring to work, you won't be able to share data this way: the one-writer-multiple-readers scenario won't work because the filesystem doesn't support it on the reader side (when the data gets modified by the writer, the reader doesn't know about it). Readonly-for-all scenario will work. (see also this: http://docs.freebsd.org/cgi/mid.cgi?438B05D6.3000108 - I'll maybe find the time soon) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Questions about geom-gate and RAID1/10 and CARP
Hello, i have searched informations about geom-gate and RAID1 or Raid10 over TCP/IP. But nothing relevant found, so that i write the questions here. My opinion/scenario that i thinked out: i Have 2 Machines Host A and Host B, both Machines have 2 Networkinterfaces, one official and one private. The official interfaces getting bound with CARP for traffic, so that peoples think they connect's to one Machine. So that i get, for this case, a high-availibility-solution on CARP-Base. The private interfaces get to be used to derive my data from one Machine to the other Machine, and also spend the possibility to watch the other Machine. To this point everything is clear for me, so let us go to the more complex part. In the description above i be suppressed to derive the shared-data for booth machines from one to another. My idea was to build an RAID1 or RAID10 over the Network by using geom-gate and vinum respective gvinum. Has anyone any experiences with geom-gate and doing RAID1 or RAID10 over TCP/IP? And has anyone a good solution in Production use? My Questions about these thema are: a) Is this generally possible with FreeBSD ? b)is this generally a good idea ? c)how must i setup the RAID? d)who must build the raid? Host A? Host B? or BOTH? e) can i use this way to become an HA-Solution? I have searched in the Web about these questions, but nothing found. Only things that i have found was Mirroring (local) and mode generals related to local work with geom. Thanks for help. regards Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdtar / libarchive bug?
- Original Message - From: "Brian Fundakowski Feldman" <[EMAIL PROTECTED]> Just don't let it accept a 0-length gzip. That wont work as the gzip file does have length ( 20 bytes ) where as the resulting tar file doesn't ( 0 bytes ) Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdtar / libarchive bug?
- Original Message - From: "Dan Nelson" <[EMAIL PROTECTED]> I managed to make it create 0-byte files: $ touch a $ tar cvf b.tar --exclude a a $ tar zcvf b.tar.gz --exclude a a $ ls -la b.tar* -rw-r--r-- 1 dan wheel 0 Dec 8 17:37 b.tar -rw-r--r-- 1 dan wheel 20 Dec 8 17:37 b.tar.gz $ gunzip -vl b.tar.gz method crc date time compressed uncompr. ratio uncompressed_name defla Dec 8 17:3720 0 0.0% b.tar This works because at the time tar creates the output file, it doesn't know that I have excluded all the listed files. I am leaning towards an empty archive being legal, though, since it makes scripting easier. There may be cases where you are archiving files generated daily, and you want to distinguish "no data today" from "the archiver didn't run". At worst it should print a warning. That's the reason here as well. It was a scripted process where we create a tar.gz of new / changed files and a shell script to remove old files. As some files had been removed only in this instance we ended up with a script file with entries but nothing in the tar.gz which then barfed on "install". Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bsdtar / libarchive bug?
- Original Message -
From: "Brian Fundakowski Feldman" <[EMAIL PROTECTED]>
I don't think it will "happily create empty tar.gz files", even where
by empty you mean the tar itself inside of the gz.
{"/home/green" [EMAIL PROTECTED] tar cfv x.tar
tar: no files or directories specified
{"/home/green" [EMAIL PROTECTED] tar cfvz x.tar.gz
tar: no files or directories specified
{"/home/green" [EMAIL PROTECTED] ls -l x.ta*
ls: x.ta*: No such file or directory
Try this instead which is how I managed it ( not on purpose )
touch test.files
tar --files-from test.files -czf blank.tar.gz
Then to trigger the bug:
tar -xvzf blank.tar.gz
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot manager beep
Hi, just installed a fresh 6.0 on a laptop, using the standard boot manager. The problem is: The default volume of pcspeaker can't be tuned in bios or anywhere else before loading a sound driver (in this case snd_ich). This especially means the pc speaker volume is always set to 100% at every boot which results in a horribly loud beep which I am afraid the built-in "speakers" can't do very often :-) So what about this one: --- /usr/src/sys/boot/i386/boot0/boot0.S +++ boot0.S @@ -201,9 +201,7 @@ /* * Start of input loop. Beep and take note of time */ -main.10: movb $ASCII_BEL,%al # Signal - callw putchr# beep! - xorb %ah,%ah# BIOS: Get +main.10: xorb %ah,%ah# BIOS: Get int $0x1a # system time movw %dx,%di# Ticks when addw _TICKS(%bp),%di# timeout This might be an issue on other architectures (amd64?) as well, I haven't checked that right now. TIA, Riggs -- - Now the world has gone to bed | Now I lay me down to sleep- -- Darkness won't engulf my head | Try to count electric sheep -- --- I can see by infra-red | Sweet dream wishes you can keep --- How I hate the night| How I hate the night ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 05:04:57PM -0700, secmgr wrote: > Whatever you do, don't complain about it on this list, or you'll just be > told that if you really wanted raid, you should be running SCSI disks > and a raid adapter. They may allow that 3ware does ok, but no ATA drive > should ever be relied on and even s/w raid on scsi is only for ignorant > lusers who are too cheap to do the "right thing". > Those who think I run to hyperbole need only visit the archives. I know what you mean but I think this write-up is a bit too harsh. As long as the goal is to get _as reliable as possible_ without spending too much money, I think software RAID has its niche. Besides, I've seen a few hardware RAID controllers having issues themselves (and they weren't the cheapest ones available either). > One can only hope that gvinum actually works in 6 vs the buggy and > incomplete alpha code that shipped in 5.x. Having a man page is nice, > but I'd rather have a raid 5 set that didn't panic the system and > corrupt the set when it lost a drive (and this with modern scsi drives > and adapter). I haven't seen this (luckily!). I do know that sometime in 5.x there was a RAID-5 bug in gvinum but then again the whole vinum/gvinum transition was pretty dodgy back then. This is why I waited until 6.x to migrate. > I'd strongly suggest anyone using GEOM raid to do some > fault insertion testing of their setup prior to actually relying on it. I did. It worked. --Stijn -- There are of course many problems connected with life, of which some of the most popular are 'Why are people born?', 'Why do they die?', and `Why do they spend so much of the intervening time wearing digital watches?' -- Douglas Adams, "The Hitchhikers Guide To The Galaxy" pgpjc3SVsnCEy.pgp Description: PGP signature
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 05:04:57PM -0700, secmgr wrote: > Christian Brueffer wrote: > > >>On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote: > >> > >> > >>In short, don't write gvinum off just yet. Documentation is around the > >>corner (as a result of a SoC project). > >> > >> > > > >Actually gvinum(8) has been committed to CURRENT and RELENG_6 a couple > >of days ago. > > > >- Christian > > > > > Whatever you do, don't complain about it on this list, or you'll just be > told that if you really wanted raid, you should be running SCSI disks > and a raid adapter. They may allow that 3ware does ok, but no ATA drive > should ever be relied on and even s/w raid on scsi is only for ignorant > lusers who are too cheap to do the "right thing". > > Those who think I run to hyperbole need only visit the archives. One > can only hope that gvinum actually works in 6 vs the buggy and > incomplete alpha code that shipped in 5.x. Having a man page is nice, > but I'd rather have a raid 5 set that didn't panic the system and > corrupt the set when it lost a drive (and this with modern scsi drives > and adapter). I'd strongly suggest anyone using GEOM raid to do some > fault insertion testing of their setup prior to actually relying on it. > Hmm, wasn't that a bug in the 5.3-RELEASE version that was fixed shortly after the release? - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp8ZAncFjEvQ.pgp Description: PGP signature
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 08:49:15PM +0100, Christian Brueffer wrote: > On Thu, Dec 08, 2005 at 02:31:00PM +0100, Stijn Hoop wrote: > > On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote: > > > I was thinking about gvinum for the storage server, but given the > > > current documentation and the discussions about it now, I don't want to > > > risk it. > > > > IMHO it's pretty stable in 6.0. I've been running gvinum RAID-5 for a > > while now; other than one strange panic (something to do with out of > > memory situations, see kern/89660) I haven't had a hitch yet. That > > said, I haven't needed to replace a disk yet either (I've demoed this > > but it was not yet needed in production use). > > > > In short, don't write gvinum off just yet. Documentation is around the > > corner (as a result of a SoC project). > > Actually gvinum(8) has been committed to CURRENT and RELENG_6 a couple > of days ago. Ah, I missed that, great :-) --Stijn -- Help Wanted: Telepath. You know where to apply. pgpjxs5Of2tKy.pgp Description: PGP signature
Re: mcast-tools make my 6.0-STABLE kernel panic
Dear Suzuki-san, SUZUKI Shinsuke ([EMAIL PROTECTED]) wrote: > I've committed the fix to -current. > Could you please try the latest ip6_mroute.c in the -current? > (There is no difference between -current and 6-stable except for the > fix. So it is safe to use the ip6_mroute.c in -current for 6-stable. > But you feel it awkward, please wait until I merge it to RELENG-6 in a > few days) thanks ! I'll grab revision 1.35. regards, -dikshie- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
