On Thu, Mar 29, 2001 at 09:45:48AM +0200, Danny Braniss wrote:
> hi all,
> (sorry if this is the wrong place, but I realy want 4,3 in production
> asap).
> ever since 4.3 BETA i can't compile anything from the ports.
> i've gone through the cycle of installing the distribution, or upgr
hi all,
(sorry if this is the wrong place, but I realy want 4,3 in production
asap).
ever since 4.3 BETA i can't compile anything from the ports.
i've gone through the cycle of installing the distribution, or upgrading,
but the result is the same, make fails, eg:
===> Extracting
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
m writes:
>the header files they tell you to include are no longer correct.
The header files are pretty much standard.
>So
>what I would like to know is the header files I will need to include to work
>with sockets. If that is not specific eno
Hello,
I am doing some tests with a traffic generator atm. It's a SmartBits 6000
and I tried to test my FreeBSD box. I did a test series which did start
at low bandwidth (5MBit) and until 85Mbit all seemed ok. But then I tried
to find the frontiers - and I did.
Test: 93MBit Constant Stream, UDP,
On Wed, 28 Mar 2001, David O'Brien wrote:
% But the point is actually mute. The STLport will not build on FreeBSD
% using either bmake or gmake. If someone wants to put some time into
% getting around the problems, then people would have a choice again.
The NetBSD guys have STLport in 'pkgsrc
On Wed, 28 Mar 2001, Alfred Perlstein wrote:
> I can't seem to get a crashdump, is there a way to take a
> ddb crash address: "Stopped at lf_setlock+0x52"
> and boot later and see what line of code that's on?
I do *lots* of debugging on very old 2.2.2 version stuff for my company,
and I have a
On Wed, Mar 28, 2001 at 10:25:30PM -0500, Arthur Munn wrote:
> hello everyone, I am just now learning about sockets in FreeBSD. I have
> managed to find some great freely available docs online, but there is a
> problem, the header files they tell you to include are no longer correct. So
> what
hello everyone, I am just now learning about sockets in FreeBSD. I have
managed to find some great freely available docs online, but there is a
problem, the header files they tell you to include are no longer correct. So
what I would like to know is the header files I will need to include to wo
I can't seem to get a crashdump, is there a way to take a
ddb crash address: "Stopped at lf_setlock+0x52"
and boot later and see what line of code that's on?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Instead of asking why a piece of software is using "1970s technology,"
sta
At 04:56 PM 03/28/2001, Mike Smith wrote:
> > > > > >It seems that only 256 bpf devices are supported. How painful would
> > > > > >it be to increase that number...I assume its an 8bit varable
> > > > > >somewhere?
> > > > > >Are there other caveats?
> > > > >
> > > > >It's pretty trivial. Send a
> > > > >It seems that only 256 bpf devices are supported. How painful would
> > > > >it be to increase that number...I assume its an 8bit varable
> > > > >somewhere?
> > > > >Are there other caveats?
> > > >
> > > >It's pretty trivial. Send a patch when you are done.
> > >
> > > I was hoping
At 04:22 PM 03/28/2001, Chistopher S. Weimann wrote:
>On Wed, Mar 14, 2001 at 12:33:21PM -0500, Dennis wrote:
> >
> > Your logic is backwards. You think that rewarding mediocre companies will
> > scare good companies into wanting a piece of the pie. The only thing that
> > it will do is consume th
At 03:17 PM 03/28/2001, David O'Brien wrote:
>On Wed, Mar 28, 2001 at 02:49:53PM -0500, Dennis wrote:
> > > >It seems that only 256 bpf devices are supported. How painful would
> it be
> > > >to increase that number...I assume its an 8bit varable somewhere?
> Are there
> > > >other caveats?
> >
On Wed, Mar 14, 2001 at 12:33:21PM -0500, Dennis wrote:
>
> Your logic is backwards. You think that rewarding mediocre companies will
> scare good companies into wanting a piece of the pie. The only thing that
> it will do is consume these companies so that the good companies can have a
> larg
> >I was hoping to get some useful insight before I looked into it..or if
> >there was a sound reason for not expanding them. Im hopeful someone
> >brighter will answer.
>
> Well, if anybody but you had answered I would have fixed it right away,
> but since it would probably help you if I did s
Nicolas Souchu wrote:
>
> On Tue, Mar 20, 2001 at 04:50:09PM +0100, Willem van Engen wrote:
> > I'm trying to write a module which should be a child of the smbus.
> > When I make the driver a child of the isa bus, identify, probe,
> > and attach functions are properly called. I use the following
>
Aloha!
David O'Brien wrote:
>
> On Wed, Mar 28, 2001 at 10:45:37AM +0100, Benny Prijono wrote:
> > the March 2001 edition of C++ Users Journal (http://www.cuj.com) has
> > surveys on comformance level of each C++ compiler and STL
> > implementation. You may want to take a look at it.
>
> I didn
On Wed, Mar 28, 2001 at 02:49:53PM -0500, Dennis wrote:
> > >It seems that only 256 bpf devices are supported. How painful would it be
> > >to increase that number...I assume its an 8bit varable somewhere? Are there
> > >other caveats?
> >
> >It's pretty trivial. Send a patch when you are done.
>
On Wed, Mar 28, 2001 at 10:45:37AM +0100, Benny Prijono wrote:
> the March 2001 edition of C++ Users Journal (http://www.cuj.com) has
> surveys on comformance level of each C++ compiler and STL
> implementation. You may want to take a look at it.
I didn't see the article on-line, so I'll have to
In message <[EMAIL PROTECTED]>, Dennis writes:
>At 01:32 PM 03/28/2001, Poul-Henning Kamp wrote:
>>In message <[EMAIL PROTECTED]>, Dennis writes:
>> >
>> >It seems that only 256 bpf devices are supported. How painful would it be
>> >to increase that number...I assume its an 8bit varable somewhere?
At 01:32 PM 03/28/2001, Poul-Henning Kamp wrote:
>In message <[EMAIL PROTECTED]>, Dennis writes:
> >
> >It seems that only 256 bpf devices are supported. How painful would it be
> >to increase that number...I assume its an 8bit varable somewhere? Are there
> >other caveats?
>
>It's pretty trivial.
It seems that only 256 bpf devices are supported. How painful would it be
to increase that number...I assume its an 8bit varable somewhere? Are there
other caveats?
VPNs and extensive frame relay setups with DHCP require more than 256 devices.
Dennis
To Unsubscribe: send mail to [EM
In message <[EMAIL PROTECTED]>, Dennis writes:
>
>It seems that only 256 bpf devices are supported. How painful would it be
>to increase that number...I assume its an 8bit varable somewhere? Are there
>other caveats?
It's pretty trivial. Send a patch when you are done.
--
Poul-Henning
In message <[EMAIL PROTECTED]> Ceri Storey writes:
: but these two command lines give me different results, eg:
: cds220# head -c 32 /dev/ad0c | hd
: so they are not equivalent?
ad0 is the whole device. ad0c is the whole slice. These can be the
same, but are often different. /dev/ad0 is the ri
In message <[EMAIL PROTECTED]> Arjan Knepper writes:
: Could anyone make recommandations on the STL to use with C++. I'm using
: the build in gcc 2.95.2 on -stable and build in gcc 2.95.3 on -current.
:
: What is preffered the build-in STL (/usr/include/g++) or STLport?
We use the builtin stl an
On Wed, Mar 28, 2001 at 04:45:41PM +0300, Peter Pentchev wrote:
> On Wed, Mar 28, 2001 at 03:42:10PM +0200, Jose M. Alcaide wrote:
> > Jim Mercer wrote:
> > >
> > > netstat gets a bus error if handed the -a option and the -i option.
> > >
> >
> > Me too:
> >
> > $ uname -v
> > FreeBSD 4.3-RC #
On Wed, Mar 28, 2001 at 09:19:04AM -0500, Michael Lucas wrote:
> Broken on a few days old -current as well:
>
> turtledawn~;netstat -ia
> Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll
> lp0* 1500 0 00 0 0
> lo0 1
Broken on a few days old -current as well:
turtledawn~;netstat -ia
Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll
lp0* 1500 0 00 0 0
lo0 16384123 0 123 0 0
Bus error
tu
Peter Pentchev wrote:
>
> Okay; Jim Mercer already confirmed the attached patch worked for him.
> Can more people test and review it?
>
Fixed, thanks!
-- JMA
** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] **
** "Beware of Programmers who carry screwdrivers" -- Leonar
On Wed, Mar 28, 2001 at 03:42:10PM +0200, Jose M. Alcaide wrote:
> Jim Mercer wrote:
> >
> > netstat gets a bus error if handed the -a option and the -i option.
> >
>
> Me too:
>
> $ uname -v
> FreeBSD 4.3-RC #0: Wed Mar 28 15:11:51 CEST 2001
>[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SATURN
On Wed, Mar 28, 2001 at 03:42:10PM +0200, Jose M. Alcaide wrote:
> Jim Mercer wrote:
> >
> > netstat gets a bus error if handed the -a option and the -i option.
> >
>
> Me too:
a fix was emailed to me by Peter Pentchev, seems to work.
thanx.
http://www.freebsd.org/cgi/query-pr.cgi?pr=26168
Jim Mercer wrote:
>
> netstat gets a bus error if handed the -a option and the -i option.
>
Me too:
$ uname -v
FreeBSD 4.3-RC #0: Wed Mar 28 15:11:51 CEST 2001
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SATURNO
$ netstat -ai
Name Mtu Network AddressIpkts IerrsOpkts Oe
Gunnar Olsson wrote:
>
> Hi there,
>
> I have configured a logical ethernet interface, so called a tap interface
> (tap0).
> I have also managed to bridged that interface to my "real" ethernet
> interface (rl0)
> and it works fine. Now to my question.
>
> Is it possible to "tunnel" my tap inter
We need to devide culture... yours too...
Please accept it, connecting you to www.humanahom.com
If you need further informations about us or our project, please connect you
to our site or simply reply to this mail.
If culture doesn't interess you, choose "optout" option, by replying to this
ma
On Wed, Mar 28, 2001 at 05:08:40AM -0800, Julian Elischer wrote:
> Ceri Storey wrote:
> >
> > On Wed, Mar 28, 2001 at 11:36:25AM +0300, Peter Pentchev wrote:
> > [...]
> > > And btw, another part of your problem could be that FreeBSD
> > > has used ad, not wd, for ATAPI devices access for some ti
Ceri Storey wrote:
>
> On Wed, Mar 28, 2001 at 11:36:25AM +0300, Peter Pentchev wrote:
> [...]
> > And btw, another part of your problem could be that FreeBSD
> > has used ad, not wd, for ATAPI devices access for some time;
> > unless you're running < 4.0 (or hmm, somebody correct me: when
> > di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Perhaps this problem is specific to your system setup. I also run 4.3-RC,
and my netstat -ia appears to work fine.
[teqnix](~)%uname -a
FreeBSD teqnix.sekt7.org 4.3-RC FreeBSD 4.3-RC #32: Mon Mar 26 06:28:30
GMT 2001 [EMAIL PROTECTED]:/usr/src/sy
On Wed, Mar 28, 2001 at 07:33:25AM -0500, Jim Mercer wrote:
>
> netstat gets a bus error if handed the -a option and the -i option.
>
> gw# uname -a
> FreeBSD gw.reptiles.org 4.3-RC FreeBSD 4.3-RC #0: Tue Mar 27 18:24:41 EST 2001
>[EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386
>
> gw
netstat gets a bus error if handed the -a option and the -i option.
gw# uname -a
FreeBSD gw.reptiles.org 4.3-RC FreeBSD 4.3-RC #0: Tue Mar 27 18:24:41 EST 2001
[EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386
gw# netstat -i
Name Mtu Network AddressIpkts IerrsOp
On Wed, 28 Mar 2001, Arjan Knepper wrote:
% Could anyone make recommandations on the STL to use with C++. I'm using
% the build in gcc 2.95.2 on -stable and build in gcc 2.95.3 on -current.
%
% What is preffered the build-in STL (/usr/include/g++) or STLport?
In general you should stick with th
the March 2001 edition of C++ Users Journal (http://www.cuj.com) has
surveys on comformance level of each C++ compiler and STL
implementation. You may want to take a look at it.
cheers,
Bennylp
David O'Brien wrote:
>
> On Wed, Mar 28, 2001 at 10:26:56AM +0200, Arjan Knepper wrote:
> > What is p
On Wed, Mar 28, 2001 at 11:36:25AM +0300, Peter Pentchev wrote:
[...]
> And btw, another part of your problem could be that FreeBSD
> has used ad, not wd, for ATAPI devices access for some time;
> unless you're running < 4.0 (or hmm, somebody correct me: when
> did the wd -> ad transition take pla
On Wed, Mar 28, 2001 at 10:26:56AM +0200, Arjan Knepper wrote:
> What is preffered the build-in STL (/usr/include/g++) or STLport?
The one bundled with (and matches) G++ of course. Unless you find your
code just will not work with it.
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mai
On Wed, Mar 28, 2001 at 08:34:53AM +0100, David Malone wrote:
> I've had a look at what other people have done about this issue.
> The NetBSD people seem to have taken the fix I'm proposing. Solaris
> and BSD/OS don't provide the required alignment and just define
> CMSG_DATA(cm) to be (cm+1).
A
On Wed, Mar 28, 2001 at 02:01:54PM +0200, Sandeep Kohli wrote:
> hi,
> i am writing kinda fdisk program..now when i opened /dev/hda in linux
> and tried to lseek to the mbr it worked
> but its not working in freebsd when i am trying to access /dev/wd0
> i donot want to use disklabel.h
> thanks
I
hi,
i am writing kinda fdisk program..now when i opened /dev/hda in linux
and tried to lseek to the mbr it worked
but its not working in freebsd when i am trying to access /dev/wd0
i donot want to use disklabel.h
thanks
sandeep
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
Hello,
Could anyone make recommandations on the STL to use with C++. I'm using
the build in gcc 2.95.2 on -stable and build in gcc 2.95.3 on -current.
What is preffered the build-in STL (/usr/include/g++) or STLport?
Thanks,
Arjan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
47 matches
Mail list logo
