Re: Anybody actually using gigabit ethernet?
On Wed, 12 May 1999, Peter Wemm wrote: > > Isn't that adequately covered by the PAWS extension from RFC 1323? > > Well, maybe it would, but > > [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > It's off by default. :-( IMO that's a good thing, because for some reason, the RFC 1323 extensions break a lot of older terminal servers. Ben @narcissus.net -- finally To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
On Tue, 11 May 1999, Dennis Glatting wrote: > In reading your message I felt compelled to ask you a question. Are > you using gb end-to-end? That probably isn't a good idea because in > TCP the sequence numbers can wrap within timeout periods and the data > stream become undetectably (from a TCP perspective) corrupt. Isn't that adequately covered by the PAWS extension from RFC 1323? Ben @narcissus.net -- finally To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Fri, 30 Apr 1999, Mike Smith wrote: > > To sum it all up is there any difference between the branches? > > Yes. We hope that people like you will help us by participating in the > testing of potential releases _before_ they go out as releases, not > _afterwards_. > > Sitting around doing nothing and then complaining after the fact > doesn't help anyone, least of all yourself. I seem to recall that there was a lot of noise about the instability of 3 before it was released, but that it went out the door because it had been taking too long. Wasn't it Greg Lehey who said that the "beta period" seemed more like "integration testing"? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Any action on PR 10570 ? getting closer to 65K :-(
On Fri, 30 Apr 1999, Poul-Henning Kamp wrote: > In message , John Polstra writes: > >Rodney W. Grimes wrote: > > > >You're being totally unrealistic. You can't create >2^32 of > >_anything_ on an i386 without running out of memory. > > Well, John, you can, the newer ones will address 2^36 bytes of memory > and even a i386 can address 2^32 bytes or 2^35 bits... Since when does FreeBSD only run on i386? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: swap-related problems
On Thu, 15 Apr 1999, Don Lewis wrote: > SunOS 4 doesn't do memory overcommit. I get the impression from Vahalia's _UNIX Internals_ that this is true of SunOS 5 as well. > This could be shaved down a bit if SunOS didn't require > (swap > total VM) instead of (swap + RAM > total VM). Again, from my readings it seems that Solaris has the latter policy. Does anyone know if this is true? This would seem to put paid to the idea that overcommit is the only way to go. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
kernel size over the last week
I just built a kernel, from sources cvsupped last night. It's over 2 megs in size, compared to 1.3 megs for a kernel built from the same config file four days ago. Is this due to the change in the debugging symbol policy? file(1) reports both kernels as 'ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped'. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: make world breakage
On Thu, 8 Apr 1999, Maxim Sobolev wrote: > Please don't disregard to read rpevious messages from this list! Sorry, I just started running current again the other day, I didn't re-subscribe until last night. > As it was pointed earlier make world now fails if -jN option used. >Try to build without -j. OK, thank you. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
make world breakage
Trying to make world today and last night, with fairly up-to-the-minute source, I keep bombing out with: `/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/i386. md' is up to date. `genattr.c' is up to date. `gencodes.c' is up to date. `genconfig.c' is up to date. `genemit.c' is up to date. `genextract.c' is up to date. `genflags.c' is up to date. `genopinit.c' is up to date. `genoutput.c' is up to date. `genpeep.c' is up to date. `genrecog.c' is up to date. `gencheck.c' is up to date. `gengenrtl.c' is up to date. `gengenrtl.c' is up to date. `gengenrtl.c' is up to date. `genattrtab.c' is up to date. `gencheck.c' is up to date. `c-parse.in' is up to date. `gencheck.c' is up to date. `c-parse.in' is up to date. ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 Does anyone know why this might be the case? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
