From owner-freebsd-hackers Sun Nov 21 6:23:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 841BD14EFC; Sun, 21 Nov 1999 06:23:31 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by hub.freebsd.org (8.9.3/8.9.3) with ESMTP id JAA33310; Sun, 21 Nov 1999 09:23:22 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sun, 21 Nov 1999 09:23:21 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: hackers@FreeBSD.org Cc: jdp@FreeBSD.org Subject: very strange undefined symbols Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an exceedingly strange problem. Every once in a while, I try running CVSup and get an undefined symbol; I try again, and then it works fine... This also happened today with Mozilla. Here's exactly what happened: {"/home/green"}$ mozilla MOZILLA_FIVE_HOME=/home/green/mozilla/dist/bin LD_LIBRARY_PATH=/home/green/mozilla/dist/bin MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= nNCL: registering deferred (0) /usr/libexec/ld-elf.so.1: /usr/local/lib/libgdk-1.2.so.5: Undefined symbol "XInternAtom" {"/home/green"}$ mozilla MOZILLA_FIVE_HOME=/home/green/mozilla/dist/bin LD_LIBRARY_PATH=/home/green/mozilla/dist/bin MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= nNCL: registering deferred (0) nsCollationUnix::Initialize mLocale = C Setting content window .... As you can see, the second time it worked. CVSup also seems to do this on the same symmbol every time it happens, so when that occurs I'll make sure to report it. Thanks John, and anyone else who may have an idea what's going on. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 6:43:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 84C6114D3D for ; Sun, 21 Nov 1999 06:43:37 -0800 (PST) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga@puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.9.3/8.9.3) with ESMTP id FAA17181 for ; Sun, 21 Nov 1999 05:10:49 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <38380476.7C43AEBA@mauibuilt.com> Date: Sun, 21 Nov 1999 04:40:54 -1000 From: Richard Puga X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: whats up with vinum? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am fooling around with vinum which I have set up in a raid 5 configuration under FreeBSD 3.3-RELEASE. The trouble is that my machine keeps locking up under heavy use. If I try and "make world" it dies about 15-60 seconds into it whit a page fault as well as trying to ftp over large files and somtimems while trying to build kernels. After several page faults and fsck's on reboot I will loose an entire drvie. It is marked as "stale"m by vinum and more than once has lost its disklabel. I am now using ccd level 0 but would like to use vinum raid 5 if possable. Any help or feed back would be greatly apreciated. Thanks in advance Richard Puga puga@mauibuilt.com Below is the latest vinum config I have tried. PS; anyone thinking of playing with vinum I suggest you dont start out with 4 18 gig drives ..:) # Vinum configuration of , saved at Sat Nov 20 02:56:06 1999 drive d1 device /dev/da0e drive d2 device /dev/da1e drive d3 device /dev/da2e drive d4 device /dev/da3e volume puga plex name puga.p0 org raid5 1024s vol puga sd name puga.p0.s0 drive d1 plex puga.p0 len 35565568s driveoffset 265s plexoffset 0s sd name puga.p0.s1 drive d2 plex puga.p0 len 35565568s driveoffset 265s plexoffset 1024s sd name puga.p0.s2 drive d3 plex puga.p0 len 35565568s driveoffset 265s plexoffset 2048s sd name puga.p0.s3 drive d4 plex puga.p0 len 35565568s driveoffset 265s plexoffset 3072s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 8:41: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5482A14DF7; Sun, 21 Nov 1999 08:40:51 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA66122; Sun, 21 Nov 1999 17:40:47 +0100 (CET) (envelope-from des) To: Julian Elischer Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: HEADS UP -stable References: From: Dag-Erling Smorgrav Date: 21 Nov 1999 17:40:47 +0100 In-Reply-To: Julian Elischer's message of "Thu, 18 Nov 1999 16:48:41 -0800 (PST)" Message-ID: Lines: 10 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > You should do a 'config' again before making a kernel from -stable > sources. *Always* re-run config(8) before building a kernel from updated sources. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 8:49:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 7DA0614F20 for ; Sun, 21 Nov 1999 08:49:23 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id RAA04592; Sun, 21 Nov 1999 17:49:26 +0100 (CET) (envelope-from assar) To: Wes Peters Cc: Garance A Drosihn , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <5l1z9kn25i.fsf@foo.sics.se> <3837692E.3EDEFBF1@softweyr.com> From: Assar Westerlund Date: 21 Nov 1999 17:49:25 +0100 In-Reply-To: Wes Peters's message of "Sat, 20 Nov 1999 20:38:22 -0700" Message-ID: <5lbt8nkcx6.fsf@foo.sics.se> Lines: 14 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Assar Westerlund wrote: > > Why can't a file system have more than 2^32 files? > > Because if it does you can't stat it! There's a great case of circular > reasoning for you. ;^) The other reasoning goes like this: va_fileid should be unique which means it needs to be large enough to make unique IDs for current filesystems, which requires it to be longer than `long long' and it's required to be an integral type, which means we should add `long'^n to GCC. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 8:51:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 436E814DF7 for ; Sun, 21 Nov 1999 08:51:16 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id RAA04598; Sun, 21 Nov 1999 17:51:21 +0100 (CET) (envelope-from assar) To: Wes Peters Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <3836FF7C.2D8236AE@newsguy.com> <38376544.96B017E9@softweyr.com> <5ln1s88o4y.fsf@foo.sics.se> <38378ACF.277A81DC@softweyr.com> From: Assar Westerlund Date: 21 Nov 1999 17:51:21 +0100 In-Reply-To: Wes Peters's message of "Sat, 20 Nov 1999 23:01:51 -0700" Message-ID: <5l7ljbkcty.fsf@foo.sics.se> Lines: 15 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Are hash collisions handled reasonably? No, they're not handled at all. :-) Doing that would require: 1. remembering all the nodes that we have seen and the hash values given to them 2. having some backup-hash to use for the node that collides and then re-hash it (and remember that). The code is basically: vap->va_fileid = hash(fid); /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 12:26:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 25F44151F5 for ; Sun, 21 Nov 1999 12:26:26 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port21.netsvr1.cst.vastnet.net [207.252.73.21]) by etinc.com (8.9.3/8.9.3) with SMTP id PAA27858; Sun, 21 Nov 1999 15:26:24 -0500 (EST) Message-Id: <199911212026.PAA27858@etinc.com> X-Sender: dennis@mail.etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 22 Nov 1999 03:46:50 -0500 To: Mike Smith From: Dennis Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Cc: hackers@freebsd.org In-Reply-To: <199911210515.VAA02741@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:15 PM 11/20/99 -0800, Mike Smith wrote: >> I'll test this in 3.3 shortly...has anything been done in this area? It >> seems to happen on passive backplace systems (although its more likely the >> chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This >> problem has been duplicated on more than 1 system with completely different >> hardware. >> >> Any ideas? > >Nope. You haven't given anything like enough information to even guess >at the nature of the problem. And what additional info, short of putting a scope on the bus, may I provide you? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 12:31: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles519.castles.com [208.214.165.83]) by hub.freebsd.org (Postfix) with ESMTP id CE9C114D0C for ; Sun, 21 Nov 1999 12:30:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA03537; Sun, 21 Nov 1999 12:21:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911212021.MAA03537@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Cc: Mike Smith , hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Mon, 22 Nov 1999 03:46:50 EST." <199911212026.PAA27858@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 12:21:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 09:15 PM 11/20/99 -0800, Mike Smith wrote: > >> I'll test this in 3.3 shortly...has anything been done in this area? It > >> seems to happen on passive backplace systems (although its more likely the > >> chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This > >> problem has been duplicated on more than 1 system with completely different > >> hardware. > >> > >> Any ideas? > > > >Nope. You haven't given anything like enough information to even guess > >at the nature of the problem. > > And what additional info, short of putting a scope on the bus, may I > provide you? Anything that might help locating the nature of the "lockup". A scope on the bus would be helpful, sure. Some idea where in the kernel the CPU was executing would be good. The values of cpl and ipending are always informative. Basically though, you're saying "I have a problem with an old version of freebsd on some sorts of hardware. Is it fixed?". There's no possible way for anyone else to answer such a totally vague question. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 14:29:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 293D715253 for ; Sun, 21 Nov 1999 14:28:59 -0800 (PST) (envelope-from partha@cs.duke.edu) Received: from moe.cs.duke.edu (moe.cs.duke.edu [152.3.140.74]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA29084; Sun, 21 Nov 1999 17:28:58 -0500 (EST) Received: from localhost (partha@localhost) by moe.cs.duke.edu (8.8.5/8.6.9) with ESMTP id RAA12097; Sun, 21 Nov 1999 17:27:48 -0500 (EST) X-Authentication-Warning: moe.cs.duke.edu: partha owned process doing -bs Date: Sun, 21 Nov 1999 17:27:48 -0500 (EST) From: "Parthasarathy M. Aji" To: Julian Elischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ip _ fw.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Julian. But we are rewriting Kernel src file ip_fw.c (which does implement the ipfw system call i guess) to do the redirection automatically for us, because redirection is faster at the Kernel than at the user level. Unfortunately I am new to writing code at the kernel level. The main problem is that I don't know what files specifically I need to rewrite, is it just ip_fw.c or any ohter files.. I don't know wether just rewriting the packet ip_dst.s_addr is enough? This is similar to network address translater except for the fact that our kernel will run on a proxy closer to the client than to the server.. Partha On Tue, 16 Nov 1999, Julian Elischer wrote: > You can use the ipfw "fwd" command > (man 8 ipfw) > you need to also run ipfw 'fwd' commands on the servers otherwise they > will send the packet back to it's original destination. > > alternatively you could have no real machine with that address but set a > loopback interface to the target address on each machine so that > each machine would accept the packet when it arrived. > if you want to actually CHANGE the packet then I believe natd can do that > but I've not done it. > julian > > (p.s. tell more about your set-up and maybe I can be more specific) > > > On Wed, 17 Nov 1999, Parthasarathy M. Aji wrote: > > > Hey, > > i want to do packet filtering and redirection through the > > kernel. Specifically, My application will be on an intermediate node, > > through which, I want to redirect every packet that comes through me to a > > different server. Would you know what files I might want to look into > > this( like ip_fw.c for eg) etc..? .. > > > > Partha > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 17: 8:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from casper.spirit.net.au (cas240.act.spirit.net.au [203.63.240.3]) by hub.freebsd.org (Postfix) with ESMTP id E833214E3F for ; Sun, 21 Nov 1999 17:08:40 -0800 (PST) (envelope-from bryan@casper.spirit.net.au) Received: (from bryan@localhost) by casper.spirit.net.au (8.9.3/8.8.5) id MAA60984 for freebsd-hackers@freebsd.org; Mon, 22 Nov 1999 12:08:38 +1100 (EST) From: Bryan Collins Message-Id: <199911220108.MAA60984@casper.spirit.net.au> Subject: Softpower To: freebsd-hackers@freebsd.org Date: Mon, 22 Nov 1999 12:08:38 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I've got myself an ATX motherboard and Powersupply, and I want to get this softpower stuff going. The manual says 'to enable soft shutdown, select shutdown from the start menu' well thats kinda usefull. Anyway, I issue commans such as 'halt' and 'shutdown -h' but I still get a message saying its safe to turn off the power. Ideally I'd like thismachine to shutdown and turn off the power itself. I'm not 100% sure if this motherboard supports it, it claims it does. Its a Pcchips M747 Any ideas? running 3.3-rc and 3.3R Thanks Bry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 17:14: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 7192214EF1 for ; Sun, 21 Nov 1999 17:13:55 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA28801; Mon, 22 Nov 1999 11:43:46 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911220108.MAA60984@casper.spirit.net.au> Date: Mon, 22 Nov 1999 11:43:45 +1030 (CST) From: "Daniel O'Connor" To: Bryan Collins Subject: RE: Softpower Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Nov-99 Bryan Collins wrote: > Anyway, I issue commans such as 'halt' and 'shutdown -h' > but I still get a message saying its safe to turn off the power. You need apm turned on, and then do shutdown -p now. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 17:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 88F7114F53 for ; Sun, 21 Nov 1999 17:26:52 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port51.netsvr1.cst.vastnet.net [207.252.73.51]) by etinc.com (8.9.3/8.9.3) with SMTP id UAA28430; Sun, 21 Nov 1999 20:27:00 -0500 (EST) Message-Id: <199911220127.UAA28430@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 22 Nov 1999 08:47:28 -0500 To: Mike Smith From: Dennis Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Cc: hackers@freebsd.org In-Reply-To: <199911212021.MAA03537@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:21 PM 11/21/99 -0800, you wrote: >> At 09:15 PM 11/20/99 -0800, Mike Smith wrote: >> >> I'll test this in 3.3 shortly...has anything been done in this area? It >> >> seems to happen on passive backplace systems (although its more likely the >> >> chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This >> >> problem has been duplicated on more than 1 system with completely different >> >> hardware. >> >> >> >> Any ideas? >> > >> >Nope. You haven't given anything like enough information to even guess >> >at the nature of the problem. >> >> And what additional info, short of putting a scope on the bus, may I >> provide you? > >Anything that might help locating the nature of the "lockup". A scope >on the bus would be helpful, sure. Some idea where in the kernel the >CPU was executing would be good. The values of cpl and ipending are >always informative. > >Basically though, you're saying "I have a problem with an old version of >freebsd on some sorts of hardware. Is it fixed?". There's no possible >way for anyone else to answer such a totally vague question. Its a late 3.2-STABLE. so its not that old. Surely someone knows if something in this area was fixed or not? Since its a DMA lockup, how would you suggest that the informatoin about what instruction was executing be obtained? The nightmare of instability of 3.x continues whilst the braintrust flogs away at 4.x. Its really a damn shame. And why is 3.x so much slower than 2.2.8? Will 4.0 be slower yet? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 17:50:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 13A5914EFA for ; Sun, 21 Nov 1999 17:50:45 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA32364; Sun, 21 Nov 1999 20:50:38 -0500 (EST) Date: Sun, 21 Nov 1999 20:50:38 -0500 (EST) From: Bosko Milekic To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: <199911220127.UAA28430@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Dennis wrote: !>Its a late 3.2-STABLE. so its not that old. Surely someone knows if !>something in this area was fixed or not? !> !>Since its a DMA lockup, how would you suggest that the informatoin about !>what instruction was executing be obtained? !> !>The nightmare of instability of 3.x continues whilst the braintrust flogs !>away at 4.x. Its really a damn shame. And why is 3.x so much slower than !>2.2.8? Will 4.0 be slower yet? !> !>DB !> Can you quantify how "slower" the 3.x code is? What's "slower" about it? A lot of people are willing to help, but providing no concrete information offers little possibility. In the mean time, did you happen to get a chance to reproduce the problem in 3.3-STABLE ? It appears from your description of the problem that's it somewhat tougher to debug, and knowing whether 3.3 remedies the problem can be of some help. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 18: 5:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7429614CEE for ; Sun, 21 Nov 1999 18:05:27 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA75113; Sun, 21 Nov 1999 18:05:24 -0800 (PST) Date: Sun, 21 Nov 1999 18:05:24 -0800 (PST) From: Julian Elischer To: "Parthasarathy M. Aji" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ip _ fw.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Parthasarathy M. Aji wrote: > Thanks Julian. But we are rewriting Kernel src file ip_fw.c (which > does implement the ipfw system call i guess) to do the redirection > automatically for us, because redirection is faster at the Kernel than at > the user level. > Unfortunately I am new to writing code at the kernel level. The main > problem is that I don't know what files specifically I need to rewrite, is > it just ip_fw.c or any ohter files.. I don't know wether just rewriting > the packet ip_dst.s_addr is enough? This is similar to network address > translater except for the fact that our kernel will run on a proxy closer > to the client than to the server.. > There is a NAT module for the ipfilter kernel package. this may do what you want (I've never used it) You need to specify a little more exactly what you wnat to do. There are many ways to do thise things already. what would the proposeed ipfw rule look like? With Netgraph you can now divert to an arbitrary processing node within the kernel without needing a daemon. That may also be of interest to you. (man 8 ng_ksocket) Julian > Partha > > > > > > On Tue, 16 Nov 1999, Julian Elischer wrote: > > > You can use the ipfw "fwd" command > > (man 8 ipfw) > > you need to also run ipfw 'fwd' commands on the servers otherwise they > > will send the packet back to it's original destination. > > > > alternatively you could have no real machine with that address but set a > > loopback interface to the target address on each machine so that > > each machine would accept the packet when it arrived. > > if you want to actually CHANGE the packet then I believe natd can do that > > but I've not done it. > > julian > > > > (p.s. tell more about your set-up and maybe I can be more specific) > > > > > > On Wed, 17 Nov 1999, Parthasarathy M. Aji wrote: > > > > > Hey, > > > i want to do packet filtering and redirection through the > > > kernel. Specifically, My application will be on an intermediate node, > > > through which, I want to redirect every packet that comes through me to a > > > different server. Would you know what files I might want to look into > > > this( like ip_fw.c for eg) etc..? .. > > > > > > Partha > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 18:13: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id B4F2714F03 for ; Sun, 21 Nov 1999 18:13:03 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id SAA01233 for ; Sun, 21 Nov 1999 18:13:04 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) Date: Sun, 21 Nov 1999 18:13:11 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Bosko Milekic > Sent: Sunday, November 21, 1999 5:51 PM > To: Dennis > Cc: hackers@FreeBSD.ORG > Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) > > > > On Mon, 22 Nov 1999, Dennis wrote: > > !>Its a late 3.2-STABLE. so its not that old. Surely someone knows if > !>something in this area was fixed or not? > !> > !>Since its a DMA lockup, how would you suggest that the informatoin about > !>what instruction was executing be obtained? > !> > !>The nightmare of instability of 3.x continues whilst the > braintrust flogs > !>away at 4.x. Its really a damn shame. And why is 3.x so much > slower than > !>2.2.8? Will 4.0 be slower yet? > !> > !>DB > !> > Dennis, Let's not forget that -STABLE is 3.3 now, not 3.2. If you want updates and patches you have to make world once in a while. It's only common sense to see if 3.3 fixes your problem before going off on developers who may have fixed YOUR problem long ago but you haven't incorporated those changes. As for 4.0, it's going to be -RELEASE someday too, so don't you think it should be developed? It isn't as if they're not working on -STABLE too. Lastly, as for slower? I've ran FreeBSD for years and now I run a combo of -STABLE and -CURRENT and you know what? It's all good! My hardware is the bottle neck and its just as fast as 2.x was. Welcome to the 21st Century, FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" > Can you quantify how "slower" the 3.x code is? What's "slower" about > it? A lot of people are willing to help, but providing no concrete > information offers little possibility. > > In the mean time, did you happen to get a chance to reproduce the > problem in 3.3-STABLE ? It appears from your description of the problem > that's it somewhat tougher to debug, and knowing whether 3.3 remedies the > problem can be of some help. > > > -- > Bosko Milekic > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 18:26:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201]) by hub.freebsd.org (Postfix) with ESMTP id 79FB014F9B for ; Sun, 21 Nov 1999 18:26:16 -0800 (PST) (envelope-from stein@eecs.harvard.edu) Received: from localhost (stein@localhost) by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id VAA05993; Sun, 21 Nov 1999 21:26:13 -0500 (EST) (envelope-from stein@eecs.harvard.edu) X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs Date: Sun, 21 Nov 1999 21:26:13 -0500 (EST) From: Christopher Stein To: FreeBSD Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis has a good point. > for slower? I've ran FreeBSD for years and now I run a combo of -STABLE > and -CURRENT and you know what? It's all good! My hardware is the bottle > neck and its just as fast as 2.x was. Do you have some numbers to back this up? (unfortunately "It's all good!" doesn't mean much to serious systems researchers). What benchmarks have you been running? chris stein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 18:57:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id A268114E62 for ; Sun, 21 Nov 1999 18:57:50 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id SAA01368 for ; Sun, 21 Nov 1999 18:57:50 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Freebsd-Hackers" Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) Date: Sun, 21 Nov 1999 18:57:58 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Christopher Stein > Sent: Sunday, November 21, 1999 6:26 PM > To: FreeBSD > Cc: freebsd-hackers@FreeBSD.ORG > Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) > > > > Dennis has a good point. > > > for slower? I've ran FreeBSD for years and now I run a combo of -STABLE > > and -CURRENT and you know what? It's all good! My hardware is the bottle > > neck and its just as fast as 2.x was. > > Do you have some numbers to back this up? (unfortunately "It's all good!" > doesn't mean much to serious systems researchers). > What benchmarks have you been running? > > chris stein > I just run the benchmark of daily use. No, I'm not concerned with that kind of detail. I've enjoyed ~2 hours of downtime (not including make worlds) this year, mostly due to insufficient UPS runtime and a few power outages. My boxes are up and working all the time (that's why I run FreeBSD) so I don't really care about the actual numbers, as long as my users are happy, all my services are running and I'm secure...I'm happy. I once had a 2.2.2-RELEASE box that had 9+months of uptime and would have gone forever if it wasn't for a little baby girl (who will remain nameless) who crawled in daddies office one day and pushed all the reset buttons. Sorry if this bothers you, but it's all good *for me*. (better?) FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 19:12:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from casper.spirit.net.au (cas240.act.spirit.net.au [203.63.240.3]) by hub.freebsd.org (Postfix) with ESMTP id A575C14D2A for ; Sun, 21 Nov 1999 19:12:17 -0800 (PST) (envelope-from bryan@casper.spirit.net.au) Received: (from bryan@localhost) by casper.spirit.net.au (8.9.3/8.8.5) id OAA67780; Mon, 22 Nov 1999 14:10:51 +1100 (EST) From: Bryan Collins Message-Id: <199911220310.OAA67780@casper.spirit.net.au> Subject: Re: Softpower - working! In-Reply-To: from Kenneth Wayne Culver at "Nov 21, 1999 09:57:52 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Mon, 22 Nov 1999 14:10:50 +1100 (EST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, in this case, you may want to check your BIOS for it's APM options, I > had to change some of my BIOS options to get my computer to shut off > properly but I don't remember which options. > fixed! I changed flags to 0x40 from 0x31 (i.e get lines from BIOS and don't force 1.0/1.1 apm) A 'halt -p' now shutsdown and turns off the pc. Thanks all. Bry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 20:12:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3BFF914D55; Sun, 21 Nov 1999 20:12:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D8191CD75C; Sun, 21 Nov 1999 20:12:52 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 21 Nov 1999 20:12:51 -0800 (PST) From: Kris Kennaway To: Christopher Stein Cc: FreeBSD , freebsd-hackers@FreeBSD.ORG Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Christopher Stein wrote: > Dennis has a good point. Dennis has no point unless he provides some numbers to quantify his claim. Witness: FreeBSD 3.X is the fastest thing I have ever seen: it's so much faster than 2.X, I can only guess what 4.X is going to be like! There, now we're neutral again :-) Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 20:20:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201]) by hub.freebsd.org (Postfix) with ESMTP id 2361915958; Sun, 21 Nov 1999 20:20:08 -0800 (PST) (envelope-from stein@eecs.harvard.edu) Received: from localhost (stein@localhost) by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id XAA06153; Sun, 21 Nov 1999 23:20:05 -0500 (EST) (envelope-from stein@eecs.harvard.edu) X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs Date: Sun, 21 Nov 1999 23:20:05 -0500 (EST) From: Christopher Stein To: Kris Kennaway Cc: FreeBSD , freebsd-hackers@FreeBSD.ORG Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Kris Kennaway wrote: > On Sun, 21 Nov 1999, Christopher Stein wrote: > > > Dennis has a good point. > > Dennis has no point unless he provides some numbers to quantify his > claim. His point was not a claim about performance, rather he was bringing into question whether performance was improving with successive releases. > > Witness: > > FreeBSD 3.X is the fastest thing I have ever seen: it's so much faster > than 2.X, I can only guess what 4.X is going to be like! > > There, now we're neutral again :-) > What do you mean by fastest? What does it do so much faster than 2.x? Fast at what? chris stein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 20:42:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0EB4014E13; Sun, 21 Nov 1999 20:42:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 054321CD74E; Sun, 21 Nov 1999 20:42:42 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 21 Nov 1999 20:42:42 -0800 (PST) From: Kris Kennaway To: Christopher Stein Cc: FreeBSD , freebsd-hackers@FreeBSD.ORG Subject: RE: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Christopher Stein wrote: > > > Dennis has a good point. > > > > Dennis has no point unless he provides some numbers to quantify his > > claim. > > His point was not a claim about performance, rather he was bringing into > question whether performance was improving with successive releases. Sounded very much to me like he was just vaguely griping about how slow and unstable newer versions of FreeBSD are compared to the good old days. Dennis will be able to clarify this for us all when he posts his benchmark specs. > > Witness: > > > > FreeBSD 3.X is the fastest thing I have ever seen: it's so much faster > > than 2.X, I can only guess what 4.X is going to be like! > > > > There, now we're neutral again :-) > > > > What do you mean by fastest? What does it do so much faster > than 2.x? Fast at what? Ah, good, now I see you understand :-) Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 21:38: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 7B4A914C92 for ; Sun, 21 Nov 1999 21:38:01 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA01826; Mon, 22 Nov 1999 00:38:01 -0500 (EST) Date: Mon, 22 Nov 1999 00:38:01 -0500 (EST) From: Daniel Eischen Message-Id: <199911220538.AAA01826@pcnet1.pcnet.com> To: eischen@vigrid.com, freebsd-hackers@FreeBSD.ORG, scott@avantgo.com Subject: Re: EINTR problems with multithreaded programs. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Hess wrote: > I've checked further, and found that FreeBSD correctly handles blocking > signals on a per-thread basis. _But_, all threads still get EINTR when a > signal happens while they're in a blocking read. > > I've attached the updated program that shows the correct delivery of the > signals, with system calls still being interrupted. [Sorry about the > attachment, but that seems the safest way to go about getting the file > delivered in usable fashion.] Thanks for the test program; it makes it much easier on the developers. After consultation with the POSIX spec and John Birrell, it seems that FreeBSD is in error. Along with incorrectly waking up threads blocked on I/O, signals should _not_ be delivered to more than one thread - FreeBSD was delivering them to every thread that had the signal unmasked. I have a fix for this, but will sit on it for another day or so, until I can test it some more. Your test program now works as it should, BTW. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 22: 7: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8A99914C1A; Sun, 21 Nov 1999 22:06:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA69143; Sun, 21 Nov 1999 22:07:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Christopher Stein Cc: Kris Kennaway , FreeBSD , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sun, 21 Nov 1999 23:20:05 EST." Date: Sun, 21 Nov 1999 22:07:01 -0800 Message-ID: <69140.943250821@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > His point was not a claim about performance, rather he was bringing into > question whether performance was improving with successive releases. Bringing something into question without detail is useless. If I seriously questioned your sexual orientation, for example, you'd have every right to ask me just what the hell I was basing such a question on and why I was uncertain about it in the first place. Dennis has no less of an obligation to define his terms and not simply wave his hands. And besides, you need to read his message again - he DID make a claim about performance, he said it was slower than 2.2.x. That by itself, unfortunately, means precisely nothing. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 23:22: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id DF75E14FAC for ; Sun, 21 Nov 1999 23:22:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA06555; Sun, 21 Nov 1999 23:12:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911220712.XAA06555@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Cc: Mike Smith , hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Mon, 22 Nov 1999 08:47:28 EST." <199911220127.UAA28430@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 23:12:29 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> I'll test this in 3.3 shortly...has anything been done in this area? It >>>>> seems to happen on passive backplace systems (although its more likely the >>>>> chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This >>>>> problem has been duplicated on more than 1 system with completely different >>>>> hardware. >>>>> >>>>> Any ideas? >>>> >>>>Nope. You haven't given anything like enough information to even guess >>>>at the nature of the problem. >>> >>> And what additional info, short of putting a scope on the bus, may I >>> provide you? >> >>Anything that might help locating the nature of the "lockup". A scope >>on the bus would be helpful, sure. Some idea where in the kernel the >>CPU was executing would be good. The values of cpl and ipending are >>always informative. >> >>Basically though, you're saying "I have a problem with an old version of >>freebsd on some sorts of hardware. Is it fixed?". There's no possible >>way for anyone else to answer such a totally vague question. > > Its a late 3.2-STABLE. so its not that old. Surely someone knows if > something in this area was fixed or not? Since you haven't actually identified the nature of the problem, how can we know whether any changes might have affected it? > Since its a DMA lockup, how would you suggest that the informatoin about > what instruction was executing be obtained? How do you know it's a DMA lockup? What other information are you hiding from us? Since this seems to be a problem fairly unique to your hardware and your particular configurations, it's beholden upon you to perform your own exploration. > The nightmare of instability of 3.x continues whilst the braintrust flogs > away at 4.x. Its really a damn shame. And why is 3.x so much slower than > 2.2.8? Will 4.0 be slower yet? This is basically all hyperbole; unsubstantiated, irrational and unconstructive. You know, you'd get much better results if you stuck to the facts. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 21 23:29:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id 39A7114FAC; Sun, 21 Nov 1999 23:29:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA06603; Sun, 21 Nov 1999 23:20:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911220720.XAA06603@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sun, 21 Nov 1999 20:42:42 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Nov 1999 23:20:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > His point was not a claim about performance, rather he was bringing into > > question whether performance was improving with successive releases. > > Sounded very much to me like he was just vaguely griping about how slow > and unstable newer versions of FreeBSD are compared to the good old days. > Dennis will be able to clarify this for us all when he posts his benchmark > specs. Dennis has been whining and griping about just about everything since day one. You can't realistically consider that sort of activity on his part as any sort of metric at all. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 5: 7:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 7EDE0158E7 for ; Mon, 22 Nov 1999 05:07:52 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 792387555; Mon, 22 Nov 1999 05:07:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 658541D86 for ; Mon, 22 Nov 1999 05:07:26 -0800 (PST) Date: Mon, 22 Nov 1999 05:07:26 -0800 (PST) From: Jamie Bowden To: hackers@freebsd.org Subject: Cardbus and FXP Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I asked on -mobile, but didn't get an answer, so now I'm asking here. I Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus 82559 based ethercard for this machine. What I want to know is, once cardbus is rolled into 3.x, or when 4.x is fianlly release, will the FXP driver be rolled into the cardbus framework for support of this card? I really don't want to buy the 3c589c just for ether on this box, I prefer the intel cards, and am willing to wait. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 5:40:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 5C7BC1528A for ; Mon, 22 Nov 1999 05:40:16 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id OAA36854; Mon, 22 Nov 1999 14:39:54 +0100 (CET) (envelope-from asmodai) Date: Mon, 22 Nov 1999 14:39:54 +0100 From: Jeroen Ruigrok van der Werven To: Jamie Bowden Cc: hackers@FreeBSD.ORG Subject: Re: Cardbus and FXP Message-ID: <19991122143954.U22782@lucifer.bart.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from ragnar@sysabend.org on Mon, Nov 22, 1999 at 05:07:26AM -0800 Organisation: bART Internet Services B.V. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991122 14:15], Jamie Bowden (ragnar@sysabend.org) wrote: > >I asked on -mobile, but didn't get an answer, so now I'm asking here. I >Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus >82559 based ethercard for this machine. What I want to know is, once >cardbus is rolled into 3.x, or when 4.x is fianlly release, will the FXP >driver be rolled into the cardbus framework for support of this card? > >I really don't want to buy the 3c589c just for ether on this box, I prefer >the intel cards, and am willing to wait. Considering the amount of work Warner(imp) still has to do on the cardbus support I sincerely doubt he will be able to get it done for 4.0. Work IS underway though. And when the support is there, adding drivers into that framework shouldn't be a problem. But that's my idea/opinion and I may be totally off here. Cheers, -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 6:34: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from beotel.yu (zevs.beotel.net [194.106.162.10]) by hub.freebsd.org (Postfix) with ESMTP id 4A4E5152A3 for ; Mon, 22 Nov 1999 06:33:22 -0800 (PST) (envelope-from milosp@emi.yu) Received: from demon.emi.yu (EMI-CACAK-A2-V34.beotel.net [194.106.168.6]) by beotel.yu (8.9.1a/8.8.7) with ESMTP id NAA12095 for ; Mon, 22 Nov 1999 13:30:38 +0100 Received: from milosp (DialUp-008.emi.yu [194.106.172.40]) by demon.emi.yu (8.8.Beta.6/8.8.8) with SMTP id PAA18507 for ; Mon, 22 Nov 1999 15:29:52 GMT Message-ID: <001901bf34f6$20798fe0$cdadfea9@milosp> From: "Milos Puzovic" To: Subject: Kernel building and more Date: Mon, 22 Nov 1999 15:30:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi to all! I am new to FreeBSD. I was on Linux, and with great help of my friend Alex I got on FreeBSD. I have several questions: 1) how can I build my kernel that he can recognize my modem...Kernel show that hi is testing COM3 but he cannot find there...2) my sound card is PnP and kernel found her on PnP devices...how can I use her...how can I test her...3) where I can find some books about Linux kernel...I did some project about detecting memory errors and want to test it on BSD kernel...4) who is doing upgrade of kernel and if there is any chance if I can send some my suggestions...that is all folks for now... Regards, Milos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 6:55:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id D0353152A3 for ; Mon, 22 Nov 1999 06:55:33 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id PAA37428; Mon, 22 Nov 1999 15:54:17 +0100 (CET) (envelope-from asmodai) Date: Mon, 22 Nov 1999 15:54:17 +0100 From: Jeroen Ruigrok van der Werven To: Milos Puzovic Cc: hackers@FreeBSD.ORG Subject: Re: Kernel building and more Message-ID: <19991122155416.A22782@lucifer.bart.nl> References: <001901bf34f6$20798fe0$cdadfea9@milosp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <001901bf34f6$20798fe0$cdadfea9@milosp>; from milosp@emi.yu on Mon, Nov 22, 1999 at 03:30:25PM +0100 Organisation: bART Internet Services B.V. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991122 15:40], Milos Puzovic (milosp@emi.yu) wrote: >Hi to all! I am new to FreeBSD. I was on Linux, and with great help of >my friend Alex I got on FreeBSD. I have several questions: 1) how can I >build my kernel that he can recognize my modem...Kernel show that hi is >testing COM3 but he cannot find there... http://www.freebsd.org/handbook/kernelconfig.html >2) my sound card is PnP and kernel found her on PnP devices...how can I >use her...how can I test her... controller pnp0 device pcm0 >3) where I can find some books about Linux kernel...I did some project >about detecting memory errors and want to test it on BSD kernel... About Linux kernel? No idea. The BSD kernel is detailed in /usr/src/sys and the Design and Implementation of 4.4 BSD. I am also in the LONG prospect of writing this documentation for the FreeBSD project. >4) who is doing upgrade of kernel and if there is any chance if I can >send some my suggestions...that is all folks for now... hackers@freebsd.org is generally one of the lists which occupies itself with kernel ideas. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 7: 9:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id BDC6D14DB3 for ; Mon, 22 Nov 1999 07:09:43 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 7860A1937; Mon, 22 Nov 1999 16:10:21 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 59AC24A1B for ; Mon, 22 Nov 1999 16:10:21 +0100 (CET) Date: Mon, 22 Nov 1999 16:10:21 +0100 (CET) From: Andrzej Bialecki To: freebsd-hackers@freebsd.org Subject: ANNOUNCE: SPY-0.1 - syscalls monitor Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, SPY allows you to monitor and/or selectively block syscalls on your system. It could be used either as a safety monitoring device, policy enforcement, or debugging tool. You can download the sources (NOTE: -current only) from: http://www.freebsd.org/~abial/spy-0.1.tgz Excerpt of README follows: --------------------------------------------------------------------- This kernel module allows you to selectivly monitor and/or disable execution of system calls (syscalls) on your system, and log detailed info to syslog service. It's sometimes desirable to monitor selected syscalls for security reasons, or for debugging. For example, many security holes are related to setuid/setgid programs. You can monitor and log all attempts to use these syscalls. You can also disable certain syscalls altogether, if you really know what you're doing... Already existing tools (like ktrace(1) or truss(1)) can provide much more detailed information, but they are more fit to tracing single processes or process groups, and not setting overall system policy (speaking of which: this module is an example of very primitive auditing and policy enforcing device). Features -------- Using SPY module you can set up your system to: * log detailed info on execution of any selected syscall. In case of a few most important ones, there are specific handlers to log also the arguments of the syscall in understandable format. They are as follows: execve, set*id, chdir, open, link, unlink, chmod, chown, mkdir, rmdir (You are welcome to add others :-) Any syscall can be monitored, but in general case its arguments cannot be interpreted. * set kind of information to be logged. You can restrict logging on a per syscall basis, with the following constraints (OR-ed): - uid or gid - superuser only - all users except superuser - combination of the above You can also adjust level of logging on a per syscall basis. There are three levels available: - basic: logs minimum information sufficient to identify the syscall and process owner - arg: logs also the arguments of the syscall, if possible - full: logs all information available. * disable selected syscalls, which prevents specified categories of users to use them at all, and any such attempt is logged. By default the SPY module logs attempts to use execve syscall by root owned processes, and setuid/setgid by any user owned process. Default mode for other syscalls, used when you add them to monitoring, is to log all uses with all arguments. --------------------------------------------------------------------- Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 7:36:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay05.indigo.ie (relay05.indigo.ie [194.125.133.229]) by hub.freebsd.org (Postfix) with SMTP id DD5F614BD2 for ; Mon, 22 Nov 1999 07:36:55 -0800 (PST) (envelope-from judgea@indigo.ie) Received: (qmail 4044 messnum 1192104 invoked from network[194.125.133.235/relay-mgr.indigo.ie]); 22 Nov 1999 15:34:55 -0000 Received: from relay-mgr.indigo.ie (HELO indigo.ie) (194.125.133.235) by relay05.indigo.ie (qp 4044) with SMTP; 22 Nov 1999 15:34:55 -0000 To: freebsd-hackers@freebsd.org Subject: Re: vmpfw in pine via NFS In-reply-to: Message from "Daniel C. Sobral" dated Thursday at 02:11. From: Alan Judge Date: Mon, 22 Nov 1999 15:34:55 +0000 Message-Id: <19991122153656.DD5F614BD2@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel> /me shivers at the thought of my (easily) 500+ new messages a day Daniel> and hundreds of thousands of messages being stored one file for each Daniel> message... Works OK for us (and a number of even larger ISPs using Maildirs). Though we use NetApps for the file storage and they have a much better system for storing large numbers of files in a directory, so it doesn't get quadratically slower. Largest single FS we have at the moment has about 3.5 million files in it; I don't know what the largest number of files in a single directory is, but I've seen 10s of thousands on occasion without problems. It works much better than a large file per user and NFS file locking, which makes me shiver. -- Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 9:36:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 15FB614C0A for ; Mon, 22 Nov 1999 09:36:13 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id MAA90554; Mon, 22 Nov 1999 12:43:45 -0500 (EST) Date: Mon, 22 Nov 1999 12:43:45 -0500 (EST) From: Ben Rosengart To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: <69140.943250821@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Jordan K. Hubbard wrote: > Bringing something into question without detail is useless. If I > seriously questioned your sexual orientation, for example, you'd have > every right to ask me just what the hell I was basing such a question > on and why I was uncertain about it in the first place. Dennis has no > less of an obligation to define his terms and not simply wave his > hands. > > And besides, you need to read his message again - he DID make a claim > about performance, he said it was slower than 2.2.x. That by itself, > unfortunately, means precisely nothing. In my tests, I've found that FreeBSD is getting faster with successive releases -- I think because the increased weight of the extra disks helps overcome wind resistance. HTH, HAND. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 10:24:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A9F2114D74 for ; Mon, 22 Nov 1999 10:24:26 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA05145; Mon, 22 Nov 1999 11:24:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA07856; Mon, 22 Nov 1999 11:24:21 -0700 (MST) Message-Id: <199911221824.LAA07856@harmony.village.org> To: Jamie Bowden Subject: Re: Cardbus and FXP Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Nov 1999 05:07:26 PST." References: Date: Mon, 22 Nov 1999 11:24:21 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jamie Bowden writes: : : I asked on -mobile, but didn't get an answer, so now I'm asking here. I : Have a Dell Latitude CPiR, and am thinking about getting the Intel cardbus : 82559 based ethercard for this machine. What I want to know is, once : cardbus is rolled into 3.x, or when 4.x is fianlly release, will the FXP : driver be rolled into the cardbus framework for support of this card? : : I really don't want to buy the 3c589c just for ether on this box, I prefer : the intel cards, and am willing to wait. cardbus in 3.x likely isn't going to happen. Cardbus in 4.x is being worked on, or at least the groundwork for it is being worked. fxp is one of the drivers that I have in mind to make work with cardbus. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 10:29:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D4EB614BCC for ; Mon, 22 Nov 1999 10:29:23 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA05165; Mon, 22 Nov 1999 11:27:39 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA07899; Mon, 22 Nov 1999 11:27:40 -0700 (MST) Message-Id: <199911221827.LAA07899@harmony.village.org> To: Ben Rosengart Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Reply-To: chat@FreeBSD.ORG Cc: "Jordan K. Hubbard" , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Nov 1999 12:43:45 EST." References: Date: Mon, 22 Nov 1999 11:27:40 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ben Rosengart writes: : In my tests, I've found that FreeBSD is getting faster with successive : releases -- I think because the increased weight of the extra disks helps : overcome wind resistance. That's just due to the beefier system requirements. of course the disks are going to weigh more. they have more 1's on them than before :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 10:30:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B484015951 for ; Mon, 22 Nov 1999 10:30:13 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id NAA30443; Mon, 22 Nov 1999 13:29:44 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Mon, 22 Nov 1999 13:29:44 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Alan Judge Cc: freebsd-hackers@freebsd.org Subject: Re: vmpfw in pine via NFS In-Reply-To: <19991122153656.DD5F614BD2@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Alan Judge wrote: > Daniel> /me shivers at the thought of my (easily) 500+ new messages a day > Daniel> and hundreds of thousands of messages being stored one file for each > Daniel> message... > > Works OK for us (and a number of even larger ISPs using Maildirs). > Though we use NetApps for the file storage and they have a much better > system for storing large numbers of files in a directory, so it > doesn't get quadratically slower. Largest single FS we have at the > moment has about 3.5 million files in it; I don't know what the > largest number of files in a single directory is, but I've seen 10s of > thousands on occasion without problems. It works much better than a > large file per user and NFS file locking, which makes me shiver. I agree that the one-file-per-message things scales fine--I have a fairly dinky 486 w/24mb of RAM running my cyrus server, and it does just fine with a lot of files for a fair number of messages: Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/wd1s1g 316999 45502 246138 16% 7224 69574 9% /usr/var/spool/imap2 /dev/wd1s1f 496367 163672 292986 36% 27949 94929 23% /usr/var/spool/imap /dev/wd2s1e 19403838 838047 17013484 5% 179066 4513412 4% /usr/var/spool/imap3 In fact, the whole thing scales a *lot* better than a single file per folder, as a lot less time is spent seeking through large mailfiles looking for arbitrarily located string boundaries, scanning through attachments, etc. I'm about to upgrade my cyrus server, but not because of performance problems :-). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12: 1:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id DD7C815334 for ; Mon, 22 Nov 1999 12:01:35 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id PAA19910 for ; Mon, 22 Nov 1999 15:01:17 -0500 (EST) Date: Mon, 22 Nov 1999 13:48:38 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: A file with holes - a bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please take a look at the following piece of code that creates a large hole in a file named hole.dat. It tries to write 0x30-0x39 both at the front and the tail of that file, the hole is therefore in the middle. main() { char c; FILE * fp; fp = fopen("hole.dat", "w"); for (c=0x30; c<0x3a; c++) fputc(c, fp); fputc('\n',fp); fflush(fp); /* XXX */ lseek(fileno(fp), 3 * 8192, SEEK_CUR); for (c=0x30; c<0x3a; c++) fputc(c, fp); fputc('\n',fp); fclose(fp); } If I remove the fflush(fp), then the characters 0x30-0x39 will be all written at the end of the file (use hexdump to find out), not as expected (one at the beginning and the other at the end). It seems to me that the first for loop happens AFTER the lseek() statement without fflush(). Can anyone explain this to me? I am using FreeBSD 3.3-Release. By the way, I also find out if you copy a file with holes into another file, the holes in the first file will be replaced with 0s in the second file, taking more disk space (check with du). Is there a better solution for this? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12: 8:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id C07E114EB3 for ; Mon, 22 Nov 1999 12:08:29 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id NAA233189 for ; Mon, 22 Nov 1999 13:08:27 -0700 (MST) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 22 Nov 1999 13:08:26 -0700 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: A file with holes - a bug? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Zhihui Zhang wrote: > lseek(fileno(fp), 3 * 8192, SEEK_CUR); don't mix things that use file descriptors with stdio. End of problem. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12:18:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id EF58A14BF5 for ; Mon, 22 Nov 1999 12:18:25 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA74002 for ; Mon, 22 Nov 1999 15:15:49 -0500 (EST) Message-Id: <199911222015.PAA74002@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: Ok, that's it, enough is enough! (rpc.lockd) Date: Mon, 22 Nov 1999 15:08:23 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... I have *had* it with the meta, but not really, lockd. Are there any kernel issues with correctly implimenting rpc.lockd? How can I take a filehandle and map it into a filename, with path, so I may open it and lock it on the server? Are there any protocol specs? I downloaded the RFC for version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to the version 3 spec, which I cannot find, and the source is not a whole lot of help on this issue. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12:42:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id CDD2615375 for ; Mon, 22 Nov 1999 12:42:01 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FLM00BD59FC9K@mta3.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 22 Nov 1999 14:40:24 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id OAA84070; Mon, 22 Nov 1999 14:41:16 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 22 Nov 1999 14:41:15 -0600 From: Chris Costello Subject: Re: A file with holes - a bug? In-reply-to: To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991122144115.L78478@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 22, 1999, Zhihui Zhang wrote: > lseek(fileno(fp), 3 * 8192, SEEK_CUR); > If I remove the fflush(fp), then the characters 0x30-0x39 will be all > written at the end of the file (use hexdump to find out), not as expected > (one at the beginning and the other at the end). It seems to me that the > first for loop happens AFTER the lseek() statement without fflush(). Can > anyone explain this to me? I am using FreeBSD 3.3-Release. That line (as quoted) where you use lseek is broken. Use fseek instead. Use only one method to access files. Either stdio or the open/read/write syscalls. -- |Chris Costello |If a group of N persons implements a COBOL compiler, there will be N-1 |passes. Someone in the group has to be the manager. -- T. Cheatham `---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12:48:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CFD5914BF7 for ; Mon, 22 Nov 1999 12:48:57 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA04071; Mon, 22 Nov 1999 13:14:24 -0800 (PST) Date: Mon, 22 Nov 1999 13:14:24 -0800 (PST) From: Alfred Perlstein To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <199911222015.PAA74002@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, David E. Cross wrote: > Ok... I have *had* it with the meta, but not really, lockd. Are there any > kernel issues with correctly implimenting rpc.lockd? How can I take a > filehandle and map it into a filename, with path, so I may open it and lock > it on the server? Are there any protocol specs? I downloaded the RFC for > version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to > the version 3 spec, which I cannot find, and the source is not a whole lot > of help on this issue. here's a url to some of the stuff I have in the works before work utterly consumed me: http://www.freebsd.org/~alfred/misc-patches/ (lockd.diff) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 12:53:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 9ABB514BE0 for ; Mon, 22 Nov 1999 12:53:55 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA01614; Mon, 22 Nov 1999 12:51:18 -0800 (PST) Date: Mon, 22 Nov 1999 12:51:18 -0800 From: Brooks Davis To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A file with holes - a bug? Message-ID: <19991122125118.A24587@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from zzhang@cs.binghamton.edu on Mon, Nov 22, 1999 at 01:48:38PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 22, 1999 at 01:48:38PM -0500, Zhihui Zhang wrote: > > By the way, I also find out if you copy a file with holes into another > file, the holes in the first file will be replaced with 0s in the second > file, taking more disk space (check with du). Is there a better solution > for this? Unfortunately, not one that preserves the holes exactly the way they existed in the original file. See http://reality.sgi.com/zwicky_neu/testdump.doc.html for a good discussion of the problems of copying files with holes via the userland interface to the file system. If all you care about is the space, you could write a version of cp that compressed all zeroed blocks into holes. -- Brooks -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 13: 1:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 44D9015479 for ; Mon, 22 Nov 1999 13:00:52 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id NAA232313; Mon, 22 Nov 1999 13:59:00 -0700 (MST) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 22 Nov 1999 13:59:00 -0700 From: "Ronald G. Minnich" To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <199911222015.PAA74002@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually I wrote a system call for opening a file given a file handle for freebsd a while back (oh, gee, has it really been 5 years ...), as part of mnfs .... i'll try to find it. You don't need to map it to a filename to make it go. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 13: 1:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web2104.mail.yahoo.com (web2104.mail.yahoo.com [128.11.68.248]) by hub.freebsd.org (Postfix) with SMTP id 566B715031 for ; Mon, 22 Nov 1999 13:01:10 -0800 (PST) (envelope-from robertbutler@yahoo.com) Message-ID: <19991122205932.12674.rocketmail@web2104.mail.yahoo.com> Received: from [205.226.11.3] by web2104.mail.yahoo.com; Mon, 22 Nov 1999 12:59:32 PST Date: Mon, 22 Nov 1999 12:59:32 -0800 (PST) From: Robert Butler Subject: Is there any xDSL driver been supported for FreeBSD? To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG or other BSD platforms? Any pointers are excellent. ps. I understand that most of the DSL modems/routers using ethernet or ATM as the interface talking to the host. However, I'm asking about the internal DSL modem that need DSL driver. Robert __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 13:27:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 5B4AC15349 for ; Mon, 22 Nov 1999 13:27:57 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA05259; Mon, 22 Nov 1999 13:54:41 -0800 (PST) Date: Mon, 22 Nov 1999 13:54:41 -0800 (PST) From: Alfred Perlstein To: "Ronald G. Minnich" Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Ronald G. Minnich wrote: > Actually I wrote a system call for opening a file given a file handle for > freebsd a while back (oh, gee, has it really been 5 years ...), as part of > mnfs .... i'll try to find it. You don't need to map it to a filename to > make it go. i forgot to include that in my last email, the syscall is availble in -current for some time now. I brought fhopen, fhstat, and fhstatfs all over from NetBSD several months ago. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 13:38:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 2722014BC8 for ; Mon, 22 Nov 1999 13:38:42 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA76632; Mon, 22 Nov 1999 16:38:33 -0500 (EST) Message-Id: <199911222138.QAA76632@cs.rpi.edu> To: Alfred Perlstein Cc: "Ronald G. Minnich" , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: Message from Alfred Perlstein of "Mon, 22 Nov 1999 13:54:41 PST." Date: Mon, 22 Nov 1999 16:38:33 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does NetBSD have a working rpc.lockd... that would make this much easier. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 13:43:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 47A9E14BC8 for ; Mon, 22 Nov 1999 13:43:25 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA05675; Mon, 22 Nov 1999 14:07:58 -0800 (PST) Date: Mon, 22 Nov 1999 14:07:58 -0800 (PST) From: Alfred Perlstein To: "David E. Cross" Cc: "Ronald G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <199911222138.QAA76632@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, David E. Cross wrote: > Does NetBSD have a working rpc.lockd... that would make this much easier. at a glance at http://cvsweb.netbsd.org/... no. Linux may have one, a temporary GPL'd port would be interesting perhaps. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 14:47: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id DFE1A159CF for ; Mon, 22 Nov 1999 14:46:45 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@a.cs.rpi.edu [128.213.12.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA78903; Mon, 22 Nov 1999 17:46:40 -0500 (EST) Message-Id: <199911222246.RAA78903@cs.rpi.edu> To: Alfred Perlstein Cc: "David E. Cross" , "Ronald G. Minnich" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: Message from Alfred Perlstein of "Mon, 22 Nov 1999 14:07:58 PST." Date: Mon, 22 Nov 1999 17:46:39 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Linux may have one, a temporary GPL'd port would be interesting perhaps. "There is nothing as permanent as a temporary decision." No thanks :) -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 15:29: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9DE4614D87 for ; Mon, 22 Nov 1999 15:28:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA79947 for ; Mon, 22 Nov 1999 18:26:02 -0500 (EST) Message-Id: <199911222326.SAA79947@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: wacky rpc.lockd idea... Date: Mon, 22 Nov 1999 18:18:36 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed about 99% of the panics on our machines are the result of NFS, more often than not it is the result of a backing store file being blown away underneath the client. ie. person editing a file on one machine, compiling and running on a second, then removing the binary on the first machine. If we had a working lock manager could we not have the kernel open a shared lock on anything it had in backing store, would that not assure that files didn't go poof in the night? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 15:45:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9229314DEA for ; Mon, 22 Nov 1999 15:45:40 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by hub.freebsd.org (8.9.3/8.9.3) with ESMTP id SAA39880; Mon, 22 Nov 1999 18:42:32 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Mon, 22 Nov 1999 18:42:32 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.org Subject: Re: A file with holes - a bug? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Zhihui Zhang wrote: > > Please take a look at the following piece of code that creates a large > hole in a file named hole.dat. It tries to write 0x30-0x39 both at the > front and the tail of that file, the hole is therefore in the middle. > > main() > { > char c; > FILE * fp; > > fp = fopen("hole.dat", "w"); > > for (c=0x30; c<0x3a; c++) fputc(c, fp); > fputc('\n',fp); > fflush(fp); /* XXX */ > lseek(fileno(fp), 3 * 8192, SEEK_CUR); This should be fseek() and not lseek(). > for (c=0x30; c<0x3a; c++) fputc(c, fp); > fputc('\n',fp); > fclose(fp); > } > > If I remove the fflush(fp), then the characters 0x30-0x39 will be all > written at the end of the file (use hexdump to find out), not as expected > (one at the beginning and the other at the end). It seems to me that the > first for loop happens AFTER the lseek() statement without fflush(). Can > anyone explain this to me? I am using FreeBSD 3.3-Release. That's because you're not using fseek() like your should be using for FILE * IO. Don't mix FILE *fp and int fd operations callously. > > By the way, I also find out if you copy a file with holes into another > file, the holes in the first file will be replaced with 0s in the second > file, taking more disk space (check with du). Is there a better solution > for this? > > Any help is appreciated. > > -Zhihui > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 15:53:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CF90E14BF6 for ; Mon, 22 Nov 1999 15:53:36 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA09036; Mon, 22 Nov 1999 16:20:34 -0800 (PST) Date: Mon, 22 Nov 1999 16:20:34 -0800 (PST) From: Alfred Perlstein To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wacky rpc.lockd idea... In-Reply-To: <199911222326.SAA79947@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, David E. Cross wrote: > I've noticed about 99% of the panics on our machines are the result of NFS, > more often than not it is the result of a backing store file being blown > away underneath the client. ie. person editing a file on one machine, > compiling and running on a second, then removing the binary on the first > machine. If we had a working lock manager could we not have the kernel open > a shared lock on anything it had in backing store, would that not assure that > files didn't go poof in the night? That's really up to the server lockd/nfsd implementation, but considering that more likely than not the server's lockd will have an open reference to the file until the lock is gone the answer is probably yes. How this would break semantics (auto-locking executables over NFS) is another matter, I would make sure it stays as an option. Another issue is that it's possible that an in kernel implementation of lockd may not follow those semantics so that even if locks are held on the executeable, it may still disapear. It would most certainly be broken behaviour, but I think NFS owns the arena on broken behavour. :) I think that nfs_bio ought to handle the loss of backing store a bit more gracefully, kill -9 wouldn't be unreasonable in such circumstances. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 16: 2:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AB40314C3B; Mon, 22 Nov 1999 16:02:44 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA09189; Mon, 22 Nov 1999 16:26:44 -0800 (PST) Date: Mon, 22 Nov 1999 16:26:44 -0800 (PST) From: Alfred Perlstein To: Brian Fundakowski Feldman Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: A file with holes - a bug? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Zhihui Zhang wrote: > > > > > Please take a look at the following piece of code that creates a large > > hole in a file named hole.dat. It tries to write 0x30-0x39 both at the > > front and the tail of that file, the hole is therefore in the middle. > > > > main() > > { > > char c; > > FILE * fp; > > > > fp = fopen("hole.dat", "w"); > > > > for (c=0x30; c<0x3a; c++) fputc(c, fp); > > fputc('\n',fp); > > fflush(fp); /* XXX */ > > lseek(fileno(fp), 3 * 8192, SEEK_CUR); > > This should be fseek() and not lseek(). > > > for (c=0x30; c<0x3a; c++) fputc(c, fp); > > fputc('\n',fp); > > fclose(fp); > > } > > > > If I remove the fflush(fp), then the characters 0x30-0x39 will be all > > written at the end of the file (use hexdump to find out), not as expected > > (one at the beginning and the other at the end). It seems to me that the > > first for loop happens AFTER the lseek() statement without fflush(). Can > > anyone explain this to me? I am using FreeBSD 3.3-Release. > > That's because you're not using fseek() like your should be using > for FILE * IO. Don't mix FILE *fp and int fd operations callously. Brian is right, a long while back it took me _forever_ to figure out that the reason I was having a ton of trouble (nulls appearing in a file) was that one part of the program was using stdio and creating the file, then it would hand it off to another part which used direct io, however I wasn't fflush()'ing or fclose()'ing the FILE before handing it off. Did I mention that the problem was difficult to reproduce because the dataset would change thereby masking the problem more often than not? *doh* yah, don't mix stdio and direct io. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 16:44:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D53F614CA5 for ; Mon, 22 Nov 1999 16:44:11 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA31108; Mon, 22 Nov 1999 16:42:29 -0800 (PST) Message-ID: <3839E2F5.2781E494@whistle.com> Date: Mon, 22 Nov 1999 16:42:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: David Gilbert Cc: Josef Karthauser , freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. References: <14322.15597.505566.676863@trooper.velocet.ca> <19990929211210.H86792@florence.pavilion.net> <14322.30121.178080.621999@trooper.velocet.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert wrote: > > >>>>> "Josef" == Josef Karthauser writes: > > Josef> As far as I'm aware it _does_ work - in the form of user-ppp > Josef> (/usr/sbin/ppp), maintained by Brian. Why do you need to use > Josef> kernel ppp - it's a mess :) > > In some discussions with some local BSD hackers, many claimed that I > would never get the performance I required out of user-ppp. The basic > requirement is that we handle somewhere between 5k and 10K > connections (on some amount of CPU). Were would I find recent patches > to user-ppp to receive PPPoE streams? Now in 3.3-Stable and -current. We also have patches in the works to allow full kernel bypass of the ppp daemon in the common case, resulting in Mucho performance increase. with the version we have now, a 100KB/sec ppp session took 6% of a P6-200 (the other end was a 486DX50 :-) with enough RAM we could probably serve 10K sessions, though that would require 10K ppp daemons until we got the kernel bypass working. in either case it would presently leave a HUGE ifconfig -a output as there would be 10000 intefeaces, each representing a channel to a client. It migh tbe worth wondering if we need to abstract a 'class of PVCs' type device that feeds to some othe rway of splitting them. (we can do this with netgraph pretty easily.) (is it worth doing?) Julian > > Dave. > > -- > ============================================================================ > |David Gilbert, Velocet Communications. | Two things can only be | > |Mail: dgilbert@velocet.net | equal if and only if they | > |http://www.velocet.net/~dgilbert | are precisely opposite. | > =========================================================GLO================ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / On assignment | / \ julian@Whistle.com +------>x USA \ in a strange | ( OZ ) 110 Marsh dr. Foster City, CA \___ ___ | country ! +- X_.---._/ USA+(650) 577-7063 (wk) \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 17:43:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Michelle.esfm.ipn.mx (Michelle.esfm.ipn.mx [148.204.104.23]) by hub.freebsd.org (Postfix) with ESMTP id 1C12B14A07; Mon, 22 Nov 1999 17:43:22 -0800 (PST) (envelope-from mrspock@esfm.ipn.mx) Received: from localhost (mrspock@localhost) by Michelle.esfm.ipn.mx (8.9.3/8.9.1) with ESMTP id TAA30194; Mon, 22 Nov 1999 19:43:53 -0600 (CST) (envelope-from mrspock@esfm.ipn.mx) X-Authentication-Warning: Michelle.esfm.ipn.mx: mrspock owned process doing -bs Date: Mon, 22 Nov 1999 19:43:53 -0600 (CST) From: Eduardo Viruena Silva To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG O! wise FreeBSD gurus! I ask for your advice... I have a FreeBSD 3.3 system in a Pentium computer and an old 486 computer that I want to make a diskless system. I found that in directory: /usr/src/sys/i386/boot/netboot there is a way of building "nb3c509.com" program. This program is used to emulate the "boot" chip for my 3c509 card. It seems to work fine. It can get the "freebsd.xxx.xxx.xxx.xxx" file containing the parameters to download the kernel image. It works ok and tries to download the image. Nevertheless it halts displaying a message saying: kernel: Bad executable format! (or something like that). FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. According to my believes, it seems that there is a function (or macro) called "N_BADMAG" that tests the kernel file type, but I could not find it in the source files. Trying to overcome this problem, I forced the test, but "elf" image did not work. Is there a way of building "nb3c509.com" accepting ELF format ? == ===== = === == ======== ============= ========= === ====== = Do I have to create an AOUT kernel image? will it work? it seems to works... Now, can you tell me which "/etc/rc.*" configuration scripts are executed in the booting process? what file systems do they try to mount? what is a "mfs" ? (memory file system? a virtual disk?) My computer gets frozen because of some kind of problem while booting. it seems to be mounting several file systems in a "mfs" while it starts. Documentation about diskless installation is *very* old. Can you HEEEELLLLPPPP me? Thank you in advance. - ______ _ * / /###\ / \ __ /\ /\ * / ./#### \ * \__|_/ | | / \/ \ | b#####| * _ | __ | | __ = .. \____ \ \_\#####/ / \| / \ | | /\_\/ = \_| * \___\###/ * \_/\_/\__/\__\/_/\__/ = \______/ _ | | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 17:47:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 6B3E914A07; Mon, 22 Nov 1999 17:47:16 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA32216; Tue, 23 Nov 1999 12:15:46 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911230145.MAA32216@gizmo.internode.com.au> Subject: Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ? To: mrspock@esfm.ipn.mx (Eduardo Viruena Silva) Date: Tue, 23 Nov 1999 12:15:46 +1030 (CST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Eduardo Viruena Silva" at Nov 22, 99 07:43:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eduardo Viruena Silva wrote: > FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. You should be able to build an a.out kernel by putting makeoptions KERNFORMAT=aout into your kernel config file. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 18:24:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id 0EC9014ED0 for ; Mon, 22 Nov 1999 18:24:24 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id VAA06557; Mon, 22 Nov 1999 21:24:07 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14393.64199.189042.641286@trooper.velocet.net> Date: Mon, 22 Nov 1999 21:24:07 -0500 (EST) To: Julian Elischer Cc: David Gilbert , Josef Karthauser , freebsd-hackers@FreeBSD.ORG Subject: Re: PPPoE offer. In-Reply-To: <3839E2F5.2781E494@whistle.com> References: <14322.15597.505566.676863@trooper.velocet.ca> <19990929211210.H86792@florence.pavilion.net> <14322.30121.178080.621999@trooper.velocet.ca> <3839E2F5.2781E494@whistle.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Julian" == Julian Elischer writes: Julian> (the other end was a 486DX50 :-) with enough RAM we could Julian> probably serve 10K sessions, though that would require 10K ppp Julian> daemons until we got the kernel bypass working. in either Julian> case it would presently leave a HUGE ifconfig -a output as Julian> there would be 10000 intefeaces, each representing a channel Julian> to a client. It migh tbe worth wondering if we need to Julian> abstract a 'class of PVCs' type device that feeds to some othe Julian> rway of splitting them. (we can do this with netgraph pretty Julian> easily.) (is it worth doing?) I'd be willing to fund that experiment. It's possible we should meet either virtually or in person. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 18:25:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-49.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.177]) by hub.freebsd.org (Postfix) with ESMTP id 2796A14F6D for ; Mon, 22 Nov 1999 18:25:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA03720; Tue, 23 Nov 1999 02:25:03 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA08646; Tue, 23 Nov 1999 02:29:10 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911230229.CAA08646@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Julian Elischer Cc: David Gilbert , Josef Karthauser , freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPPoE offer. In-Reply-To: Message from Julian Elischer of "Mon, 22 Nov 1999 16:42:29 PST." <3839E2F5.2781E494@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Nov 1999 02:29:10 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > We also have patches in the works to allow full kernel bypass of > the ppp daemon in the common case, resulting in Mucho performance > increase. > > with the version we have now, a 100KB/sec ppp session took 6% of a > P6-200 [.....] CCP will kill performance. Without it however, I've squeezed 1.5Mb per second (AFAIR using ppp/udp on a Mobile PII/366) out of ppp(8). We're still on the right side of the line for regular users, but not by a great deal these days :-/ > Julian -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 18:36:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 3DD3514EF2; Mon, 22 Nov 1999 18:36:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 941C51C6D; Tue, 23 Nov 1999 10:36:06 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Newton Cc: mrspock@esfm.ipn.mx (Eduardo Viruena Silva), freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ? In-Reply-To: Message from Mark Newton of "Tue, 23 Nov 1999 12:15:46 +1030." <199911230145.MAA32216@gizmo.internode.com.au> Date: Tue, 23 Nov 1999 10:36:06 +0800 From: Peter Wemm Message-Id: <19991123023606.941C51C6D@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton wrote: > Eduardo Viruena Silva wrote: > > > FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. > > You should be able to build an a.out kernel by putting > > makeoptions KERNFORMAT=aout > > into your kernel config file. Also, the plan is that it should one day be possible (one day) to use /boot/ loader (which is an a.out image) and have it pull the kernel and modules down via tftp or minimal NFS or something. That of course requires real-mode network card drivers, or Intel's PXE (preboot execution environment) to catch on. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 18:53:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 8E8CB14C88 for ; Mon, 22 Nov 1999 18:53:12 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 7483 invoked by uid 1001); 23 Nov 1999 02:52:20 -0000 Date: Mon, 22 Nov 1999 18:52:20 -0800 From: Jason Evans To: current@freebsd.org, hackers@freebsd.org Subject: Threads and my new job. Message-ID: <19991122185220.D301@sturm.canonware.com> Reply-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Walnut Creek has hired me as a full time employee to work primarily on improving and expanding FreeBSD's threads support. This is very exciting to me, and I hope my work will be of benefit the FreeBSD community. There is a lot of work to be done in order to make FreeBSD's threads support truly excellent, and it will take more than just me working on it. Fortunately, there are a number of other people also interested in improving threads support, and as work progresses, I expect this will very much be a group effort. Some very fruitful long-range architecture discussions have been taking place on the -arch mailing list, and discussion will likely continue there for some time as design decisions are hashed out. If you are interested in participating in the design discussion, please subscribe to -arch (if you haven't already), read the -arch archives for the past couple of weeks to bring yourself up to speed on what has been discussed so far, read some of the more pertinent references listed throughout the discussion, then jump in. The signal-to-noise ratio on -arch is exceptionally high; please do your part in keeping it that way. What am I going to do? My first mandate is to round out the edges of our current libc_r and to bring it closer to standards compliance before 4.0. Specifically, I know that the following work is necessary: *) Address and close approximately 20 PRs. The list of PRs I know about is: i386/7426, bin/7587, misc/8202, bin/8281, kern/8729, misc/9778, misc/9903, misc/10599, bin/10992, kern/11982, kern/11984, bin/13008, misc/13117, kern/13644, misc/14264, i386/14383, kern/14685, and docs/14858. If there are other PRs that I didn't list that are directly related to threads, please let me know about them in private email so that I can keep track of them. *) Signal delivery fixes. I think Daniel Eischen has already taken care of this. *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in PR bin/7587) need to be implemented. *) Make a real libpthread, rather than relying on the -pthread linker magic. This is high on Daniel Eischen's wish list, so maybe he already has something in the works. =) If you know of other outstanding issues that have a prayer of being addressed before 4.0 ships, please speak up. Jason Jason Evans http://www.canonware.com/~jasone Home phone: (650) 856-8204 "I once knew a happy medium. Her name was Zohar." - James Foster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 19: 1: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 60A8314C23; Mon, 22 Nov 1999 19:01:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA01520; Mon, 22 Nov 1999 19:00:45 -0800 (PST) (envelope-from dillon) Date: Mon, 22 Nov 1999 19:00:45 -0800 (PST) From: Matthew Dillon Message-Id: <199911230300.TAA01520@apollo.backplane.com> To: Jason Evans Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Threads and my new job. References: <19991122185220.D301@sturm.canonware.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :*) Make a real libpthread, rather than relying on the -pthread linker : magic. This is high on Daniel Eischen's wish list, so maybe he already : has something in the works. =) : :If you know of other outstanding issues that have a prayer of being :addressed before 4.0 ships, please speak up. : :Jason : :Jason Evans A natively implemented linux-compatible clone() call would be cool (rather then the one in the linux compatibility suite). Or if not that, then clib support for the equivalent of rfork(RFMEM|RFPROC) (currently C code will crash if it calls rfork() with RFMEM due to the new process not getting a new %esp). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 19:12:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id CD78A1593F; Mon, 22 Nov 1999 19:12:18 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-211.bellatlantic.net [151.198.117.211]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id WAA13458; Mon, 22 Nov 1999 22:12:04 -0500 (EST) Message-ID: <383A0760.CCD09C66@bellatlantic.net> Date: Mon, 22 Nov 1999 22:17:52 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Eduardo Viruena Silva Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.3, DISKLESS, kernel format must be AOUT ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eduardo Viruena Silva wrote: > > O! wise FreeBSD gurus! > I ask for your advice... > > I have a FreeBSD 3.3 system in a Pentium computer and an old 486 > computer that I want to make a diskless system. > > I found that in directory: /usr/src/sys/i386/boot/netboot > there is a way of building "nb3c509.com" program. > This program is used to emulate the "boot" chip for my 3c509 card. > It seems to work fine. Cool! It still works! :-) > It can get the "freebsd.xxx.xxx.xxx.xxx" file containing the parameters to > download the kernel image. It works ok and tries to download the > image. Nevertheless it halts displaying a message saying: > > kernel: Bad executable format! > > (or something like that). > > FreeBSD 3.3 uses ELF format and previous versions (2.x.y) use AOUT format. > > According to my believes, it seems that there is a function (or macro) > called "N_BADMAG" that tests the kernel file type, but I could not find it > in the source files. Trying to overcome this problem, I forced the test, > but "elf" image did not work. I guess when the new fancy 3-stage disk boot and ELF format support was introduced the network boot code was not updated and this seems to be the root of the problem. > Is there a way of building "nb3c509.com" accepting ELF format ? > == ===== = === == ======== ============= ========= === ====== = I guess yes but that would need some significant amount of work. > Do I have to create an AOUT kernel image? > > will it work? > it seems to works... > > Now, can you tell me which "/etc/rc.*" configuration scripts are executed > in the booting process? what file systems do they try to mount? The main script is /etc/rc which calls the other scripts. Normally it tries to mount the filesystems listed in /etc/fstab. > what is a "mfs" ? (memory file system? a virtual disk?) Yes, memory filesystem. > My computer gets frozen because of some kind of problem while booting. > it seems to be mounting several file systems in a "mfs" while it > starts. Does it happen during the diskless boot ? A good way of finding out which command is running now is pressing Control+T. And Control+C may be used to interrupt the current command if it seems to hang by unknown reason. I think that to use mfs a large enough amount of swap space must be configured. Otherwise I don't know what would happen when it gets out of memory but certainly nothing good. And if the swap space is configured over NFS then swapping is very slow. > Documentation about diskless installation is *very* old. I guess I was about the last one who touched it around '95. I can't remember any use of mfs in the netboot. I ran it with both root filesystem and swap on NFS and it ran although very slowly. Also I remember that I had very little memory (2MB to 4MB) on the diskless machines and the boot worked VERY slowly even on the 4MB machines until I cut the rc script to the very basics. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 20:14:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 1CB6915076 for ; Mon, 22 Nov 1999 20:14:14 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@a.cs.rpi.edu [128.213.12.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA85404; Mon, 22 Nov 1999 23:14:04 -0500 (EST) Message-Id: <199911230414.XAA85404@cs.rpi.edu> To: Alfred Perlstein Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: wacky rpc.lockd idea... In-Reply-To: Message from Alfred Perlstein of "Mon, 22 Nov 1999 16:20:34 PST." Date: Mon, 22 Nov 1999 23:14:03 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That's really up to the server lockd/nfsd implementation, but considering > that more likely than not the server's lockd will have an open reference > to the file until the lock is gone the answer is probably yes. Hmm... I wold think even without having the file "open" a lock would be enough. Seems kinda pointless of a lock if it doesn't protect something as trivial as an rm ;) > How this would break semantics (auto-locking executables over NFS) is > another matter, I would make sure it stays as an option. As long as you make it a shared lock, read-only, I think those are always guaranteed to suceed, and to never affect other locks. Perhaps I am wrong in this. > Another issue is that it's possible that an in kernel implementation of > lockd may not follow those semantics so that even if locks are held on > the executeable, it may still disapear. It would most certainly be > broken behaviour, but I think NFS owns the arena on broken behavour. :) > > I think that nfs_bio ought to handle the loss of backing store a bit > more gracefully, kill -9 wouldn't be unreasonable in such circumstances. I agree that nfs_bio should be more tolerant of these types of faults. However a process in the middle of a page-in is not killable, and leaving it stuck in disk-wait is also not a viable option IMO. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 20:21: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 1728F14C2F; Mon, 22 Nov 1999 20:20:57 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-366.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FLM007KGUQ1HP@mail.uni-bielefeld.de>; Tue, 23 Nov 1999 05:20:26 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id FAA01326; Tue, 23 Nov 1999 05:20:09 +0100 (CET envelope-from bjoern) Date: Tue, 23 Nov 1999 05:20:09 +0100 From: Bjoern Fischer Subject: stat(2) weirdness To: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Message-id: <19991123051328.A292@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, recently while debugging a problem in wwwoffle-2.5b I realized, that stat(2) behaves at least extremely strange on 3.3-STABLE: This small example... #include #include #include int main(int argc, char *argv[]) { char *fname =3D argv[0]; struct stat sb; int res =3D stat(argv[0], &sb); printf("filename : %s\n" \ "st_size : %d\n" \ "st_blocks : %d\n" \ "st_blksize : %d\n", fname, sb.st_size, sb.st_blocks, sb.st_blksize); return res; } would emerge this when run: filename : ./a.out st_size : 3342 st_blocks : 0 st_blksize : 8 Any idea why st_blocks is always zero? This can't be correct. st_blksize seems to be the number of blocks allocated for filename, although assuming a blocksize of 512 the object would fit into 7 blocks. Maybe that's the result of the underlying FFS's fsize (1024). Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 20:58:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1337514BE2; Mon, 22 Nov 1999 20:58:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C76D71C6D; Tue, 23 Nov 1999 12:57:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Bjoern Fischer Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: stat(2) weirdness In-Reply-To: Message from Bjoern Fischer of "Tue, 23 Nov 1999 05:20:09 +0100." <19991123051328.A292@frolic.no-support.loc> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Tue, 23 Nov 1999 12:57:36 +0800 From: Peter Wemm Message-Id: <19991123045736.C76D71C6D@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bjoern Fischer wrote: > Hello, > > recently while debugging a problem in wwwoffle-2.5b I realized, > that stat(2) behaves at least extremely strange on 3.3-STABLE: > > This small example... > > #include > #include > #include > > int main(int argc, char *argv[]) { > > char *fname = argv[0]; > struct stat sb; > int res = stat(argv[0], &sb); > > printf("filename : %s\n" \ > "st_size : %d\n" \ > "st_blocks : %d\n" \ > "st_blksize : %d\n", > fname, sb.st_size, sb.st_blocks, sb.st_blksize); > > return res; > > } > > would emerge this when run: > > filename : ./a.out > st_size : 3342 > st_blocks : 0 > st_blksize : 8 > > Any idea why st_blocks is always zero? This can't be correct. > st_blksize seems to be the number of blocks allocated for > filename, although assuming a blocksize of 512 the object > would fit into 7 blocks. Maybe that's the result of the > underlying FFS's fsize (1024). > > Björn > > -- > -----BEGIN GEEK CODE BLOCK----- > GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ > K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ > ------END GEEK CODE BLOCK------ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message peter@overcee[12:55pm]/tmp-158> cc -Wall -o stat stat.c stat.c: In function `main': stat.c:15: warning: int format, different type arg (arg 3) stat.c:15: warning: int format, different type arg (arg 4) You are mixing int and 'long long' arg types. If it's fixed, eg: printf("filename : %s\n" \ "st_size : %lld\n" \ "st_blocks : %lld\n" \ "st_blksize : %d\n", fname, sb.st_size, sb.st_blocks, sb.st_blksize); Then: peter@overcee[12:56pm]/tmp-162> cc -Wall -o xx xx.c peter@overcee[12:56pm]/tmp-163> ./xx filename : ./xx st_size : 3522 st_blocks : 7 st_blksize : 4096 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 21: 7:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3194914D12 for ; Mon, 22 Nov 1999 21:07:57 -0800 (PST) (envelope-from partha@cs.duke.edu) Received: from astaire.cs.duke.edu (astaire.cs.duke.edu [152.3.140.39]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id AAA01188; Tue, 23 Nov 1999 00:07:37 -0500 (EST) Received: from localhost (partha@localhost) by astaire.cs.duke.edu (8.8.5/8.6.9) with ESMTP id AAA01667; Tue, 23 Nov 1999 00:07:37 -0500 (EST) X-Authentication-Warning: astaire.cs.duke.edu: partha owned process doing -bs Date: Tue, 23 Nov 1999 00:07:37 -0500 (EST) From: "Parthasarathy M. Aji" To: freebsd-hackers@FreeBSD.ORG Cc: Clinton Xavier Berni Subject: ip checksum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I am trying to recompute the checksum of an IP packet. I use netinet/in_chksum.c to do this. The values returned are not correct. I've reset the ip_sum field to 0 before doing the sum. Is there something missing? thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 21:22:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 1199014BE2 for ; Mon, 22 Nov 1999 21:22:24 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id AAA03921; Tue, 23 Nov 1999 00:22:05 -0500 (EST) Date: Tue, 23 Nov 1999 00:22:05 -0500 (EST) From: Bosko Milekic To: "Parthasarathy M. Aji" Cc: freebsd-hackers@FreeBSD.ORG, Clinton Xavier Berni Subject: Re: ip checksum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Parthasarathy M. Aji wrote: !>Hey, !> !>I am trying to recompute the checksum of an IP packet. I use !>netinet/in_chksum.c to do this. The values returned are not correct. I've !>reset the ip_sum field to 0 before doing the sum. Is there something !>missing? !> !>thanks !> !> Would you be able to provide some code to illustrate the situation? There are several things that may go wrong. What exactly are you trying to do here? (You may be using the wrong procedure) and what are you getting for return values? --Bosko -- Bosko Milekic "I want now to tell you, gentlemen, whether you care to hear it or not, why I could not even become an insect." --F. Dostoyevski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 21:57: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2130414A04 for ; Mon, 22 Nov 1999 21:56:57 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA47647; Mon, 22 Nov 1999 21:56:27 -0800 (PST) Date: Mon, 22 Nov 1999 21:56:27 -0800 (PST) From: Julian Elischer To: "Parthasarathy M. Aji" Cc: freebsd-hackers@FreeBSD.ORG, Clinton Xavier Berni Subject: Re: ip checksum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How many bytes have you changed? is it possible that some of the values have already been ntohs()'d or something similar? rather than recalculate the whole packet, just update the exisitng value. there is an rfc for this but it took me a while to get the code right in C on a 386. The trick is getting the 1s complement arithmetic right. #define FIXSUM16(c, op, np) \ do { \ (c) -= (u_int16_t) ~*((u_int16_t *) (op)); \ if ((c) < 0) { \ (c) += 0xffff; \ } \ (c) -= (u_int16_t) *((u_int16_t *) (np)); \ if ((c) < 0) { \ (c) += 0xffff; \ } \ } while (0) /* * IpsumReplaceShort() * * Replace a 16 bit aligned (relative to the checksum) 16 bit value * in a packet and change the IP/TCP/UDP checksum at the same time. * * Works with both big and little endian machines(!) * * If for some wierd reason you want to replace a nonaligned value, * you need to byteswap it and the old value before doing the * subtractions. */ void IpsumReplaceShort(u_int16_t *cksump, u_int16_t *oldvalp, u_int16_t newval) { register int cksum; cksum = *cksump; FIXSUM16(cksum, oldvalp, &newval); *cksump = cksum; *oldvalp = newval; } On Tue, 23 Nov 1999, Parthasarathy M. Aji wrote: > Hey, > > I am trying to recompute the checksum of an IP packet. I use > netinet/in_chksum.c to do this. The values returned are not correct. I've > reset the ip_sum field to 0 before doing the sum. Is there something > missing? > > thanks > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 22: 2:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id B771614A04 for ; Mon, 22 Nov 1999 22:02:26 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id AAA04318; Tue, 23 Nov 1999 00:01:53 -0600 (CST) From: Joe Greco Message-Id: <199911230601.AAA04318@aurora.sol.net> Subject: Re: Non-standard FFS parameters In-Reply-To: from Andrzej Bialecki at "Oct 8, 1999 10:10: 0 pm" To: abial@webgiro.com (Andrzej Bialecki) Date: Tue, 23 Nov 1999 00:01:53 -0600 (CST) Cc: dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 8 Oct 1999, Matthew Dillon wrote: > > > :> > > :> Adjusting the bytes-per-inode (-i) specification in newfs should not > > :> pose a problem. > > : > > :IOW now you say it's ok to use very high values of -i... ;-) > > : > > :Andrzej Bialecki > > > > No, I didn't say that. My recommended maximum is still 262144. Fsck > > should be reasonably fast with that number and the filesystem should > > still be able to maintain reasonable efficiency. > > Ok, I can live with that, I guess. Thanks a lot for your help! What's the recommended way to reduce the number of cylinder groups a bit? -c's maximum limit is affected by combinations of -b and -i, possibly some others. PHK was talking about new, more sensible values for filesystem parameters, but I don't know what happened. I just think it's a bit silly to go generating hundreds of cg's for a 34GB unit... and this _with_ the max -c setting of 26 (for this fs). /dev/vinum/rn8: 63700992 sectors in 15552 cylinders of 1 tracks, 4096 sectors 31104.0MB in 599 cyl groups (26 c/g, 52.00MB/g, 256 i/g) super-block backups (for fsck -b #) at: 32, 106528, 213024, 319520, 426016, 532512, 639008, 745504, 852000, 958496, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 22 22:42:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A79A14C4F for ; Mon, 22 Nov 1999 22:42:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA02469; Mon, 22 Nov 1999 22:41:29 -0800 (PST) (envelope-from dillon) Date: Mon, 22 Nov 1999 22:41:29 -0800 (PST) From: Matthew Dillon Message-Id: <199911230641.WAA02469@apollo.backplane.com> To: Joe Greco Cc: abial@webgiro.com (Andrzej Bialecki), freebsd-hackers@FreeBSD.ORG Subject: Re: Non-standard FFS parameters References: <199911230601.AAA04318@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What's the recommended way to reduce the number of cylinder groups a bit? :-c's maximum limit is affected by combinations of -b and -i, possibly some :others. PHK was talking about new, more sensible values for filesystem :parameters, but I don't know what happened. I just think it's a bit silly :to go generating hundreds of cg's for a 34GB unit... and this _with_ the :max -c setting of 26 (for this fs). : :/dev/vinum/rn8: 63700992 sectors in 15552 cylinders of 1 tracks, 4096 sectors : 31104.0MB in 599 cyl groups (26 c/g, 52.00MB/g, 256 i/g) :super-block backups (for fsck -b #) at: : 32, 106528, 213024, 319520, 426016, 532512, 639008, 745504, 852000, 958496, : :... Joe : :------------------------------------------------------------------------------- :Joe Greco - Systems Administrator jgreco@ns.sol.net Well, -i doesn't effect c/g any where near as much as -b does. Try bumping the block size up to 16K and use '-c 999' and see what newfs tells you the max c/g is. -b 16384 -f 2048 -c 999. On my test it let me do 89 c/g. As we already know, non-standard block sizes will create problems under stable and may create them under current. I believe I have fixed the bugs under current (in getnewbuf()) but since no comprehensive testing has been done you still have a lockup risk. Work on the VM system mainly by Luoqi a few months ago fixed the buffer corruption bugs, so only lockup bugs should be left. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 0: 0:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 709BB14A2D; Tue, 23 Nov 1999 00:00:01 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id HAA26173 Tue, 23 Nov 1999 07:59:50 GMT Message-ID: <383A442B.E8CCC284@cs.strath.ac.uk> Date: Tue, 23 Nov 1999 07:37:15 +0000 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: multimedia@freebsd.org, hackers@freebsd.org Subject: Help: SoundBlaster PCI 16, 64, 128, 64V, 128V revisions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to list the full range of SoundBlaster PCI models. >From my research I have found the following Creative Labs models. CT4700 SB PCI 128 - (12 months ago) ES1370. 2 line outs for 4 speakers. Retail Box CT???? SB PCI 64V - unknown chip. 64 Value edition. 1 line out. OEM Market. CT4750 SB PCI 128V - unknown chip. 128 Value edition. 1 line out. OEM market. CT4740 SB PCI 16 - ES1373. 2 line outs for 4 speakers. Retail Box. 12 months ago, Creatives UK web site promoted the SB PCI 128 and the SB Live models. Today, they only promote the SB PCI 16 and SB Live models. Can those of you with SoundBlaster PCI cards help me fill out this table Thanks Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://www.telepresence.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 0:43:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 95C7514E93 for ; Tue, 23 Nov 1999 00:43:03 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id CAA15655; Tue, 23 Nov 1999 02:42:59 -0600 (CST) From: Joe Greco Message-Id: <199911230842.CAA15655@aurora.sol.net> Subject: Serial console oddity To: hackers@freebsd.org Date: Tue, 23 Nov 1999 02:42:59 -0600 (CST) Cc: wpaul@skynet.ctr.columbia.edu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, I've been doing serial consoles for a while and every so often, the following pops up. Seems to happen on SMP machines. Don't recall if it happens on non-SMP machines. This has happened for a _very_long_time_ (like since pre-3.0). BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS drive F: is disk4 BIOS drive G: is disk5 BIOS drive H: is disk6 BIOS drive I: is disk7 BIOS drive J: is disk8 FreeBSD/i386 bootstrap loader, Revision 0.7 640/65472kB (jkh@highwing.cdrom.com, Thu Sep 16 22:16:41 GMT 1999) |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08= /=08-=08\=08|=08/=08Loading /boot/defaults/loader.conf=20 -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/kernel = text=3D0x10a418 /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08data=3D0x17= b48+0x1a97c \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08syms=3D[0x4+0x1= ee30\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08+0x4+0x= 206b3\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08] \=08|=08/=08-=08\=08|=08/=08 Hit [Enter] to boot immediately, or any other key for command prompt. Type '?' for a list of commands, 'help' for more detailed help. boot: spool0-nwblwi.newsops.execpc.com > m=08 =08boot -s Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-RELEASE #0: Mon Nov 22 13:38:07 CST 1999 root@host:/usr/src/sys/compile/DEMO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 Features=3D0x183fbff real memory =3D 536870912 (524288K bytes) avail memory =3D 519716864 (507536K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc027e000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci= 0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=3D7, 16/255 SCBs hfa0: rev 0x00 int a irq 19 on pci0.9.0 chip4: rev 0x03 on pci0.1= 0.0 ahc1: rev 0x00 int a irq 17 on pci0.11.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=3D7, 16/255 SCBs ahc2: rev 0x00 int a irq 16 on pci0.12.0 ahc2: aic7880 Wide Channel A, SCSI Id=3D7, 16/255 SCBs Probing for devices on PCI bus 1: Probing for devices on PCI bus 2: de0: rev 0x22 int a irq 18 on pci2.4.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de0: address 00:e0:29:3c:fb:84 de1: rev 0x22 int a irq 19 on pci2.5.0 de1: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de1: address 00:e0:29:3c:fb:85 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=3D0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 sio2 not found at 0x3e8 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3 not found at 0x2e8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface we0 at 0x2e8 on isa we0: kernel is keeping watchdog alive APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert disabled, rule-based forwarding dis= abled, logging limited to 100 packets/entry by default ccd0-15: Concatenated disk drivers Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! de0: enabling 100baseTX port de1: enabling 100baseTX port cda1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device=20 da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da4 at ahc1 bus 0 target 3 lun 0 da4: Fixed Direct Access SCSI-2 device=20 da4: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da4: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da7 at ahc1 bus 0 target 6 lun 0 da7: Fixed Direct Access SCSI-2 device=20 da7: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da7: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da10 at ahc2 bus 0 target 0 lun 0 da10: Fixed Direct Access SCSI-2 device=20 da10: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da10: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da6 at ahc1 bus 0 target 5 lun 0 da6: Fixed Direct Access SCSI-2 device=20 da6: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da6: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da13 at ahc2 bus 0 target 3 lun 0 da13: Fixed Direct Access SCSI-2 device=20 da13: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da13: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da5 at ahc1 bus 0 target 4 lun 0 da5: Fixed Direct Access SCSI-2 device=20 da5: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da5: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da16 at ahc2 bus 0 target 6 lun 0 da16: Fixed Direct Access SCSI-2 device=20 da16: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da16: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da3 at ahc1 bus 0 target 2 lun 0 da3: Fixed Direct Access SCSI-2 device=20 da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da15 at ahc2 bus 0 target 5 lun 0 da15: Fixed Direct Access SCSI-2 device=20 da15: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da15: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device=20 da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da14 at ahc2 bus 0 target 4 lun 0 da14: Fixed Direct Access SCSI-2 device=20 da14: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da14: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da9 at ahc1 bus 0 target 9 lun 0 da9: Fixed Direct Access SCSI-2 device=20 da9: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da9: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da8 at ahc1 bus 0 target 8 lun 0 da8: Fixed Direct Access SCSI-2 device=20 da8: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da8: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da12 at ahc2 bus 0 target 2 lun 0 da12: Fixed Direct Access SCSI-2 device=20 da12: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da12: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da11 at ahc2 bus 0 target 1 lun 0 da11: Fixed Direct Access SCSI-2 device=20 da11: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da11: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da18 at ahc2 bus 0 target 9 lun 0 da18: Fixed Direct Access SCSI-2 device=20 da18: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da18: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da17 at ahc2 bus 0 target 8 lun 0 da17: Fixed Direct Access SCSI-2 device=20 da17: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing En= abled da17: 17366MB (35566480 512 byte sectors: 64H 32S/T 17366C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device=20 da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing En= abled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) hanging root device to da0s2a WARNING: / was not properly dismounted Enter full pathname of shell or RETURN for /bin/sh:=20 erase ^H, kill ^U, intr ^C # fsck -p mou/dev/rda0s2a: 5502 files, 21624 used, 137159 free (327 frags, 17104 bloc= ks, 0.2% fragmentation) nt -a /dev/rda0s2h: 59 files, 95 used, 771980 free (36 frags, 96493 blocks, 0.0% = fragmentation) /dev/rda0s2e: 12345 files, 143748 used, 54651 free (8323 frags, 5791 blocks= , 4.2% fragmentation) /dev/rda0s2f: 880 files, 8264 used, 110791 free (39 frags, 13844 blocks, 0.= 0% fragmentation) /dev/rda0s2g: 170 files, 1265 used, 1015038 free (158 frags, 126860 blocks,= 0.0% fragmentation) # #=20 # sh /etc/netstart Doing stage one network startup: Doing initial network setup: hostname. de0: enabling 100baseTX port de0: enabling Full Duplex 100baseTX port de0: flags=3D884@@@@@@@````=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00ppp= pp=00=00pp=00=00=00=00p=00`p=00=00=00=00=00=00@x=00=00=00xx=00x=00`=0C=00= =00=18=0C=00=1Fp=00x=0C=00=00=00=00=00=00peT de1: enabling Full Duplex 100baseTX port @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @=00=00=00=00=00x=00=00px=00=00=00=00=00=00=00p=00=00=00=00@=00g=00=00=00= =00=00=00p=00=00=00=00=00=00=00~=0C=00=00=00=00=00=00=00=00=00=00p=00@x=00= =00x=00=00=00=00@=00=00=00=00=00=00=00x=00=00xx=00=00x=00=00=00=00xx=00=00= =00@x=00=00=00=00=00=00=1Cp=00=00=00=00=00=00=00pp=00=00=00=00=00=00=00=00= =00x=00=00=00=00=00xxx=00=00=00=00=00=00=1Cp=00=00=00=00=00=00=00=00=00=00`= =00=00=00`xxx=00=00=00=00=00=00=00=00=00=00=00=00=00p=00=07=0C=00=00=00p=00= =00=00=7F=00=00=0E=00=00pp=00x=00=00pp=00=00=00=00p=00=00=00=00=00=00x=00@x= =00=00x=00|xx=00=00=00=00=00=00=00=00=1Cp=00=00=00=00=00=00x=00=00~=00~=00= =00=00~x=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00= =00=00=00=00=00=00=03=00=00=00=00=00=00=00x=00=00=00p=00=00x=00= =00=00=00=00=00=00=00=00x=00=00~=00~=00=00=00=00=00=00=00=00=00=00x=00=00@= =00=00=00=00=00=00=00@=00x=00x=00=00=00=00=00=00=00|=00=00=00x=00=00=00=00= =00x=00=00~=00|=00=00=00=00=00=00=00@=00=00=00=00`=00=00=00=00`x=00=00=00@x= =00@=00=00=00@=00=00=00=00=00=00=00=00=00`x=00=00x=00~x=00~x=00~x=00=00=00@= =00=00x=00=00@=00=00=00`=00=00=00=00=00=00=00|=00@x=00~x=00|=00=00=00=00=00= =00=00=00=00=00=00=00=00=00`=00=00=00=00=00=00=00=00=00=00=00=00=00=00`=00x= =00=00=00=00=00=00=00=00x=00~x=00~=00=00=00@x=00=00=00=00`=00=00=00=00=00= =00x=00=00=00=00=00@=00`x=00=00=00x=00=00=00x=00=00`=00=00=00`=00x=00=00x= =00=00=00=00=00@=00=00~x=00=00=00`=00=00= =00=00=00=00`=00=00x=00=00=00=00x=00=00=00=00=00`=00=00~x=00=00=00x=00=00`= =00=00=00@=00=00=00@=00=00=00x=00=00=00=00@x=00=00=00x=00=00=00=00=00=00=00= `x=00=00=00=00x=00=00=00=00=00=00`=00=00=00=00=00=00=00=00=00=00x=00=00=00= =00`x=00=00=00=00x=00=00`=00=00=00@=00=00=00~=00@=00x=00=00=0F=00=00=00=00= =00=00`=00=00=00=00=00=00=00=00=00|=00=00x=00=00=00=00=00=00x=00|x=00~=00= =00=00=00x=00xx=00=00=00`x=00=00x=00=00=00=00|=00=00=00=00x=00=00=00=00=00= =00=00=00@=00=00|x=00=00=00=00=00=00=00=00=00x=00=00=00x=00~=00=00=00=00=00= =00=00=00=00=00=00=00x=00=00=00=00=00@=00=00|x=00=00=00|=00x=00|=00=00=00= =00=00=00xx=00=00=00@=00=00=00=00=00=00=00xx=00=00= =00=00=00=00=00=00=00xx=00=00=00=00=00`=00=00~x=00=00=00|=00=00=00@=00=00= =00`x=00=00=00=00=00=00=00=00=00@=00=00=00=00=00=00x=00|=00=00=00=00=00=00= =00=00=00x=00=00@=00=00=00=00=00=00@=00=00=00x=00=00=00x=00=00=00=00=00=00@= x=00=00=00=00=00=00=00`=00=00=00@=00=00=00@=00=00@x=00~=00=00x=00=00`=00=00= =00=00=00=00=00=00=00=00=00=00=00`=00=00=00@=00=00=00@=00=00@x=00=00=00`=00= x=00=00`=00=00=00=00=00=00@=00=00=00@=00=00=00@=00=00`=00x=00=00=00=00x=00= =00=00x=00xx=00=00=00`x=00=00=00=00=00`=00=00=00=00x=00=00=00x=00=00@=00=00= =00`=00=00=00=00=00=00xx=00=00=00x=00=00=00=00@x=00=00=00=00@x=00=00=00=00= =00=00=00=00=00=00=00=00@x=00=00=00=00x=00=00= @=00=00=00x=00|=00=00=00=00=00=00=00=00=00x=00=00`=00=00=00=00=00=00`=00=00= =00=00@x=00=00=00x=00|x=00|=00=00x=00=00=00=00=00xx=00=00=00=00=00=00=00=00= =00=00x=00=00=00`=00=00=00@=00=00=00x=00=00=00`xx=00=00=00x=00=00`=00=00=00= @=00=00=00x=00=00=00=00=00@=00=00|x=00=00=00=00=00x=00=00`=00=00=00`=00=00= =00=00x=00=00=00`=00=00=00@=00=00=00x=00=00=00`x=00=00=00=00x=00=00=00=00= =00=00x=00=00=00`=00=00=00@=00=00=00x=00=00=00`x=00=00=00=00x=00=00=00xx=00= =00=00@=00=00=00=00=00=00=00`=00=00=00@=00=00=00@=00=00x=00=00=00`xx=00x=00= =00=00x=00=00`=00=00=00`=00=00=00=00x=00=00`=00=00=00=00=00=00=00=00=00=00= =00=00xx=00=00=00=00=00=00=00=00=00=00= x=00|x=00|=00=00=00=00`=00=00=00=00=00=00=00=00=00=00=00=00=00@p=00=00=00= =00=00=00=00p=00=00p=00=00=00=00=00=00=00=00=00~=00=00=00x=00|x=00=00=00=00= =00=00x=00=00=00=00=00=00=00=00=00=00xx=00=00=00`x=00=00xx=00=00=00=00=00= =00=00=00`x=19&=0B=00 =00=00w=00=00x=00=00px=00=00=00=00x=00=00xx=00=00=00x= =00=00@=00=00=00=00xx=00=00=00@x=00=00x=00=00x=00|x=00|=00=00=00=00@=00=00|= =00=00@=00=00=00=00=00=00=00=00=00=00=00x=00|x=00|=00=00=00=00x2=00=00=00= =00x=00=00@=00=00=000x=00=00x=00=00=00xx=00=00=00=00=00=00=00.=00=00=00=00= =00=00@=00xx=00|x=00|=00=00=00=00=00xx=00=00=00@x=00=00=00=00@=00=00=7F=00= =00=00=7F=00=00=00@1=00=00= =00x=00|x=00|=00=00=00=00=00@=00=00=00=00x=00=00=00=00=00=7F=00=00=00@=00x= =00=00=00=7F=00=00=00=00=00=00=00x=00=00@=00=00=00=00=00=00x=00|x=00=00=00= =00x=00=00=7F=00=00=00=7F=00=00=00@=00x=00=00=00=00=00x=00=00=00xx=00=00=00= x=00=00|=00@=00x=00=00=00=00=00=00x=00|x=00=00=00=00=00=00=00x=00=00=00xx= =003=00=00=00x=00=00@=00.=00=00=00=00=00x=00=0063:513 =00=00=00=00@=00=00|x= =00=00=00=00x=00=00@=00=00=00@=00=00xx=00=00=00=00=00=00=00=00xx=00=00|=00= =00=00=00x=00|x=00=00=00=00=00=00=00=00@=00=00=7F=00=00=00=7F=00=00=00@=00x= =00=00=00=00=00=00=00=00x=00=00@=00=00=00=00=00=00=00x=00=00=00=00x=00|x=00= |=00=00=00=00=00=00=00@=00=00=7F=00= =00=00=7F=00=00=00@=00x=00=00x=00=00@=00=00=00=00@=00=00x=00|x=00x=00=00=00= =00=00=00=00@=00=00=00=00x=00=00@=00=00=00=00xx=00=00=00@x=00=00=00=00=00@x= =00|x=00|=00=00=7Fx=00=00=00=00=00=00x=00x=00=00=00=00=00=00=7Fx=00|x=00=00= =00=00=00=00=00=00=00x=00=00=00xx=00=00=00=00=00=00=00x=00=00=00=00x=00|x= =00|=00=00=7Fx=00=00=00=00=00=00x=00@=00=00=00=00@=00=00=00=00@x=00=00=00= =00=00=00=00=00=00=00x=00|x=00|=00=00=00=00=00@=00=00=00=00x=00=00@=00=00xx= =00=00=00@=00x=00=00=00=7F=00=00=00=00=00@=00=00|x=00=00=7Fx=00=00xx=00=00= =00x=00=00@=00=00=00@=00=00=00=00=00=00=00=00=00xx=00=00=00=00=00x=00=00xx= =00=00=00@x=00=00=00=00x=00=00= =00x=00=00=00=00x=00=00=00=00=00=00=00@=00=00=00=00=00=00=00=00@=00=00|=00= =00x=00=00@=00=00=00@=00=00@x=00=00x=00x=00|x=00|=00=00=00=00=00=00=00=00= =00@x=00=00=00=00=00=00=00=00=00=00=00x=00|x=00=00=00=00=00=00=00=00=00=00x= =00=00@=00=00=00x=00x=00x=00xx=00=00=00x=00x=00=00=00=00=00=00=00=00@=00=00= =00=00x=00=00@=00=00xx=00=00=00@=00=00x=00=00|=00x=00|x=00=00=00=00=00=00= =00@=00=00=00=00x=00=00x=00x=00=00|=00@x=00=00=00=00=7F=00=00=00=00=00@=00= =00|x=00=00=7Fx=00=00x=00=00=00=00x=00=00=00x=00=00=00xx=00=00=00=00=00=00x= =00|x=00|=00=00=00=00@=00=00=00=00x=00=00@=00=00=00=00xx=00=00=00@x=00=00= =00=00=00=7F=00x=00=00x=00=00=00= =00=00=00=00=00=00=00=00=00x=00=00xx=00=00=00@x=00=00=00=00=00xx=00|x=00|= =00x=00x=00x=00=00=00=00=00=00x=00@x=00=00=00=00=00=00@=00=00=00=00x=00=00@= =00=00=00=00=00=00=00=00=00=00=00x=00=00=00=00=00=00x=00@x=00=00=00=00=00= =00@=00=00=00=00@=00=00=00=00=00=00=00=00=00@x=00=00=00=00@=00=00=00=00=00= =00=00=00=00=00=00=00=00=00=00x=00=00x=00|x=00|=00=00=7Fx=00=00=00=00=00@x= =00=00=00=00=00=00=00x=00@x=00=00p=00x=00|x=00|=00=00=7Fx=00|x=00=00=00=00= =00=00=00=00=00@=00=00|=00x=00=00=00x=00=00=00=00=00x=00=00=00=00px=00=00x= =00=00=7Fx=00|x=00@x=00|=00=00=00=00=00=00=00x=00x=00x=00=00=00=00=00=00=00= x=00=00@=00=00=00@=00=00=00=00=00=00= x=00=00=00x=00@x=00|=00=00=00px=00|x=00@x=00|=00=00=00x=00=00=00=00|=00=00= =00=00=00=00=00=00=7Fx=00|x=00@x=00|=00=00@x=00=00=7F=00=00x=00=00x=00@=00x= =00=00=00x=00=00x=00=00=00x=00|x=00|=00=00|=00=00=00=00=00=00=00x=00=00=00x= =00=00x=00=00x=00@=00x=00=00=00x=00=00x=00=00=00x=00|x=00|=00=00|=00=00xx= =00=00x=00=00=00=00@=00x=00=00p=00x=00=00=00x=00=00=00=00x=00@x=00x=00@=00x= =00=00=00x=00|=00x=00x=00=00=00x=00|x=00|=00=00|=00=00=00x=00=00x=00=00=00= =00@x=00=00p=00=00=00=7F=00=00=7F=00x=00@x=00x=00@=00x=00=00=00x=00|=00|x= =00|=00@=00x=00=00=00x=00|x=00=00=00=00=00=00=00=00x=00=00|= x=00|x=00=00=00=00@x=00=00=00=7F=00=00=7Fx=00@x=00x=00@=00x=00=00=00x=00|= =00|x=00|=00@=00x=00=00=00=00=00=00=00x=00=00=00|x=00|x=00=00=00=00@x=00=00= =00=7F=00=00=7Fx=00@x=00x=00=00=00x=00|x=00|=00=00|=00x=00|=00@=00x=00=00= =00x=00|x=00|=00x=00=00=00=00=00=00=00|x=00|x=00=00=00=00=00=00=00=00=00=7F= =00=00=7Fx=00|x=00=00=00=00@xx=00=00=00x=00|x=00|=00=00|=00x=00|=00@=00x=00= =00=00x=00|x=00|=00=00=00=00=00=00=00=00=00|x=00|x=00=00=00=00=00=00=00=00= =7F=00=00=7Fx=00|x=00=00=00=00@x=00x=00@=00x=00=00=00x=00|x=00=00|x=00|=00@= =00x=00=00=00x=00|x=00|=00=00=00=00=00=00|x=00|x=00=00= =00=00=00=00=00=7F=00=00=7Fx=00|x=00=00=00=00@x=00=00x=00@=00x=00=00=00x=00= |x=00=00|x=00=00@=00x=00=00=00x=00|x=00|=00=00=00=00=00=00=00=00=00=00=00= =00|x=00|x=00=00=00=00=00=00=00=00=00=7F=00=00=00=00=00=00=00x=00@=00=00=00= =00=00=00=00=00=00=00=00|x=00|x=00=00=00=00=00=00=00xarp: 169.207.30.1 is o= n de0 but got reply fr=00:=00=00=00=00e:ef:40 on de1 =00=00x=00=00xxxxxxxxxarp: 169.207.30.1 is on de0 but got reply from 00:60:= 3e:7e:ef:40 on de1 ipfw: 951 Deny UDP 169.207.30.9:513 169.207.30.63:513 in via de1 arp: 169.207.30.1 is on de0 but got reply from 00:60:3e:7e:ef:40 on de1 ipfw: 951 Deny UDP 169.207.30.4:513 169.207.30.63:513 in via de1 Now, this doesn't show it real good, but the basic thing is that when the ifconfig runs, it seems to somehow mess up the serial console. Userland I/O is messed up, although kernel output remains OK. A "stty -a" while it is messed up (from a shell script) does not reveal anything different than the settings that exist while things are OK. If the system gets to multi- user mode, and brings up a getty on ttyd0, then it corrects itself at the point where it starts spitting out the banner. Up to then, all I see are kernel messages, and garbage where userland stuff is spitting up output. How in the world do I even figure out the next debugging step? :-) ... Joe ---------------------------------------------------------------------------= ---- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 2:25: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from patachou.sti.com.br (patachou.sti.com.br [200.212.48.251]) by hub.freebsd.org (Postfix) with ESMTP id F2D4A14A00; Tue, 23 Nov 1999 02:24:51 -0800 (PST) (envelope-from VideBula@sti.com.br) Received: from carlos (dial-lc11-149.sti.com.br [200.188.73.149] (may be forged)) by patachou.sti.com.br (8.9.3/8.9.3) with SMTP id IAA18313; Tue, 23 Nov 1999 08:23:15 -0200 Message-Id: <199911231023.IAA18313@patachou.sti.com.br> From: "VideBula" To: VB Date: Tue, 23 Nov 1999 08:19:44 -0300 Subject: VB Reply-To: VideBula@sti.com.br Organization: ViaNet Comunicação & Informação Ltda. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001_4295711_29984,04_4325695,0390625" Content-Transfer-Encoding: 7bit X-Priority: 1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a Multipart MIME message. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPart_000_001_4295711_29984,04_4325695,0390625 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit ------=_NextPart_000_001_4295711_29984,04_4325695,0390625 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7bit VideBula-991118

VideBula

 

"Não importa o que tiraram de você,
o que importa é o que você vai fazer com o que sobrou."

 

"Você não pode estar só se gostar da pessoa com quem fica quando esta sozinho." 

RECEBER NÃORECEBER

PUBLICAR CRÍTICAS, DÚVIDAS & SUGESTÕES

------=_NextPart_000_001_4295711_29984,04_4325695,0390625-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 2:57: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 5678C14BEC for ; Tue, 23 Nov 1999 02:56:52 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 0542C1937; Tue, 23 Nov 1999 11:57:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id E5F8C4A1B; Tue, 23 Nov 1999 11:57:16 +0100 (CET) Date: Tue, 23 Nov 1999 11:57:15 +0100 (CET) From: Andrzej Bialecki To: Joe Greco Cc: dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Non-standard FFS parameters In-Reply-To: <199911230601.AAA04318@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Joe Greco wrote: > > On Fri, 8 Oct 1999, Matthew Dillon wrote: > > > > > :> > > > :> Adjusting the bytes-per-inode (-i) specification in newfs should not > > > :> pose a problem. > > > : > > > :IOW now you say it's ok to use very high values of -i... ;-) > > > : > > > :Andrzej Bialecki > > > > > > No, I didn't say that. My recommended maximum is still 262144. Fsck > > > should be reasonably fast with that number and the filesystem should > > > still be able to maintain reasonable efficiency. > > > > Ok, I can live with that, I guess. Thanks a lot for your help! > > What's the recommended way to reduce the number of cylinder groups a bit? ...except manually changing the calculations in newfs/mkfs.c ? What values are reasonable for large filesystems? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 6:47:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 0285B14E93 for ; Tue, 23 Nov 1999 06:46:55 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991122211726.00106@mojave.sitaranetworks.com> Date: Mon, 22 Nov 1999 21:17:26 -0500 From: Greg Lehey To: Richard Puga , freebsd-hackers@freebsd.org Subject: Re: whats up with vinum? Reply-To: Greg Lehey References: <38380476.7C43AEBA@mauibuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <38380476.7C43AEBA@mauibuilt.com>; from Richard Puga on Sun, Nov 21, 1999 at 04:40:54AM -1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 21 November 1999 at 4:40:54 -1000, Richard Puga wrote: > I am fooling around with vinum which I have set up in a raid 5 > configuration under FreeBSD 3.3-RELEASE. > > The trouble is that my machine keeps locking up under heavy use. If I > try and "make world" it dies about 15-60 seconds into it whit a page > fault as well as trying to ftp over large files and somtimems while > trying to build kernels. If you have problems with Vinum, please read what it says at the end of vinum(4) in the section DEBUGGING PROBLEMS WITH VINUM. You can also read it at and http://www.lemis.com/vinum/how-to-debug.html, and you should normally check known bugs at http://www.lemis.com/vinum/bugs.html. > After several page faults and fsck's on reboot I will loose an entire > drvie. It is marked as "stale"m by vinum and more than once has lost its > disklabel. > > I am now using ccd level 0 but would like to use vinum raid 5 if > possable. With the information you supply, it's difficult to tell. It could be a known problem: we do have one outstanding problem with RAID-5. To quote the man page: 4. The RAID-5 functionality is new in FreeBSD 3.3. Some problems have been reported with vinum in combination with soft updates, but these are not reproducible on all systems. If you are planning to use vinum in a production environment, please test carefully. > PS; anyone thinking of playing with vinum I suggest you dont start out > with 4 18 gig drives ..:) If you make these suggestions, you should say why. I don't know of any problems. What have you had? Maybe they are related to your panics. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 7:42:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 17F98152DD for ; Tue, 23 Nov 1999 07:42:17 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id IAA261108; Tue, 23 Nov 1999 08:41:39 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id IAA04553; Tue, 23 Nov 1999 08:41:39 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Tue, 23 Nov 1999 08:41:39 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wacky rpc.lockd idea... In-Reply-To: <199911222326.SAA79947@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, David E. Cross wrote: > I've noticed about 99% of the panics on our machines are the result of NFS, > more often than not it is the result of a backing store file being blown > away underneath the client. ie. person editing a file on one machine, > compiling and running on a second, then removing the binary on the first > machine. If we had a working lock manager could we not have the kernel open > a shared lock on anything it had in backing store, would that not assure that > files didn't go poof in the night? I think you're really proposing to add state to NFS, but add it via a 'back door', the lockd. I think this is not as good an idea as getting coda or intermezzo working -- for the latter, www.inter-mezzo.org nfs is just plain broken for this sort of thing, and has been forever. I'm not sure you want to start grafting on fixes of this sort. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 8:28:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id 3E84715284; Tue, 23 Nov 1999 08:27:27 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from WIN2K1 (st84042.nobell.com [216.140.184.42]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id KAA22245; Tue, 23 Nov 1999 10:26:59 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: "zshack" , , Subject: arpresolve: can't allocate llinfo for 127.0.0.1rt Date: Tue, 23 Nov 1999 10:31:13 -0600 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01BF359D.DDCFBD60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 In-Reply-To: Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002E_01BF359D.DDCFBD60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit This one fell through the cracks on the questions list… probably cause its not a simple question… or at least I would like to think so ;-) It is regarding an error occurring in the route table on various machines under various configurations. The one similarity is dhclient. Read below… I was fairly detailed with the description of the problem… thanks! Aaron Sonntag -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Aaron Sonntag Sent: Monday, November 22, 1999 10:08 AM To: zshack; FreeBSD-questions@FreeBSD.ORG Subject: RE: slight problem I HAVE THIS PROBLEM TOO… I am not sure what causes it… but if you do a netstat –rn I am sure you will see that the route to your nic interface address is pointing to 127.0.0.1 instead of a mac address (as show below under [BEFORE]). Do a ‘route delete [interface address]’… for instance in the example below… I type ‘route delete 216.140.184.45’. Then ping the interface and run netstat –rn again and you will see (as shown below under [AFTER]) that the mac addy will appear and the machine will be happy. Temporarily :-( [BEFORE] Internet: Destination Gateway Flags Refs Use Netif Expire default 216.140.184.33 UGSc 11 2528899 rl0 10.0.1/24 link#3 UC 0 0 mx1 127.0.0.1 127.0.0.1 UH 2 80 lo0 216.140.184.32/27 link#1 UC 0 0 rl0 216.140.184.45 127.0.0.1 UGHS 0 232 rl0 [AFTER] Internet: Destination Gateway Flags Refs Use Netif Expire default 216.140.184.33 UGSc 11 2528999 rl0 10.0.1/24 link#3 UC 0 0 mx1 127.0.0.1 127.0.0.1 UH 1 80 lo0 216.140.184.32/27 link#1 UC 0 0 rl0 216.140.184.45 0:4f:4e:1:1a:88 UHLW 0 2 lo0 A friend/coworker of mine helped me with this temporary fix (THANKS DAVID!). But he seemed to think it was a larger issue with the dhclient script. I have had this problem on three different 3.3 machines on three COMPLETELY different networks and the one similarity between them was dhclient. Two of them were nat boxes on RR and one is a workstation. To reinforce this theory… on the nat boxes that have the problem… its only the interfaces that are getting dhcp via dhclient that have the problem. My point is… the above is a temporary solution. The following message will completely flood my dmesg buffer until the machine stops responding… arplookup 127.0.0.1 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 127.0.0.1rt anybody have any permanent solutions?? Thanks Aaron Sonntag -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of zshack Sent: Monday, November 22, 1999 9:40 AM To: FreeBSD-questions@FreeBSD.ORG Subject: slight problem I just installed freebsd 3.3 stable and i keep getting this message: /kernet: arplookup 127.0.0.1 failed: can't allocate llinfo /kernet arpresolve can't allocate llinfo for 127.0.0.1 any idea what is causing this and how i can fix it? Thanks zshack ------=_NextPart_000_002E_01BF359D.DDCFBD60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

This one fell through the cracks on the questions list… = probably cause its not a simple question… or at least I would like to think so = ;-)

It is regarding an error occurring in the route table on various machines under various configurations.  The one similarity is = dhclient.

Read below… I was fairly detailed with the description of = the problem…

 

thanks!

 

Aaron Sonntag

 

 

-----Original Message-----
From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Aaron Sonntag
Sent: Monday, November = 22, 1999 10:08 AM
To: zshack; FreeBSD-questions@FreeBSD.ORG
Subject: RE: slight = problem

 

I HAVE THIS PROBLEM = TOO…

I am not sure what causes it… but if you = do a netstat –rn I am sure you will see that the route to your nic interface = address is pointing to 127.0.0.1 instead of a mac address (as show below under [BEFORE]).  Do a = ‘route delete [interface address]’… for instance in the example = below… I type ‘route delete 216.140.184.45’.  = Then ping the interface and run netstat –rn again and you will see (as shown = below under [AFTER]) that the mac addy will appear and the machine will be = happy.  Temporarily = L

 

[BEFORE]

Internet:

Destination        Gateway            Flags     Refs     Use     = Netif Expire

default            216.140.184.33     UGSc       11  2528899      = rl0

10.0.1/24          = link#3           &n= bsp; UC          0        0      = mx1

127.0.0.1          127.0.0.1          = UH          2       80      lo0

216.140.184.32/27  link#1           &n= bsp; UC          0        0      = rl0

216.140.184.45     127.0.0.1          = UGHS        0    =   232      = rl0

 

[AFTER]

Internet:

Destination        Gateway            Flags     Refs     Use     = Netif Expire

default            216.140.184.33     UGSc       11  2528999      = rl0

10.0.1/24          = link#3           &n= bsp; UC          = 0        0      mx1

127.0.0.1          127.0.0.1          = UH          1       80      lo0

216.140.184.32/27  link#1           &n= bsp; UC          0        0      = rl0

216.140.184.45     0:4f:4e:1:1a:88    UHLW        0        2      lo0

 

 A friend/coworker of mine helped me with this temporary fix (THANKS = DAVID!).  But he seemed to think it was = a larger issue with the dhclient script.  = I have had this problem on three different 3.3 machines on three = COMPLETELY different networks and the one similarity between them was = dhclient.  Two of them were nat boxes on = RR and one is a workstation.  To = reinforce this theory… on the nat boxes that have the problem… its = only the interfaces that are getting dhcp via dhclient that have the = problem.

My point is… the above is a temporary = solution.

The following message will completely flood my = dmesg buffer until the machine stops = responding…

 

arplookup 127.0.0.1 failed: could not allocate = llinfo

arpresolve: can't allocate llinfo for = 127.0.0.1rt

 

anybody have any permanent = solutions??

 

Thanks

 

Aaron = Sonntag

 

-----Original Message-----
From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of zshack
Sent: Monday, November = 22, 1999 9:40 AM
To: = FreeBSD-questions@FreeBSD.ORG
Subject: slight = problem<= /p>

 <= /p>

 I just installed freebsd 3.3 stable and i keep getting this = message:<= /p>

 <= /p>

/kernet: arplookup 127.0.0.1 failed: can't allocate llinfo<= /p>

/kernet arpresolve can't allocate llinfo for 127.0.0.1<= /p>

 <= /p>

 <= /p>

any idea what is causing this and how i can fix it?<= /p>

 <= /p>

 <= /p>

Thanks<= /p>

zshack<= /p>

------=_NextPart_000_002E_01BF359D.DDCFBD60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 9: 2: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 75C3F15326 for ; Tue, 23 Nov 1999 09:01:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA08884; Tue, 23 Nov 1999 10:00:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA13906; Tue, 23 Nov 1999 10:01:02 -0700 (MST) Message-Id: <199911231701.KAA13906@harmony.village.org> To: "David E. Cross" Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Nov 1999 15:08:23 EST." <199911222015.PAA74002@cs.rpi.edu> References: <199911222015.PAA74002@cs.rpi.edu> Date: Tue, 23 Nov 1999 10:01:02 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911222015.PAA74002@cs.rpi.edu> "David E. Cross" writes: : Ok... I have *had* it with the meta, but not really, lockd. Are there any : kernel issues with correctly implimenting rpc.lockd? How can I take a : filehandle and map it into a filename, with path, so I may open it and lock : it on the server? Are there any protocol specs? I downloaded the RFC for : version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to : the version 3 spec, which I cannot find, and the source is not a whole lot : of help on this issue. One area that Solbourne had lots and lots of problems with years ago when it tried to implenent rpc.lockd was that Sun, at the time, has 5! incompatible versions that had to be interoperated with. Don't know if things have changed in the ensuing years or not... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 9:18:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D4541534B for ; Tue, 23 Nov 1999 09:18:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA07636; Tue, 23 Nov 1999 09:17:46 -0800 Date: Tue, 23 Nov 1999 09:17:46 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <199911231701.KAA13906@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Ok... I have *had* it with the meta, but not really, lockd. Are there any > : kernel issues with correctly implimenting rpc.lockd? How can I take a > : filehandle and map it into a filename, with path, so I may open it and lock > : it on the server? Are there any protocol specs? I downloaded the RFC for > : version 4 nlm (which we do not supoprt at *all*), but it only lists diffs to > : the version 3 spec, which I cannot find, and the source is not a whole lot > : of help on this issue. > > One area that Solbourne had lots and lots of problems with years ago > when it tried to implenent rpc.lockd was that Sun, at the time, has 5! > incompatible versions that had to be interoperated with. Don't know > if things have changed in the ensuing years or not... Not really, no. Insofar as I know, the only distributed open source lock manager that might ever have a chance of being usable is the one the GFS guys are working on now, and naturally that will be tied to GFS, etc... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 9:45: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 1106E14BE3 for ; Tue, 23 Nov 1999 09:44:49 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id A11107555; Tue, 23 Nov 1999 09:44:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 904841D86; Tue, 23 Nov 1999 09:44:56 -0800 (PST) Date: Tue, 23 Nov 1999 09:44:56 -0800 (PST) From: Jamie Bowden To: "Ronald G. Minnich" Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: wacky rpc.lockd idea... In-Reply-To: Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Ronald G. Minnich wrote: :On Mon, 22 Nov 1999, David E. Cross wrote: :> I've noticed about 99% of the panics on our machines are the result of NFS, :> more often than not it is the result of a backing store file being blown :> away underneath the client. ie. person editing a file on one machine, :> compiling and running on a second, then removing the binary on the first :> machine. If we had a working lock manager could we not have the kernel open :> a shared lock on anything it had in backing store, would that not assure that :> files didn't go poof in the night? : :I think you're really proposing to add state to NFS, but add it via a :'back door', the lockd. I think this is not as good an idea as getting :coda or intermezzo working -- for the latter, www.inter-mezzo.org : :nfs is just plain broken for this sort of thing, and has been forever. I'm :not sure you want to start grafting on fixes of this sort. How would this be different that what Sun has done? They designed NFS stateless (do to stupid utopian visions of 0 latency infinite bandwidth networks), and then added state via rpc.lockd to try and fix their silly design flaw. Sure, locking still has problems due to race conditions and deadlocks, but it beats what you have without it. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 9:51:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.ifrance.com (www.ifrance.com [209.67.249.134]) by hub.freebsd.org (Postfix) with SMTP id C8B0214BF4 for ; Tue, 23 Nov 1999 09:51:19 -0800 (PST) (envelope-from brunoc@ifrance.com) Received: from 212.124.1.118 [212.124.1.118] by www.ifrance.com; Tue, 23 Nov 1999 17:41:27 GMT Message-ID: <01df01bf35db$b0ce8e20$1ec809c0@motte.alpes-net.fr> From: "Christian Bruno" To: Subject: H323/Ldap support in natd/libalias Date: Tue, 23 Nov 1999 18:53:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, i am trying to add an H323/LDAP support to NATD in FreeBSD to enable full video/audio functionnalities of video-conference clients in a private network. i posted some messages in newsgroups, but the only answer i got was to buy a commercial product like "phonepatch" (which does not work on my freebsd box) could you tell me if someone is working on this problem ? it could be interesting to exchange ideas (and maybe solutions ?) any comments or ideas are welcome Best Regards, Christian Bruno ( brunoc@ifrance.com ) ps : sorry, my english is a beta-test version ______________________________________________________________________ Message envoye depuis iFrance >> http://www.ifrance.com Gratuit >> Hebergement (50 Mo)/Vos emails (POP&HTML,20 Mo) Votre agenda online gratuit >> http://agenda.ifrance.com NOUVEAU : Faxez gratuitement ! >> http://fax.ifrance.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 11:17:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (Postfix) with ESMTP id 9253D15391 for ; Tue, 23 Nov 1999 11:17:10 -0800 (PST) (envelope-from haskin@ptway.com) Received: from brianjr (104R1.infinitecom.com [199.176.148.47] (may be forged)) by apollo.ptway.com (8.8.7/8.8.7) with SMTP id OAA23099; Tue, 23 Nov 1999 14:14:30 -0500 From: "Brian Haskin Jr." To: Cc: "Christian Bruno" Subject: RE: H323/Ldap support in natd/libalias Date: Tue, 23 Nov 1999 14:18:20 -0500 Message-ID: <000001bf35e7$80acf7c0$0b00000a@haskin.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <01df01bf35db$b0ce8e20$1ec809c0@motte.alpes-net.fr> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You might take a look at http://www.willamowius.de/openh323gk.html I haven't looked at it in a couple of months but they are basically working on a H323 stack and proxy. It's not exactly what your talking about but close enough that it might be a good starting place. Brian Haskin haskin@ptway.com Home page: http://www.geocities.com/ResearchTriangle/4333/ Always remember, money is simply a level of indirection. > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Christian Bruno > Sent: Tuesday, November 23, 1999 12:54 PM > To: freebsd-hackers@FreeBSD.ORG > Subject: H323/Ldap support in natd/libalias > > > Hello, > > i am trying to add an H323/LDAP support to NATD in FreeBSD to enable full > video/audio functionnalities of video-conference clients in a private > network. > > i posted some messages in newsgroups, but the only answer i got > was to buy a > commercial product like "phonepatch" (which does not work on my > freebsd box) > > could you tell me if someone is working on this problem ? > it could be interesting to exchange ideas (and maybe solutions ?) > > any comments or ideas are welcome > > Best Regards, > Christian Bruno ( brunoc@ifrance.com ) > > ps : sorry, my english is a beta-test version > > > > ______________________________________________________________________ > Message envoye depuis iFrance >> http://www.ifrance.com > Gratuit >> Hebergement (50 Mo)/Vos emails (POP&HTML,20 Mo) > Votre agenda online gratuit >> http://agenda.ifrance.com > NOUVEAU : Faxez gratuitement ! >> http://fax.ifrance.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 11:27:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bootstrap.agcs.com (bootstrap.agcs.com [130.131.48.11]) by hub.freebsd.org (Postfix) with ESMTP id EEFCB14A2D; Tue, 23 Nov 1999 11:27:35 -0800 (PST) (envelope-from lorenzaj@agcs.com) Received: from pxmail1.agcs.com (pxmail1.agcs.com [130.131.168.5]) by bootstrap.agcs.com (8.9.3/8.9.1) with ESMTP id MAA01458; Tue, 23 Nov 1999 12:26:48 -0700 (MST) Posted-Date: Tue, 23 Nov 1999 12:26:48 -0700 (MST) Received: from agcs.com ([130.131.59.116]) by pxmail1.agcs.com (Netscape Messaging Server 3.61) with ESMTP id AAA560B; Tue, 23 Nov 1999 12:26:52 -0700 Message-ID: <383AEA4F.ABE8D3DD@agcs.com> Date: Tue, 23 Nov 1999 12:26:07 -0700 From: "Juan Lorenzana" Organization: AG Communication Systems X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, hackers@freebsd.org Subject: NFS hangs/locks CPU Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running FreeBSD 2.2.8. We have used 2.2.8 to build a telecom application and have had great success deploying other telecom applications on 2.2.8 until now. We are using NFS to distribute binaries and config files to others machines so that we can achieve availability. Here's our problem: I have two machines one acting as a server and the other as a client. The processes are started as follows NFS Server (king-n1) mountd nfsd -u -t 10 rpc.statd NFS Client (king-c1) mount_nfs -T -w 1024 king-n1:/u /u Both machines are Pentium II 450 mhz with 512 megs of ram and 1024 megs of swap. We use an Intel Ethernet Express Pro 100 cards with the fxp0 driver. I turned on debug for the fxp0 driver and see nothing out of the ordinary. Please note that king-n1 is a dual homed. That is why we use the -T option. Otherwise, we can not use NFS to the virtual ip address without installing the NFS_Security_Cookie workaround. Since the nfs_security_cookie workaround has not been tested on 2.2.8, we chose to use the -T option (odd but it allows us to mount a directory from a virtual ip address instead of the real ip address). It is interesting to note that this hang still occurs whether or not we use the real ip address or a virtual ip address. The problem is that under heavy load, we see that the client does a lot of Getattr and Access (nfsstat -w 1). We were able to compile the DDB option into the kernel and when the machine hung,we entered into the debugger and saw that we were stuck in a _write call. The following is what we saw when we did a trace. _boidone(f418d200,f418d200,f22bf000,f22dc600,3) at _boidone 0x2e6 _nfs_doio(f418d200,f22df000,f22dc600,1,f418d200) at _nfs_doio 0x4c5 _nfs_strategy(efbffddc) at _nfs_strategy 0x68 _nfs_writebp(f418d200,1,efbffec4,f0163000,efbffe50) at _nfs_writebp 0x125 _nfs_bwrite(efbff50) at _nfs_bwrite 0x10 _nfs_write(efbffee08,f02564e0,1,efbff94,2) at _nfs_write 0x648 _vn_write(f25d6f80,efbfff34,f22bf000,f02564e0,f22c600) at _vn_write 0x93 _write(f220c600,efbff94,efbff84,0,5167) at _write 0x97 _syscall I am not sure what to do from here. We can only run traffic for about 4 hours before our machine hangs. I suspect that this might be related to a GETATTR or ACCESS nfs problem or a possible tcp/ip bug under heavy load. Can anyone help or point me in the right direction. Moving to 3.x is not possible because we are using a product that we purchased from Sweden. The Swedish product is the base of all our telecom products here at AGCS and it only runs on 2.2.8. Any help is appreciated. Thanks. Regards, -- Juan Lorenzana AG Communication Systems Phoenix, AZ 602-582-7442 lorenzaj@agcs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 11:51:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 09B9C152D6 for ; Tue, 23 Nov 1999 11:51:30 -0800 (PST) (envelope-from xavier@cs.duke.edu) Received: from mackerel.cs.duke.edu (mackerel.cs.duke.edu [152.3.140.156]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA17466; Tue, 23 Nov 1999 14:51:15 -0500 (EST) Received: from localhost (xavier@localhost) by mackerel.cs.duke.edu (8.8.5/8.6.9) with ESMTP id OAA22308; Tue, 23 Nov 1999 14:51:13 -0500 (EST) X-Authentication-Warning: mackerel.cs.duke.edu: xavier owned process doing -bs Date: Tue, 23 Nov 1999 14:51:13 -0500 (EST) From: Clinton Xavier Berni To: Julian Elischer Cc: "Parthasarathy M. Aji" , freebsd-hackers@FreeBSD.ORG Subject: Re: ip checksum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I am sort of confused with the parameters for IPsumReplaceShort function, I understand that I will pass the &ip-ip_sum for the cksump parameter. but I am not able to understand wht oldvap & newvalp stand for.. Xavier. On Mon, 22 Nov 1999, Julian Elischer wrote: > How many bytes have you changed? > > is it possible that some of the values have already been ntohs()'d > or something similar? > > rather than recalculate the whole packet, just update the exisitng > value. > > there is an rfc for this but it took me a while to get > the code right in C on a 386. The trick is getting the 1s complement > arithmetic right. > > > > #define FIXSUM16(c, op, np) \ > do { \ > (c) -= (u_int16_t) ~*((u_int16_t *) (op)); \ > if ((c) < 0) { \ > (c) += 0xffff; \ > } \ > (c) -= (u_int16_t) *((u_int16_t *) (np)); \ > if ((c) < 0) { \ > (c) += 0xffff; \ > } \ > } while (0) > > > /* > * IpsumReplaceShort() > * > * Replace a 16 bit aligned (relative to the checksum) 16 bit value > * in a packet and change the IP/TCP/UDP checksum at the same time. > * > * Works with both big and little endian machines(!) > * > * If for some wierd reason you want to replace a nonaligned value, > * you need to byteswap it and the old value before doing the > * subtractions. > */ > > void > IpsumReplaceShort(u_int16_t *cksump, u_int16_t *oldvalp, u_int16_t newval) > { > register int cksum; > > cksum = *cksump; > FIXSUM16(cksum, oldvalp, &newval); > *cksump = cksum; > *oldvalp = newval; > } > > > On Tue, 23 Nov 1999, Parthasarathy M. Aji wrote: > > > Hey, > > > > I am trying to recompute the checksum of an IP packet. I use > > netinet/in_chksum.c to do this. The values returned are not correct. I've > > reset the ip_sum field to 0 before doing the sum. Is there something > > missing? > > > > thanks > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 12:10:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 89DAC1514E for ; Tue, 23 Nov 1999 12:10:52 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA93916; Tue, 23 Nov 1999 12:09:56 -0800 (PST) Date: Tue, 23 Nov 1999 12:09:55 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Clinton Xavier Berni Cc: "Parthasarathy M. Aji" , freebsd-hackers@FreeBSD.ORG Subject: Re: ip checksum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999, Clinton Xavier Berni wrote: > Hey, > I am sort of confused with the parameters for IPsumReplaceShort function, > I understand that I will pass the &ip-ip_sum for the cksump parameter. > > but I am not able to understand wht oldvap & newvalp stand for.. cksump points to the existing checksum IN THE PACKET oldvalp points to the old value that will be replaecd IN THE PACKET newval is the value that will replace the old value. The function will replace the old value with the new value, and update the checksum accordigly. julian > > Xavier. > > > > On Mon, 22 Nov 1999, Julian Elischer wrote: > > > How many bytes have you changed? > > > > is it possible that some of the values have already been ntohs()'d > > or something similar? > > > > rather than recalculate the whole packet, just update the exisitng > > value. > > > > there is an rfc for this but it took me a while to get > > the code right in C on a 386. The trick is getting the 1s complement > > arithmetic right. > > > > > > > > #define FIXSUM16(c, op, np) \ > > do { \ > > (c) -= (u_int16_t) ~*((u_int16_t *) (op)); \ > > if ((c) < 0) { \ > > (c) += 0xffff; \ > > } \ > > (c) -= (u_int16_t) *((u_int16_t *) (np)); \ > > if ((c) < 0) { \ > > (c) += 0xffff; \ > > } \ > > } while (0) > > > > > > /* > > * IpsumReplaceShort() > > * > > * Replace a 16 bit aligned (relative to the checksum) 16 bit value > > * in a packet and change the IP/TCP/UDP checksum at the same time. > > * > > * Works with both big and little endian machines(!) > > * > > * If for some wierd reason you want to replace a nonaligned value, > > * you need to byteswap it and the old value before doing the > > * subtractions. > > */ > > > > void > > IpsumReplaceShort(u_int16_t *cksump, u_int16_t *oldvalp, u_int16_t newval) > > { > > register int cksum; > > > > cksum = *cksump; > > FIXSUM16(cksum, oldvalp, &newval); > > *cksump = cksum; > > *oldvalp = newval; > > } > > > > > > On Tue, 23 Nov 1999, Parthasarathy M. Aji wrote: > > > > > Hey, > > > > > > I am trying to recompute the checksum of an IP packet. I use > > > netinet/in_chksum.c to do this. The values returned are not correct. I've > > > reset the ip_sum field to 0 before doing the sum. Is there something > > > missing? > > > > > > thanks > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 12:34:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.nobell.com (ns.nobell.com [216.140.184.2]) by hub.freebsd.org (Postfix) with ESMTP id 713BC14CB4; Tue, 23 Nov 1999 12:34:25 -0800 (PST) (envelope-from aaron@nobell.com) Received: from WIN2K1 (st84042.nobell.com [216.140.184.42]) by ns.nobell.com (8.9.3/8.9.3) with SMTP id OAA59111; Tue, 23 Nov 1999 14:34:16 -0600 (CST) (envelope-from aaron@nobell.com) From: "Aaron Sonntag" To: , , Cc: Subject: arpresolve: can't allocate llinfo for 127.0.0.1rt [PLAIN TEXT] Date: Tue, 23 Nov 1999 14:38:30 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... my apologies to all those whose email clients are not capable of parsing html emails... my settings indicated that my email was to be sent plain text... this was apparently not the case as someone was kind enough to point out... thanks! Aaron Sonntag -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Aaron Sonntag Sent: Monday, November 22, 1999 10:08 AM To: zshack; FreeBSD-questions@FreeBSD.ORG Subject: RE: slight problem I HAVE THIS PROBLEM TOO... I am not sure what causes it... but if you do a netstat -rn I am sure you will see that the route to your nic interface address is pointing to 127.0.0.1 instead of a mac address (as show below under [BEFORE]). Do a 'route delete [interface address]'... for instance in the example below... I type 'route delete 216.140.184.45'. Then ping the interface and run netstat -rn again and you will see (as shown below under [AFTER]) that the mac addy will appear and the machine will be happy. Temporarily L [BEFORE] Internet: Destination Gateway Flags Refs Use Netif Expire default 216.140.184.33 UGSc 11 2528899 rl0 10.0.1/24 link#3 UC 0 0 mx1 127.0.0.1 127.0.0.1 UH 2 80 lo0 216.140.184.32/27 link#1 UC 0 0 rl0 216.140.184.45 127.0.0.1 UGHS 0 232 rl0 [AFTER] Internet: Destination Gateway Flags Refs Use Netif Expire default 216.140.184.33 UGSc 11 2528999 rl0 10.0.1/24 link#3 UC 0 0 mx1 127.0.0.1 127.0.0.1 UH 1 80 lo0 216.140.184.32/27 link#1 UC 0 0 rl0 216.140.184.45 0:4f:4e:1:1a:88 UHLW 0 2 lo0 A friend/coworker of mine helped me with this temporary fix (THANKS DAVID!). But he seemed to think it was a larger issue with the dhclient script. I have had this problem on three different 3.3 machines on three COMPLETELY different networks and the one similarity between them was dhclient. Two of them were nat boxes on RR and one is a workstation. To reinforce this theory... on the nat boxes that have the problem... its only the interfaces that are getting dhcp via dhclient that have the problem. My point is... the above is a temporary solution. The following message will completely flood my dmesg buffer until the machine stops responding... arplookup 127.0.0.1 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 127.0.0.1rt anybody have any permanent solutions?? Thanks Aaron Sonntag -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of zshack Sent: Monday, November 22, 1999 9:40 AM To: FreeBSD-questions@FreeBSD.ORG Subject: slight problem I just installed freebsd 3.3 stable and i keep getting this message: /kernet: arplookup 127.0.0.1 failed: can't allocate llinfo /kernet arpresolve can't allocate llinfo for 127.0.0.1 any idea what is causing this and how i can fix it? Thanks zshack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 13:30:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id 7B02D153D9; Tue, 23 Nov 1999 13:30:21 -0800 (PST) (envelope-from sh@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by proteus.eclipse.net.uk (Postfix) with ESMTP id F05F29B17; Tue, 23 Nov 1999 21:30:14 +0000 (GMT) Message-ID: <383B078A.384782E9@eclipse.net.uk> Date: Tue, 23 Nov 1999 21:30:50 +0000 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: Aaron Sonntag Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, zshack@alliancelink.com Subject: Re: arpresolve: can't allocate llinfo for 127.0.0.1rt [PLAIN TEXT] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See PR bin/12136. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 14:40:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sev.mtelecom.ru (host2.mtelecom.ru [212.44.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A33815205 for ; Tue, 23 Nov 1999 14:40:28 -0800 (PST) (envelope-from seva@mtelecom.ru) Received: from mtelecom.ru (localhost.mtelecom.ru [127.0.0.1]) by sev.mtelecom.ru (8.9.3/8.9.3) with ESMTP id BAA04721 for ; Wed, 24 Nov 1999 01:38:13 +0300 (MSK) (envelope-from seva@mtelecom.ru) Message-ID: <383B1755.F432A049@mtelecom.ru> Date: Wed, 24 Nov 1999 01:38:13 +0300 From: Seva "Semenov" X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in 3.X !!!! References: <383222DF.164E86DB@mtelecom.ru> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms5C988043D8A5764470713967" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms5C988043D8A5764470713967 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Why my little proggy can't get SIGIO in FreeBSD 3.3-RELEASE, when i type my keyboard? In 2.2.6-RELEASE it works right. #include #include #include #include #include #include #include #include #include #include void rkbd(int sig) { int i,j; u_char b[1024],*c; syslog(LOG_DEBUG,"***** "); i=read(0,b,1024); if(i<0) syslog(LOG_DEBUG,"read failed due to %s",strerror(errno)); else if(!i) syslog(LOG_DEBUG,"read null bites"); else{ b[i]='\0'; puts("\n******"); fputs(b,stdout); puts("******\n"); fflush(stdout); } } int main(int argc,char **argv) { if(fcntl(0,F_SETFL,O_ASYNC)==-1) err(errno,NULL); signal(SIGIO,rkbd); for(;;){ sleep(10); } } --------------ms5C988043D8A5764470713967 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIFlAYJKoZIhvcNAQcCoIIFhTCCBYECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC A8gwggPEMIIDLaADAgECAgEDMA0GCSqGSIb3DQEBBAUAMIGpMQswCQYDVQQGEwJSVTEPMA0G A1UECBMGUnVzc2lhMQ8wDQYDVQQHEwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29t MR8wHQYDVQQLExZFbmdlbmVlcmluZyBEZXBhcnRtZW50MRowGAYDVQQDExFNb2JpbGUgVGVs ZUNvbSBDQTEiMCAGCSqGSIb3DQEJARYTc2V2YUBjYS5tdGVsZWNvbS5ydTAeFw05OTEwMjMw ODM3NDdaFw0wMDEwMjIwODM3NDdaMIGhMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lh MQ8wDQYDVQQHEwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZF bmdlbmVlcmluZyBEZXBhcnRtZW50MRUwEwYDVQQDEwxTZXZhIFNlbWVub3YxHzAdBgkqhkiG 9w0BCQEWEHNldmFAbXRlbGVjb20ucnUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEArb40drlz HavZ+fHM5nifO42IMJKP+IA417y7ODYYMpBzNXak72qMLgAP4QM1I7O54/xAMrCXtba6XEoA IIm/swIDAQABo4IBRDCCAUAwCQYDVR0TBAIwADA7BglghkgBhvhCAQ0ELhYsTW9iaWxlIFRl bGVDb20gT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFJhWSG2bfRBR ceXclK949wSLAIOqMIHWBgNVHSMEgc4wgcuAFMEcgpfRMoe1D3e8GnVKl53QSOhdoYGvpIGs MIGpMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lhMQ8wDQYDVQQHEwZNb3Njb3cxFzAV BgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZFbmdlbmVlcmluZyBEZXBhcnRtZW50 MRowGAYDVQQDExFNb2JpbGUgVGVsZUNvbSBDQTEiMCAGCSqGSIb3DQEJARYTc2V2YUBjYS5t dGVsZWNvbS5ydYIBADANBgkqhkiG9w0BAQQFAAOBgQBuvsNeN8XOWxXdxn7VWC+T90aUWyjF HQGUEvDJruBqD7VyfSpf76x8IAJI+FreUYh0Ra5X8uDUCXfILxkEvLt9xHKFnbU7/Fx4hRXm JD7kiRYPyFf0GhgsUiPfl8ydSfS6tCIwfUwxJokUtOCQi49iOiK7lj1m9Yw5gIu5eCz4XjGC AZQwggGQAgEBMIGvMIGpMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lhMQ8wDQYDVQQH EwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZFbmdlbmVlcmlu ZyBEZXBhcnRtZW50MRowGAYDVQQDExFNb2JpbGUgVGVsZUNvbSBDQTEiMCAGCSqGSIb3DQEJ ARYTc2V2YUBjYS5tdGVsZWNvbS5ydQIBAzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsG CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNOTkxMTIzMjIzODEzWjAeBgkqhkiG9w0BCQ8x ETAPMA0GCCqGSIb3DQMCAgEoMCMGCSqGSIb3DQEJBDEWBBT4oZomgbe/Gp1tyzTK9TUIb2S6 BjANBgkqhkiG9w0BAQEFAARAfl9QTcizdmCYTvzMH5MQuTOXx0orZxnwJ/2rSCyb/ewrRRY3 l5t4JlUMAKepb31T3l6eP3nf5iUM32FM/YJRmA== --------------ms5C988043D8A5764470713967-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 15:17:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 18E4B15458 for ; Tue, 23 Nov 1999 15:17:18 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id PAA17666; Tue, 23 Nov 1999 15:42:52 -0800 (PST) Date: Tue, 23 Nov 1999 15:42:52 -0800 (PST) From: Alfred Perlstein To: Seva "Semenov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in 3.X !!!! In-Reply-To: <383B1755.F432A049@mtelecom.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Seva Semenov wrote: > Why my little proggy can't get SIGIO in FreeBSD 3.3-RELEASE, > when i type my keyboard? > > In 2.2.6-RELEASE it works right. > > > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include > > void > rkbd(int sig) > { > int i,j; > u_char b[1024],*c; > > syslog(LOG_DEBUG,"***** "); > > i=read(0,b,1024); > if(i<0) > syslog(LOG_DEBUG,"read failed due to %s",strerror(errno)); > > else > if(!i) > syslog(LOG_DEBUG,"read null bites"); > else{ > b[i]='\0'; > puts("\n******"); > fputs(b,stdout); > puts("******\n"); > fflush(stdout); > } > } > > int > main(int argc,char **argv) > { > if(fcntl(0,F_SETFL,O_ASYNC)==-1) > err(errno,NULL); > signal(SIGIO,rkbd); > for(;;){ > sleep(10); > } > } i'm not sure why the change happened, but here's a fix: --- sigio.old.c Tue Nov 23 19:18:01 1999 +++ sigio.c Tue Nov 23 19:19:21 1999 @@ -36,7 +36,14 @@ int main(int argc,char **argv) { + int arg; + + arg = getpid(); + + if(fcntl(0,F_SETFL,O_ASYNC)==-1) + err(errno,NULL); + if(fcntl(0,F_SETOWN,arg)==-1) err(errno,NULL); signal(SIGIO,rkbd); for(;;){ unless this is strictly a test program you should be using the constants "STDIN_FILENO" afaik. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 15:30: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sev.mtelecom.ru (host2.mtelecom.ru [212.44.147.2]) by hub.freebsd.org (Postfix) with ESMTP id AD22B15176 for ; Tue, 23 Nov 1999 15:29:56 -0800 (PST) (envelope-from seva@mtelecom.ru) Received: from mtelecom.ru (localhost.mtelecom.ru [127.0.0.1]) by sev.mtelecom.ru (8.9.3/8.9.3) with ESMTP id CAA04943; Wed, 24 Nov 1999 02:29:53 +0300 (MSK) (envelope-from seva@mtelecom.ru) Message-ID: <383B235C.7F4613E1@mtelecom.ru> Date: Wed, 24 Nov 1999 02:29:32 +0300 From: Seva "Semenov" X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fcntl(0,F_SETFL,O_ASYNC) & signal(SIGIO,rkbd); don't work in3.X !!!! References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms6A05663F8DEF72D2183F2B5D" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms6A05663F8DEF72D2183F2B5D Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Great!!!! Thanx... > i'm not sure why the change happened, but here's a fix: > > --- sigio.old.c Tue Nov 23 19:18:01 1999 > +++ sigio.c Tue Nov 23 19:19:21 1999 > @@ -36,7 +36,14 @@ > int > main(int argc,char **argv) > { > + int arg; > + > + arg = getpid(); > + > + > if(fcntl(0,F_SETFL,O_ASYNC)==-1) > + err(errno,NULL); > + if(fcntl(0,F_SETOWN,arg)==-1) > err(errno,NULL); > signal(SIGIO,rkbd); > for(;;){ > > unless this is strictly a test program you should be using > the constants "STDIN_FILENO" afaik. > > -Alfred --------------ms6A05663F8DEF72D2183F2B5D Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIFlAYJKoZIhvcNAQcCoIIFhTCCBYECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC A8gwggPEMIIDLaADAgECAgEDMA0GCSqGSIb3DQEBBAUAMIGpMQswCQYDVQQGEwJSVTEPMA0G A1UECBMGUnVzc2lhMQ8wDQYDVQQHEwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29t MR8wHQYDVQQLExZFbmdlbmVlcmluZyBEZXBhcnRtZW50MRowGAYDVQQDExFNb2JpbGUgVGVs ZUNvbSBDQTEiMCAGCSqGSIb3DQEJARYTc2V2YUBjYS5tdGVsZWNvbS5ydTAeFw05OTEwMjMw ODM3NDdaFw0wMDEwMjIwODM3NDdaMIGhMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lh MQ8wDQYDVQQHEwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZF bmdlbmVlcmluZyBEZXBhcnRtZW50MRUwEwYDVQQDEwxTZXZhIFNlbWVub3YxHzAdBgkqhkiG 9w0BCQEWEHNldmFAbXRlbGVjb20ucnUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEArb40drlz HavZ+fHM5nifO42IMJKP+IA417y7ODYYMpBzNXak72qMLgAP4QM1I7O54/xAMrCXtba6XEoA IIm/swIDAQABo4IBRDCCAUAwCQYDVR0TBAIwADA7BglghkgBhvhCAQ0ELhYsTW9iaWxlIFRl bGVDb20gT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFJhWSG2bfRBR ceXclK949wSLAIOqMIHWBgNVHSMEgc4wgcuAFMEcgpfRMoe1D3e8GnVKl53QSOhdoYGvpIGs MIGpMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lhMQ8wDQYDVQQHEwZNb3Njb3cxFzAV BgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZFbmdlbmVlcmluZyBEZXBhcnRtZW50 MRowGAYDVQQDExFNb2JpbGUgVGVsZUNvbSBDQTEiMCAGCSqGSIb3DQEJARYTc2V2YUBjYS5t dGVsZWNvbS5ydYIBADANBgkqhkiG9w0BAQQFAAOBgQBuvsNeN8XOWxXdxn7VWC+T90aUWyjF HQGUEvDJruBqD7VyfSpf76x8IAJI+FreUYh0Ra5X8uDUCXfILxkEvLt9xHKFnbU7/Fx4hRXm JD7kiRYPyFf0GhgsUiPfl8ydSfS6tCIwfUwxJokUtOCQi49iOiK7lj1m9Yw5gIu5eCz4XjGC AZQwggGQAgEBMIGvMIGpMQswCQYDVQQGEwJSVTEPMA0GA1UECBMGUnVzc2lhMQ8wDQYDVQQH EwZNb3Njb3cxFzAVBgNVBAoTDk1vYmlsZSBUZWxlQ29tMR8wHQYDVQQLExZFbmdlbmVlcmlu ZyBEZXBhcnRtZW50MRowGAYDVQQDExFNb2JpbGUgVGVsZUNvbSBDQTEiMCAGCSqGSIb3DQEJ ARYTc2V2YUBjYS5tdGVsZWNvbS5ydQIBAzAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsG CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNOTkxMTIzMjMyOTMyWjAeBgkqhkiG9w0BCQ8x ETAPMA0GCCqGSIb3DQMCAgEoMCMGCSqGSIb3DQEJBDEWBBQBZ5q7yWUAWmS4NJcWjk5mc8zy GjANBgkqhkiG9w0BAQEFAARAKgyxeRZSUeuLR58wCbvLRTPU0cXC/GLRR0qqhBqr0J0PPOa0 cxT/o1F4UWrOqnkUq6BZkWw2dT6i2LvCMishLQ== --------------ms6A05663F8DEF72D2183F2B5D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 16:11:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 2DF9014D96 for ; Tue, 23 Nov 1999 16:11:38 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id QAA00671 for ; Tue, 23 Nov 1999 16:11:34 -0800 (PST) To: freebsd-hackers@freebsd.org Subject: gdb and ELF shared libraries Date: Tue, 23 Nov 1999 16:11:34 -0800 Message-ID: <669.943402294@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears to me that the gdb 4.18 port on FreeBSD 3.3 doesn't provide support for ELF shared libraries. Am I correct about that, or did I just snag myself on some obscure gdb bug that was masquerading as ELF shared library non-support? Anyway, assuming that my supposition is correct, and that gdb 4.18 on FreeBSD does not yet support debugging of ELF shared libraries, I'd like to maybe take a whack at making it do that. (I've worked on gdb and gcc before, and have pretty good knowledge of ELF, so I think that I could actually make a useful contribution here.) But I have a first-order problem to overcome first. I can't even get the gnu gdb 4.18 source tree to build on FreeBSD 3.3. It craps out while trying to compile the file solib.c. (And looking at DejaNews, I see that I am not the only person who has run into this problem, so I know that it's not just me.) So will somebody please tell me the trick to get past these compile-time problems with solib.c? Obviously, *somebody* knows how to get past them, because FreeBSD 3.3 ships with a binary of gdb 4.18 and that *does* kinda sorta work. So how was that built, and who built it? Where are the patches that were used to make it build? P.S. I already wrote to David Greenman and asked him who is the current maintainer of the FreeBSD port for gdb, but he didn't respond. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 16:32:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from casper.spirit.net.au (cas240.act.spirit.net.au [203.63.240.3]) by hub.freebsd.org (Postfix) with ESMTP id 7AA7315183 for ; Tue, 23 Nov 1999 16:32:26 -0800 (PST) (envelope-from bryan@casper.spirit.net.au) Received: (from bryan@localhost) by casper.spirit.net.au (8.9.3/8.8.5) id LAA73130 for freebsd-hackers@freebsd.org; Wed, 24 Nov 1999 11:30:21 +1100 (EST) From: Bryan Collins Message-Id: <199911240030.LAA73130@casper.spirit.net.au> Subject: more softpower/apm.. To: freebsd-hackers@freebsd.org Date: Wed, 24 Nov 1999 11:30:21 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Does anyone know if its possible for FreeBSD to execute a halt from the powerswitch? From reading the apmd doco, this is what apmd is suppose to do, handle events from the APM bios and execute according to apmd.conf If an ATX powersupply/motherboard is setup to suspend on power button, (i.e hold down for 5 seconds to turn off) can FreeBSD pick up this button press and do clean shutdown? I tried running apmd -dv, but I cant seem to see any events from the power button pressing. Thanks Bry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 23 21: 4: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 2DD14154FE; Tue, 23 Nov 1999 21:03:53 -0800 (PST) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga@puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.9.3/8.9.3) with ESMTP id TAA23700; Tue, 23 Nov 1999 19:33:07 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <383B70ED.E6DC31AE@mauibuilt.com> Date: Tue, 23 Nov 1999 19:00:29 -1000 From: Richard Puga X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: sorry about the vinum comment. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to apologise for the missleading comment I made about vinum and using 4 18 gig drives with vinum. In teaching myself the software I have been using 4 18 gig drives in serveral configurations including striping, striping/mirroring and raid 5. in each situation I had to wait a long time to init the volumes and newfs because of their great size. I also took drives out of the vinum volume to simulate failures so that I could learn how to restore from failure. I have had no problems with vinum using mirroring or striping. In fact I am impressed with the speed. the only problems I have had were with raid 5 and doccumented on the vinum web site. Again I did not mean to imply there was a problem with vinum or using 18 gig drives with it. Richard Puga puga@Mauibuilt.com (missleading comment) > > PS; anyone thinking of playing with vinum I suggest you dont start out > > with 4 18 gig drives ..:) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 0:47: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 9ED9914D3F for ; Wed, 24 Nov 1999 00:47:01 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id JAA14650 for freebsd-hackers@FreeBSD.ORG; Wed, 24 Nov 1999 09:45:06 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id JAA26371 for freebsd-hackers@FreeBSD.ORG; Wed, 24 Nov 1999 09:30:50 +0100 (MET) From: Juergen Lock Date: Wed, 24 Nov 1999 09:30:50 +0100 To: freebsd-hackers@FreeBSD.ORG Subject: HP Cascade driver (100VG-AnyLan) Message-ID: <19991124093050.A25384@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is based on Joerg's work (joerg@FreeBSD.ORG, and the linux version of course), my current version only is for -stable and it has only been tested with a J2585B card, but yesterday it got nearly 3MB/sec copying off a nt box (and i guess the limitation here is nt's filesystem) and it no longer seems to cause panics. What I still haven't figured out is why with about half of the packets it receives it doesn't get the first long (contains the packet size and flags), joerg already found a workaround for that but what makes me wonder is that neither the linux version nor a DOS packet driver which i also took a quick look at seem to need anything like that. Oh and it also doesn't (yet?) do DMA. If anyone wants to help i can mail my current version... (its in my local cvs tree so if you want the cvs files instead just say so.) Thanx and Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 2:30:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2948C15125; Wed, 24 Nov 1999 02:30:01 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id CAA81013; Wed, 24 Nov 1999 02:29:57 -0800 (PST) Date: Wed, 24 Nov 1999 02:29:57 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: <19991122185220.D301@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly there is some threads discussion going on in -arch so I'm going to really reply to this over there.. This is just redirector mail julian On Mon, 22 Nov 1999, Jason Evans wrote: > Walnut Creek has hired me as a full time employee to work primarily on > improving and expanding FreeBSD's threads support. This is very exciting > to me, and I hope my work will be of benefit the FreeBSD community. > [chop] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 9:20:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-47.cpinternet.com [208.149.16.47]) by hub.freebsd.org (Postfix) with ESMTP id F0BF21501B for ; Wed, 24 Nov 1999 09:19:19 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id LAA70407; Wed, 24 Nov 1999 11:19:08 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 24 Nov 1999 11:19:07 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: hackers@freebsd.org Subject: 'door' calls X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14396.7572.75335.23959@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the closest approximation to a Solaris door call in FreeBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 13:50:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 142AC152EE for ; Wed, 24 Nov 1999 13:50:20 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id QAA07128 for hackers@freebsd.org; Wed, 24 Nov 1999 16:48:15 -0500 (EST) (envelope-from mwlucas) Message-Id: <199911242148.QAA07128@blackhelicopters.org> Subject: Request for Article Review To: hackers@freebsd.org Date: Wed, 24 Nov 1999 16:48:15 -0500 (EST) From: mwlucas@gltg.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm writing an article for Sys Admin magazine called "FreeBSD for the System V/Linux administrator." Sadly, my usual SysV/Linux guru has been wholly consumed by the randomly ravenous monster that is independent consulting. I'm hereby putting out a plea for vaguely literate people who can give this article a technical review from both the FreeBSD side, and the SysV side. I'd especially appreciate anyone who switched to FreeBSD somewhat recently, or who administers both SysV/Linux and FreeBSD. The article is aimed at the competent SysV/Linux admin who needs to administer a FreeBSD box. It covers basic things like, where do you set system defaults, ports & packages, kernel compilation, and getting help. It's only about 2k words long. The catch is, they want a finished article by next Wednesday. I'd need any commentary by Monday night. I only need (at most) two or three people, so please don't feel bad if my mailbox gets flooded and I say "no, thanks"; it's not personal. (Having said this, of course, the innate perversity of the universe will make me get no replies. ;) There is no guarantee that this article will be accepted; they approved the proposal, but they can decide to kill it upon delivery. Such is the life of the freelance writer. If it is accepted, it will appear in the March issue. Thanks, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 14:11:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 468A5154D2 for ; Wed, 24 Nov 1999 14:11:26 -0800 (PST) (envelope-from partha@cs.duke.edu) Received: from mackerel.cs.duke.edu (mackerel.cs.duke.edu [152.3.140.156]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA15286; Wed, 24 Nov 1999 17:10:54 -0500 (EST) Received: from localhost (partha@localhost) by mackerel.cs.duke.edu (8.8.5/8.6.9) with ESMTP id RAA23758; Wed, 24 Nov 1999 17:10:51 -0500 (EST) X-Authentication-Warning: mackerel.cs.duke.edu: partha owned process doing -bs Date: Wed, 24 Nov 1999 17:10:51 -0500 (EST) From: "Parthasarathy M. Aji" To: freebsd-hackers@FreeBSD.ORG Cc: Kirill Komarov Subject: Redirection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, We are doing packet redirection. The client sends packets through our node to a given server. The server contents are replicated in 2 other servers. We want to redirect new syn packets from the client to a specific server in a round robin fashion. Here 's typical scenarion, let the client's ip address be, C1 and let the three replicated servers have ip addresses S1,S2 and S3. and let us say that the client and the world knows only about the existence of S1. Our program will reside on an intermediate node between C1 and S1 such that every packet sent by C1 to S1 will pass through our program. Now what we want to do is, when ever a new connection requested from the client (it sends syn packet) to S1, we redirect the destination address of the packet to S2 and S3 in a round robin fashion. Similarly when we receive data back from server S2 we change the destination address of the S2 packet to our clien C1t.. Now here's the problem... We seem to have recomputd the check sum and changed the destination address correclty when the client sends the syn packet to the server, but the problem is when the server sends an ack back (in the 3 way handshake) the client is not able to accept it. here's the TCP dump output which was run on the server cricket.. cricket is the client hugo is the server to which we redirected the client syn packet. for some reason cricket is not able to accept the syn+ack from hugo.. 16:19:30.524349 cricket.cs.duke.edu.1048 > hugo.cs.duke.edu.telnet: S 1156355247:1156355247(0) win 65535 (DF) [tos 0x10] 16:19:30.524349 hugo.cs.duke.edu.telnet > cricket.cs.duke.edu.1048: S 872384000:872384000(0) ack 1156355248 win 33580 (DF) 16:19:31.231553 hugo.cs.duke.edu.telnet > cricket.cs.duke.edu.1048: S 872384000:872384000(0) ack 1156355248 win 33580 (DF) 16:19:33.261917 cricket.cs.duke.edu.1048 > hugo.cs.duke.edu.telnet: S 1156355247:1156355247(0) win 65535 (DF) [tos 0x10] 16:19:33.261917 hugo.cs.duke.edu.telnet > cricket.cs.duke.edu.1048: S 872384000:872384000(0) ack 1156355248 win 33580 (DF) 16:19:36.231575 hugo.cs.duke.edu.telnet > cricket.cs.duke.edu.1048: S 872384000:872384000(0) ack 1156355248 win 33580 (DF) 16:19:42.231668 hugo.cs.duke.edu.telnet > cricket.cs.duke.edu.1048: S 872384000:872384000(0) ack 1156355248 win 33580 (DF) 16:19:42.231668 cricket.cs.duke.edu.1048 > hugo.cs.duke.edu.telnet: R 1156355248:1156355248(0) win 0 Partha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 15:15:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 47A9714EA9 for ; Wed, 24 Nov 1999 15:15:24 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id RAA00460 for ; Wed, 24 Nov 1999 17:13:06 -0600 (CST) Message-Id: <199911242313.RAA00460@chiba.3jane.net> To: freebsd-hackers@freebsd.org Subject: porting question MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <457.943485185.1@chiba.3jane.net> Date: Wed, 24 Nov 1999 17:13:05 -0600 From: "Damon M. Conway" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i'm interested in porting some linux apps to freebsd to help me start learning c better. i think my first project is to port mnemonic to freebsd. i was wondering if there is a good resource that describes the differences between glibc2.1 and the libc that freebsd uses. i have a feeling i'm going to be searching through the sources to find similar functionality between them, but i thought i'd ask first. thanks, damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 15:32:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 089AF15063 for ; Wed, 24 Nov 1999 15:32:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01211; Wed, 24 Nov 1999 15:22:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911242322.PAA01211@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Damon M. Conway" Cc: freebsd-hackers@freebsd.org Subject: Re: porting question In-reply-to: Your message of "Wed, 24 Nov 1999 17:13:05 CST." <199911242313.RAA00460@chiba.3jane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Nov 1999 15:22:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi, i'm interested in porting some linux apps to freebsd to help me start > learning c better. i think my first project is to port mnemonic to > freebsd. i was wondering if there is a good resource that describes the > differences between glibc2.1 and the libc that freebsd uses. i have a > feeling i'm going to be searching through the sources to find similar > functionality between them, but i thought i'd ask first. glibc and the FreeBSD C library are basically meant to cover the same things. Unfortunately, glibc suffers from the "kitchen sink" syndrome. As a general rule, once you've ported to FreeBSD, the code should still build on Linux, and you'll have a much more portable result. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 15:56:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id A945C1520C for ; Wed, 24 Nov 1999 15:56:15 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id AAA46119; Thu, 25 Nov 1999 00:56:19 +0100 (CET) (envelope-from assar) To: alk@pobox.com Cc: hackers@FreeBSD.ORG Subject: Re: 'door' calls References: <14396.7572.75335.23959@avalon.east> From: Assar Westerlund Date: 25 Nov 1999 00:56:18 +0100 In-Reply-To: Anthony Kimball's message of "Wed, 24 Nov 1999 11:19:07 -0600 (CST)" Message-ID: <5lpuwzo34t.fsf@foo.sics.se> Lines: 6 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony Kimball writes: > What is the closest approximation to a Solaris door call in FreeBSD? Create a unix socket and send messages over that. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 16:14:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 9724514F3E for ; Wed, 24 Nov 1999 16:14:28 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 6821 invoked by uid 1000); 25 Nov 1999 00:29:00 -0000 Date: Thu, 25 Nov 1999 01:29:00 +0100 From: Andreas Braukmann To: freebsd-hackers@freebsd.org Subject: MCA-support - IBM PS/2 Model 70 to be donated? Message-ID: <19991125012900.Y34446@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, ... I'm in the process of putting my hands on an elderly IBM PS/2 Model 70 machine. The machine was duty as a very reliable and stable Netware server for many many years and was retired just a few weeks ago. It contains: the base-unit ;) i486 8 MByte RAM VGA graphics on-board SCSI hostadapter 2 * ca. 200 MByte SCSI harddisks additional Adaptec 1640 (formerly used for an external DDS-drive) SMC NIC If I'll eventually be able to 'aquire' the beast, I would like to loan (or even donate) the machine to the FreeBSD MCA effort. There's only one problem: ... the transportation to the development- team. Currently the machine is located in Germany (near Muenster). Any interest? ... then contact me ... Regards, Andreas -- : TSE GmbH Neue Medien : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 17:25: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 3B887150D5; Wed, 24 Nov 1999 17:24:59 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id UAA24178; Wed, 24 Nov 1999 20:23:40 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199911250123.UAA24178@spoon.beta.com> To: freebsd-stable@cisco.com, hackers@freebsd.org, questions@freebsd.org Subject: QA ramping up... Date: Wed, 24 Nov 1999 20:23:40 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the cross-post, but I expect that this will have multiple audiences. Based on a lot of messages traveling in the -stable mailing list, we're once again looking at putting together some volunteers to do QA on the upcoming 3.4 release, as well as working on testing new features and replicating/debugging bugs. If you're interested in helping out, drop me a line. I'm trying to get some initial coordination set up by the end of this weekend, so we can be ready to go around December 1st, which is when Jordan has been discussing having the first release candidate ready. The real requirements are that a.) you're willing to give the time (this is the biggest), b.) you have a reasonably speeded internet connection (you have to be able to turn over a release candidate in 4-6 hours - and they'll be between 200-600MBs), and you have some hardware to use for testing. For everyone else, this is a heads up that we're trying to get the project under way. We have about a half a dozen people who have offered to help out, so we should be off to a good start. More to follow as there is more to announce. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 17:29:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 697A61554C; Wed, 24 Nov 1999 17:29:16 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id AAA28968; Wed, 24 Nov 1999 00:25:15 GMT (envelope-from nik) Date: Wed, 24 Nov 1999 00:25:15 +0000 From: Nik Clayton To: current@freebsd.org Cc: hackers@freebsd.org Subject: Re: Threads and my new job. Message-ID: <19991124002515.A28472@catkin.nothing-going-on.org> References: <19991122185220.D301@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991122185220.D301@sturm.canonware.com>; from Jason Evans on Mon, Nov 22, 1999 at 06:52:20PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason, On Mon, Nov 22, 1999 at 06:52:20PM -0800, Jason Evans wrote: > Walnut Creek has hired me as a full time employee to work primarily on > improving and expanding FreeBSD's threads support. This is very exciting > to me, and I hope my work will be of benefit the FreeBSD community. That's great. Is it part of your remit to maintain http://www.FreeBSD.org/threads/? That URL doesn't exist at the moment, but if we're going to have an active threads project, it probably should. Are you (or anyone else reading this, you don't have to be a committer at the moment) interested in keeping this section up to date? N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 19: 6:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id EF59915002; Wed, 24 Nov 1999 19:06:41 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA03095; Thu, 25 Nov 1999 12:06:40 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id MAA06625; Thu, 25 Nov 1999 12:06:40 +0900 (JST) Date: Thu, 25 Nov 1999 12:06:40 +0900 (JST) Message-Id: <199911250306.MAA06625@lavender.yy.cs.keio.ac.jp> To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Threads and my new job. In-Reply-To: Your message of "Tue, 23 Nov 1999 11:52:20 JST". <19991122185220.D301@sturm.canonware.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jasone@canonware.com wrote: >> *) Lacking interfaces, such as pthread_cancel() (mentioned specifically in >> PR bin/7587) need to be implemented. It's good news for me. I hope to port xmovie -- QuickTime movie Player for Linux to FreeBSD. But I can not compile it under FreeBSD, because it's need pthread_cancel. xmovie http://heroine.linuxbox.com/xmovie.html MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 24 21:40: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 5C9E314D07 for ; Wed, 24 Nov 1999 21:40:00 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA23513; Thu, 25 Nov 1999 00:38:22 -0500 (EST) Date: Thu, 25 Nov 1999 00:38:22 -0500 (EST) From: "Matthew N. Dodd" To: Andreas Braukmann Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: MCA-support - IBM PS/2 Model 70 to be donated? In-Reply-To: <19991125012900.Y34446@paert.tse-online.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm the only MCA developer at this point so I guess you're talking to me. (Unless someone else wants to step up and lend a hand. :) On Thu, 25 Nov 1999, Andreas Braukmann wrote: > ... I'm in the process of putting my hands on an elderly > IBM PS/2 Model 70 machine. The machine was duty as > a very reliable and stable Netware server for many many years and > was retired just a few weeks ago. > It contains: > the base-unit ;) > i486 > 8 MByte RAM > VGA graphics I've got some problems to work out with the keyboard controller before the graphics console is of much use. > on-board SCSI hostadapter This isn't supported. > 2 * ca. 200 MByte SCSI harddisks > additional Adaptec 1640 (formerly used for an external DDS-drive) The Adaptec is supported. I have my m77 dual booting DOS and FreeBSD right now; DOS is on the onboard SCSI and FreeBSD is on a disk hanging off the Adaptec. > SMC NIC I've got a bus front end that currently has problems; this may be due to the card being broken but is most likely due to something I've missed. I need to pull the card and replace it, and test the front end with a WD8013/A. Is your card an 8003 or an 8013? > If I'll eventually be able to 'aquire' the beast, I would like to > loan (or even donate) the machine to the FreeBSD MCA effort. That probably isn't needed; I have more than enough hardware at this point. (I'll put up a picture of my MCA card collection at some point just to prove it.) What I do need are testers. Get the machine and compile an MCA kernel for it; copy to the boot disks and try installing. I should probably update LINT and GENERIC since the MCA support is somewhat usable at this point. Thanks for the offer of hardware though! -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 25 8: 4:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 85D0C14E66 for ; Thu, 25 Nov 1999 08:04:49 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA09400 for hackers@freebsd.org; Thu, 25 Nov 1999 11:04:48 -0500 (EST) (envelope-from mwlucas) Message-Id: <199911251604.LAA09400@blackhelicopters.org> Subject: Request for Article Review -- enough, thanks! To: hackers@freebsd.org Date: Thu, 25 Nov 1999 11:04:48 -0500 (EST) From: mwlucas@gltg.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Yesterday I sent out a request for article reviewers. Much to my surprise, my mailbox has been completely choked with offers from around the world. Anyway, I'm all set. Thanks to everyone. With luck, you'll see the article in March's issue of Sys Admin. Regards, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 25 10:35:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hejira.hunter.cuny.edu (hejira.hunter.cuny.edu [146.95.128.97]) by hub.freebsd.org (Postfix) with ESMTP id 9CABE14BCD for ; Thu, 25 Nov 1999 10:35:08 -0800 (PST) (envelope-from jpenney@hejira.hunter.cuny.edu) Received: from hejira (hejira [146.95.128.97]) by hejira.hunter.cuny.edu (8.9.3/8.9.3) with ESMTP id NAA17777 for ; Thu, 25 Nov 1999 13:37:35 -0500 (EST) Date: Thu, 25 Nov 1999 13:37:35 -0500 (EST) From: JP To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 25 11: 6:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 6472414CBF for ; Thu, 25 Nov 1999 11:06:22 -0800 (PST) (envelope-from fanf@demon.net) Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id TAA03235; Thu, 25 Nov 1999 19:06:19 GMT Received: from fanf by fanf.eng.demon.net with local (Exim 3.03 #2) id 11r4Cg-00050F-00; Thu, 25 Nov 1999 19:05:14 +0000 To: dillon@apollo.backplane.com, hackers@freebsd.org From: Tony Finch Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: <199911181700.JAA85880@apollo.backplane.com> References: Message-Id: Date: Thu, 25 Nov 1999 19:05:14 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > The solution Apache takes is to surround the accept() with a file lock > so only one process blocks in accept() at any given point (the file lock > uses wakeup_one and is safe). Apache doesn't lock accept() if there's only one listening socket. (Look for the #define SINGLE_LISTEN_UNSERIALIZED_ACCEPT in apache-1.3/src/include/ap_config.h) > The solution that I took with BestWWWD was to have just one process > accept all the connections and then have it dole the descriptor out to the > appropriate sub-processes over a unix-domain socket. Demon has a large server based on thttpd running on IRIX. One of the changes that was made to thttpd was to fork the server several times to get some parallelism for disk operations. When I came to port the code to FreeBSD I found that it worked fine as it was on a UP machine, but on an SMP machine when a connection came in two processes would symultaneously wake up from select() then try to accept() the connection; one would succeed and one would block and snarl up a load of other connections. My solution was the same as Matt's :-) (I'm not happy about the extra context switching that it requires but I was more interested in working code than performance; I haven't benchmarked it.) Tony. -- i am the dot at dotat dot at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 25 23: 1:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web2103.mail.yahoo.com (web2103.mail.yahoo.com [128.11.68.247]) by hub.freebsd.org (Postfix) with SMTP id EC16314D93 for ; Thu, 25 Nov 1999 23:01:29 -0800 (PST) (envelope-from kyky_2000@yahoo.com) Message-ID: <19991126070128.27934.rocketmail@web2103.mail.yahoo.com> Received: from [216.88.74.7] by web2103.mail.yahoo.com; Thu, 25 Nov 1999 23:01:28 PST Date: Thu, 25 Nov 1999 23:01:28 -0800 (PST) From: Kyky Effe Subject: Email To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last couple days, I could not sent nor recieve email from outside server(Internet) but I can recieve email from any other server in the domain(local). Is it possible that the network administrator put firewall so that my server cannot send or recieve email?(external problems) Or Is it somethiing wrong with the configuration?(internal problems) ------ I made a special directory that have all the avaiable commands for the user, so the user cannot acces "/bin /sbin /usr/bin /usr/sbin etc..." but I made copy all the necesary files to the directory where users can access it(/home/commands). thank you Kyky_2000 __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 10:52:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 37BFF1519E; Fri, 26 Nov 1999 10:52:20 -0800 (PST) (envelope-from intmktg@CAM.ORG) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id NAA13336; Fri, 26 Nov 1999 13:51:50 -0500 Date: Fri, 26 Nov 1999 13:51:50 -0500 (EST) From: Marc Tardif To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: disassembling syscalls Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can syscalls be disassembled on BSD? So far, I tried using ktrace -tc on compiled code using the syscall I wanted, but the output from kdump doesn't look like asm. I also tried using gdb directly, compiling the source with the -g and -static flags, but I couldn't use the disassemble command on the syscall which appeared in the output of 'disassemble main'. Any suggestions would be greatly appreciated, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 10:57:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pernet.net (mail.pernet.net [205.229.0.40]) by hub.freebsd.org (Postfix) with ESMTP id 18B3014BC7 for ; Fri, 26 Nov 1999 10:57:53 -0800 (PST) (envelope-from dimwit@pernet.net) Received: from deadpixi.pernet.net (deadpixi.pernet.net [205.229.0.243]) by mail.pernet.net (8.9.1a/8.9.1) with ESMTP id MAA28411 for ; Fri, 26 Nov 1999 12:57:53 -0600 (CST) Date: Fri, 26 Nov 1999 12:57:52 -0600 (CST) From: Rob King X-Sender: jking@deadpixi.pernet.net Reply-To: dimwit@pernet.net To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm writing a server that multiplexes a MySQL connection to several clients. Since the connection has to be shared, I can't fork(), I have to thread. This isn't a problem, except that when I accept() and assign a socket descriptor, the first thread runs fine, but the next thread simply grabs the descriptor (since it's shared) from the previous thread and starts doing all its writing to that socket. Any idea how to get around this? If there's any good example code, please let me know. Thanks, Rob -- dimwit@pernet.net http://ota.pernet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 11: 3:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 58C361510F; Fri, 26 Nov 1999 11:03:08 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991126140306.21678@mojave.sitaranetworks.com> Date: Fri, 26 Nov 1999 14:03:06 -0500 From: Greg Lehey To: Marc Tardif , freebsd-hackers@FreeBSD.ORG Subject: Re: disassembling syscalls Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Marc Tardif on Fri, Nov 26, 1999 at 01:51:50PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removing -questions; this is a technical question] On Friday, 26 November 1999 at 13:51:50 -0500, Marc Tardif wrote: > How can syscalls be disassembled on BSD? > > So far, I tried using ktrace -tc on compiled code using the syscall I > wanted, but the output from kdump doesn't look like asm. I also tried > using gdb directly, compiling the source with the -g and -static flags, > but I couldn't use the disassemble command on the syscall which appeared > in the output of 'disassemble main'. I'm not sure what you want to do here. Use a debugger for disassembly. But what do you really want to do? And what do you mean by 'syscall'? The userland stub function, the interface, or the kernel code which implements the call? In any case, since we have the source code to all of it, it's not clear that there's much to be gained by disassembling them. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 11:18:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id D5947154AE; Fri, 26 Nov 1999 11:18:45 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id LAA66703; Fri, 26 Nov 1999 11:18:32 -0800 (PST) To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: disassembling syscalls In-reply-to: Your message of Fri, 26 Nov 1999 13:51:50 -0500. Date: Fri, 26 Nov 1999 11:18:32 -0800 Message-ID: <66701.943643912@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrote : >How can syscalls be disassembled on BSD? > >So far, I tried using ktrace -tc on compiled code using the syscall I >wanted, but the output from kdump doesn't look like asm. I also tried >using gdb directly, compiling the source with the -g and -static flags, >but I couldn't use the disassemble command on the syscall which appeared >in the output of 'disassemble main'. GDB disassembles stuff. As far as I know, that functionality works. What do you mean when you say that you ``couldn't use the disassemble command''. Why couldn't you? (Carpal tunnel finally getting to you perhaps? :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 11:21: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pernet.net (mail.pernet.net [205.229.0.40]) by hub.freebsd.org (Postfix) with ESMTP id 2AFDD154C2 for ; Fri, 26 Nov 1999 11:20:54 -0800 (PST) (envelope-from dimwit@pernet.net) Received: from deadpixi.pernet.net (deadpixi.pernet.net [205.229.0.243]) by mail.pernet.net (8.9.1a/8.9.1) with ESMTP id NAA01287 for ; Fri, 26 Nov 1999 13:20:53 -0600 (CST) Date: Fri, 26 Nov 1999 13:20:52 -0600 (CST) From: Rob King X-Sender: jking@deadpixi.pernet.net Reply-To: dimwit@pernet.net To: freebsd-hackers@freebsd.org Subject: PThreads and Sockets Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm writing a server that multiplexes a MySQL connection to several clients. Since the connection has to be shared, I can't fork(), I have to thread. This isn't a problem, except that when I accept() and assign a socket descriptor, the first thread runs fine, but the next thread simply grabs the descriptor (since it's shared) from the previous thread and starts doing all its writing to that socket. Any idea how to get around this? If there's any good example code, please let me know. Thanks, Rob -- dimwit@pernet.net http://ota.pernet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 11:31:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 6AF4B1592F; Fri, 26 Nov 1999 11:31:40 -0800 (PST) (envelope-from intmktg@CAM.ORG) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id OAA13634; Fri, 26 Nov 1999 14:31:05 -0500 Date: Fri, 26 Nov 1999 14:31:05 -0500 (EST) From: Marc Tardif To: "Ronald F. Guilmette" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: disassembling syscalls In-Reply-To: <66701.943643912@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On FreeBSD 2.2.5 (I know I should change, but it works), gcc 2.7.2.1, gdb 4.16, typing 'disassemble syscall_as_seen_in_main' I get: No function contains specified address. Using the same procedure on FreeBSD 3.3-RELEASE, gcc 2.7.2.3, gdb 4.18, I get some output which is shorter than I expected, but I'll probably have to trace through more calls and branches. By the way, how can I trace names which start with a period? they sometime appear when I type 'disassemble' followed by a tab, but typing the name with and without the period doesn't work either. On Fri, 26 Nov 1999, Ronald F. Guilmette wrote: > > In message , you wrote > : > > >How can syscalls be disassembled on BSD? > > > >So far, I tried using ktrace -tc on compiled code using the syscall I > >wanted, but the output from kdump doesn't look like asm. I also tried > >using gdb directly, compiling the source with the -g and -static flags, > >but I couldn't use the disassemble command on the syscall which appeared > >in the output of 'disassemble main'. > > GDB disassembles stuff. > > As far as I know, that functionality works. > > What do you mean when you say that you ``couldn't use the disassemble > command''. Why couldn't you? (Carpal tunnel finally getting to you > perhaps? :-) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 11:37:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 73904150C2; Fri, 26 Nov 1999 11:37:05 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id SAA49129; Thu, 25 Nov 1999 18:58:04 GMT (envelope-from joe) Date: Thu, 25 Nov 1999 18:58:04 +0000 From: Josef Karthauser To: Warner Losh Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: VAIO F270, ep0 and -current Message-ID: <19991125185803.F93499@florence.pavilion.net> References: <19991119172025.A97321@florence.pavilion.net> <19991118192338.D55314@florence.pavilion.net> <19991117143759.A3011@spirit.jaded.net> <19991118192338.D55314@florence.pavilion.net> <199911182135.OAA28043@harmony.village.org> <19991119172025.A97321@florence.pavilion.net> <199911191740.KAA33661@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199911191740.KAA33661@harmony.village.org> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 19, 1999 at 10:40:19AM -0700, Warner Losh wrote: > In message <19991119172025.A97321@florence.pavilion.net> Josef Karthauser writes: > : If you can give me some clues I'll work on it. I've got zero familiarity > : with the code :(. > [..] > Somewhere in the above, something goes wrong :-(. Maybe it is the > first parenthetical statement about waiting for the spl to be > lowered, which would be something like: > > /* > * disable_slot - Disables the slot by removing > * the power and unmapping the I/O > */ > static void real_disable_slot(struct slot *slt); > static void > disable_slot(struct slot *slt) > { > slt->poff_ch = timeout(real_disable_slot, (caddr_t) slot, 0); > } > > static void > real_disable_slot(struct slot *slt) > { > // guts of the old disable_slot goes here > } > > but there may be some more complicated book keeping needed... This didn't help. Interestingly if I unplug the network card and wait a while (minutes) and then suspend it hangs, however if I _never_ put the card in in the first place susspend works fine. I believe that the suspend is a read herring, and what actually happen is that the card doesn't detatch properly. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 12:10:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 8DC2415112; Fri, 26 Nov 1999 12:10:49 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id MAA66902; Fri, 26 Nov 1999 12:01:00 -0800 (PST) To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: disassembling syscalls In-reply-to: Your message of Fri, 26 Nov 1999 14:31:05 -0500. Date: Fri, 26 Nov 1999 12:01:00 -0800 Message-ID: <66900.943646460@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrote : >On FreeBSD 2.2.5 (I know I should change, but it works), gcc 2.7.2.1, gdb >4.16, typing 'disassemble syscall_as_seen_in_main' I get: >No function contains specified address. What the heck is "syscall_as_seen_in_main"? (Sorry if I'm ignorant, but I have no idea what that stands for.) >Using the same procedure on FreeBSD 3.3-RELEASE, gcc 2.7.2.3, gdb 4.18, I >get some output which is shorter than I expected, but I'll probably have >to trace through more calls and branches. > >By the way, how can I trace names which start with a period? What do you mean by ``trace''? >they sometime >appear when I type 'disassemble' followed by a tab, but typing the name >with and without the period doesn't work either. Symbols that begin with periods are used for various things, some of which are NOT things that you can set breakpoints on (or disassemble, or whatever). For example ELF *section names* (e.g. .text) begin with periods, but section names are not things that you can set breakpoints on. Some versions of gcc (for some targets) also create regular symbols which begin with periods, but these are just so-called ``local'' symbols. Depending upon the assembler in use, they may or may not still be known in the binary object files and/or in the final executable file. If you have loaded something into gdb and then disassembled a part of it and if you see some symbol in the disassembled code that begins with a period, then you _may_ perhaps be able to get its address by just doing: print &.foo (where `.foo' is the symbol), but then again, maybe not. Actually, I think that gdb will probably not allow you to do this because its built-in expression parser only understands higher-level language syntax (e.g. for C and/or C++) and in either C or C++, the expression &.foo has invalid syntax. So you may just have to find the address of whatever ``normal'' symbol most directly preceeds the symbol you care about and then figure out the distance from that symbol to the symbol you do care about. Then you can get the address of the symbol that you do care about by doing something like: print &preceeding_symbol+0x7e where `0x7e' is the distance between `preceeding_symbol' and the symbol that you actually care about, e.g. `.foo'. And before you ask, yes, it *is* a bummer that the assembler accepts names (for symbols) that gdb cannot deal with, but you've got to remember that gdb is first and foremost a ``source level'' debugger (for C, C++, etc.)... not an assembly level debugger. P.S. Actually, symbols with periods probably shouldn't even be showing up in your gdb-disassembled output *or* in your object file symbol tables. If they are, then this may perhaps just be due to a small glitch in the specific versions of the FreeBSD assembler that you are using. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 12:35:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id E9CB91529E for ; Fri, 26 Nov 1999 12:35:12 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id PAA02374; Fri, 26 Nov 1999 15:36:49 -0500 (EST) Date: Fri, 26 Nov 1999 15:36:49 -0500 From: Dan Moschuk To: Rob King Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets Message-ID: <19991126153649.A1358@spirit.jaded.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dimwit@pernet.net on Fri, Nov 26, 1999 at 01:20:52PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Hi all, | I'm writing a server that multiplexes a MySQL connection to several | clients. Since the connection has to be shared, I can't fork(), I have to | thread. This isn't a problem, except that when I accept() and assign a | socket descriptor, the first thread runs fine, but the next thread simply | grabs the descriptor (since it's shared) from the previous thread and | starts doing all its writing to that socket. Any idea how to get around | this? If there's any good example code, please let me know. | | Thanks, | Rob Err, how exactly is your server model setup? Do you create a thread after the accept call to handle the connection, or do you pre-spawn threads in a pool? If you allocate the socket descriptor for the client in the starting routine for the thread, it should have its own copy. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 13:42: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dustdevil.waterspout.com (dial-166.bford.kiva.net [208.233.252.166]) by hub.freebsd.org (Postfix) with ESMTP id E782914A1F for ; Fri, 26 Nov 1999 13:41:57 -0800 (PST) (envelope-from csg@waterspout.com) Received: by dustdevil.waterspout.com (Postfix, from userid 1000) id 4ABBEA0; Thu, 25 Nov 1999 16:36:15 -0500 (EST) Date: Thu, 25 Nov 1999 16:36:13 -0500 From: "C. Stephen Gunn" To: hackers@freebsd.org Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) Message-ID: <19991125163613.A2147@dustdevil.waterspout.com> References: <199911222138.QAA76632@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 22, 1999 at 02:07:58PM -0800, Alfred Perlstein wrote: > On Mon, 22 Nov 1999, David E. Cross wrote: > > > Does NetBSD have a working rpc.lockd... that would make this much easier. > > at a glance at http://cvsweb.netbsd.org/... no. > > Linux may have one, a temporary GPL'd port would be interesting perhaps. I'm fairly certain that rpc.lockd is included with Darwin from Apple, I've not closely compared it to what we have in -STABLE or -CURRENT to see if it actually works. Just thought I'd mention it. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc. Email: csg@waterspout.com 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 14:30:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id DFCCA1527B; Fri, 26 Nov 1999 14:30:29 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id RAA03141; Fri, 26 Nov 1999 17:32:28 -0500 (EST) Date: Fri, 26 Nov 1999 17:32:28 -0500 From: Dan Moschuk To: Rob King Cc: Dan Moschuk , hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets Message-ID: <19991126173228.A2608@spirit.jaded.net> References: <19991126153649.A1358@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dimwit@pernet.net on Fri, Nov 26, 1999 at 02:42:35PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | int sd2; | if((sd2=accept(sd, (struct sockaddr*)&cad, &alen)) > 0) { | pthread_create(&thread1, pthread_attr_default, | serverstart, &sd2); | } | | Then the serverstart function: | | void *serverstart(void *ptr) | { | int *sd2; | sd2 = (int*)ptr; | | dowhatever(sd2); | } | | Any ideas as to what I'm doing wrong? Also, thanks for your help. | | Rob Try this. void *serverstart(void *ptr) { int sd2; sd2 = *((int *) ptr); ... } -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 26 22:57:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id 5643114DD9 for ; Fri, 26 Nov 1999 22:57:47 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id WAA18665 for ; Fri, 26 Nov 1999 22:57:46 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <383F80EA.D851032B@gorean.org> Date: Fri, 26 Nov 1999 22:57:46 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: minor nag for minor PR Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.freebsd.org/cgi/query-pr.cgi?pr=14239 In case someone's bored this weekend... Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 9:43:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id 2363014CF4; Sat, 27 Nov 1999 09:43:28 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iveaea.dialup.mindspring.com [165.247.41.202]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA04711; Sat, 27 Nov 1999 12:43:26 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id MAA01184; Sat, 27 Nov 1999 12:43:23 -0500 (EST) (envelope-from vsilyaev) Message-Id: <199911271743.MAA01184@mindspring.com> Subject: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD To: freebsd-hackers@freebsd.org Date: Sat, 27 Nov 1999 12:43:22 -0500 (EST) Cc: emulation@freebsd.org From: "Vladimir N. Silyaev" X-Reply-To-Back: "Vladimir N. Silyaev" X-Touch-Of-Mind: vns@delta.odessa.ua X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At this time I can successful run the VMware 1.1 for Linux on the FreeBSD. It could be used to run Linux on the FreeBSD box, or to run another FreeBSD on the same box. Of course you can run some piece of Microsoft products: MS DOS, Windows 9X, Windows NT and etc. You can download the port (NOTE: -current only) from: http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz Some more information about this port available at: http://www.mindspring.com/~vsilyaev/vmware/ General information about VMware available at: http://www.vmware.com Vladimir N. Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 10:28:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5218314C36; Sat, 27 Nov 1999 10:28:07 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id SAA96125; Sat, 27 Nov 1999 18:33:41 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Nov 1999 18:33:41 +0000 (GMT) From: Doug Rabson To: "Vladimir N. Silyaev" Cc: freebsd-hackers@freebsd.org, emulation@freebsd.org Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-Reply-To: <199911271743.MAA01184@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Nov 1999, Vladimir N. Silyaev wrote: > Hi, > > At this time I can successful run the VMware 1.1 for Linux on the FreeBSD. > It could be used to run Linux on the FreeBSD box, or to run another FreeBSD > on the same box. Of course you can run some piece of Microsoft products: > MS DOS, Windows 9X, Windows NT and etc. You can download the port > (NOTE: -current only) from: > > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz > > > Some more information about this port available at: > http://www.mindspring.com/~vsilyaev/vmware/ > > General information about VMware available at: > http://www.vmware.com > > > Vladimir N. Silyaev Well done indeed! This is excellent work! -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 12: 2:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles559.castles.com [208.214.165.123]) by hub.freebsd.org (Postfix) with ESMTP id 71B3B155EA; Sat, 27 Nov 1999 12:02:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA93837; Sat, 27 Nov 1999 12:03:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911272003.MAA93837@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Vladimir N. Silyaev" Cc: freebsd-hackers@freebsd.org, emulation@freebsd.org Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-reply-to: Your message of "Sat, 27 Nov 1999 12:43:22 EST." <199911271743.MAA01184@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 12:03:13 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is great stuff, unfortunately VMware 1.1.1-330 isn't available anymore. Any chance of you updating your port to work with 1.1.2-364? > At this time I can successful run the VMware 1.1 for Linux on the FreeBSD. > It could be used to run Linux on the FreeBSD box, or to run another FreeBSD > on the same box. Of course you can run some piece of Microsoft products: > MS DOS, Windows 9X, Windows NT and etc. You can download the port > (NOTE: -current only) from: > > http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz > > > Some more information about this port available at: > http://www.mindspring.com/~vsilyaev/vmware/ > > General information about VMware available at: > http://www.vmware.com > > > Vladimir N. Silyaev > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 12:17:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id C866414CCC; Sat, 27 Nov 1999 12:17:04 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA08599; Sat, 27 Nov 1999 21:15:43 +0100 (CET) Message-Id: <199911272015.VAA08599@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mike Smith Cc: "Vladimir N. Silyaev" , freebsd-hackers@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 27 Nov 1999 12:03:13 PST." <199911272003.MAA93837@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 21:15:43 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > >This is great stuff, unfortunately VMware 1.1.1-330 isn't available >anymore. Any chance of you updating your port to work with 1.1.2-364? > I just grabbed VMware-1.1.1-330.tar.gz using his port, no problem. Couldn't run vmware, it complains that it can't find /dev/tty0 and exits. >> At this time I can successful run the VMware 1.1 for Linux on the FreeBSD. >> It could be used to run Linux on the FreeBSD box, or to run another FreeBSD >> on the same box. Of course you can run some piece of Microsoft products: >> MS DOS, Windows 9X, Windows NT and etc. You can download the port >> (NOTE: -current only) from: >> >> http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz >> >> >> Some more information about this port available at: >> http://www.mindspring.com/~vsilyaev/vmware/ >> >> General information about VMware available at: >> http://www.vmware.com >> >> >> Vladimir N. Silyaev >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> > >-- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-emulation" in the body of the message > --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 12:26:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp5.mindspring.com (smtp5.mindspring.com [207.69.200.82]) by hub.freebsd.org (Postfix) with ESMTP id D611E14EE3; Sat, 27 Nov 1999 12:26:09 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ive63o.dialup.mindspring.com [165.247.24.120]) by smtp5.mindspring.com (8.8.5/8.8.5) with ESMTP id PAA00234; Sat, 27 Nov 1999 15:26:04 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id PAA01324; Sat, 27 Nov 1999 15:26:01 -0500 (EST) (envelope-from vsilyaev) Message-Id: <199911272026.PAA01324@mindspring.com> Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-Reply-To: <199911272003.MAA93837@mass.cdrom.com> from Mike Smith at "Nov 27, 1999 12:03:13 pm" To: Mike Smith Date: Sat, 27 Nov 1999 15:26:01 -0500 (EST) Cc: "Vladimir N. Silyaev" , freebsd-hackers@freebsd.org, emulation@freebsd.org From: "Vladimir N. Silyaev" X-Reply-To-Back: "Vladimir N. Silyaev" X-Touch-Of-Mind: vns@delta.odessa.ua X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > This is great stuff, unfortunately VMware 1.1.1-330 isn't available > anymore. I'm sorry what is mean not available? At this time you can download it from the VMware download sites (but you are need to know right URL, and port really know it). When you are obatined license, only mean major version number. From VMware website: Product [VMware 1.1.x for Linux____________________] > Any chance of you updating your port to work with 1.1.2-364? Sure. But right now, I don't investegate the difference between these versions. And I think will be very helpful to do some testing of the existing versions, because this driver doing some very unclean things with virtual memory. Vladimir N. Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 12:27:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles559.castles.com [208.214.165.123]) by hub.freebsd.org (Postfix) with ESMTP id 013F615498; Sat, 27 Nov 1999 12:27:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA94237; Sat, 27 Nov 1999 12:27:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911272027.MAA94237@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: "Vladimir N. Silyaev" , freebsd-hackers@freebsd.org, emulation@freebsd.org Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-reply-to: Your message of "Sat, 27 Nov 1999 12:03:13 PST." <199911272003.MAA93837@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 12:27:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is great stuff, unfortunately VMware 1.1.1-330 isn't available > anymore. Any chance of you updating your port to work with 1.1.2-364? I take that back; it is available, but the 1.1.2 version is current. Now to see if I can wrangle this into working... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 12:35:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 8F2F514EE5; Sat, 27 Nov 1999 12:35:14 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ive63o.dialup.mindspring.com [165.247.24.120]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id PAA28389; Sat, 27 Nov 1999 15:35:08 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id PAA01410; Sat, 27 Nov 1999 15:35:06 -0500 (EST) (envelope-from vsilyaev) Message-Id: <199911272035.PAA01410@mindspring.com> Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-Reply-To: <199911272015.VAA08599@peedub.muc.de> from Gary Jennejohn at "Nov 27, 1999 09:15:43 pm" To: Gary Jennejohn Date: Sat, 27 Nov 1999 15:35:06 -0500 (EST) Cc: Mike Smith , "Vladimir N. Silyaev" , freebsd-hackers@FreeBSD.ORG, emulation@FreeBSD.ORG From: "Vladimir N. Silyaev" X-Reply-To-Back: "Vladimir N. Silyaev" X-Touch-Of-Mind: vns@delta.odessa.ua X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > >This is great stuff, unfortunately VMware 1.1.1-330 isn't available > >anymore. Any chance of you updating your port to work with 1.1.2-364? > > > > I just grabbed VMware-1.1.1-330.tar.gz using his port, no problem. > > Couldn't run vmware, it complains that it can't find /dev/tty0 and > exits. Did you read section about Full Screen mode from README.FreeBSD file: - Fullscreen modes VMware would not even started session when our DISPLAY variable will be like ':0.0'. So to run VMware on the local display you are need to change DISPLAY environment to something like 'localhost:0.0'. For example use the following commands (for bourne shell): DISPLAY=localhost${DISPLAY};export DISPLAY Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 13:55:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles559.castles.com [208.214.165.123]) by hub.freebsd.org (Postfix) with ESMTP id D1DB315247; Sat, 27 Nov 1999 13:55:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA95151; Sat, 27 Nov 1999 13:55:34 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911272155.NAA95151@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Vladimir N. Silyaev" Cc: freebsd-hackers@freebsd.org, emulation@freebsd.org Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-reply-to: Your message of "Sat, 27 Nov 1999 12:43:22 EST." <199911271743.MAA01184@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Nov 1999 13:55:33 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At this time I can successful run the VMware 1.1 for Linux on the FreeBSD. Ok. Now I have some real commentary, and sorry for the erroneous complaint before. Firstly; the detection you do for a patched Linux module is great. I was very happy to be told off for not loading a new one first. 8) Secondly; you don't install the vmware-wizard script. Are there others that you might have missed? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 15: 5: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.7.89.179]) by hub.freebsd.org (Postfix) with ESMTP id 4B8F514C03 for ; Sat, 27 Nov 1999 15:04:58 -0800 (PST) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (Windmoon-Patched/8.9.3/8.9.3) with ESMTP id PAA42297 for ; Sat, 27 Nov 1999 15:11:36 -0800 (PST) Date: Sat, 27 Nov 1999 15:11:36 -0800 (PST) From: FengYue To: hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets In-Reply-To: <19991126173228.A2608@spirit.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Nov 1999, Dan Moschuk wrote: > > | int sd2; > | if((sd2=accept(sd, (struct sockaddr*)&cad, &alen)) > 0) { > | pthread_create(&thread1, pthread_attr_default, > | serverstart, &sd2); > | } > | > | Then the serverstart function: > | > | void *serverstart(void *ptr) > | { > | int *sd2; > | sd2 = (int*)ptr; > | > | dowhatever(sd2); > | } > | > | Any ideas as to what I'm doing wrong? Also, thanks for your help. > | > | Rob > > Try this. > > void *serverstart(void *ptr) > { > int sd2; > > sd2 = *((int *) ptr); > ... > } There is a race condition. You're passing sd2's address to serverstart() and inside serverstart() you def' the pointer. What if "sd2=accept(sd, (struct sockaddr*)&cad, &alen)" gets executed before your previous serverstart() finishs "sd2 = *((int*)ptr)"? btw, IMHO, creating threads per connection is a very bad design. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 15:49:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pernet.net (mail.pernet.net [205.229.0.40]) by hub.freebsd.org (Postfix) with ESMTP id 62A1314BE0 for ; Sat, 27 Nov 1999 15:49:10 -0800 (PST) (envelope-from jking@pernet.net) Received: from deadpixi.pernet.net (deadpixi.pernet.net [205.229.0.243]) by mail.pernet.net (8.9.1a/8.9.1) with ESMTP id RAA19257; Sat, 27 Nov 1999 17:48:59 -0600 (CST) Date: Sat, 27 Nov 1999 17:48:58 -0600 (CST) From: Rob King To: FengYue Cc: hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There is a race condition. You're passing sd2's address to serverstart() > and inside serverstart() you def' the pointer. What if > "sd2=accept(sd, (struct sockaddr*)&cad, &alen)" gets > executed before your previous serverstart() finishs "sd2 = *((int*)ptr)"? > > btw, IMHO, creating threads per connection is a very bad design. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > How would you recommend I do it? Please remember, I have no experience with pthreads, and any advice you give would be greatly appreciated. I tried doing a pool of threads created at startup, and I think that may be a better approach...That would allow tighter control of resource limits - do something like Apache, have a "maximum number" of processes running. Anyway, thanks for the help. Rob -- Rob King Network Administrator - PERnet Communications, Inc. jking@pernet.net - http://www.pernet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 15:58:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 0FD0C14E3D; Sat, 27 Nov 1999 15:58:41 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iveap4.dialup.mindspring.com [165.247.43.36]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id SAA12757; Sat, 27 Nov 1999 18:58:39 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id SAA01856; Sat, 27 Nov 1999 18:58:37 -0500 (EST) (envelope-from vsilyaev) Message-Id: <199911272358.SAA01856@mindspring.com> Subject: Re: ANNOUNCE: VMware 1.1 for Linux on the FreeBSD In-Reply-To: <199911272155.NAA95151@mass.cdrom.com> from Mike Smith at "Nov 27, 1999 01:55:33 pm" To: Mike Smith Date: Sat, 27 Nov 1999 18:58:36 -0500 (EST) Cc: "Vladimir N. Silyaev" , freebsd-hackers@freebsd.org, emulation@freebsd.org From: "Vladimir N. Silyaev" X-Reply-To-Back: "Vladimir N. Silyaev" X-Touch-Of-Mind: vns@delta.odessa.ua X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > Secondly; you don't install the vmware-wizard script. Are there others > that you might have missed? What is the sense to install this script, when it doesn't have any chance to working??? It really very dependent from linux internals. At this time only one application working the vmware, nor vmware-wizard, nor something else. Ok. New port, based on the VMware 1.1.2 will be install all the executables. This port available right now from the old url: http://www.mindspring.com/~vsilyaev/vmware/vmware.tar.gz Nothing changed, only version number and user level application. Vladimir Silyaev. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 17:59:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id C6A4614CCB for ; Sat, 27 Nov 1999 17:59:22 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id UAA07223; Sat, 27 Nov 1999 20:59:21 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199911280159.UAA07223@spoon.beta.com> To: hackers@freebsd.org Cc: mike@sentex.net, calvinng@brel.com, ludo_koren@tempest.sk, tmb@sophos.com, syed@pinenut.nosc.mil, hank@black-hole.com, mistwolf@mushhaven.net, dec@groov.ie, cwass99@home.com, doogie@staff.accessus.net, varju@mail.webct.com, mota@bocal.cs.univ-paris8.fr, dwhite@resnet.uoregon.edu Subject: Test code... Date: Sat, 27 Nov 1999 20:59:21 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone have any suggestions (or feel like writing) code to exercise the following subsystems? - Virtual Memory - The threads library - mmap() and friends We want to try to bang on them a little more for 3.4 than we have in the past. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 18:43:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id 0835414D3A for ; Sat, 27 Nov 1999 18:43:29 -0800 (PST) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id VAA28246; Sat, 27 Nov 1999 21:43:08 -0500 (EST) Date: Sat, 27 Nov 1999 21:43:08 -0500 From: Dan Moschuk To: FengYue Cc: hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets Message-ID: <19991127214308.A27972@november.jaded.net> References: <19991126173228.A2608@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from FengYue on Sat, Nov 27, 1999 at 03:11:36PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | > Try this. | > | > void *serverstart(void *ptr) | > { | > int sd2; | > | > sd2 = *((int *) ptr); | > ... | > } | | There is a race condition. You're passing sd2's address to serverstart() | and inside serverstart() you def' the pointer. What if | "sd2=accept(sd, (struct sockaddr*)&cad, &alen)" gets | executed before your previous serverstart() finishs "sd2 = *((int*)ptr)"? Since accept isn't atomic, it would be best to enclose the whole sha-bang in a mutex up until the sd2 = *((int *) ptr) call finishes. -- Dan Moschuk (TFreak!dan@freebsd.org) "Try not. Do, or do not. There is no try." -- Yoda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 19:18: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id ECBE314EF6 for ; Sat, 27 Nov 1999 19:17:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA40584; Sat, 27 Nov 1999 19:17:42 -0800 (PST) (envelope-from dillon) Date: Sat, 27 Nov 1999 19:17:42 -0800 (PST) From: Matthew Dillon Message-Id: <199911280317.TAA40584@apollo.backplane.com> To: Tony Finch Cc: hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :of other connections. My solution was the same as Matt's :-) :(I'm not happy about the extra context switching that it requires but :I was more interested in working code than performance; I haven't :benchmarked it.) : :Tony. Yah, neither was I, but I figured that the overhead was (A) deterministic, and (B) absorbed under heavy loads because the subprocess in question was probably already in a run state under those conditions. So the method scales to load quite well and gives us loads of other features. For example, I could do realtime reverse DNS lookups with a single cache (in the main acceptor process) and then a pool of DNS lookup subprocesses which I communicated with over pipes. Thus the main load-bearing threads had very small core loops which was good for the L1/L2 cpu caches. It's kinda funny how something you might expect to generate more overhead can actually generate less. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 27 19:23: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.7.89.179]) by hub.freebsd.org (Postfix) with ESMTP id 8734A14EF6 for ; Sat, 27 Nov 1999 19:23:06 -0800 (PST) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (Windmoon-Patched/8.9.3/8.9.3) with ESMTP id TAA42618 for ; Sat, 27 Nov 1999 19:29:45 -0800 (PST) Date: Sat, 27 Nov 1999 19:29:45 -0800 (PST) From: FengYue To: hackers@FreeBSD.ORG Subject: Re: PThreads and Sockets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Nov 1999, Rob King wrote: > > How would you recommend I do it? Please remember, I have no experience > with pthreads, and any advice you give would be greatly appreciated. There are couple of ways you could do this: 1) pass sd2's value instead of its memory address to serverstart() pthread_create(&thread1, pthread_attr_default,serverstart, sd2); then inside serverstart: void serverstart (void *p) { int sockfd = (int) p; ....blah...blah } if you worry about void * being not as the same size as int on some platforms, then u should use 2) 2) Use a mutex lock: pthread_mutex_lock (&mp_lock); _do_the_accept_ _create_thread_ inside serverstart(), right after u def' the pointer, do this pthread_mutex_unlock (&mp_lock); > > I tried doing a pool of threads created at startup, and I think that may > be a better approach...That would allow tighter control of resource limits > - do something like Apache, have a "maximum number" of processes running. Yes, that's a better approach in many cases. Creating threads itself is a quiet expensive operation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message