Re: C++ writing/compiling with 3.4 stable

2000-03-23 Thread Warner Losh
In message <[EMAIL PROTECTED]> David Kanter writes: : How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program : I just wrote needed the header files with the .h extension, and didn't like : using namespace std; : : And which version of gcc should I use? There is a 2.95 (egcs)

Re: What does "Voxware still supported in 4.0" mean exactly?

2000-03-23 Thread Warner Losh
I know that Walnut creek was most generous in their support of me in my cardbus efforts. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: C++ writing/compiling with 3.4 stable

2000-03-23 Thread Brooks Davis
On Thu, Mar 23, 2000 at 06:11:53PM -0600, David Kanter wrote: > How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program > I just wrote needed the header files with the .h extension, and didn't like > using namespace std; > > And which version of gcc should I use? There is a 2.

C++ writing/compiling with 3.4 stable

2000-03-23 Thread David Kanter
How ANSI/ISO-compliant is 3.4 stable? I ask because compiling a C++ program I just wrote needed the header files with the .h extension, and didn't like using namespace std; And which version of gcc should I use? There is a 2.95 (egcs) and 2.8.1 (gcc) but the glibstdc++ seems to want 2.8.1 -- Dav

Re: repeatable lockup (pipe related?)

2000-03-23 Thread Matthew Dillon
:: .SH foo, bar, baz :: ::and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, ::when I do :: :: nroff -ms foo.ms 2>&1 | less :: ::and quit 'less' straight away, the whole system seems to lockup. ^T ::worked (sometimes), and showed troff using lots of system time

Re: "dangerously dedicated"

2000-03-23 Thread Daniel C. Sobral
"Brandon D. Valentine" wrote: > > On i386 machines this is usually something lame like: > NO ROM BASIC > SYSTEM HALTED > despite the fact that no machine has included a ROM BASIC since the last > of the IBM PS/2 386s came out. However most of the BIOSes until *very* > recently still contained co

Re: Compiler problems with -O2 (was Re: CVS Trouble, even under4.0-RELEASE (alpha) HELP!)

2000-03-23 Thread Daniel C. Sobral
Charles Cox wrote: > > I would like to add that some of us who do a lot of numerically intensive > programming, and that need to squeeze every last available cycle out of > our CPU's would really appreciate having -O2 available for userland > programs. To me, getting rid of the -O2+ switch would

Re: What else to remove after 4.0 upgrade

2000-03-23 Thread Kris Kennaway
On Thu, 23 Mar 2000, robert bowen wrote: > Are there any binary files that have changed location or > gone away since 3.4-R? I saw the post on "cruft" but I > am worried that after a binary 4.0R upgrade there will > be some "leftovers" in /bin or /usr/bin that are not > overwritten by the new rel

Problem with NIC card GFC2204

2000-03-23 Thread Stephen Montgomery-Smith
I just got a GFC2204 card and I'm trying to get it to work with FreeBSD 3.3 stable. So I added the ax0 device into the kernel config, compiled the kernel, and rebooted. Right at the beginning of the kernel's boot up, I got a panic with the message: ifmedia_set: no match for 0x0/0x This

Re: src/UPDATING for RELENG_3 to RELENG_4 upgrade works.

2000-03-23 Thread Andrew Reilly
On Thu, Mar 23, 2000 at 10:49:56AM -0600, WMC, O'Gorman, James wrote: > The one and only problem that I have had that I have not fixed yet is > with xdm. I had started it from rc.local before, but now when rc.local > starts is, the keyboard will not interact with it. If I comment out that > line,

System lockup, 3.4-STABLE, two machines

2000-03-23 Thread Phil Homewood
The last two days have seen two lockups on one of our firewall machines. Box is pingable, accepts TCP connections but does nothing more. syslog shows it logging "MARK" every five minutes even when unresponsive. First thought: DoS attack. After cvsupping and recompiling kernel and world yesterday

Re: repeatable lockup (pipe related?)

2000-03-23 Thread Matthew Dillon
: .SH foo, bar, baz : :and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then, :when I do : : nroff -ms foo.ms 2>&1 | less : :and quit 'less' straight away, the whole system seems to lockup. ^T :worked (sometimes), and showed troff using lots of system time (no use

Re: Samba perf in the toilet with 4.0

2000-03-23 Thread Jim King
fwiw, I'm getting 3-4 MB/sec on an Alpha running 4.0 from last week and Samba 2.0.6. - Original Message - From: "Jaye Mathisen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 23, 2000 4:12 PM Subject: Samba perf in the toilet with 4.0 > > > I have reviewed the mail lo

Re: What does "Voxware still supported in 4.0" mean exactly?

2000-03-23 Thread Brandon D. Valentine
On Thu, 23 Mar 2000, Mike Smith wrote: >What makes you think that we haven't? The problem is simply that it's >very hard to _buy_ a lot of these cards, and if someone already has one, >asking them to send it to Cameron is a lot more effective than wasting a >day of my or Bill Swingle's time tryi

Re: Off-topic News: WAS: Re: 3.4-Stable crashes..(heavydiskio+networking)

2000-03-23 Thread Brad Knowles
At 5:24 PM -0700 2000/3/22, Forrest W. Christian wrote: > Has there been any progress made on a decent news CACHE software? > > I'd love to try something the likes of nntpcache, but hopefully something > that works better than nntpcache did a couple of years ago. In this role, I think

Re: cvsup to RELENG_4 = 5.0-CURRENT?

2000-03-23 Thread Alexandr Listopad
> >I just cvsup'd from my freshly installed 4.0 system, using the following >supfile, and now that I reboot, and do a uname -a; I find I am in >5.0-CURRENT? > >supfile is: ># Defaults that apply to all the collections >*default host=cvsup5.FreeBSD.org >*default base=/usr >*default prefix=/usr >#

Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE (alpha) HELP!)

2000-03-23 Thread Ed Hall
Andrew Gallatin writes: : I take it the O2 bugs are not unique to us, but rather they are : generic across all OSes that gcc version 2.95.2 runs on? Do the gcc : people know these problems exist? Just FYI, the Linux kernel is compiled with: -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer