RE: 4.0 slower than 3.4?
Jason Young wrote: Saturday, January 08, 2000 9:02 AM > It probably isn't the best of all ideas to have BOTH IP firewalling > solutions installed and running at once. This will add some > overhead. Pick one and stick with it. And why do you have DUMMYNET > running? > > There is a new version of IPFilter in -CURRENT if I recall > correctly, and this may be related to your timing issues. Really > you ought to just take IPFILTER out of your configuration. To my understanding, both IPFW (ipfw.ko) and IPFILTER (ipl.ko) can be built as modules. I have made some lmbench tests and they show that ipfilter actually adds more latency than ipfw. Here are some lmbench results taken on a P3-500, -current (2 days old) First, plain (no module loaded): UDP latency using localhost: 65 microseconds TCP latency using localhost: 67 microseconds RPC/udp latency using localhost: 111 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 71.97 MB/sec Now, ipl.ko loaded (ipfilter), no rulesets UDP latency using localhost: 80 microseconds TCP latency using localhost: 85 microseconds RPC/udp latency using localhost: 129 microseconds RPC/tcp latency using localhost: 155 microseconds TCP/IP connection cost to localhost: 145 microseconds Socket bandwidth using localhost: 67.72 MB/sec The following is for ipfw.ko loaded (default policy to accept, no other rules). UDP latency using localhost: 68 microseconds TCP latency using localhost: 73 microseconds RPC/udp latency using localhost: 115 microseconds RPC/tcp latency using localhost: 143 microseconds TCP/IP connection cost to localhost: 127 microseconds Socket bandwidth using localhost: 70.11 MB/sec And finally, both ipl.ko and ipfw.ko loaded (rather stupid imho, I think they're supposed to work as an either-or solution :) ). UDP latency using localhost: 84 microseconds TCP latency using localhost: 90 microseconds RPC/udp latency using localhost: 132 microseconds RPC/tcp latency using localhost: 160 microseconds TCP/IP connection cost to localhost: 152 microseconds Socket bandwidth using localhost: 66.04 MB/sec -- /"\ / \ / ASCII RIBBON CAMPAIGN /For every single problem you can X AGAINST HTML MAIL/ find a solution, which is simple, / \ AND POSTINGS/ neat and wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: 4.0 slower than 3.4?
Garrett Wollman [mailto:[EMAIL PROTECTED]] wrote: Sent: Saturday, January 08, 2000 7:27 PM > You should also try it with `options COMPAT_IPFW=0' in your config > file. Hm, what's this option for? When I put it into my kernel config, the config program complained about an "unknown option". A quick grep over the kernel sources also didn't find it anywhere. Anyway, since I'am using ipfilter as a module, I still have IPFILTER_LKM in my config file (it is required, otherwise the ipl.ko kernel module will not load and complain about a undefined function). This option is still in the source (ip_input.c and ip_output.c), but is missing in the configuration files (even in LINT) for some (?) reason. After removing IPFILTER_LKM, I ran the bench again and got following results. UDP latency using localhost: 63 microseconds TCP latency using localhost: 66 microseconds RPC/udp latency using localhost: 109 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 72.63 MB/sec - To make comparing easier, here are the results I already posted yesterday. First, plain (no module loaded): UDP latency using localhost: 65 microseconds TCP latency using localhost: 67 microseconds RPC/udp latency using localhost: 111 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 71.97 MB/sec Now, ipl.ko loaded (ipfilter), no rulesets UDP latency using localhost: 80 microseconds TCP latency using localhost: 85 microseconds RPC/udp latency using localhost: 129 microseconds RPC/tcp latency using localhost: 155 microseconds TCP/IP connection cost to localhost: 145 microseconds Socket bandwidth using localhost: 67.72 MB/sec The following is for ipfw.ko loaded (default policy to accept, no other rules). UDP latency using localhost: 68 microseconds TCP latency using localhost: 73 microseconds RPC/udp latency using localhost: 115 microseconds RPC/tcp latency using localhost: 143 microseconds TCP/IP connection cost to localhost: 127 microseconds Socket bandwidth using localhost: 70.11 MB/sec And finally, both ipl.ko and ipfw.ko loaded (rather stupid imho, I think they're supposed to work as an either-or solution :) ). UDP latency using localhost: 84 microseconds TCP latency using localhost: 90 microseconds RPC/udp latency using localhost: 132 microseconds RPC/tcp latency using localhost: 160 microseconds TCP/IP connection cost to localhost: 152 microseconds Socket bandwidth using localhost: 66.04 MB/sec -- /"\ / \ / ASCII RIBBON CAMPAIGN /For every single problem you can X AGAINST HTML MAIL/ find a solution, which is simple, / \ AND POSTINGS/ neat and wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
At 17:16 09.03.2000 -0800, Kris Kennaway wrote: > > the variable being defined and not its value. You might try removing > > your object directory and doing a make cleandir twice to make sure > > nothing is left in source tree that shouldn't be there. > >Yes, thats a likely candidate. Can you try blowing away /usr/obj and see >if the problem persist? Testa aslfdj slkdflaskdf lksflskf laksdflkas dflskf sldkfjsl lskdfj laskdjf lksdlks fskdjfls slkdfjs dlkasldk sjdlfkjs fskdjfl sdlfjslf sldjf sldfjs ldkfj To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re[2]: "The Matrix" screensaver, v.0.2
On 27.08.1999, 10:52, Jordan K. Hubbard wrote: > Sorry, I've lived in Europe, you can't pull that one on me. :) > In Germany, for example, it's possible to sue someone simply for > sticking their finger against their forehead. The myth that only the > U.S. is litigious is just that, a myth. Europeans sue the crap out of > one another all the time, and for issues just as silly. :) True. A well known german lawyer is currently about to sue a few webhosters for using the name "Webspace" in their ads. (Yes, some silly - or maybe not-so-silly - dude has registered the word "Webspace" as a trademark). In this case, the problem are not the lawyers, but the fact that you can actually register trademarks like this one. Others have been threatened with lawsuits for using the word "Triton" in mainboard advertisments a few years ago, because "Triton" sounds very similar to the registered trademark "Tricon". -- # My PGP public key (ID=7A2AFB8F): http://darkstar.psa.at/aspgp.txt# # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Shared memory changes in current?
Anyone aware of them? After building a complete kernel + world with a very recent -current (Saturday morning, european time) I now get lots of shared memory errors in gnome (most coming from gdk and imlib, some from Xfree 4 aswell). I recompiled parts of gnome (gtk+, imlib, glib) and the situation has slightly changed, but gdk still throws a lot of shmget() failed: errors. -- Q: What have american beer and sex in a canoe in common? A: Both are fucking close to water. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 16:30 23.06.2000 -0400, Garance A Drosihn wrote: >> > modified my shared memory settings in my kernel config either. If >> > the problem is indeed Xfree 4.0, then I guess it must be a driver >> > issue (I'm using the neomagic driver). >> >>You are running sawfish, and I'm willing to bet a not very graphics >>intensive config at that. > >Note that Chris (who posted the original message) is also running >sawmill/sawfish... (they are the same thing, right?) Same here. Latest sawfish, and yes, they're the same. The name was changed from sawmill to sawfisch because of some trademark/copyright problems. I'am ready to try another WM and see whether the SHM problems stay or not (other solutions didn't exactly work, I _dramatically_ increased all the SHM limits in the kernel but still get tons of shm errors from imlib or gdk). Yet, I still see excessive shm usage in the output of ipcs (similar to the output reported by the original poster). BTW: It's for sure _not_ a -current issue and might have nothing to do with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with Xfree 4.0 and Gnome 1.2. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Gnome INSANE shared memory usage
At 18:41 23.06.2000 -0400, Christopher Masto wrote: > > BTW: It's for sure _not_ a -current issue and might have nothing to do > > with FreeBSD at all, since I'am running 4.0-STABLE on this machine, with > > Xfree 4.0 and Gnome 1.2. > >Which video card/driver are you using? (Mine is tdfx and s3virge) nVidia GeForce DDR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: emu10k1 problems solved
At 09:15 07.08.2000 +0200, Benedikt Schmidt wrote: >Just wanted to say that with the recent changes in the >emu10k1 driver all my problems with it have disappeared. > >There are no more "dodgy irq" messages >and the sound quality has improved too (no more crackling). Just a quick question... Is it possible to get this driver working under 4.1-STABLE aswell, or are the changes in the -current kernel already too big? Or is it officially planned to merge this updated driver into the -STABLE branch? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current (aka 4.x) breaks libtool
Hi This isn't exactly topic here, but it might be useful as a little hint or warning... Even most recent versions of libtool (1.2e imho) fail to check for freebsd4* (as expected). As a result, they set can_build_shared to "no" which disables building of shared libraries. This affects most major projects like kde or gnome and can result in major abuse of disk- and memory space :) (some kde or gnome binaries tend to get *very* large when linked statically). Workarounds ? I'am currently using --host=i386-unknown-freebsd3 as a possible workaround, another way might be a small modification of ltconfig. Sorry, if this has been already mentioned... -- # /AS/ http://privat.schlund.de/entropy/ # # # # If Jesus was never born, we would not have a Y2K problem.# To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
PPP (userland) troubles ?
Hi! I'am not sure where this comes from, but at the moment I have some troubles with the userland ppp. The symptoms: After establishing the connection and setting the defaultroute *nothing* works, that means, the line seems to be completely dead. Not even the peer can be pinged. However, after a short while the symptoms vanish and everything is as it should be. I don't believe in faults at my provider, since I tested it with different accounts and basically got the same results. Sometimes when I try to ping the peer, I get some "sendto: no buffer space available" messages before the reply packets start to drop in. Config: (very)-current, everything ELF, ppp via plain and simple modem dialup. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated.-- From The Gimp manual # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: PPP (userland) troubles ?
On Tue, 26 Jan 1999, Brian Somers wrote: > Are you using a routing daemon ? Also, have you tried just having > ``add default HISADDR'' in ppp.conf and leaving everything out of > ppp.linkup ? What do your routing tables look like before/during/after > the hang ? I usually run routed, yes, and it didn't ever affect the dialup functionality. Disabling routed does not change the behaviour in any way. My ppp.linkup doesn't really contain much stuff. The only thing it does is running the mailqueue. Also, I have "add default HISADDR" in my ppp.conf. A sample output of netstat -nr after establishing the connection looks like follows: [73]r...@darkstar:/root #>netstat -nr Routing tables Internet: DestinationGatewayFlags Refs Use Netif Expire default131.130.230.14 UGSc 101 tun0 127.0.0.1 127.0.0.1 UH 21 1910 lo0 131.130.230.14 131.130.231.66 UH 110 tun0 131.130.231.66 127.0.0.1 UH 00 lo0 [74]r...@darkstar:/root #> In this case, 131.130.231.66 is the adress assigned to my tun0 interface, 131.130.230.14 is the peer. So this, really looks ok. To remove any possible influences, I have temporarily removed the lan configuration (normally, this box has a 3c905 NIC for my littly lan). In fact, I never had problems like that, they started to show up a few days ago (a lot of stuff has been commited the last couple of days, and I also noted small changes to /usr/src/usr.sbin/ppp. The delay until everything works ok looks like something waits for some buffer to be filled up, because there is absolutely no modem activity for the first couple of seconds. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated.-- From The Gimp manual # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: PPP (userland) troubles ?
On Wed, 27 Jan 1999, Brian Somers wrote: > To find out if this is the problem, can you try connecting > interactively. You should see the same delay. You can then try > again, but during the delay, pressing return a few times at the > prompt should wake ppp up. Is this happening ? Well, I tried and didn't find any relationship between pressing return and triggering the wakeup. This is someway hard to find, since ppp wakes up automagically a few couple of seconds after the connection has been established. However: I noticed a real big commit to ppp last night, so I decided to wipe out /usr/src/usr.sbin/ppp + /usr/src/sys completely, recvsup'd, recompiled kernel, ppp and tested again - problems are gone. So there are now 2 possibilities for this problem: a) I was out of sync :( b) Someone fixed ppp -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated.-- From The Gimp manual # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Celeron 333 kernel panic
On Thu, 28 Jan 1999, Mike Zanker wrote: > Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I > attempted to boot into my 3.0-STABLE system. However, as soon as the kernel > starts to boot I get > > panic: cpu class not configured > > and the machine reboots (and so on...) > > Is this cpu supported? As far as I know, yes. Check your kernel config and include cpu "I686_CPU" (valid for Pentium Pro, P2 and probably celerons). You could comment out the other cpu options, but this isn't 100% necessary. They don't do any harm, but they *might* have an impact on performance and probably bloat the kernel a bit. (the GENERIC kernel always includes all cpu types, that's why it is called "GENERIC", i think :) -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated.-- From The Gimp manual # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
First year of FreeBSD...
[NOTE: this article has nothing technical, but since I assume most of the developers are reading here, I'am posting this here.] Tomorrow, I will "celebrate" my 1-year anniversary with FreeBSD. When I started with fbsd, I wasn't exactly an Unix newbie. In fact, I have been using Linux and other Unices on non-x86 platforms for years before. I started with a stable -RELEASE (like every newbie should) and since this day, I have installed about 20 boxes (sure, not very much) with fbsd. About half a year ago, I started to follow -current on my home box. Some of them were running linux before, some of them are completely fresh systems. Most of those boxes are acting as typical Intra/Internet servers, performing www, ftp, mail, news, smb and various other services. None of those boxes *ever* crashed or had to be taken down due to an OS fault. None of them ever lost a single bit of data, because of an OS failure. Nuff said, imho... The reason for posting this here, is that I just want to say "thank you" to all the people involved in this wonderful project. They really deserve it and I can imagine that it is not always easy to be involved in such a big project. Beeing a software engineer (or developer) is not always an easy job (I have been involved in software development for years, just on another "level"). In my opinion, FreeBSD gets way to few attention, but - who knows - perhaps this is a better situation than beeing hyped all the time. -- # /AS/ http://privat.schlund.de/entropy/ # # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. -unknown # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: How many people use VI? This is unbelievable..
John Birrell writes: > FWIW, this message is being edited with vi on a 2.2.8-STABLE machine > rlogged in from a dxterm running on an OSF/1 box. The keyboard is one > of DEC's LK401 things with the funny "Do" keys etc from back when VAX > was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD > environment, dxterm configured with the "Numeric Keypad" option checked > and vt100 emulation, so keypad keys are 0.123456789, just like you'd > expect. It's not vi that's the problem, just your termcap setting doesn't > match the keyboard. But why is it only vi ? I see the same behaviour here (-current, Eterm, TERM=xterm). The numeric keypad works for XEmacs forced to use term instead of X, pico, mcedit (midnight commanders builtin editor), shell - everywhere else, but not for vi. -- # /AS/ http://privat.schlund.de/entropy/ # # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. -unknown # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Netscape, again
Chris Tubutis writes: > > whenever I click a mailto: HREF it inadvertly dumps core. > > > Does it truly dump core, or does it merely go away? Can't speak for the original poster, but my Netscrap 4.5 shows the same behaviour: [16]a...@darkstar:/alex #>/usr/local/netscape/netscape [now clicking on a mailto:] zsh: bus error /usr/local/netscape/netscape [17]a...@darkstar:/alex #>lsl *.core -rw--- 1 alex staff 5697536 Feb 16 02:52 netscape.core Launching the messgenger before using any mailto: links does in fact help. P.S. -current, everything ELF (except netscape of course). Not that I think that matters... -- # /AS/ http://privat.schlund.de/entropy/ # To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Mike Smith writes: > > > I usually keep -O to just '-O' - I had been upping it recently, but then > > > it > > > started breaking even some of my simple programs, so leasson learn't, it's > > > staying at just '-O' from now on in... (safety first? :-) > > > > -O2 works fine too. -O3 does not. We'll probably see the newer version > > of compiler before this is fixed. > > No, -O2 does not work fine; we've seen reports of it breaking things > before. Maybe that's an explantation for the strange things I have seen with gnome a while ago ? I frequently got floating point exceptions in libgtk, (especially when running the pager applet), but I wasn't able to find anything. Recompiling everthing with pgcc did solve this for me. -- # /AS/# To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gcc
Monday, March 01, 1999, 6:20:06 PM, you wrote: >> Just make libg++ a port. :-) > Yes, or abandon it entirely. We surely don't need it in our base > system. Even for ports, I'd be surprised to find anything useful that > still relied on libg++. Any software that still uses libg++ is almost > certainly unmaintained, and uncompilable with modern C++ compilers. > (I.e., it does not conform to the C++ standard.) Libg++ is _ancient_. > It pre-dated templates even. Netscape still uses libg++ /usr/local/netscape/netscape: [...] -lg++.4 => /usr/lib/aout/libg++.so.4.0 (0x10c5c000) -lm.2 => /usr/lib/aout/libm.so.2.0 (0x10c98000) -lstdc++.2 => /usr/lib/aout/libstdc++.so.2.0 (0x10cb2000) -lc.3 => /usr/lib/aout/libc.so.3.1 (0x10ce8000) And most will imho agree on the fact, that Netscape is in some ways useful :) -- # /AS/ a...@psa.at / PGP key available on request and from keys.pgp.com # # If jesus was never born, we would not have a Y2K problem.# To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: gcc
Dienstag, Dienstag, 02. März 1999, you wrote: DOB> Netscape uses a *A.OUT* libg++. We are an *ELF* system now. If you want DOB> to run Netscape (also a piece of a.out code) you would install the DOB> compat22 distribution bits. Then I probably misinterpreted the term "abandon it entirely". DOB> What we are talking about here has nothing to do with Netscape. Maybe. But what if Netscape decides to make the next fbsd release ELF (and still keeps linking with libg++) ? What about Mozilla ? Is it libg++ - free ? I agree that libg++ is (almost) useless today, but dropping it from the source and making it a port shouldn't disturb anyone. -- Alexander To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
