gcc 2.95.3 and STL
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 "unsubscribe freebsd-hackers" in the body of the message
accessing ide
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 freebsd-hackers" in the body of the message
Re: accessing ide
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 think you need to open the *c device to get raw device I/O. In your case that would be /dev/wd0c. 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 place?), try opening /dev/ad0 or /dev/ad0c. Both 'head -c 512 /dev/ad0 | hd' and 'head -c 512 /dev/ad0c | hd' work for me, on 4.2-stable (4.3-RC from March 25th). G'luck, Peter -- If there were no counterfactuals, this sentence would not have been paradoxical. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Control messages.
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). Actually - I had only looked at the BSD/OS 4.1 and smp-ng sources. Someone pointed out to me that in 4.2 they do align the data. I'm not sure what kernel changes they made corrisponding to this change though. Maybe someone with access to BSD/OS 4.2 kernel sources could have a look and see. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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 mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: accessing ide
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 place?), try opening /dev/ad0 or /dev/ad0c. Both 'head -c 512 /dev/ad0 | hd' and 'head -c 512 /dev/ad0c | hd' work for me, on 4.2-stable (4.3-RC from March 25th). but these two command lines give me different results, eg: cds220# head -c 32 /dev/ad0c | hd eb 1b 90 90 16 1f 66 6a 00 51 50 06 53 31 c0 88 |..fj.QP.S1..| 0010 f0 50 6a 10 89 e5 e8 c7 00 8d 66 10 cb fc 31 c9 |.Pj...f...1.| 0020 cds220# head -c 32 /dev/ad0 | hd fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c bd 00 0a 89 |.1.|| 0010 ef b9 08 00 f3 ab fe 45 f2 52 bb 00 06 89 ee b8 |...E.R..| so they are not equivalent? -- Ceri Storey [EMAIL PROTECTED] http://pkl.net/~cez/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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 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 mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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 the built-in STL. However, you may find it lacks certain features of the standard. The GCC team is slowly bringing STLport into their tree. For the moment, OpenOffice, at least requires STLport. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.3-RC bug in /usr/bin/netstat
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 IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827697 0 3751908 0 230193 xl0 1500 net.net-117/2 198.96.117.684827576 - 3751877 - - xl0 1500 fe80:1::201 fe80:1::201:2ff:f0 -0 - - lp0* 1500 Link#2 0 00 0 0 gif0* 1280 Link#3 0 00 0 0 gif1* 1280 Link#4 0 00 0 0 gif2* 1280 Link#5 0 00 0 0 gif3* 1280 Link#6 0 00 0 0 lo0 16384 Link#7 4 04 0 0 lo0 16384 fe80:7::1 fe80:7::10 -0 - - lo0 16384 localhost ::1 0 -0 - - lo0 16384 loopback.loca localhost 4 -4 - - ppp0* 1500 Link#8 0 00 0 0 sl0* 552 Link#9 0 00 0 0 faith 1500 Link#100 00 0 0 gw# netstat -ia Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827676 0 3751896 0 230193 Bus error -- [ Jim Mercer [EMAIL PROTECTED] ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka[EMAIL PROTECTED] +1 416 410-5633 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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 -i Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827697 0 3751908 0 230193 xl0 1500 net.net-117/2 198.96.117.684827576 - 3751877 - - xl0 1500 fe80:1::201 fe80:1::201:2ff:f0 -0 - - lp0* 1500 Link#2 0 00 0 0 gif0* 1280 Link#3 0 00 0 0 gif1* 1280 Link#4 0 00 0 0 gif2* 1280 Link#5 0 00 0 0 gif3* 1280 Link#6 0 00 0 0 lo0 16384 Link#7 4 04 0 0 lo0 16384 fe80:7::1 fe80:7::10 -0 - - lo0 16384 localhost ::1 0 -0 - - lo0 16384 loopback.loca localhost 4 -4 - - ppp0* 1500 Link#8 0 00 0 0 sl0* 552 Link#9 0 00 0 0 faith 1500 Link#100 00 0 0 gw# netstat -ia Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827676 0 3751896 0 230193 Bus error I get the same error on my P3/650 laptop running FreeBSD laptop.irrelevant.org 4.3-RC FreeBSD 4.3-RC #12: Fri Mar 23 13:33:14 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP i386 -- Simon Dick [EMAIL PROTECTED] "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
-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/sys/compile/KAWORU i386 [teqnix](~)%netstat -ia Name Mtu Network AddressIpkts Ier dc0 1500 Link#100:a0:cc:63:e1:8f27235 33:33:12:a4:4b:93 33:33:0:0:0:1 33:33:ff:63:e1:8f 1:0:5e:0:0:1 dc0 1500 169.69.6/24 teqnix 26969 ALL-SYSTEMS.MCAST.NET dc0 1500 fe80:1::2a0 fe80:1::2a0:ccff:0 ff02:1::2:12a4:4b93(refs: 1) ff:2:0:1:0:0 ff02:1::1 (refs: 1) ff:2:0:1:0:0 ff02:1::1:ff63:e18f(refs: 1) ff:2:0:1:0:0 etc.. etc... etc.. Evan Sarmiento ([EMAIL PROTECTED]) http://sekt7.org/es On Wed, 28 Mar 2001, 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 -i Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827697 0 3751908 0 230193 xl0 1500 net.net-117/2 198.96.117.684827576 - 3751877 - - xl0 1500 fe80:1::201 fe80:1::201:2ff:f0 -0 - - lp0* 1500 Link#2 0 00 0 0 gif0* 1280 Link#3 0 00 0 0 gif1* 1280 Link#4 0 00 0 0 gif2* 1280 Link#5 0 00 0 0 gif3* 1280 Link#6 0 00 0 0 lo0 16384 Link#7 4 04 0 0 lo0 16384 fe80:7::1 fe80:7::10 -0 - - lo0 16384 localhost ::1 0 -0 - - lo0 16384 loopback.loca localhost 4 -4 - - ppp0* 1500 Link#8 0 00 0 0 sl0* 552 Link#9 0 00 0 0 faith 1500 Link#100 00 0 0 gw# netstat -ia Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827676 0 3751896 0 230193 Bus error -- [ Jim Mercer [EMAIL PROTECTED] ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka[EMAIL PROTECTED] +1 416 410-5633 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (SunOS) Comment: Made with pgp4pine 1.75-6 iEYEARECAAYFAjrB3FoACgkQa7CFsJ0L22xh9wCfVSGIWxRaGyZZU1iDP3Y+rrTX Z5cAn17vwXP4+Q8zxnouyipJvgWHeW45 =yoe8 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: accessing ide
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 did the wd - ad transition take place?), try opening /dev/ad0 or /dev/ad0c. Both 'head -c 512 /dev/ad0 | hd' and 'head -c 512 /dev/ad0c | hd' work for me, on 4.2-stable (4.3-RC from March 25th). but these two command lines give me different results, eg: cds220# head -c 32 /dev/ad0c | hd eb 1b 90 90 16 1f 66 6a 00 51 50 06 53 31 c0 88 |..fj.QP.S1..| 0010 f0 50 6a 10 89 e5 e8 c7 00 8d 66 10 cb fc 31 c9 |.Pj...f...1.| 0020 cds220# head -c 32 /dev/ad0 | hd fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c bd 00 0a 89 |.1.|| 0010 ef b9 08 00 f3 ab fe 45 f2 52 bb 00 06 89 ee b8 |...E.R..| so they are not equivalent? yes they are not equivalent.. ad0 is the entire physical drive ad0c is the same as ad0s1 (or whatever slice is your first BSD slice). Do NOT use ad0c. it is magicly the same as ad0s1 but the magic is scheduled to dissappear some time in the next 10 years. -- Ceri Storey [EMAIL PROTECTED] http://pkl.net/~cez/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: accessing ide
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 time;
unless you're running 4.0 (or hmm, somebody correct me: when
did the wd - ad transition take place?), try opening /dev/ad0
or /dev/ad0c.
Both 'head -c 512 /dev/ad0 | hd' and 'head -c 512 /dev/ad0c | hd'
work for me, on 4.2-stable (4.3-RC from March 25th).
but these two command lines give me different results, eg:
cds220# head -c 32 /dev/ad0c | hd
eb 1b 90 90 16 1f 66 6a 00 51 50 06 53 31 c0 88 |..fj.QP.S1..|
0010 f0 50 6a 10 89 e5 e8 c7 00 8d 66 10 cb fc 31 c9 |.Pj...f...1.|
0020
cds220# head -c 32 /dev/ad0 | hd
fc 31 c0 8e c0 8e d8 8e d0 bc 00 7c bd 00 0a 89 |.1.||
0010 ef b9 08 00 f3 ab fe 45 f2 52 bb 00 06 89 ee b8 |...E.R..|
so they are not equivalent?
yes they are not equivalent..
ad0 is the entire physical drive
ad0c is the same as ad0s1 (or whatever slice is your first BSD slice).
Do NOT use ad0c. it is magicly the same as ad0s1 but the magic is scheduled to
dissappear
some time in the next 10 years.
(open mouth; take foot out; shoot foot)
Oops. Forget I said anything then. Sorry for the confusion.
G'luck,
Peter
--
I am the thought you are now thinking.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Your culture
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 mail, with "optout" in its subject. Best regards, Christophe Parmentier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: tunnel question
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 interface including the ip and ethernet header into a new ip and ethernet header, see figure below. -|-|---|---| | | data | ip(tap0) | eth(tap0) | ip(rl0) | eth(rl0) | -|-|---|---| | It is almost as a tun interface, but I would like to keep the layer 2(ARP handling) with the logical interface, that's why I want to use the tap interface and not the tun interface. Any idea have to make this to work appreciates a lot! check out the netgraph examples.. you can create a simple tunnel of this type using the ksocket node and the iface node (amongst others possibilities) The examples in /usr/share/examples/netgraph show an IP/UDP tunnel. other combinations are possible. Best Regards, Gunnar Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67 Mobile: +46 73 3279765 SE-10386 Stockholm Web: http://www.xelerated.com Email: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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 Oerrs Coll fxp0 1500 Link#100:90:27:17:09:28 9792 0 789 044 Bus error I am getting this error on all machines I have running 4.3-RC: MP and UP, desktops and laptops, with and without IPv6 :-( -- JMA ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
fixed: Re: 4.3-RC bug in /usr/bin/netstat
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 [EMAIL PROTECTED] ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka[EMAIL PROTECTED] +1 416 410-5633 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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/SATURNO
$ netstat -ai
Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll
fxp0 1500 Link#100:90:27:17:09:28 9792 0 789 044
Bus error
I am getting this error on all machines I have running 4.3-RC:
MP and UP, desktops and laptops, with and without IPv6 :-(
Okay; Jim Mercer already confirmed the attached patch worked for him.
Can more people test and review it?
G'luck,
Peter
--
I've heard that this sentence is a rumor.
Index: src/usr.bin/netstat/if.c
===
RCS file: /home/ncvs/src/usr.bin/netstat/if.c,v
retrieving revision 1.32.2.5
diff -u -r1.32.2.5 if.c
--- src/usr.bin/netstat/if.c2001/03/22 13:48:42 1.32.2.5
+++ src/usr.bin/netstat/if.c2001/03/28 13:14:35
@@ -448,9 +448,10 @@
const char *fmt;
LIST_FOREACH(multiaddr, ifnet.if_multiaddrs, ifma_link) {
- if (kread(*(u_long *)multiaddr, (char *)ifma,
+ if (kread((u_long)multiaddr, (char *)ifma,
sizeof ifma))
break;
+ multiaddr = ifma;
if (kread((u_long)ifma.ifma_addr, (char *)msa,
sizeof msa))
break;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
Broken on a few days old -current as well: turtledawn~;netstat -ia Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll lp0* 1500 Link#1 0 00 0 0 lo0 16384 Link#2 123 0 123 0 0 Bus error turtledawn~; 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 -i Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827697 0 3751908 0 230193 xl0 1500 net.net-117/2 198.96.117.684827576 - 3751877 - - xl0 1500 fe80:1::201 fe80:1::201:2ff:f0 -0 - - lp0* 1500 Link#2 0 00 0 0 gif0* 1280 Link#3 0 00 0 0 gif1* 1280 Link#4 0 00 0 0 gif2* 1280 Link#5 0 00 0 0 gif3* 1280 Link#6 0 00 0 0 lo0 16384 Link#7 4 04 0 0 lo0 16384 fe80:7::1 fe80:7::10 -0 - - lo0 16384 localhost ::1 0 -0 - - lo0 16384 loopback.loca localhost 4 -4 - - ppp0* 1500 Link#8 0 00 0 0 sl0* 552 Link#9 0 00 0 0 faith 1500 Link#100 00 0 0 gw# netstat -ia Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 Link#100:01:02:6e:26:05 4827676 0 3751896 0 230193 Bus error -- [ Jim Mercer [EMAIL PROTECTED] ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka[EMAIL PROTECTED] +1 416 410-5633 ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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 Link#1 0 00 0 0
lo0 16384 Link#2 123 0 123 0 0
Bus error
turtledawn~;
Yes, it seems the same bug's in -current, too; patch attached.
G'luck,
Peter
--
This sentence would be seven words long if it were six words shorter.
Index: src/usr.bin/netstat/if.c
===
RCS file: /home/ncvs/src/usr.bin/netstat/if.c,v
retrieving revision 1.38
diff -u -r1.38 if.c
--- src/usr.bin/netstat/if.c2001/03/04 22:25:05 1.38
+++ src/usr.bin/netstat/if.c2001/03/28 14:24:44
@@ -448,9 +448,10 @@
const char *fmt;
TAILQ_FOREACH(multiaddr, ifnet.if_multiaddrs, ifma_link) {
- if (kread(*(u_long *)multiaddr, (char *)ifma,
+ if (kread(multiaddr, (char *)ifma,
sizeof ifma))
break;
+ multiaddr = ifma;
if (kread((u_long)ifma.ifma_addr, (char *)msa,
sizeof msa))
break;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-RC bug in /usr/bin/netstat
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 #0: Wed Mar 28 15:11:51 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SATURNO $ netstat -ai Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll fxp0 1500 Link#100:90:27:17:09:28 9792 0 789 044 Bus error I am getting this error on all machines I have running 4.3-RC: MP and UP, desktops and laptops, with and without IPv6 :-( Okay; Jim Mercer already confirmed the attached patch worked for him. Can more people test and review it? OK, I just (finally) finished rebuilding world with that fix in and it now works fine for me -- Simon Dick [EMAIL PROTECTED] "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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 and it seems to work fairly well for us. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: accessing ide
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 right device to open if you want to access the mbr. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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 Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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. Send a patch when you are done. 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. dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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? Are there other caveats? It's pretty trivial. Send a patch when you are done. 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 so I morally can't defend to do it. I hope nobody else helps you either... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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. 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. You did. "pretty trival". I.E. will not take much work, and no good reason not to expand them. Since you've said so many times you can hack your own system, sounds like PHK told you what you needed to know. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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't see the article on-line, so I'll have to try my local Borders. Just to be nitpicking (and to prove that my glasses works sometimes), there is an article that deals with conformance in different compilers at the site: http://www.cuj.com/roundup/a.htm Fast-browsing it seems that conformance visavi STL is not the main focus of this article. It doeas talk about a STL roundup though. -- Cheers! Joachim - Alltid i harmonisk svngning --- FairLight -- FairLight -- FairLight -- FairLight --- Joachim Strmbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47Web: http://www.ludd.luth.se/~watchman --- Spamfodder: [EMAIL PROTECTED] --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: driver: probe not called when smbus child
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
code to do that:
DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0);
But when I put it on the smbus using
DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0);
only identify is called. The identify function is as follows:
static void
my_identify(driver_t *driver, device_t parent)
{
devclass_t dc;
device_t child;
printf("my: my_identify called\n");
dc = devclass_find("my");
if (devclass_get_device(dc, 0)==NULL) {
child = BUS_ADD_CHILD(parent, 0, "my", -1);
}
}
The driver only uses smbus calls, so I think the best parent
would be smbus.
I'm currently working on this.
And when I do a smbus_request_bus, the call waits forever as
it seems. That seems sensible to me, because it asks the
parent for the bus and the isa bus can't grant requests for
the smbus. So I think the driver has to be a child of the smbus.
requesting the smbus is needed when the smbus controller potentially
share resources on another bus (like lpbb(4) does on ppbus).
Looking in the kernel sources, I see that the only smbus child
I can find, smb, (if there are others, I'm certainly interested)
is attached in the smbus code itself. So the next question rises:
Is it possible to have an smbus child in a dynamically loadable
module (I can't find smbus.ko in /modules, so loading the child
first and then smbus isn't an option I guess) ?
Currently, smb is the only smbus child. This is due to the fact that
most people prefer programming their SMB chips from user space.
I have a patch and a complete modules/i2c tree for compiling smbus and
smb as modules. You must be interested... But I have to fix some issues
like identification and driver dynamic addition.
Sure! Do you have the patch somewhere? For development, I could live
with changing the smbus driver to add my driver statically. The
driver currently works with parent_add_child in driver_identify, but
the system freezes regularly when about 2 smbus reads / sec are made.
Maybe I can find out more with your patch.
--
[EMAIL PROTECTED]
Alcve - Open Source Software Engineer - http://www.alcove.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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 so I morally can't defend to do it. I hope nobody else helps you either... This is conduct entirely inappropriate for this or any other FreeBSD list. Please keep the discussion relevant. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
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 larger share of the more profitable sun/NT market, and convince them that they want no part of the "free" market if they have to compete with cut-rate hardware from hungry companies. Ok, let me get this Free Market thing straight. Not buying from a good company that provides a useful product and instead buying from a bad company that doesn't provide a useful product will make things better. That seems to be what you are saying dennis. Or did I misunderstand? -- Christopher Weimann SysAdmin 400 Higgins Ave Wall Internet LLC.Brielle NJ, 08730 732-223-1777 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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? It's pretty trivial. Send a patch when you are done. 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. You did. "pretty trival". I.E. will not take much work, and no good reason not to expand them. Since you've said so many times you can hack your own system, sounds like PHK told you what you needed to know. What a helpful bunch. thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
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 these companies so that the good companies can have a larger share of the more profitable sun/NT market, and convince them that they want no part of the "free" market if they have to compete with cut-rate hardware from hungry companies. Ok, let me get this Free Market thing straight. Not buying from a good company that provides a useful product and instead buying from a bad company that doesn't provide a useful product will make things better. That seems to be what you are saying dennis. No, I said just the opposite. This was in response to someone suggesting that we boycott companies like Intel for not providing full disclosure on their boards, and reward companies that do by touting their products. So I said that promoting lesser products because they are "cooperative" will make good hardware less available to the freebsd community, which might make some little people feel powerful but it wont serve the user base, which I assume is the goal. Get it? Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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 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. You did. "pretty trival". I.E. will not take much work, and no good reason not to expand them. Since you've said so many times you can hack your own system, sounds like PHK told you what you needed to know. What a helpful bunch. thanks. Just ignore them. I know it's hard, but once you get used to it, it'll hurt less. Trust me on this one. 8) Anyway, I just had a quick look, and I think that your basic problem is that MAKEDEV uses the wrong encoding for devices above 255. This is fixed in -CURRENT, and if you bring back the unit2minor changes from there to -STABLE you should be in business. If this works, please file a PR so that it gets fixed. Thanks, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
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 patch when you are done. 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. You did. "pretty trival". I.E. will not take much work, and no good reason not to expand them. Since you've said so many times you can hack your own system, sounds like PHK told you what you needed to know. What a helpful bunch. thanks. Just ignore them. I know it's hard, but once you get used to it, it'll hurt less. Trust me on this one. 8) it doesnt "hurt" at all. Dealing with bitter losers is part of the public experience :-) Thanks for the tip. i'll forward it to the customer who needs it and let him do the work. I've got some more flames to deflect :-) Dennis Anyway, I just had a quick look, and I think that your basic problem is that MAKEDEV uses the wrong encoding for devices above 255. This is fixed in -CURRENT, and if you bring back the unit2minor changes from there to -STABLE you should be in business. If this works, please file a PR so that it gets fixed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ddb - gdb help?
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," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
header files for sockets
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 work with sockets. If that is not specific enough, here is a brief summary of the system calls i will need to use: socketpair(); socket(); bind(); connect(); listen(); sendto(); recvfrom(); send(); recv(); ok thats about the gist of it, so if anyone know the header files I need to include to access those systems calls it would be great, because the only way i am ever gonna really learn this is if i get in there and code :-) _ Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: header files for sockets
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 I would like to know is the header files I will need to include to work with sockets. If that is not specific enough, here is a brief summary of the system calls i will need to use: socketpair(); socket(); bind(); connect(); listen(); sendto(); recvfrom(); send(); recv(); ok thats about the gist of it, so if anyone know the header files I need to include to access those systems calls it would be great, because the only way i am ever gonna really learn this is if i get in there and code :-) the header files necessary for all of these system calls are listed at the top of the man pages describing them. if you want a more in depth treatment, i suggest reading "Unix Network Programming" by W. Richard Stevens, widely regarded as the best text on network programming anywhere. -- garrett rooney Unix was not designed to stop you from [EMAIL PROTECTED] doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ddb - gdb help?
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 method that works for me. Don't know if it still works for current, but you can find out. I use cscope to find out what file the function in question is in, then I go to the kernel build directory (and it must use exactly the same sources, for reasons you'll find obvious) and rm the object file involved. Actually, before you do that, do another make, so that you can be certain that the object file you rm is the *only* one that needs to be rebuilt. I have a hacked Makefile in there, so that I can set CC remotely, you may have to hack the Makefile youself, because you need to change the definition of CC or cflags in such a way that the option "-Wa,-a" gets added; this causes the assembler listing file to come out to stdout. do another make then, and catch the output, either in a file or via less. Find in the listing the starting address for the function. Notice that the C code is in that file also, making it easier to find what you're after. Also, in the second column from the left, is the binary offsets into the file. Locate the function you're after, and find out what it's binary offset is. Look at the error above, it says it ""Stopped at lf_setlock+0x52" so after you find the offset of lf_setlock, add (using hex math) 0x52 to it, and locate that offset in the assembler listing. Look higher in the listing for the immediately previous C source code line, you've got your target line. Tell me, does this still work in current now? Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
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' to facilitate the progress they've made with OpenOffice. I haven't looked at the changes they made but as soon as I get NetBSD on that U1 I'll take a look at it. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Network Throughput;SMP
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, PktSize:491 Bytes Results: 1 Proc: shows clean linear growth of the delay time over the Pckt# 2 Proc: the line shows increased growth at the beginning which than grows (SMP)in parallel to the other line. (so it shows higher delays) This astonished me. But netstat -w1 shows the same: 1 Proc shows: [...] 27083 0 11793296 27079 0 11793296 0 27072 0 11793296 27048 0 11793296 0 27083 0 11795052 27085 0 11793576 0 SMP shows: [...] 26299 7 11435222 26462 0982452510 26226 8 11441218 3788 098515 26312 7 11453406 47716 09998115 0 It seems that SMP has some performance losses compared to single proc. I think this behaviour is already well known. Is there an explanation for it (maybe SMP overhead, APIC routes IRQ wrong)? Is there an Analysis? Used Hardware, Tyan Board Dual PIII 800MHz, BX440, 512MB, 2 fxp, 1xl Thanks for your time cheers, Jochen p.s: don't stone when this belongs to the smp list, please, just reroute me :) -- Jochen Kaiserkind@IRCNET, phone +49 9131 85-28134 Network Administration mailto:[EMAIL PROTECTED] Regionales Rechenzentrum Universitaet Erlangen-Nuernberg, Germany GPG public key: http://www.uni-erlangen.de/~unrza2/public_key.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: header files for sockets
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 enough, here is a brief summary of the system calls i will need to use: Most if not all of the relevant system calls are prototyped in sys/socket.h. For reasons that made since when cave men wrote code on stone tablets, sys/* usually don't include sys/types.h, so putting that first would be a good idea. Of course, for all properly documented library functions the man pages give the header files, and you could always type man command For example drew@revolt% man socketpair NAME socketpair - create a pair of connected sockets LIBRARY Standard C Library (libc, -lc) SYNOPSIS #include sys/types.h #include sys/socket.h ... etc. -- a href="http://www.poohsticks.org/drew/"Home Page/a For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
help with 4.3-RC1 / ports
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 for bzip-0.21 Checksum OK for bzip-0.21.tar.gz. === Patching for bzip-0.21 === Applying FreeBSD patches for bzip-0.21 === Configuring for bzip-0.21 === Building for bzip-0.21 make: don't know how to make configure. Stop *** Error code 2 Stop in /v0/obj/usr/ports/archivers/bzip/work/bzip-0.21. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: help with 4.3-RC1 / ports
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 upgrading, but the result is the same, make fails, eg: === Extracting for bzip-0.21 Checksum OK for bzip-0.21.tar.gz. === Patching for bzip-0.21 === Applying FreeBSD patches for bzip-0.21 === Configuring for bzip-0.21 === Building for bzip-0.21 make: don't know how to make configure. Stop *** Error code 2 Stop in /v0/obj/usr/ports/archivers/bzip/work/bzip-0.21. *** Error code 1 What environment variables have you set to get the port to build in this nonstandard location? Kris PGP signature
# of bpf devices
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 [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
