Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
If memory serves me right, "Steve O'Hara-Smith" wrote: On Wed, 04 Apr 2001 23:49:40 -0500 "Brian D. Woodruff" [EMAIL PROTECTED] wrote: BW I would rather be consistent across my servers than have some be one BW release past the others. Allow me to investigate this a little further. Do you want to have all your servers running the same code or code with the same name ? The former can only be achieved by installing them from the same build (except for RELEASEs which can be exactly recreated at any time). "man cvsup" and look at the description of the "date" tag in the supfile. Bruce. PGP signature
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
On Wed, 4 Apr 2001, Brian D. Woodruff wrote: At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? can anyone tell me how to get the STABLE version I want? I would rather be consistent across my servers than have some be one release past the others. If you're using CVS to get RELENG_4 at different points in time, even if they're all 4.2-STABLE, your servers will NOT be consistent anyway. The -STABLE branch is a stream, in constant development. If you update your sources via CVS to build one server, then the next day update sources again to build another server, the two servers will be different. This is the essence of -STABLE, even though it seems to contradict the meaning of the word "stable". :-) If you require absolute consistency across servers, you need to either update all servers from the very same source, or specify an exact CVS tag to get the same sources for all servers. And if it doesn't bother you that your servers are on different points of 4.2-STABLE, then 4.3-RC is just another point a little farther down the development stream. I'd actually consider the -RC to be safer bet than the average -STABLE. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
On 05-Apr-2001 Ken Bolingbroke wrote: If you require absolute consistency across servers, you need to either update all servers from the very same source, or specify an exact CVS tag to get the same sources for all servers. You can check out a branch at a specific time using -D which you might find useful.. Also, you could check it out and build it on one machine and then do an installworld via NFS (assuming all the machines are on a fast link and running the same architecture) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
There may be some value in the multiple servers case, of running one as a cvs server, and updating all the others off that one. Then all your servers are reflections of the one that is cvsupping the - remote-cvs-server just a thought. Bob On Wed, 4 Apr 2001, Brian D. Woodruff wrote: At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? can anyone tell me how to get the STABLE version I want? I would rather be consistent across my servers than have some be one release past the others. If you're using CVS to get RELENG_4 at different points in time, even if they're all 4.2-STABLE, your servers will NOT be consistent anyway. The -STABLE branch is a stream, in constant development. If you update your sources via CVS to build one server, then the next day update sources again to build another server, the two servers will be different. This is the essence of -STABLE, even though it seems to contradict the meaning of the word "stable". :-) If you require absolute consistency across servers, you need to either update all servers from the very same source, or specify an exact CVS tag to get the same sources for all servers. And if it doesn't bother you that your servers are on different points of 4.2-STABLE, then 4.3-RC is just another point a little farther down the development stream. I'd actually consider the -RC to be safer bet than the average -STABLE. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
I agree with you completely, Bob. The idea of keeping one "master server" to push out updates to many is extremely useful when you are maintaining a large number of similar systems. It is much less work-intensive to maintain several hundred systems if they are running on exactly the same configuration, kernel, etc. The only caveat is that you must be extremely careful with any changes you make to the master, and make certain that any changes that you make to your master system are pushed out to all of the "leaf" systems. If not, then you get some updates here and there on various systems and you may as well be running different software on all of the machines. CVS is definately the way to go, as it helps you to be disciplined about distribution. Just make sure that the master server that is cvsuping is thoroughly tested before you push things out, or you're heading for trouble very quickly :) Robert wrote: There may be some value in the multiple servers case, of running one as a cvs server, and updating all the others off that one. Then all your servers are reflections of the one that is cvsupping the - remote-cvs-server just a thought. Bob On Wed, 4 Apr 2001, Brian D. Woodruff wrote: At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? can anyone tell me how to get the STABLE version I want? I would rather be consistent across my servers than have some be one release past the others. If you're using CVS to get RELENG_4 at different points in time, even if they're all 4.2-STABLE, your servers will NOT be consistent anyway. The -STABLE branch is a stream, in constant development. If you update your sources via CVS to build one server, then the next day update sources again to build another server, the two servers will be different. This is the essence of -STABLE, even though it seems to contradict the meaning of the word "stable". :-) If you require absolute consistency across servers, you need to either update all servers from the very same source, or specify an exact CVS tag to get the same sources for all servers. And if it doesn't bother you that your servers are on different points of 4.2-STABLE, then 4.3-RC is just another point a little farther down the development stream. I'd actually consider the -RC to be safer bet than the average -STABLE. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Spontaneous reboot, no panic. Recovering from a crash.
* fury [EMAIL PROTECTED] [010405 06:28]: No it was NOT a hardware issue unlike many ppl stated, fact is, I have never figured it out. Then how do you know it wasn't hardware? I'm not saying you're wrong, fury, and I can see you're more than a bit pissed off, but in the vast majority of cases it *does* turn out to be hardware. I had similar problems to The Anarcat about a month ago, (spontaneous reboots under fairly high load - make -j4 buildworld etc) and couldn't get a fix here except for 'bad RAM/CPU/mobo' No kernel errors, CVSupped at least once a week, no difference. Decided to put up with it until I could upgrade the box, fitted a new CPU and 4X the RAM. It was only then that I noticed that my second SIMM was only half in the slot. Which meant that the minute BSD tried to use the last 8Mb of that SIMM, I'd get a reboot. I really don't know how to put this, but since we're in a code freeze and I'm running stable, if a few people witness this behavior, well... And that was my question too. All I can say to help is that 4-3-RC0 (built on April Fools Day) is running a treat now. FreeBSD shall.anarcat.yi.org 4.3-BETA FreeBSD 4.3-BETA #2: Wed Mar 14 18:50:48 EST 2001 root@:/usr/obj/usr/src/sys/SHALL i386 A few minutes ago, I was doing a few things at the same time on my machine. I was doing a make install clean in sysutils/[gcombust|gtoaster|xcdroast], copying /mnt/cdr to ~/cdr, and opening a ssh session to my shell account. Before I could get to a password prompt on the shell account, I didn't even had time to realize what's going on that my computer beeped and was back to the BIOS POST startup procedure. nods Shikima usually did it when I was on the wrong end of an SSH session. I had so much scrapped files that I interrupted the process at some point to restart it with "fsck -y". Things like UNREF DIR, LINK COUNT DIR, UNREF FILE, and all sort of evil warnings of the kind. That was a big worry too - didn't lose any data here though. Do you run softupdates? Might be worth enabling them until you get this fixed; I didn't really notice the overhead on a P133/32Mb. The "crash" has somehow been recorded in wtmp. last says: anarcat ttyp1:0 Mer 4 avr 23:45 - 23:47 (00:01) reboot ~ Mer 4 avr 23:43 anarcat ttyp4:1 Mer 4 avr 23:26 - crash (00:17) apocalypse. That's interesting. I never managed to find any log evidence that a crash had happened. Don't do as daddy does, boys and girls. Do backups. Often. You never know when the shit'll the fan. :) I(n my experience, it's the day before you make a monthly backup :^] -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Disklabel 101?
Is there a decent walkthrough anywhere on the Net for using disklabel, fdisk , etc - along with an explanation of what a,c etc all mean? man disklabel etc all assume you know what those letters mean. I know c is the whole partition, but that's it. I need to know because: PHYSICAL-EXTENDED---PHYSICAL ad0s1ad0s5ad0s6 ad0s3 -winXX---msdos-Slackware---BSD | 2Gb| 1.5Gb | 2Gb | / | swap | /usr | /var | ^ | I have an old Slackware partition that has FUBARed itself so throuoghly that it can't even be mounted. (Actually there were about 3 partitions in there, but they're lost now) It's in the second logical partition in an extended DOS partition on my second physical partition (dev/ad0s6 in FreeBSD) There's a Gb of data in ad0s5 (which is fine). BSD dumps ad0s6 altogether when it boots; and fdisk from a boot CD says something along the lines of: "Second slice extended past end of disk" or similar (box is offline today, so I can't check right now) This concerns me; if I try to fdisk/newfs ad0s2 (assuming I could see it), I risk losing ad0s3, which is the only bit of the disk I really want to keep. I assume/hope that if I blow away the extended partition entirely, I can just recreate it. But I don't really know what it's called? Is it ad0s2? And won't I need to let BSD know where / has moved to? What I'd really like is some advice from anyone who knows this stuff. But I'm surprised the Handbook doesn't go into a lot of detail on this, since dual-boot systems are fairly common amongst cheapskates like me. If I can free up that 2Gb, maybe I'll have space for the docproj port... :) -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
Brian D. Woodruff wrote: At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? excellent answer to part 2 can anyone tell me how to get the STABLE version I want? Did you read the first sentence of that FAQ entry? "Short answer: it's just a name." If you cvsup the RELENG_4 branch, you're getting FreeBSD-stable, whether it be called -STABLE, -RC, -BETA, -FISHCAKE, -UNSTABLE-AS-HELL, or even -CURRENT if someone felt like playing an April Fool's day joke in /sys/conf/newvers.sh. :-) I would rather be consistent across my servers than have some be one release past the others. Well if it said 4.2-STABLE and you builtworld on one and not the others you still wouldn't be consistent, they'd still be different codebases but with the same name. If it _really_ bothers you just change /sys/conf/newvers.sh appropriately so your kernel reports itself as 4.2-STABLE, if all you want is the same name but different codebases. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Further question Re: cvsupped to RELENG_4 but got 4.3-RC
Date: Wed, 04 Apr 2001 23:49:40 -0500 From: "Brian D. Woodruff" [EMAIL PROTECTED] Subject: Further question Re: cvsupped to RELENG_4 but got 4.3-RC At 10:35 PM 4/4/01 -0400, you wrote: On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote: Here are my questions: 1.) is there a way to specify 4.2-STABLE, which is what I have been using? excellent answer to part 2 can anyone tell me how to get the STABLE version I want? If you want to have identical code on all of your systems, you need to specify your update by date rather than "the latest -STABLE" (which is what the tag you are using does). Unfortunately, I don't know the details of how to do that, so I can't help with that part. To restate that, the cvsup tag you are using always fetches the latest 4.x code, whatever that may be. Unless you cvsup all of your systems at the same time, they will likely end up with different code, because -STABLE is continuously updated. The 4.3-RC you fetched is, by the way, exactly the same thing as the latest 4.2-STABLE. There is no difference. It is NOT a snapshot of -CURRENT. Good luck. - Bob I would rather be consistent across my servers than have some be one release past the others. Valid thinking or not, I would like to know how to do this with cvsup, if possible. Thanks! BDW 2.) is this a mistake? If so, when will it be corrected? http://www.FreeBSD.org/FAQ/book.html#RELEASE-CANDIDATE -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org -- * Bob JohnsonSenior Systems Programmer [EMAIL PROTECTED]College of Engineering 523 Weil Hall 352-392-9217 OfficeUniversity of Florida 352-392-7063 Fax Gainesville, FL 32611 * "Security is not a product, it's a mentality." . . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
`id` is identical at both aterm, eterm, rxvt, and console: uid=1001(lipshitz) gid=1001(lipshitz) groups=1001(lipshitz), 0(wheel) --- Alfred Perlstein [EMAIL PROTECTED] wrote: * Larry Librettez [EMAIL PROTECTED] [010405 09:42] wrote: With 4.3-RC2, I cannot su to root in X using either aterm, eterm, or rxvt terminals. However, in xterm or gnome-terminal or at a plain console, I am able to do so. (This was not a problem with 4.2-STABLE where I could su to root in any type of terminal in X.) What does "id" say in aterm? what about on console? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
re: netstat
Hello, Fixed my problem. I was indeed not using a kernel that was built with the updated source. I compiled my new kernel with 'make -kernel=sampson' and installed with 'make install -kernel=sampson' but did not set up boot.conf to boot that kernel =P. Thanks to all that replied. Couple of questions: 1) Is there any good reason why you would want to use the '-kernel=foo' other than customization? 2) I've noticed in the handbook that you can 'make all install' certain portions of the source tree and update your system. This seems appealing since you don't have to build anything and can update only certain parts (ntpd for instance). The question is should you go to single user mode (because of chflags being set or what not)? When is it ok to not go to single user mode and how can you tell? Galen Sampson On Tuesday 03 April 2001 02:13, you wrote: Hi all, I have been experiencing some strange behavior with netstat. It only displays UDP sockets for the inet family. TCP sockets do not show up. I know it is listening on TCP sockets because I can ssh/telnet/ftp/etc to the machine. Netstat has been exhibiting this behavior from a make world 2 weeks ago. After updating my source tree today from cvsup10.freebsd.org and rebuilding the world I am getting the same symptoms. I'd love to put up some debug info for someone to figure this out, but I have know idea what to put. Is this problem just me? pointers/tips welcome Galen Sampson Hi Galen, Must be only you, I certainly don't have that problem. 4.3-RC2 from the CD. Sources have been upgraded, but haven't built world yet. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
I am not having su problems, but perhaps our problems are related somehow, since the "login" process is involved... I am running Exceed under Win98 to access my FreeBSD with xterm, to my now "4.3-RC2" box. It now hangs waiting to login (using the rlogin method). From my other FreeBSD machine (4.2-RELEASE), if I try to rlogin to my 4.3-RC2 box, it also hangs for a long time after I enter the password (approx 2-3 minutes). Then it finally plunks me into the shell as expected. From an existing session, the ps display shows that the login process is hung up waiting for something. Otherwise, its a mystery, and I cvsup-ed again today, hoping the problem would be fixed, but not so yet... here's hoping for tomorrow.. Warren. Alfred Perlstein wrote: * Larry Librettez [EMAIL PROTECTED] [010405 09:42] wrote: With 4.3-RC2, I cannot su to root in X using either aterm, eterm, or rxvt terminals. However, in xterm or gnome-terminal or at a plain console, I am able to do so. (This was not a problem with 4.2-STABLE where I could su to root in any type of terminal in X.) What does "id" say in aterm? what about on console? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Warren W. Gay VE3WWG http://members.home.net/ve3wwg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: mbuf leak? fxp?
Bosko Milekic writes: NMBUFS accordingly. Chances are, if you are explicitly declaring `NMBCLUSTERS NO' in your kernel configuration file, that you are actually lowering the number of clusters/mbufs that would otherwise be allowed with your given `maxusers' value (unless you have an unreasonably low maxusers). Mmm.. I don't understand that.. can you explain? -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cvsup dumps core
In article [EMAIL PROTECTED], Michael R. Wayne [EMAIL PROTECTED] wrote: With the recent ntpd exploit, I wanted to update only the files in /usr/src/contrib/ntp/ntpd. Based on the man page, I should be able to use -i to do this. But cvsup seems pretty unhappy: 1162 /usr/local/bin/cvsup @M3stackdump -g -L 2 -i ntpd /usr/local/etc/stable-supfile I don't know why you got a core dump. It doesn't do that here when I try it. Unrelated to the core dump, you didn't use the -i option quite right. As the man page says: "The pattern is a standard file name pattern. It is interpreted relative to the collection's prefix directory." So you should have used "-i src/contrib/ntp/ntpd". John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
SOLVED: Neither aterm, eterm, nor rxvt can su to root in 4.3-RC2
Problem solved. Turns out my use of "nonstandard"
characters in my root password (like ^*(@$#) were the
cause of the problem. Specifically, use of the '('
character somehow was causing authentication problems
with rxvt in X, thus disallowing su to root and the
error "BAD SU to root on ttyp*". After changing my
root password to no longer use the ( character, I now
can su to root in rxvt, eterm, and aterm in 4.3RC.
And thus the wild goose chase finally comes to an end.
Again, strange that this was not causing difficulty
with 4.2-STABLE, I only noticed it in 4.3-BETA and now
in 4.3-RC1 and 4.3-RC2.
Thank you all for your helpful suggestions, it helps
to eliminate potential problems one by one.
Larry
--- "Warren W. Gay VE3WWG" [EMAIL PROTECTED] wrote:
I am not having su problems, but perhaps our
problems are related
somehow, since the "login" process is involved...
I am running Exceed under Win98 to access my FreeBSD
with xterm,
to my now "4.3-RC2" box.
It now hangs waiting to login (using the rlogin
method).
From my other FreeBSD machine (4.2-RELEASE),
if I try to rlogin to my 4.3-RC2 box,
it also hangs for a long time after I enter the
password (approx
2-3 minutes). Then it finally plunks me into the
shell as expected.
From an existing session, the ps display shows that
the login process
is hung up waiting for something.
Otherwise, its a mystery, and I cvsup-ed again
today, hoping the problem
would be fixed, but not so yet... here's hoping for
tomorrow..
Warren.
Alfred Perlstein wrote:
* Larry Librettez [EMAIL PROTECTED] [010405
09:42] wrote:
With 4.3-RC2, I cannot su to root in X using
either
aterm, eterm, or rxvt terminals. However, in
xterm or
gnome-terminal or at a plain console, I am able
to do
so. (This was not a problem with 4.2-STABLE
where I
could su to root in any type of terminal in X.)
What does "id" say in aterm? what about on
console?
--
-Alfred Perlstein -
[[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Represent yourself, show up at BABUG
http://www.babug.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of
the message
--
Warren W. Gay VE3WWG
http://members.home.net/ve3wwg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of
the message
__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
RE: SOLVED: Neither aterm, eterm, nor rxvt can su to root in 4.3
On 06-Apr-2001 Larry Librettez wrote:
Problem solved. Turns out my use of "nonstandard"
characters in my root password (like ^*(@$#) were the
cause of the problem. Specifically, use of the '('
character somehow was causing authentication problems
with rxvt in X, thus disallowing su to root and the
error "BAD SU to root on ttyp*". After changing my
root password to no longer use the ( character, I now
can su to root in rxvt, eterm, and aterm in 4.3RC.
And thus the wild goose chase finally comes to an end.
Again, strange that this was not causing difficulty
with 4.2-STABLE, I only noticed it in 4.3-BETA and now
in 4.3-RC1 and 4.3-RC2.
Thank you all for your helpful suggestions, it helps
to eliminate potential problems one by one.
You know I have a weird problem with aterm (which uses the rxvt core AFAIK)..
When I run tclsh8.2 (or maybe 8.3?) on my 4-STABLE, XFree86 4 system either ( or )
(I can't remember which) generates a backspace (!)
Related?
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
my i810 card doesn't work
i use 4.2 release,my display card is i810,4.2 release does not contain XFree86 4.0, so i download source for XFree86 4.02,after compile and install,i use XF86Setup,but failed.it told me can not start X.what's the matter? i choose some X Server(VGA SVGA...) when i install my system,shall i remove them before i install XFree86 4.02 ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Silo overflows
With FreeBSD 4.3RC1 I am also seeing quite a few silo overflow messages sio0: 3 more silo overflows (total 61) I've been seeing these as well, and I'm using 4.3-RC. On a 550 MHz Athlon, I might add, at 38400 bps. I applied the patch mentioned yesterday, it seems to have helped, however I still see them occasionally. -- /~~~___~\ | [EMAIL PROTECTED] //Z@|___ | | http://home.kscable.com/natedac |'(__ [_ | \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
