Mr Denninger
Oh, I think he douched with a molatov cocktail, after his boyfriend fisted him. >will somebody filter Mr Denninger from the list his >postings are beginning to to >irritate and look more and >more like the ravings of an offensive lunatic who drank >too much methanol during new years celebrations -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
* From: Karl Denninger <[EMAIL PROTECTED]> Wow, that was good! I'm going to nominate this for "this century's most amusing message on the FreeBSD lists" award. :) Satoshi "you can figure out which century I'm talking about" Asami To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested
Mike Smith wrote: > > > I'm putting together some specs for a type of firewall appliance using > > the eventual released version of FreeBSD 4 (targeting 4.x because I need > > GCC 2.95.x as core compiler). My current machine specs use the > > following hardware which I am not yet sure will be well supported. > > > > FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) > > AMD K6-III/450 processor > > (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) > > These should all be fine, although you may want to go for something in the > 5400rpm range if thermal issues concern you. The speed differential > isn't massive, and disk speed probably isn't an issue for you. This hard drive seems to be somewhat extraordinary in regards to heat generation. I'm using two now in a test machine, it remains cool to the touch after a 'make world -j4' under FreeBSD 3.3 even though enclosed in a standard single fan cooled ATX case. It also outperformed a 10k WD Digital Advantage SCSI drive in the same task by about 7%. I have to really hand it to Maxtor for releasing some exceedingly high quality drives as of late. I'm concerned about possible poor interactions with the new ATA driver however. I have seen very little posted regarding the MVP3 or MVP4 chipset in freebsd-current. > > Poware IM-7500 IDE Hot Swappable IDE RAID device > > This one might be interesting. Does it do automatic rebuilds? > Yes, it claims to do on-line recovery. It is also OS independent. I will be testing a few of these units this month. Try http://www.poware.com.tw for more info. > > Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp > > devices?) > > Yup. > > > I have not been running CURRENT extensively, so I would like to know > > anyone's experiences with any of the above hardware, or any > > recommendations on hardware with a better price/performance ratio at a > > low thermal (chassis is very compact). > > You might want a slower and cooler CPU (consider a Celeron), a board with > less cache (cooler), and slower disks. Without any sort of benchmarking > feel for your application, it's hard to know where tradeoffs are > worthwhile. I was looking at the PPGA Celerons earlier. I'm a little concerned about the cache size though. What is interesting to me is the K6-III/450's and their 64KB Level 1 cache and 256KB Level 2 cache. I am guessing that coupled with the FIC PAG-2130's 2MB Level 3 cache, there could be a significant performance advantage for memory intensive processing. I may put together a Celeron 500 system and benchmark it against a K6-III/450 with the FIC motherboard. Perhaps the K6-III cache size advantage is just theoretical. Processing performance is critical as I would like to minimize as much as possible the additional latency added by the firewall and filtering applications, as the amount of conditions being processed is extensive. > > I was also considering using a NIC from 3COM, or Netgear, or even > > Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently > > the best option. I understand the 3C905 may also be good, but it lacks > > an onboard processor. > > The EtherExpress Pro/100 also 'lacks an onboard processor'. Both the > Intel and 3Com adapters are good choices; I would be choosing based on > price and performance in your application. Aah, yes, I was thinking of the Pro/100 Intelligent Server Adapter with the i960 processor (I'm don't see any driver support for this one). Hmm... is there any supported NICs with a processor to offload the main CPU? What about the Thunderlan based cards? Perhaps spending more on a NIC could justify a lower powered CPU. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] Thanks for the insights. -- Nathan Kinsman |[EMAIL PROTECTED]| |http://www.mentisworks.com| Managing Partner / Network Systems Architect, Mentisworks LLC Voice/Fax: | Chicago | +1 312 803-2220 | Sydney | + 61 2 9475 4500 All correspondence should be considered confidential. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mr Denninger has a problem
will somebody filter Mr Denninger from the list his postings are beginning to to irritate and look more and more like the ravings of an offensive lunatic who drank too much methanol during new years celebrations To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
On Sun, 2 Jan 2000, Matthew Dillon wrote: > --> enters stage right > > ... opens door ... > heyy a party! And nobody invited me! > > U, Why's the piano broken in two and all the tables > overturned? Ahhh, whats with all the stares? guys? > Guys! > > exits stage left (at a run) --> > > -Matt Aww, you missed it! We had a broken bottle with your name on it! :-) Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
--> enters stage right ... opens door ... heyy a party! And nobody invited me! U, Why's the piano broken in two and all the tables overturned? Ahhh, whats with all the stares? guys? Guys! exits stage left (at a run) --> -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SUBMIT: compat.linux.pathmunge
I'm bringing this back up to -current to kick around some more. We may want to move it to -emulators. On Sun, 2 Jan 2000, Marcel Moolenaar wrote: > > This isn't intended as a 'final solution' :-) The problem is *very* > > difficult since you're asking the syscall to intuit what the user/program > > intends to do with the file. > Hmmm.. What we want is a way to tell the Linuxulator on a process/binary > level whether we want /compat/linux overlaying or not. Indeed, backup > clients will pick up /compat/linux as an ordinary directory without > overlaying and that is exactly what we want. In most cases we do want > the overlaying. Having process/binary granularity would be more useful, but is hard to implement in an inobrusive way, as we're discovering below. :) Binary granulatirty could be an issue for shells. > > If you could tag dynamic loader open()s you could have a selective > > translator for just that, but when it's hunting for /etc/host.conf, which > > one do you give it? Is it a call from resolv+ looking for it's > > configuration, or a backup client putting it on tape? > > What about brandelf? When a static ELF binary is branded as `Linux', we > have overlaying; when it's branded as 'LinuxBSD' (or what's in a name) > it's a Linux binary that don't want/need overlaying. Dynamic ELF > binaries are more tricky, but can make to work by setting > LD_LIBRARY_PATH in a wrapper. Yuck. brandelf is an agreed-on standard (or is supposed to be) and it wouldn't be appropriate to abuse it. I'd be more apt to run the target app in a wrapper that makes a 'shut off translation for this pid' type syscall then execve()s the app. Kinda like nohup. > > I don't have any ideas at this point. I'd be willing to add some features > > to this patch (i.e. specify arbitrary root) but I don't want to sit on it > > until linuxmode grows a psychic user mind reader. :) > > :-) It isn't as easy as it looks, eh? Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested
> I'm putting together some specs for a type of firewall appliance using > the eventual released version of FreeBSD 4 (targeting 4.x because I need > GCC 2.95.x as core compiler). My current machine specs use the > following hardware which I am not yet sure will be well supported. > > FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) > AMD K6-III/450 processor > (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) These should all be fine, although you may want to go for something in the 5400rpm range if thermal issues concern you. The speed differential isn't massive, and disk speed probably isn't an issue for you. > Poware IM-7500 IDE Hot Swappable IDE RAID device This one might be interesting. Does it do automatic rebuilds? > Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp > devices?) Yup. > I have not been running CURRENT extensively, so I would like to know > anyone's experiences with any of the above hardware, or any > recommendations on hardware with a better price/performance ratio at a > low thermal (chassis is very compact). You might want a slower and cooler CPU (consider a Celeron), a board with less cache (cooler), and slower disks. Without any sort of benchmarking feel for your application, it's hard to know where tradeoffs are worthwhile. > I was also considering using a NIC from 3COM, or Netgear, or even > Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently > the best option. I understand the 3C905 may also be good, but it lacks > an onboard processor. The EtherExpress Pro/100 also 'lacks an onboard processor'. Both the Intel and 3Com adapters are good choices; I would be choosing based on price and performance in your application. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD 4.0-RELEASE hardware specs, advice/experience requested
Howdy all, I'm putting together some specs for a type of firewall appliance using the eventual released version of FreeBSD 4 (targeting 4.x because I need GCC 2.95.x as core compiler). My current machine specs use the following hardware which I am not yet sure will be well supported. FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) AMD K6-III/450 processor (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) Poware IM-7500 IDE Hot Swappable IDE RAID device Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp devices?) I have not been running CURRENT extensively, so I would like to know anyone's experiences with any of the above hardware, or any recommendations on hardware with a better price/performance ratio at a low thermal (chassis is very compact). I was also considering using a NIC from 3COM, or Netgear, or even Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently the best option. I understand the 3C905 may also be good, but it lacks an onboard processor. Anything with better performance and lower CPU utilization then the EtherExpress PRO/100+?? Thanks for any assistance. -- Nathan Kinsman |[EMAIL PROTECTED]| |http://www.mentisworks.com| Managing Partner / Network Systems Architect, Mentisworks LLC Voice/Fax: | Chicago | +1 312 803-2220 | Sydney | + 61 2 9475 4500 All correspondence should be considered confidential. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new PCM problems
Thanks. I would've tried to fix it myself, but I am not too familiar with programming for a soundcard. I'm only famaliar with the ata driver right now. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 2 Jan 2000, Brian Fundakowski Feldman wrote: > On Sun, 2 Jan 2000, Kenneth Wayne Culver wrote: > > > OK, there is still the static problem with the pcm driver with a ViBRA16X > > soundcard. It also seems that the problem with xmms's analyzer is gone. > > However, now whenever a sound that is shorter than roughly 1 second or so > > plays, it gets cut short. The sound doesn't completely play. I just > > thought I'd let someone know what is going on here on my -CURRENT box. > > I'm noticing the exact same thing. I'll CC this to cg and tanimura, > since they're the big maintainers of the driver. > > > = > > | Kenneth Culver | FreeBSD: The best OS around.| > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: AgRSkaterq | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > = > > (I didn't know you lived so close :) > > -- > Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / > [EMAIL PROTECTED]`--' > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
On Sun, 2 Jan 2000, Kip Macy wrote: > > Any pointers to web pages on setting up a killfile? The signal to noise > ratio on this list is dropping rapidly. I haven't done it myself, but I know that you can read some of the documentation for procmail (/usr/ports/mail/procmail) and easily forward certain mail to /dev/null. If you want an example, I'm certain I could come up with one for you :) > -Kip -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
Hi David, My post is not really based upon the last Karl vs. Pohl thread. It is more on what I have observed quietly over the last few months . If the behavior is left unchecked you can rest assure that their will be more flares up. Again, to have waited for Karl to cool off is not that unreasonable to ask if the interested party wanted to reason with him. I supposed that there are some who are a virtuoso at calming and reasoning with extremely angry people. I have always opted to wait for the person to calm down and then try to reason with them. Perhaps , in this new WWW world my ways are wrong and old fashioned... Take Care Guys, I am back to hacking and yes I am having a great time ! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new PCM problems
On Sun, 2 Jan 2000, Kenneth Wayne Culver wrote: > OK, there is still the static problem with the pcm driver with a ViBRA16X > soundcard. It also seems that the problem with xmms's analyzer is gone. > However, now whenever a sound that is shorter than roughly 1 second or so > plays, it gets cut short. The sound doesn't completely play. I just > thought I'd let someone know what is going on here on my -CURRENT box. I'm noticing the exact same thing. I'll CC this to cg and tanimura, since they're the big maintainers of the driver. > = > | Kenneth Culver| FreeBSD: The best OS around.| > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > = (I didn't know you lived so close :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
At 08:20 PM 1/2/00 -0800, David Greenman wrote: > >He is just expressing his point. From what I can tell someone removed him > >from the list with no reason and now he is angry. I probably would be too. > >That is not at all what happend. Karl went off the deep end about phk >recommending a Motorola GPS to do timekeeping. Then, after a pile of >insulting messages from Karl, Karl made an accusation that someone removed >him from three of the mailing lists. For at least two of those lists, he >was simply wrong. For the third (freebsd-current), there is no evidence >to support his claim. > > >Also, I can tell that someone is doing some good covering up. Its ashame to > >see leaders do this. > >How can you tell that? There is no evidence to support that. *I'm* >certainly not covering anything up and I've seen no reason to believe that >anyone else is, either. > >-DG PLEASE STOP THIS There are things that need fixing and this is going nowhere. You are all very talented people. Enough Enough Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
On Sun, Jan 02, 2000 at 09:59:28PM -0600, wrote: > He is just expressing his point. From what I can tell someone removed him > from the list with no reason and now he is angry. I probably would be too. That does not excuse his style of communication. Shouting and calling people names is no solution. It will damage the relationship between the involved parties and will make an agreement among them impossible. You can express emotions, but please do it in a civilized and controlled way. I usually recommened the following books to disagreeing parties. They are easy to read and tell you much about communication. Getting to Yes, by Fisher and Ury, ISBN 0140157352 (Focusing on Interests, not on Positions) Getting Past No, by Ury, ISBN 0553371312 (Negotiating Your Way from Confrontation to Cooperation) -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
>He is just expressing his point. From what I can tell someone removed him >from the list with no reason and now he is angry. I probably would be too. That is not at all what happend. Karl went off the deep end about phk recommending a Motorola GPS to do timekeeping. Then, after a pile of insulting messages from Karl, Karl made an accusation that someone removed him from three of the mailing lists. For at least two of those lists, he was simply wrong. For the third (freebsd-current), there is no evidence to support his claim. >Also, I can tell that someone is doing some good covering up. Its ashame to >see leaders do this. How can you tell that? There is no evidence to support that. *I'm* certainly not covering anything up and I've seen no reason to believe that anyone else is, either. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The mails from dev-null
On Sun, 2 Jan 2000 [EMAIL PROTECTED] wrote: > Congratulations, Karl. You just proven to the world what a complete > asshole you really are. > > Now get out of here. We don't want you. Will whoever this is, please stop? There is no valid reason for anonymity here (and to be honest, in this situation, it rather strikes me as cowardly) and we don't need the sentiments, because you're only going to provoke this further. Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
On Sun, 2 Jan 2000, Amancio Hasty wrote: > I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) > > > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. > > The proper tactic to resolve the conflict should have > been to wait a cool off period and then slug it off > technically. Nevertheless, instead of waiting for > Karl to cool off and attempt to ration with him , > it was much easier to drive him further down: hence > thru censorship the "technical" argument was won > with virtually no technical effort at all -- Like I said > earlier very very nice tactic ! Amancio, you are making assumptions, ones that are completely incorrect here. Karl's frothing started with a lot of raging at Steve on the ports list, and at the entire structure of ports. Poul didn't get into it until quite a bit later, and it was Karl who went after Poul, not vice versa. Poul reacted to someone accusing him of a complete lack of integrity (with no more evidence than McCarthy had in the 50's) merely by asking him to step back a little ways before he really annoyed folks. I wonder if I would react as well? What's more, while you're right that Poul's sometimes been abrasive in the past, his behaviour has been so above reproach here that I felt it necessary to jump in, just to highlight the fact, and maybe to avoid having people jump at the assumption you made (I referenced that directly in my post). I've never met Poul personally, but I *have* met Jonathan Bresler. That last post of Karl's, well, if that doesn't categorize him in your eyes, then I guess nothing will. Believe me, Amancio, Jonathan didn't deserve that. I think everyone really should let this darn thread die Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no LYING message to me
He is just expressing his point. From what I can tell someone removed him from the list with no reason and now he is angry. I probably would be too. Also, I can tell that someone is doing some good covering up. Its ashame to see leaders do this. Sam - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, January 02, 2000 9:56 PM Subject: Your misleading, no, LYING message to me > Congratulations, Karl. You just proven to the world what a complete asshole you really are. > > Now get out of here. We don't want you. > > -- > This message has been sent via an anonymous mail relay at www.no-id.com. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
Alright, that was childish and uncalled for. People need to learn to deal with these kinds of things differently. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 2 Jan 2000 [EMAIL PROTECTED] wrote: > Congratulations, Karl. You just proven to the world what a complete asshole you >really are. > > Now get out of here. We don't want you. > > -- > This message has been sent via an anonymous mail relay at www.no-id.com. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Your misleading, no, LYING message to me
Congratulations, Karl. You just proven to the world what a complete asshole you really are. Now get out of here. We don't want you. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
>I have to say that PHK has become the MASTER at pissing >people off, ensuring that his opponent goes the deep end >and staying calm so the blame obviously does not fall on >him. Got to admit his formula is very very nice 8) > > >By a long shot the problem is NOT Karl. It takes at least >TWO to engage in a combatitive conflict -- that is if >you are not schizophreniac. > >The proper tactic to resolve the conflict should have >been to wait a cool off period and then slug it off >technically. Nevertheless, instead of waiting for >Karl to cool off and attempt to ration with him , >it was much easier to drive him further down: hence >thru censorship the "technical" argument was won >with virtually no technical effort at all -- Like I said >earlier very very nice tactic ! May I respectfully request that people not jump to conclusions without a lot more to go on than some angry accusations. I would also like to say that Poul-Henning's behavior in this thread was exceptional and that Karl had no reason to react the way he did. I think Karl owes a lot of people some apologies. His behavior was clearly inappropriate and continues to be so. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
> I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) I dont think so. Whatever PHK may or may not have done in the past his answers in this latest storm in a tea cup were more than reasonable and informative. > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. Yes it was two - Karl vs reasoned discussion. tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
>Someone logged into HUB the EDITED me out of the CURRENT mailing list. As near as I can tell, noone with the ability to su was logged into hub earlier today when you claim that you were removed. As far as I know, noone had removed you. I have not seen any messages (other than your claim) or any other evidence that would indicate such an action occured. >Again, who was su'd or logged into the majordomo account (or any account >with write access to the list directories) a few hours ago? Noone as far as I can tell. Jonathan is a man of exceptional integrity and you have no basis for making the accusations that you have against him. I think you owe him an apology. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest version of threads library
Do you know what the timeline is on this integration? -Kip On Sun, 2 Jan 2000, Daniel Eischen wrote: > Kip Macy <[EMAIL PROTECTED]> wrote: > > Sorry for sending this again but when I first sent it -current was > > embroiled in a flame war. > > > > I would like to use the latest threads source because my application does > > not work correctly with the signal handling bugs in 3.x's threads. > > However, it does not appear that I can change it without replacing all of > > libc. Is this correct? Or is there some simple change I can make to the > > files in libc that include pthread_private.h when compiled in libc_r? > > Hmm, I think the only thing that will bite you in bringing in -currents > libc_r are the socket.h changes that went in around Nov 24, 1999. I > haven't tried it myself... YMMV > > Someone is working on merging -current libc_r into -stable, so perhaps > if you want to hold out a little longer, it'll get done for you. > > Dan Eischen > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
I have to say that PHK has become the MASTER at pissing people off, ensuring that his opponent goes the deep end and staying calm so the blame obviously does not fall on him. Got to admit his formula is very very nice 8) By a long shot the problem is NOT Karl. It takes at least TWO to engage in a combatitive conflict -- that is if you are not schizophreniac. The proper tactic to resolve the conflict should have been to wait a cool off period and then slug it off technically. Nevertheless, instead of waiting for Karl to cool off and attempt to ration with him , it was much easier to drive him further down: hence thru censorship the "technical" argument was won with virtually no technical effort at all -- Like I said earlier very very nice tactic ! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: latest version of threads library
Kip Macy <[EMAIL PROTECTED]> wrote: > Sorry for sending this again but when I first sent it -current was > embroiled in a flame war. > > I would like to use the latest threads source because my application does > not work correctly with the signal handling bugs in 3.x's threads. > However, it does not appear that I can change it without replacing all of > libc. Is this correct? Or is there some simple change I can make to the > files in libc that include pthread_private.h when compiled in libc_r? Hmm, I think the only thing that will bite you in bringing in -currents libc_r are the socket.h changes that went in around Nov 24, 1999. I haven't tried it myself... YMMV Someone is working on merging -current libc_r into -stable, so perhaps if you want to hold out a little longer, it'll get done for you. Dan Eischen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Note about Majordomo (Re: Your misleading, no, LYING message to me)
On Sun, 2 Jan 2000, Karl Denninger wrote:
> That's not the issue either. Again, someone logged into HUB and
> removed me.
>
> Again, who was su'd or logged into the majordomo account (or any account
> with write access to the list directories) a few hours ago?
This isn't required ... with nothing more then the admin password to the
mailing list, anyone around the world could easily have removed anyone
else from the list by sending an administrative request to the majordomo
account...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Your misleading, no, LYING message to me
On Sun, Jan 02, 2000 at 06:55:50PM -0800, Jonathan M. Bresler wrote:
> From: "Jonathan M. Bresler" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> In-reply-to: <[EMAIL PROTECTED]> (message from Karl
> Denninger on Sun, 2 Jan 2000 18:50:17 -0600)
> Subject: Recent cat fighting in the FreeBSD mailing lists.
> Message-Id: <[EMAIL PROTECTED]>
> Date: Sun, 2 Jan 2000 18:50:01 -0800 (PST)
> Sender: [EMAIL PROTECTED]
>
>
> Karl,
>
> Hi, my name is Jonathan Bresler. I am the postmaster for
> FreeBSD. Usually, I tend to stay in the background and do the
> postmastering. The recent fractious behavior in the mailing lists has
> become so galling that I am forced to "come out from behind the
> curtain."
>
> Lets set the record straight on a couple items:
>
> 1. Karl, you are still subscribed to both of the "missing" mailing
> lists. I disabled the "which" command for those two lists:
> freebsd-arch and freebsd-security-notifications. That is why your
> subscription to those two lists did not appear when you sent the
> "which " request to majordomo.
That's not the issue.
Someone logged into HUB the EDITED me out of the CURRENT mailing list.
You are mis-representing the facts. Exactly what I expect from CORE.
> 2. I remove people that bounce mail. I dont send them email to tell
> them that I am reomving them for bouncing mailI sincerely expect
> that the notification email would bounce. A bounced email is one that
> appears in the list(s)-owners mailbox on hub. So, sites with problems
> that do *not* result in immediate bounces and that fix their mail
> problems before the email is aged out of the queue, dont have to
> worry. If you suspect that you have been removed, or that I might
> remove you, send me an email...explain that you have been having a
> mail problem and when you expect the problem to be resolved.
That's not the issue either. Again, someone logged into HUB and
removed me.
Again, who was su'd or logged into the majordomo account (or any account
with write access to the list directories) a few hours ago?
> 3. Everyone, the FreeBSD mailing lists are a community resource.
> While there are many lists. There is only one set of lists. We all
> share in that set of lists. When one or more people significantly
> degrade the quality of the lists, the only option is to remove that
> person from the lists. I have done this about six times in my role as
> postmaster these past 5 or 6 years.
Yeah, so who's the asshole who signed in and removed me?
> 4. Core recently published guidelines for committers. These
> guidelines included a minimal acceptable behavior standard. The recent
> emails fail to come within a country mile of meeting those standards.
> Which perhaps does not matter as the author is not a committer.
> Nonetheless, the author is degrading our mailing lists and I am
> empowered to act on behalf to the project to prevent people from
> degrading the quality of the lists.
>
> It seems that today around 4:51pm PST, Karl unsubscribed from
> freebsd-{security,hackers,ports,scsi}.
Yes, *AFTER* I was removed by a fraud who signed into HUB. *I* unsubscribed
from those lists LATER, after resubscribing to current, posting my "where"
command, and making it known that someone else had been tampering.
Go look at the DATE AND TIME STAMPED messages, AND the logs on hub.
Or would you prefer to protect the GUILTY?
> So what's the upshot of all this?
>
> Karl, take a two week sabbatical from the FreeBSD mailing lists.
> Consider it enforced leave. I will remove you from the remaining two
> mailing lists: freebsd-{announce,security-notifications}.
Jonathan, two words for you: Go Stuff.
Got it?
It ain't a two-week sabbatical. Its a permanent one. You and your
blow-hard assholes can go shove this "enforced leave" up your puny pucker
and leave it there until it explodes. I beg in front of NOBODY, and
that goes double for puny-brained cowards such as yourself who try to
deliberately cover up for the unethical and inappropriate actions of
other "annointed ones".
You DISGUST me.
I've had it.
You Lord-Mighty-and-all-things-shitheaded have pulled this crap before.
Yes, YOU. YOU is a plural Jonathan, for YOU speak for CORE.
YOU identify as CORE and Postmaster. I want to know who the person was
who su'd on Hub and removed me from the lists.
I want that person ejected from your systems and publically called out for
what they did. IN PUBLIC.
I know damn well you won't do it, but the call remains the same, and until
and unless you *DO* take this action your posting here is nothing other than
YET ANOTHER fraud and piece of deceit.
You should be ashamed of yourself for trying to cover up the actions of a
member of your own crew. Yet that is EXACTLY what I have come to expect
from FreeBSD-CORE - insular, treehouse behavior unfitting of anything except
public illumination.
Walnut Creek should be ashamed. And
RE: One final note and a "bite me" to you
On Sun, 2 Jan 2000, Will Andrews wrote: > Theo split from NetBSD. Again, further ignorance. I suggest you sit down with a > copy of /usr/share/misc/bsd-family-tree and read a little history that you seem > to have missed. Cool, I never even knew that was there...now I have something to look at when I tell ppl that Unix has been around for 30+ years :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a "bite me" to you
On Sun, 2 Jan 2000, Karl Denninger wrote:
> Just for those of you who think this whole "magical unsubscribe" is
> a "fluke";
I run/maintain the PostgreSQL mailing lists ... there is a piece of
software that you can "add on" called bouncefilter that auto-unsubscribes
based on various criteria ...
... and those criteria don't require the subscriber to authenticate his
unsubscription ... last time this thread went through, I believe
Paol(sp?) was doing similar manually?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
latest version of threads library
Sorry for sending this again but when I first sent it -current was embroiled in a flame war. I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? I am running: FreeBSD io.lyris.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Dec 27 15:20:33 PST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/KMM i386 Thanks. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent cat fighting in the FreeBSD mailing lists.
Karl,
Hi, my name is Jonathan Bresler. I am the postmaster for
FreeBSD. Usually, I tend to stay in the background and do the
postmastering. The recent fractious behavior in the mailing lists has
become so galling that I am forced to "come out from behind the
curtain."
Lets set the record straight on a couple items:
1. Karl, you are still subscribed to both of the "missing" mailing
lists. I disabled the "which" command for those two lists:
freebsd-arch and freebsd-security-notifications. That is why your
subscription to those two lists did not appear when you sent the
"which " request to majordomo.
2. I remove people that bounce mail. I dont send them email to tell
them that I am reomving them for bouncing mailI sincerely expect
that the notification email would bounce. A bounced email is one that
appears in the list(s)-owners mailbox on hub. So, sites with problems
that do *not* result in immediate bounces and that fix their mail
problems before the email is aged out of the queue, dont have to
worry. If you suspect that you have been removed, or that I might
remove you, send me an email...explain that you have been having a
mail problem and when you expect the problem to be resolved.
3. Everyone, the FreeBSD mailing lists are a community resource.
While there are many lists. There is only one set of lists. We all
share in that set of lists. When one or more people significantly
degrade the quality of the lists, the only option is to remove that
person from the lists. I have done this about six times in my role as
postmaster these past 5 or 6 years.
4. Core recently published guidelines for committers. These
guidelines included a minimal acceptable behavior standard. The recent
emails fail to come within a country mile of meeting those standards.
Which perhaps does not matter as the author is not a committer.
Nonetheless, the author is degrading our mailing lists and I am
empowered to act on behalf to the project to prevent people from
degrading the quality of the lists.
It seems that today around 4:51pm PST, Karl unsubscribed from
freebsd-{security,hackers,ports,scsi}.
So what's the upshot of all this?
Karl, take a two week sabbatical from the FreeBSD mailing lists.
Consider it enforced leave. I will remove you from the remaining two
mailing lists: freebsd-{announce,security-notifications}.
That's all folks! I am going back "behind the curtain" to
continue my spam fighting efforts. Try to behave a little better out
here. Some of the mailing list subscribers are trying to sleep.
jmb
--
Jonathan M. Bresler FreeBSD Core Team, Postmaster [EMAIL PROTECTED]
FreeBSD--The Power to Serve http://www.freebsd.org/
PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a "bite me" to you
On Sun, 2 Jan 2000, Karl Denninger wrote: > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. Not that you'll listen, but: OpenBSD split from NetBSD. FreeBSD is and always has been a seperate project from NetBSD. Your credibility isn't getting any better. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: several procmail jobs hang ...
According to Andreas Klemm: > procmail 3.14 bug, or does the new procmail version introduce > some new features in area where in -current is something wrong. > Not easy to say for me ... Check your locking settings on both versions. You may find that you're using different locking mechanisms... PS : and please, don't quote your own entire message, everybody including you has already seen it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 05:44:57PM -0600, Karl Denninger wrote: > > We can point to the Internet's evolution of these "treehouse" organizations > and show off how PROUD we are of them and those who support them. > Let's start a nice short list, shall we? > > Network Solutions. > ARIN. > FreeBSD-CORE. > > > Shall I keep going? Yes, all the way to switching everyone of your machines to RedHat Linux, or OpenBSD (since in the past you've claimed to be so security concerned); and then removing yourself from anything even remotely FreeBSD related. I'm sure the various Linux lists and development groups would greet you with open arms and would be so very glad to benefit from your "contributions". -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 06:08:31PM -0600, Karl Denninger wrote: > As for whoever the person is who force-removed me from the list, trust > me on this - I won't forget that act, and until you're identified and > permanently removed from both the list and the entire project you'll > have no contributions from me to your little treehouse project in any > way, shape or form. Do you promise?? We'll really have *NO* contributions from you? Including contributing your emails to this list?? Pretty please!!! Oh please say this is true. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Karl's day off
OK, enough of this, let Karl be on his own for a while. Stop responding, Karl's too mad to think clearly, and you guys are just baiting him. Anyone responding is asking for addition to the kill-file. I already posted this to ports, where the other part of this has unfortunately spilled into. I won't post again. Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a "bite me" to you
On Sun, 2 Jan 2000, Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; This does not involve any of the rest of the list subscribers, and I'm sure the majority of us don't really want to see EITHER side's rantings. Really, grow up. If you want to flame each other, start a mailing list and do so, if you want to split, do so. Regardless, I don't care for your language nor your spamming of your political (ambiguous at that) beliefs. Just go away or be useful. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: One final note and a "bite me" to you
On 03-Jan-00 Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; > > All unsubscribes and subscribes to FreeBSD's lists must be > authenticated. Majordomo is set to confirm all transactions. It is still possible for Majordomo to screw up by itself. > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. Theo split from NetBSD. Again, further ignorance. I suggest you sit down with a copy of /usr/share/misc/bsd-family-tree and read a little history that you seem to have missed. Besides, with all your commercial "work" to do, what purpose would it serve to have done your own split? -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2 hours to compile mysql?
On Sat, Jan 01, 2000 at 01:32:19PM -0600, Dan Nelson wrote: > > The box is a 333MHz PII, with 64M ram. Do I just need more ram to be > > able to compile in reasonable time, or is something broken? > > You probably need more RAM. sql_yacc.cc is one of those "worst-case" > programs as far as gcc is concerned; I don't think gcc can parse large > case statements like this efficiently. Adding "--with-low-memory" to > your port Makefile, in the CONFIGURE_ARGS line, will help. I have the same thing compiling mysql (daily updated cvs of ports, and just yesterday recompiled my world). I have a P2 450 with 256MB of ram. So, I don't think that RAM is an issue here... -Steve -- Stephan van Beerschoten Email: [EMAIL PROTECTED] Network EngineerLuna Internet Services PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a "bite me" to you
Grow up. -Kip On Sun, 2 Jan 2000, Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; > > All unsubscribes and subscribes to FreeBSD's lists must be > authenticated. Majordomo is set to confirm all transactions. > > Whoever did this did it directly by logging into Freefall and editing the > mailing list files themselves, or otherwise forged the request so as > to get the "key" for the response. > > Have a nice year folks. THIS time, with only other people to benefit from > my participation here, I'm not willing to play. > > Some of you will remember that about two years ago a SIMILAR forged > unsubscribe was sent in for me during a heated discussion right here > on this list. > > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. > > This makes twice - and that's enough for me. > > As for you Paol, perhaps some day you'll stop trying to bullshit people. > Occasionally when you do that you run into someone who has AT LEAST a > single class in physical science and understands the uncertainty of > measurements. > > -- > -- > Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org > Isn't it time we started putting KIDS first? See the above URL for > a plan to do exactly that! > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
One final note and a "bite me" to you
Just for those of you who think this whole "magical unsubscribe" is a "fluke"; All unsubscribes and subscribes to FreeBSD's lists must be authenticated. Majordomo is set to confirm all transactions. Whoever did this did it directly by logging into Freefall and editing the mailing list files themselves, or otherwise forged the request so as to get the "key" for the response. Have a nice year folks. THIS time, with only other people to benefit from my participation here, I'm not willing to play. Some of you will remember that about two years ago a SIMILAR forged unsubscribe was sent in for me during a heated discussion right here on this list. Theo was right in splitting off from you folks. I should have followed him a couple of years ago and done my own split. Now, its simply not worth it. This makes twice - and that's enough for me. As for you Paol, perhaps some day you'll stop trying to bullshit people. Occasionally when you do that you run into someone who has AT LEAST a single class in physical science and understands the uncertainty of measurements. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CORE-treehouse felling
Naw, it ain't worth the gas for the chainsaw. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Any pointers to web pages on setting up a killfile? The signal to noise ratio on this list is dropping rapidly. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Doesn't change the facts Gary. This isn't the first time either Gary. Plausable deniability isn't going to wash here. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 07:33:10PM -0500, Gary Palmer wrote: > Karl Denninger wrote in message ID > <[EMAIL PROTECTED]>: > > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. > > Wrong side of the SMTP transaction Karl. Logs on the receiver mean > *NOTHING*. And you don't have an account, or root, or access to the > majordomo bounce mailbox on hub, so your claim isn't worth the > electrons you used to send it. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results:
In all the years I've known you, Karl, you've always thought you were so far above everyone else. Apparently, you get off on treating people like shit. Go away, we don't need your "contributions" here... I'm not sure we ever did. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Karl Denninger wrote in message ID <[EMAIL PROTECTED]>: > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. Wrong side of the SMTP transaction Karl. Logs on the receiver mean *NOTHING*. And you don't have an account, or root, or access to the majordomo bounce mailbox on hub, so your claim isn't worth the electrons you used to send it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
On Sunday, 2 January 2000 at 18:09:37 -0600, Karl Denninger wrote: > On Sun, Jan 02, 2000 at 04:05:22PM -0800, Matthew Jacob wrote: >> On Sun, 2 Jan 2000, Karl Denninger wrote: >> >>> Oh, so the treehouse maggots continue to fester, eh? >>> >>> Nice move shitheads. >>> >>> Do you intend to continue? >>> >>> Consider this forwarded to Steve, a withdrawal of my port, and notice of my >>> intent to post it along with a transcript on my web page for HomeDaemon. >>> >>> Who is the two-bit-peckerhead who removed my subscription to several of >>> the lists? >> >> Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if >> there was a mail bounce. >> >> It may be a stupid mail robot problem, not a human out to get you. If so, >> you've directed your vituperation at the wrong ip address/port combo- try >> port 9 instead of port 25. > > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. > > And yes, I do know how SMTP works too. > > Nice try though. Karl, based on the behaviour you have shown and continue to show, I think you've given every reason for being removed from the mailing lists. But you appear only to have been removed from one, and anyway, you get warned before you're removed. So I suspect that it's been some other glitch; they do happen. On the other hand, I would be really grateful if you would go away and shut up. If it requires forcibly removing you from the mailing lists to get this to happen, then I'm in favour of doing so. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Uh, Matthew, I have the system logs here. I'm root. There was no bounce. And yes, I do know how SMTP works too. Nice try though. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 04:05:22PM -0800, Matthew Jacob wrote: > > Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if > there was a mail bounce. > > It may be a stupid mail robot problem, not a human out to get you. If so, > you've directed your vituperation at the wrong ip address/port combo- try > port 9 instead of port 25. > > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > Oh, so the treehouse maggots continue to fester, eh? > > > > Nice move shitheads. > > > > Do you intend to continue? > > > > Consider this forwarded to Steve, a withdrawal of my port, and notice of my > > intent to post it along with a transcript on my web page for HomeDaemon. > > > > Who is the two-bit-peckerhead who removed my subscription to several of > > the lists? > > > > -- > > -- > > Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org > > Isn't it time we started putting KIDS first? See the above URL for > > a plan to do exactly that! > > > > > > - Forwarded message from [EMAIL PROTECTED] - > > > > To: [EMAIL PROTECTED] > > From: [EMAIL PROTECTED] > > Subject: Majordomo results: which > > Reply-To: [EMAIL PROTECTED] > > Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) > > > > -- > > > > which denninger.net > > > > > > NOTE: the "which" command does not show subscriptions > >to either freebsd-arch or freebsd-security-notifications > > > > > > The string 'denninger.net' appears in the following > > entries in lists served by [EMAIL PROTECTED]: > > > > ListAddress > > === > > freebsd-hackers [EMAIL PROTECTED] > > freebsd-ports [EMAIL PROTECTED] > > freebsd-scsi[EMAIL PROTECTED] > > freebsd-security[EMAIL PROTECTED] > > > > > > > > - End forwarded message - > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 04:58:57PM -0700, Warner Losh wrote: > Karl, I was my hands of this conversation. You aren't listening. > > We have custom hardware. We're a control and measurement system. The > <10ns is needed for that control and measurement part. The sync we > get of the system clock, like I said before, is on the order of a few > hundred ns on pentium hardware and a few us on 486 hardware. > > That's why we spend more $$ on the hardware. If you don't like it, > forget the chill pill and just play in traffic. > > I'm done with this conversation. > > Warner That's fine Warner, but isn't germane to the point. Poul claimed that his favorite device was *superior* in *ordinary* use. Then he admitted that he needed custom hardware (as you do as well) to get that kind of accuracy. Recommending something that is twice as expensive for people trying to keep network time when the INHERENT stability of the system clock is at least a couple orders of magnitude worse than the proclaimed PPS stability is just flat STUPID. Maintaining and defending that position when it is pointed out in bold letters that the uncertainty on the system clock and interrupt latency is FAR greater than the claimed 10ns resolution has only three possible explainations: 1. The poster has an interest in the device being shilled for. 2. The poster has an IQ below that of tap water's temperature in Celcius. 3. The poster has never in their life had to specify an uncertainty with a measurement, which in and of itself disqualifies them for the discussion at hand. As for whoever the person is who force-removed me from the list, trust me on this - I won't forget that act, and until you're identified and permanently removed from both the list and the entire project you'll have no contributions from me to your little treehouse project in any way, shape or form. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Majordomo@FreeBSD.ORG: Majordomo results: which]
Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if there was a mail bounce. It may be a stupid mail robot problem, not a human out to get you. If so, you've directed your vituperation at the wrong ip address/port combo- try port 9 instead of port 25. On Sun, 2 Jan 2000, Karl Denninger wrote: > Oh, so the treehouse maggots continue to fester, eh? > > Nice move shitheads. > > Do you intend to continue? > > Consider this forwarded to Steve, a withdrawal of my port, and notice of my > intent to post it along with a transcript on my web page for HomeDaemon. > > Who is the two-bit-peckerhead who removed my subscription to several of > the lists? > > -- > -- > Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org > Isn't it time we started putting KIDS first? See the above URL for > a plan to do exactly that! > > > - Forwarded message from [EMAIL PROTECTED] - > > To: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] > Subject: Majordomo results: which > Reply-To: [EMAIL PROTECTED] > Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) > > -- > > which denninger.net > > > NOTE: the "which" command does not show subscriptions >to either freebsd-arch or freebsd-security-notifications > > > The string 'denninger.net' appears in the following > entries in lists served by [EMAIL PROTECTED]: > > ListAddress > === > freebsd-hackers [EMAIL PROTECTED] > freebsd-ports [EMAIL PROTECTED] > freebsd-scsi[EMAIL PROTECTED] > freebsd-security[EMAIL PROTECTED] > > > > - End forwarded message - > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
Karl, I was my hands of this conversation. You aren't listening. We have custom hardware. We're a control and measurement system. The <10ns is needed for that control and measurement part. The sync we get of the system clock, like I said before, is on the order of a few hundred ns on pentium hardware and a few us on 486 hardware. That's why we spend more $$ on the hardware. If you don't like it, forget the chill pill and just play in traffic. I'm done with this conversation. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[Majordomo@FreeBSD.ORG: Majordomo results: which]
Oh, so the treehouse maggots continue to fester, eh? Nice move shitheads. Do you intend to continue? Consider this forwarded to Steve, a withdrawal of my port, and notice of my intent to post it along with a transcript on my web page for HomeDaemon. Who is the two-bit-peckerhead who removed my subscription to several of the lists? -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! - Forwarded message from [EMAIL PROTECTED] - To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Majordomo results: which Reply-To: [EMAIL PROTECTED] Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) -- which denninger.net NOTE: the "which" command does not show subscriptions to either freebsd-arch or freebsd-security-notifications The string 'denninger.net' appears in the following entries in lists served by [EMAIL PROTECTED]: ListAddress === freebsd-hackers [EMAIL PROTECTED] freebsd-ports [EMAIL PROTECTED] freebsd-scsi[EMAIL PROTECTED] freebsd-security[EMAIL PROTECTED] - End forwarded message - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS-UP newppbus for beta-testing
Hi there! FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current A major ppbus(4) release is available for beta-testing. It includes the port of the ppbus framework to the newbus system. http://www.freebsd.org/~nsouch/ppbus.html provides usefull notes about the configuration of ppbus through the MACHINE file and the newppbus developement progression (stability, caveats...) The newppbus will come in remplacement to the previous standalone ppbus architectural system. I did not read recent announces about future FreeBSD 4.x releases :( Of course, newppbus introduction would better before any -stable jump. Note that, only probe/attach and function interfaces were concerned by the port and tests are consequently only regression tests. The port was not to hard and the result should not be too bad. Moreover the current ppbus high level drivers stress the system well I think: vpo (SCSI controller), lpt (with PS data filtered by ghostscript and interrupts) Feel free to contact me for more, Nicholas. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 06:37:31PM -0500, Bill Fumerola wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > How many millions does Paol have to count in HIS bank as a result of this > > shilling and "advocacy"? > > > > SOME OF US have *REAL* successes to point to - not just bullshit pats on the > > back. > > Like eDNS, right? > > -- > - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - > > > PS. Some of us aren't in it for the money. No, you're in it to pat yourself on the back and play "treehouse". We can point to the Internet's evolution of these "treehouse" organizations and show off how PROUD we are of them and those who support them. Let's start a nice short list, shall we? Network Solutions. ARIN. FreeBSD-CORE. Shall I keep going? .At least the folks in it for the money are honest - you know exactly what their goals are. With the rest you have real trouble figuring out exactly what REALLY drives them. I prefer my cards face up, thank you very much. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new PCM problems
OK, there is still the static problem with the pcm driver with a ViBRA16X soundcard. It also seems that the problem with xmms's analyzer is gone. However, now whenever a sound that is shorter than roughly 1 second or so plays, it gets cut short. The sound doesn't completely play. I just thought I'd let someone know what is going on here on my -CURRENT box. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: several procmail jobs hang ...
On Sun, Jan 02, 2000 at 08:00:03PM +0100, Andreas Klemm wrote: > A few days ago I updated -current and build /usr/local completely new. > One remaining problem is, that procmail jobs seems to hang. > First it was a port problem, I installed some (for me) basic services > in /home/local and procmail tried to call /usr/local/bin/formail. > Now I recompiled procmail using normal /usr/local as PREFIX, but > the jobs still hang. After some time they seem to timeout and > mail seems to be delivered. Can't say exactly if I have some mail > loss. I don't know that much about procmail itself and how you use it, but with the default local delivery you can get such a situation if there's a stale lock file in /var/mail. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, 2 Jan 2000, Karl Denninger wrote: > How many millions does Paol have to count in HIS bank as a result of this > shilling and "advocacy"? > > SOME OF US have *REAL* successes to point to - not just bullshit pats on the > back. Like eDNS, right? -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - PS. Some of us aren't in it for the money. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 06:31:22PM -0500, Bill Fumerola wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > Why the hell Walnut Creek wastes their money on your type REMAINS beyond > > my comprehension. > > It really hasn't been a problem for anyone but you. It's more successful, > then say, alternative top level domain projects that have gone nowhere. > > -- > - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - Really? How many millions does Paol have to count in HIS bank as a result of this shilling and "advocacy"? SOME OF US have *REAL* successes to point to - not just bullshit pats on the back. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 03:05:49PM -0800, David Schwartz wrote: > > > Now explain to me how stability of your timing source ON THOSE MACHINES > > is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > > between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. > > A battle you would win is if you said, "synchronizing the time of other > UNIX machines without specialized hardware over a LAN or WAN". :) Of course, which is my point. > You can see 2 microsecond differences inside a single machine with no > specialized hardware. MICROseconds. *NOT* NANOseconds, which is what Paol was claiming! > You can see 5 microseconds over a good LAN. For > example, youknow.youwant.to is synchronized to both tick.gpsclock.com and > tock.gpsclock.com through a full-duplex 100Mbps LAN switch. Watch this: > > > ntpdate -q -p 8 209.133.29.16 209.133.29.20 > server 209.133.29.16, stratum 1, offset -0.000298, delay 0.02579 > server 209.133.29.20, stratum 1, offset -0.000302, delay 0.02579 > 2 Jan 15:01:01 ntpdate[2491]: adjust time server 209.133.29.20 > offset -0.000302 sec > > Note that it claims that Tick and Tock agree with each other to 5 > microseconds. But it has been unable to keep its own time to any better than > 300 microseconds (it's been under heavy load, swapping in fact). Correct. And the issue there is that its the COMPLETE timekeeping environment, not some bullshit-manufacturered claim of 10ns time stability that is CLEARLY bogus. As soon as you put a REAL workload on the machine(s) involved interrupt latency starts to cause trouble. Hell, just READING THE FRIGGING PORT to SEE the PPS output involves interrupt latency which is INDETERMINATE beyond a LOT more elapsed time than 10ns! > In actual reality, the GPSClock 200 is better than the specifications > indicate. If it really did alternate between 1us early pulses and 1us late > pulses, stability would be measurably impacted. NTP is very good at > smoothing things out anyway, especially since it only probes the clock every > 64 seconds or so. > > David Schwartz > http://www.gpsclock.com/ Yep. My entire point, David, is that there is ZERO actual, real-world difference between your reasonably-priced receiver and the shilled-for Motorola receiver that Poul and others like to promote at twice the price. Now if you're willing to stuff a custom PCI board (that in and of itself probably violates all manner of FCC regulations in terms of emissions) to keep nanosecond-level track of the number of "ticks" between seeing a PPS signal and the processor getting around to reading the latch, then Poul and the shills might be right on a TECHNICAL level - as long as they never actually USE that computer for anything, never access a disk, and never hit any other I/O port. But that's not the real world, its not a real application, and geeking-up something just to prove you can (while probably breaking the law in terms of emissions - the clock rates to get nanosecond timing accuracy are non-trivial, and that board would need FCC appoval here in the states) doesn't count. It also has ZERO relavence to those of us who want to keep time on our networks. It is precisely this kind of elitism and bullshit that I continually run into when trying to deal with the "treehouse" FreeBSD kids, and in this particular instance its so blatent that I simply refuse to shut up about it. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, 2 Jan 2000, Karl Denninger wrote: > Why the hell Walnut Creek wastes their money on your type REMAINS beyond > my comprehension. It really hasn't been a problem for anyone but you. It's more successful, then say, alternative top level domain projects that have gone nowhere. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 06:17:59PM -0500, Chuck Robey wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > > If you intend to keep up this "sour grapes" attitude, despite all > > > the helpful answers you have gotten so far, you should consider > > > stopping before you have worn out your welcome. > > > > > > -- > > > Poul-Henning Kamp FreeBSD coreteam member > > > > > > > > Yes, the "F-word". > > > > You have no ability to determine "my welcome". > > Karl, you've now managed to irritate a lot of folks. Jumping on Steve, > who is normally a huge worker, and totally inoffensive, was really pushing > things, but then jumping on Poul, who is somewhat easier to touch off, > well, you have been just about advertising "I want a fight!", although no > one's really given you much reason for it. > > Poul's response was right, you should come back in a few days, when you've > had time to cool off. No one else really wants to keep the fight going. I don't give a shit what Poul wants - or what you want. Corporate shilling does NOT go past me without a response, and Paol is completely full of shit in the context (time servers used by HUMANS for ORDINARY uses) that we were discussing at the time. Sticking custom PCI boards into a PC that count nanosecond-level clock transitions before the processor can get around to reading the input latch (at a cost of several hundred dollars MORE as a one-off science project) *DOES NOT COUNT*. Since I see the FreeBSD "treehouse" mentality hasn't changed, I guess my ORIGINAL assessment was correct. Duplicity and bullshit still rule the roost, just as they did a couple of years ago. Why the hell Walnut Creek wastes their money on your type REMAINS beyond my comprehension. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
Although your interaction is amusing, I subscribe to this mailing list to keep up to date on -current and not to see the script for the latest sitcom for geeks. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 03:13:10PM -0800, David O'Brien wrote: > On Sun, Jan 02, 2000 at 04:53:55PM -0600, Karl Denninger wrote: > > On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: > ..snip.. > > > If you intend to keep up this "sour grapes" attitude, despite all > > > the helpful answers you have gotten so far, you should consider > > > stopping before you have worn out your welcome. > > > > Go fuck yourself Poul. > > > > Yes, the "F-word". > > You have no ability to determine "my welcome". > > Karl you are one fscking asshole. As a member of this list, you *HAVE* > worn out your welcome in my inbox. So what? > You asked Poul-Henning about *good* timekeeping HW. He told you. $600 > isn't that much for computer server related hardware. Warner seconded > the recommendation. So what? > You pay less, you don't get the best. Its up to you to weigh your needs > vs. what you are willing to pay. Shilling for a difference that is irrelavent is horseshit. It amounts to lying. Statistically these two time sources are almost EXACTLY equivalent. > And you want to bitch?? What is your fscking problem? Its a bullshit argument David and is nothing other than BLATENT shilling for Motorola - at someone else's expense! Without a specialized board that counts these nanosecond ticks from the time it gets the PPS signal to the time the latch is read this kind of accuracy claim is worth exactly NOTHING. WITHOUT it, which is EXACTLY what REAL WORLD use of these devices is going to be running under, the impact is ZERO. Further, the ACTUAL impact in the real world of time stability to the dozen-nanosecond-range is ALSO zero, with the possible exception of physical control processes in the nuclear research field (such applications are NOT running on "standard" Unix machines!) Finally, in the world of sync'ing time between systems (say, in a multiple server cluster) that kind of precision is ALSO worth ZERO! NOBODY with off-the-shelf hardware can obtain repeatable 10ns results from a standard Unix machine. NOBODY. And THAT is a fact, easily determined through nothing more than Intel's databooks on their processors and the interrupt response time they exhibit. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, 2 Jan 2000, Karl Denninger wrote: > > If you intend to keep up this "sour grapes" attitude, despite all > > the helpful answers you have gotten so far, you should consider > > stopping before you have worn out your welcome. > > > > -- > > Poul-Henning Kamp FreeBSD coreteam member > > > > Yes, the "F-word". > > You have no ability to determine "my welcome". Karl, you've now managed to irritate a lot of folks. Jumping on Steve, who is normally a huge worker, and totally inoffensive, was really pushing things, but then jumping on Poul, who is somewhat easier to touch off, well, you have been just about advertising "I want a fight!", although no one's really given you much reason for it. Poul's response was right, you should come back in a few days, when you've had time to cool off. No one else really wants to keep the fight going. Chuck Robey| Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 04:53:55PM -0600, Karl Denninger wrote: > On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: ..snip.. > > If you intend to keep up this "sour grapes" attitude, despite all > > the helpful answers you have gotten so far, you should consider > > stopping before you have worn out your welcome. > > Go fuck yourself Poul. > > Yes, the "F-word". > You have no ability to determine "my welcome". Karl you are one fscking asshole. As a member of this list, you *HAVE* worn out your welcome in my inbox. You asked Poul-Henning about *good* timekeeping HW. He told you. $600 isn't that much for computer server related hardware. Warner seconded the recommendation. You pay less, you don't get the best. Its up to you to weigh your needs vs. what you are willing to pay. And you want to bitch?? What is your fscking problem? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 03:50:35PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Karl Denninger writes: > : Yes, you have HARDWARE timers that do that. > : > : So what? > : > : I'm talking about TIME SERVERS on UNIX machines. > > So am I. > > : You know, ntpd and friends? Yes, that. > > That's one of the things in our application. So what? > : Now explain to me how stability of your timing source ON THOSE MACHINES > : is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > : between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. > > It is better because the variance in the measurements that we make is > much smaller than 1uS would give. Not possible without custom hardware. The inherent uncertainty in a PPS interface delivered through a parallel port in the interrupt context of a common grade-processor is greater than picosecond claims. Now the *integration* of many of these signals may not be, but the point still holds. That you FLUNKED your first science course where the uncertainty of measurements was discussed, and the boundaries on certainty were laid out, does not change those FACTS. You CANNOT declare a measurement (no matter what it is) to be more precise than the sum of ALL uncertainties in the measurement domain. This is a material FACT, and no amount of posturing changes it. PAYING for precision in a measurement source that is a few orders of magnitude beyond the response windows of what it is connected to is *STUPID*. This includes your claim of anything approaching 10ns resolution on consumer-grade computer hardware. > : I'm simply not interested in NON-GERMANE devices to the discussion; we were > : talking about FreeBSD on REAL computers, not specialty hardware for process > : control or nuclear physics experiments. > > Get a life Karl. I was telling you about my experiences and if you > don't like it, take a chill pill or go play in traffic. > > Warner Go stick your finger in a 220V socket, or sit on whatever Poul uses to do what I asked HIM to do just a few minutes ago. Perhaps that would reduce the population of this group by two people who don't deserve the term "scientist" applied to them. Scientists. BAH! You'd have to flunk first-semester physical science courses to not understand how the boundaries of uncertainty in measurements work, and why buying a reference source that is more precise than the LEAST PRECISE element in your entire measurement chain is almost always a COMPLETE waste of money. If you have two elements in a measurement chain, and one has 10ns repeatability and the other has 10us repeatability, the measurement you obtain is FOR ALL INTENTS AND PURPOSES equivalent to the 10us one. Even if the OTHER timebase is only accurate to 10us, the TOTAL inaccuracy is 20us MAXIMUM. What, Warner, is the INTERRUPT LATENCY (including processing time) specification on a Pentium? You know, the amount of time the chip requires to (1) recognize the INTERRUPT being dragged, (2) save the current context, (3) switch to the interrupt context, and (4) execute the FIRST instructions in that context. Now add to that the ACTUAL gate delays for ALL the gates between your piece of wire and the processor. Then tell me that this sums to ~10ns. You're smoking hard drugs - the processor cannot respond to the interrupt until (potentially) a multi-cycle instruction has been COMPLETED. Further, the act of responding itself requires several MORE cycles, as does the physical act (in the interrupt context) of reading the input latch. In fact, for an ISA parallel port, the speed involved in reading that latch is limited by ISA bus speed! Be careful with the pontification here Warner - some of us actually HAVE done hard real-time work and some of us also know a bit about how MPUs REALLY work in the REAL world. Posturing does NOT work with me on topics like this. You ain't getting no 10ns resolution off any production FreeBSD box without specialized timekeeping hardware that READS the pps output and has its OWN high-precision clock so it can tell the processor how many ticks elapsed from the time IT saw the PPS output until the processor got around to reading the latch. No way in hell. You want to claim otherwise? Fine - show me a gate analysis on the port you connect that clock to (from the wire to the processor's INTERRUPT pin), along with a gate propagation analysis on the processor and the execution path it must take, both worst and best case, from receipt of a signal on the interrupt pin until the FIRST instruction in the handler is executed. Have fun. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: xntpd - VERY old folks, how about updating? :-)
> Now explain to me how stability of your timing source ON THOSE MACHINES > is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. A battle you would win is if you said, "synchronizing the time of other UNIX machines without specialized hardware over a LAN or WAN". :) You can see 2 microsecond differences inside a single machine with no specialized hardware. You can see 5 microseconds over a good LAN. For example, youknow.youwant.to is synchronized to both tick.gpsclock.com and tock.gpsclock.com through a full-duplex 100Mbps LAN switch. Watch this: > ntpdate -q -p 8 209.133.29.16 209.133.29.20 server 209.133.29.16, stratum 1, offset -0.000298, delay 0.02579 server 209.133.29.20, stratum 1, offset -0.000302, delay 0.02579 2 Jan 15:01:01 ntpdate[2491]: adjust time server 209.133.29.20 offset -0.000302 sec Note that it claims that Tick and Tock agree with each other to 5 microseconds. But it has been unable to keep its own time to any better than 300 microseconds (it's been under heavy load, swapping in fact). In actual reality, the GPSClock 200 is better than the specifications indicate. If it really did alternate between 1us early pulses and 1us late pulses, stability would be measurably impacted. NTP is very good at smoothing things out anyway, especially since it only probes the clock every 64 seconds or so. David Schwartz http://www.gpsclock.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Karl Denninger writes: > >Yes, you have HARDWARE timers that do that. > >So what? I have a commercially available PCI card which costs about the same as a good diskdrive... >I'm talking about TIME SERVERS on UNIX machines. > >You know, ntpd and friends? Yes, that. Yes, exactly. Suggest you poke gps.freebsd.dk a bit and see what performance it shows. >I'm simply not interested in [...] Karl, I'm simply not interested in continuing to listen to your belly aching. Unless you all of sudden develop something constructive to say, you will see this as my last reply. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Karl Denninger writes: > >On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: > >> In message <[EMAIL PROTECTED]>, Karl Denninger writes: > >> > >> >Why spend twice what Mr. Schwartz seems to want to charge? > >> > >> Well, suit your own political manifests as you will, but the Motorola > >> unit is the best time receiver you can buy for humane amounts of money. > >> > >> You can see some of my measurements at http://phk.freebsd.dk > > > >Yeah, so what? > > > >Your system can't resolve events to that degree of accuracy, so the ability > >of the receiver to deliver them is irrelavent. > > Karl, > > In fact I *do* have a computer that can resolve events to +/- 10nsec > (http://gps.freebsd.dk) so I need it. In fact that machine is > probably one of the best NTP servers in the entire world right now. > > >More geek nonsense - about what I expected. > > Call it "geek nonsense" if you want to. Warner is employed by the > company that builds the stuff which figures out what time it is > for NIST and although my professional affiliation isn't anywhere > near that level, I can claim to be the first person to truly split > the microsecond with a standard UNIX box. > > > Listen, it is really too bad that you didn't get that pony for > X-mas, and I can understand you why you are disappointed about it, > but when do you plan to stop being grumpy about it ? :-) > > If you intend to keep up this "sour grapes" attitude, despite all > the helpful answers you have gotten so far, you should consider > stopping before you have worn out your welcome. > > -- > Poul-Henning Kamp FreeBSD coreteam member > [EMAIL PROTECTED] "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! Go fuck yourself Poul. Yes, the "F-word". You have no ability to determine "my welcome". -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]> Karl Denninger writes: : Yes, you have HARDWARE timers that do that. : : So what? : : I'm talking about TIME SERVERS on UNIX machines. So am I. : You know, ntpd and friends? Yes, that. That's one of the things in our application. : Now explain to me how stability of your timing source ON THOSE MACHINES : is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH : between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. It is better because the variance in the measurements that we make is much smaller than 1uS would give. : I'm simply not interested in NON-GERMANE devices to the discussion; we were : talking about FreeBSD on REAL computers, not specialty hardware for process : control or nuclear physics experiments. Get a life Karl. I was telling you about my experiences and if you don't like it, take a chill pill or go play in traffic. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
latest version of threads library
I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? I am running: FreeBSD io.lyris.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Dec 27 15:20:33 PST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/KMM i386 Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 03:32:00PM -0700, Warner Losh wrote: >> In message <[EMAIL PROTECTED]> Karl Denninger writes: >> : Why spend twice what Mr. Schwartz seems to want to charge? >> >> Because we need a PPS that is < 10nS from the true start of second for >> our application? 1uS is really really bad for the timing geeks in the >> audience. >> >> Warner > >And on what hardware do you think you can obtain 10ns resolution RELIABLY >at the software level in the Unix environment and under FreeBSD? > >Answer: NONE! > >The actual usable resolution of a timing source is determined by the >maximum slop in ANY part of the complete system. > >I challenge you to get actual REPEATABLE 10ns results while a multi-tasking >anything is running on the recipient of that data. What rides on this challenge ? What is the prize ? I would use some cash, and this will be like picking cherries... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: >> In message <[EMAIL PROTECTED]>, Karl Denninger writes: >> >> >Why spend twice what Mr. Schwartz seems to want to charge? >> >> Well, suit your own political manifests as you will, but the Motorola >> unit is the best time receiver you can buy for humane amounts of money. >> >> You can see some of my measurements at http://phk.freebsd.dk > >Yeah, so what? > >Your system can't resolve events to that degree of accuracy, so the ability >of the receiver to deliver them is irrelavent. Karl, In fact I *do* have a computer that can resolve events to +/- 10nsec (http://gps.freebsd.dk) so I need it. In fact that machine is probably one of the best NTP servers in the entire world right now. >More geek nonsense - about what I expected. Call it "geek nonsense" if you want to. Warner is employed by the company that builds the stuff which figures out what time it is for NIST and although my professional affiliation isn't anywhere near that level, I can claim to be the first person to truly split the microsecond with a standard UNIX box. Listen, it is really too bad that you didn't get that pony for X-mas, and I can understand you why you are disappointed about it, but when do you plan to stop being grumpy about it ? :-) If you intend to keep up this "sour grapes" attitude, despite all the helpful answers you have gotten so far, you should consider stopping before you have worn out your welcome. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 03:42:24PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Karl Denninger writes: > : And on what hardware do you think you can obtain 10ns resolution RELIABLY > : at the software level in the Unix environment and under FreeBSD? > : > : Answer: NONE! > > WRONG. > > : The actual usable resolution of a timing source is determined by the > : maximum slop in ANY part of the complete system. > : > : I challenge you to get actual REPEATABLE 10ns results while a multi-tasking > : anything is running on the recipient of that data. > > We have hardware timers that let us get into the pico second range on > a regular basis. > > Warner Yes, you have HARDWARE timers that do that. So what? I'm talking about TIME SERVERS on UNIX machines. You know, ntpd and friends? Yes, that. Now explain to me how stability of your timing source ON THOSE MACHINES is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. I'm simply not interested in NON-GERMANE devices to the discussion; we were talking about FreeBSD on REAL computers, not specialty hardware for process control or nuclear physics experiments. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
tip features (cdelay and ldelay)?
Hi, I have a couple of really dumb devices that I use 'tip' to talk to. One is a Motorola 6811 microcontroller and the other is an old EEPROM burner. I find that 'tip' overflows these devices when I'm sending Motorola s-record and Intel Hex formatted files. It looks like tip's 'cdelay' and 'ldelay' features do just the trick. However, they are disabled, surrounded by '#ifdef notdef' sequences. Just to make sure, I re-enabled them locally, and re-implemented the apparently lost 'nap()' function to make sure that these features work for my application, and they do. My question is: does anyone remember why these were disabled in the first place? Is there an equivalent replacement feature that I can use instead to pace the outgoing characters so that I don't overrun dumb devices with no flow control? Thanks, -Brian -- Brian Dean [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]> Karl Denninger writes: : And on what hardware do you think you can obtain 10ns resolution RELIABLY : at the software level in the Unix environment and under FreeBSD? : : Answer: NONE! WRONG. : The actual usable resolution of a timing source is determined by the : maximum slop in ANY part of the complete system. : : I challenge you to get actual REPEATABLE 10ns results while a multi-tasking : anything is running on the recipient of that data. We have hardware timers that let us get into the pico second range on a regular basis. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Karl Denninger writes: > > > >Why spend twice what Mr. Schwartz seems to want to charge? > > > >For the Motorola name? Sorry, the Batwing Menace to employee's rights was > >long ago placed on my "do not buy, do not recommend, actively boycott" list. > > Well, suit your own political manifests as you will, but the Motorola > unit is the best time receiver you can buy for humane amounts of money. > > You can see some of my measurements at http://phk.freebsd.dk Yeah, so what? Your system can't resolve events to that degree of accuracy, so the ability of the receiver to deliver them is irrelavent. More geek nonsense - about what I expected. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 03:32:00PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Karl Denninger writes: > : Why spend twice what Mr. Schwartz seems to want to charge? > > Because we need a PPS that is < 10nS from the true start of second for > our application? 1uS is really really bad for the timing geeks in the > audience. > > Warner And on what hardware do you think you can obtain 10ns resolution RELIABLY at the software level in the Unix environment and under FreeBSD? Answer: NONE! The actual usable resolution of a timing source is determined by the maximum slop in ANY part of the complete system. I challenge you to get actual REPEATABLE 10ns results while a multi-tasking anything is running on the recipient of that data. - -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]> Karl Denninger writes: : Why spend twice what Mr. Schwartz seems to want to charge? Because we need a PPS that is < 10nS from the true start of second for our application? 1uS is really really bad for the timing geeks in the audience. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Karl Denninger writes: >Why spend twice what Mr. Schwartz seems to want to charge? > >For the Motorola name? Sorry, the Batwing Menace to employee's rights was >long ago placed on my "do not buy, do not recommend, actively boycott" list. Well, suit your own political manifests as you will, but the Motorola unit is the best time receiver you can buy for humane amounts of money. You can see some of my measurements at http://phk.freebsd.dk -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 02:33:35PM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Karl Denninger writes: > : That's EXPENSIVE. > > Worth every penny. We've seen sub-micro second syncronization with > our unit on good hardware, and 1-2us on the 486 based hardware. > > : Common handheld GPS units with NEMA outputs on them are well under $200 > : these days! > > NEMA gives you only millisecond accuracy, if you are lucky. > > Warner Why spend twice what Mr. Schwartz seems to want to charge? For the Motorola name? Sorry, the Batwing Menace to employee's rights was long ago placed on my "do not buy, do not recommend, actively boycott" list. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]> Karl Denninger writes: : That's EXPENSIVE. Worth every penny. We've seen sub-micro second syncronization with our unit on good hardware, and 1-2us on the 486 based hardware. : Common handheld GPS units with NEMA outputs on them are well under $200 : these days! NEMA gives you only millisecond accuracy, if you are lucky. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
: >Still no feature freeze for 4.0 BTW? : : Feature freeze is in effect I think, but minor upgrades and bugfixes are : not only allowed, they're mandatory :-) Jordan told me that the feature freeze was put off until Jan 15. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: : I will (as always) recommend the Motorola Oncore UT+. If you buy it We've also had excellent luck with the OEM version of the Oncore that we embed in our products. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
False alarm ? (was Re: Weird interaction between cvs and a recent kernel)
Bonsoir, Well, I don't remember indulging (Lagavulin, Glen Deveron, what else ...), but I'm stumped : I can't reproduce what I've seen : a full "cvs co" of the ports and src has been running ok till its normal end. more after some make world's TfH Thierry Herbelot wrote: > > Hello, > > I'm rebuilding my -Current box. > > it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT > snapshot. > > I have on another box the full repository of FreeBSD (source, ports, > docs, ...) on another box, running 3.3-Stable and exporting the > repository via NFS. > > I've tried to remake the world to the latest sources I had (got on 12/31 > around 4PM GMT). > > I can't get the "cvs co src" to finish properly : each time I launch > "cvs co src", the kernel crashes with page fault while in supervisor > mode : page not present (I don't have a serial console, so this is not > the full message). The instruction address for the faulting instruction > is always the same, in the "generic_bzero" (from a "nm" run on the > kernel). > > The running process is always "cvs". > > I have been able to check the sources out (one subdirectory after > another) and the machine has completed a full make world. I also run the > corresponding kernel. > > with the new sources, there is the same problem with cvs : I have not > been able to check out the ports tree in one step (same error, in the > same routine). > > The machine works fine : I have just completed a X11 3.3.5 build. > > As I have got plenty of RAM, I'm not quite sure a full crash dump would > be usable. > > Open to any suggestions > > TfH > > PS : dmesg for the box : > [SNIP] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: xntpd - VERY old folks, how about updating? :-)
> That sucks severely - NONE of the common units have the PPS output?! > > Barf. Oh well. Many of them do, but it's still not meant for precision timekeeping and the exact relationship between its PPS pulse edges and UTC's second boundaries may not be precisely specified. It's not a good idea to use a GPS unit not specifically made for timing as an NTP reference clock. Sorry to plug myself, but I offer a GPS timing unit that is made specifically for timing use. It's $375 (quantity one) and more info is available at http://www.gpsclock.com/ PPS output is specified as +/- 1 us of UTC second boundary. DS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: several procmail jobs hang ...
Well, found out, that I don't have any problems using the previous
version of procmail 3.13.1.
So it's solved for me now. The remaining question is, is this a
procmail 3.14 bug, or does the new procmail version introduce
some new features in area where in -current is something wrong.
Not easy to say for me ...
Remains to tell Andrey, that new procmail port is broken for -current.
Andreas ///
On Sun, Jan 02, 2000 at 08:00:03PM +0100, Andreas Klemm wrote:
> A few days ago I updated -current and build /usr/local completely new.
> One remaining problem is, that procmail jobs seems to hang.
> First it was a port problem, I installed some (for me) basic services
> in /home/local and procmail tried to call /usr/local/bin/formail.
> Now I recompiled procmail using normal /usr/local as PREFIX, but
> the jobs still hang. After some time they seem to timeout and
> mail seems to be delivered. Can't say exactly if I have some mail
> loss.
>
> Here, what a ps -axuww shows.
>
> andreas 1038 0.0 0.5 1024 704 ?? INs 7:28PM 0:00.03 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> andreas 1039 0.0 0.5 1024 704 ?? RN7:28PM 0:00.00 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> andreas 1041 0.0 0.5 1024 704 ?? SNs 7:28PM 0:00.59 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> andreas 1338 0.0 0.5 1024 704 ?? INs 7:45PM 0:00.02 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> andreas 1339 0.0 0.5 1024 704 ?? RN7:45PM 0:00.00 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> andreas 1612 0.0 0.5 1024 712 ?? SNs 7:53PM 0:00.04 procmail -f owner
> [EMAIL PROTECTED] -Y -a -d andreas
> root@titan{1006} $ ps -axuww | grep sendmail
> root 173 0.0 0.7 1372 1060 ?? Is7:16PM 0:00.15 sendmail: accepti
> ng connections on port 25 (sendmail)
> root 1035 0.0 0.7 1420 1124 ?? I 7:28PM 0:00.10 /usr/sbin/sendmai
> l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
> root 1040 0.0 0.7 1420 1120 ?? I 7:28PM 0:00.09 /usr/sbin/sendmai
> l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
> root 1337 0.0 0.7 1420 1124 ?? I 7:45PM 0:00.08 /usr/sbin/sendmai
> l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
> root 1611 0.0 0.7 1420 1128 ?? I 7:53PM 0:00.09 /usr/sbin/sendmai
> l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
> .com
>
> When recompiling procmail I noticed, that procmail port has been
> updated as well.
>
> Is this port related or might this be due to signal changes in current,
> which I read shortly in the lists ???
>
> --
> Andreas Klemm http://www.FreeBSD.ORG/~andreas
> http://www.freebsd.org/~fsmp/SMP/SMP.html
>powered by Symmetric MultiProcessor FreeBSD
> Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
http://www.freebsd.org/~fsmp/SMP/SMP.html
powered by Symmetric MultiProcessor FreeBSD
Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
several procmail jobs hang ...
A few days ago I updated -current and build /usr/local completely new.
One remaining problem is, that procmail jobs seems to hang.
First it was a port problem, I installed some (for me) basic services
in /home/local and procmail tried to call /usr/local/bin/formail.
Now I recompiled procmail using normal /usr/local as PREFIX, but
the jobs still hang. After some time they seem to timeout and
mail seems to be delivered. Can't say exactly if I have some mail
loss.
Here, what a ps -axuww shows.
andreas 1038 0.0 0.5 1024 704 ?? INs 7:28PM 0:00.03 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
andreas 1039 0.0 0.5 1024 704 ?? RN7:28PM 0:00.00 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
andreas 1041 0.0 0.5 1024 704 ?? SNs 7:28PM 0:00.59 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
andreas 1338 0.0 0.5 1024 704 ?? INs 7:45PM 0:00.02 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
andreas 1339 0.0 0.5 1024 704 ?? RN7:45PM 0:00.00 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
andreas 1612 0.0 0.5 1024 712 ?? SNs 7:53PM 0:00.04 procmail -f owner
[EMAIL PROTECTED] -Y -a -d andreas
root@titan{1006} $ ps -axuww | grep sendmail
root 173 0.0 0.7 1372 1060 ?? Is7:16PM 0:00.15 sendmail: accepti
ng connections on port 25 (sendmail)
root 1035 0.0 0.7 1420 1124 ?? I 7:28PM 0:00.10 /usr/sbin/sendmai
l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
root 1040 0.0 0.7 1420 1120 ?? I 7:28PM 0:00.09 /usr/sbin/sendmai
l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
root 1337 0.0 0.7 1420 1124 ?? I 7:45PM 0:00.08 /usr/sbin/sendmai
l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
root 1611 0.0 0.7 1420 1128 ?? I 7:53PM 0:00.09 /usr/sbin/sendmai
l -oee -odi -oi -pUUCP [EMAIL PROTECTED] [EMAIL PROTECTED]
.com
When recompiling procmail I noticed, that procmail port has been
updated as well.
Is this port related or might this be due to signal changes in current,
which I read shortly in the lists ???
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
http://www.freebsd.org/~fsmp/SMP/SMP.html
powered by Symmetric MultiProcessor FreeBSD
Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
That sucks severely - NONE of the common units have the PPS output?! Barf. Oh well. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 05:42:24PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Karl Denninger writes: > >On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: > >> > >> >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver > >> >that (1) has an external-able antenna that will work with somewhere between > >> >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such > >> >so it can be used for this? > >> > >> I will (as always) recommend the Motorola Oncore UT+. If you buy it > >> from syngergy-gps it comes mounted in their nice box and the cable > >> has the PPS on DCD and is ready to plug into a serial port. I paid > >> $605.73 for the one I'm delivering to the Danish Internet eXchange > >> point, that included antenna and 15m of cable. > > > >That's EXPENSIVE. > > > >Common handheld GPS units with NEMA outputs on them are well under $200 > >these days! > > Common handheld GPS units are pointless as NTP refclocks because they > lack (a decent) PPS output. > > -- > Poul-Henning Kamp FreeBSD coreteam member > [EMAIL PROTECTED] "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: >> >> >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver >> >that (1) has an external-able antenna that will work with somewhere between >> >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such >> >so it can be used for this? >> >> I will (as always) recommend the Motorola Oncore UT+. If you buy it >> from syngergy-gps it comes mounted in their nice box and the cable >> has the PPS on DCD and is ready to plug into a serial port. I paid >> $605.73 for the one I'm delivering to the Danish Internet eXchange >> point, that included antenna and 15m of cable. > >That's EXPENSIVE. > >Common handheld GPS units with NEMA outputs on them are well under $200 >these days! Common handheld GPS units are pointless as NTP refclocks because they lack (a decent) PPS output. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: > > >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver > >that (1) has an external-able antenna that will work with somewhere between > >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such > >so it can be used for this? > > I will (as always) recommend the Motorola Oncore UT+. If you buy it > from syngergy-gps it comes mounted in their nice box and the cable > has the PPS on DCD and is ready to plug into a serial port. I paid > $605.73 for the one I'm delivering to the Danish Internet eXchange > point, that included antenna and 15m of cable. That's EXPENSIVE. Common handheld GPS units with NEMA outputs on them are well under $200 these days! -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
In message <[EMAIL PROTECTED]>, Ollivier Robert writes: >According to Poul-Henning Kamp: >> I'm sure Ollivier will upgrade us every so often now :-) > >'98i' looks like a nice release candidate and will probably become 4.1.0 >soon. I'll update us to that level of course. > >Still no feature freeze for 4.0 BTW? Feature freeze is in effect I think, but minor upgrades and bugfixes are not only allowed, they're mandatory :-) -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[solicite review and confirmation of tcp for IPv6 patches]
Hello, I prepared tcp for IPv6 patches to the current. I would like it to be reviewed and confirmed in many environment before committing it, because I think updating tcp code is very critical to system stability. (Apps for tcp/IPv6 is not yet ready, but I think confirming that it doesn't harmful to IPv4 environment is important at first.) The patches are placed below. http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.2103 http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228 Anyone interested, please give me comments for them or please try to apply those patches to some of your freebsd-current machines. Either confimation on INET6 defined kernel and INET6 non defined kernel will be helpful. Thanks in advance, Yoshinobu Inoue KAME project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
According to Poul-Henning Kamp: > I'm sure Ollivier will upgrade us every so often now :-) '98i' looks like a nice release candidate and will probably become 4.1.0 soon. I'll update us to that level of course. Still no feature freeze for 4.0 BTW? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
>BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver >that (1) has an external-able antenna that will work with somewhere between >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such >so it can be used for this? I will (as always) recommend the Motorola Oncore UT+. If you buy it from syngergy-gps it comes mounted in their nice box and the cable has the PPS on DCD and is ready to plug into a serial port. I paid $605.73 for the one I'm delivering to the Danish Internet eXchange point, that included antenna and 15m of cable. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 12:22:38PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Karl Denninger writes:
>
> >> >Well... that won't help the 20 or so boxes here doing this all the
> >> >time:
> >> >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s
> >> >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s
> >>
> >>(-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340
> >>
> >> Your clock is too sick, (or our calibration of it is hosed), no
> >> version of {X}NTP will touch a clock which is outside +/- 500ppm.
> >>
> >> Could you try to measure the 14.31818... MHz base frequency and
> >> the 32768 kHz wristwatch xtal as well (I know you're RadioActive,
> >> so I pressume you have a counter ?)
> >>
> >> If they're both OK, then we have a code problem...
> >
> >You have a code problem ;-)
>
> If you have access to a frequency counter, could you try to make the
> same measurements please ?
I don't have one handy, BUT I saw this SAME problem across oh, 20 machines.
Every one. Every time.
And oh, by the way, when one of them (mine) was upgraded to the newest ntpd,
it *WENT AWAY*. Thus, I think its quite reasonable to say its not the clock
and must be the code (since the hardware could not have magically changed
:-)
> Do you have any refclocks we can use to measure against ?
Had one at MCS (Spectracom WWV receiver), but its there and I'm here. It
appears from their strata change (from 1 to 2; I chime off them) that they
turned it off. I should have taken it with me when I left :-)
BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver
that (1) has an external-able antenna that will work with somewhere between
50 and 100 feet of lead, and (2) has the appropriate pps outputs and such
so it can be used for this?
--
--
Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org
Isn't it time we started putting KIDS first? See the above URL for
a plan to do exactly that!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, Jan 02, 2000 at 12:20:35PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Karl Denninger writes: > > >> >> Anyway, ntpd4 is in CURRENT... > >> > > >> >Now it is. > >> > > >> >And it works correctly too. > >> > >> In general yes, but not if you use the hardpps() with a refclock, > >> it works better after I fixed a couple of almost-mutually-canceling > >> sign-bugs, but the parameters of the hardpps() PLL relative to the > >> FLL are wrong. > > > >You're still a bunch of revs back - the current is either "h" or "i", and it > >has a bunch of fixes (including one here, I think) > > No, the NTP distribution doesn't contain the kernel code, it only interfaces > to it. Well yes you're saying that the bug was *in* the kernel and not ntpd then? Ok.. > I'm sure Ollivier will upgrade us every so often now :-) No problem. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weird interaction between cvs and a recent kernel
Hello, I'm rebuilding my -Current box. it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT snapshot. I have on another box the full repository of FreeBSD (source, ports, docs, ...) on another box, running 3.3-Stable and exporting the repository via NFS. I've tried to remake the world to the latest sources I had (got on 12/31 around 4PM GMT). I can't get the "cvs co src" to finish properly : each time I launch "cvs co src", the kernel crashes with page fault while in supervisor mode : page not present (I don't have a serial console, so this is not the full message). The instruction address for the faulting instruction is always the same, in the "generic_bzero" (from a "nm" run on the kernel). The running process is always "cvs". I have been able to check the sources out (one subdirectory after another) and the machine has completed a full make world. I also run the corresponding kernel. with the new sources, there is the same problem with cvs : I have not been able to check out the ports tree in one step (same error, in the same routine). The machine works fine : I have just completed a X11 3.3.5 build. As I have got plenty of RAM, I'm not quite sure a full crash dump would be usable. Open to any suggestions TfH PS : dmesg for the box : Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 2 10:07:04 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/multiUP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 402653184 (393216K bytes) config> q avail memory = 387637248 (378552K bytes) Preloaded elf kernel "kernel" at 0xc02be000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02be09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 5 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 12 chip1: at device 7.3 on pci0 ed0: irq 10 at device 13.0 on pci0 ed0: address 00:4f:49:08:17:72, type NE2000 (16 bit) ata-pci1: irq 11 at device 19.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xd800 irq 11 on ata-pci1 ata-pci2: irq 11 at device 19.1 on pci0 ata-pci2: Busmastering DMA supported devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed1: not probed (disabled) unknown: can't assign resources unknown0: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b, 0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0xf0-0xff irq 13 on isa0 unknown4: at iomem 0-0x9,0xfffe-0x, 0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x17ff on isa0 unknown5: at iomem 0xf-0xf3fff,0xf4000-0xf7fff, 0xf8000-0xf,0xd1800-0xd3fff on isa0 unknown6: at port 0x294-0x297,0x4d0-0x4d1,0xcf8-0xcff, 0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad2: ATA-4 disk at ata1 as master ad2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 32 depth queue, UDMA33 ad4: ATA-5 disk at ata2 as master ad4: 17418MB (35673120 sectors), 35390 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 Mounting root from ufs:/dev/ad4s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
