From owner-freebsd-hackers Sun Dec 8 00:26:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA01816 for hackers-outgoing; Sun, 8 Dec 1996 00:26:55 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA01811 for ; Sun, 8 Dec 1996 00:26:51 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id TAA19537; Sun, 8 Dec 1996 19:24:22 +1100 Date: Sun, 8 Dec 1996 19:24:22 +1100 From: Bruce Evans Message-Id: <199612080824.TAA19537@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, mbarkah@hemi.com Subject: Re: bug in 2.2-alpha loopback (?) Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I can't reproduce this with your test program: >> >> j@uriah 1455% ./bar >> Waiting for client on port 2000 >> Attention, read() returned 0. > >Sorry, I wasn't very careful considering all the variables. This >might be a "telnet" problem instead of a loop interface problem See another thread in freebsd-bugs about bugs in telnet LINEMODE. I lost your example program, but the following simple program shows the bug: main() { char buf[4]; int i, nr; while (1) { nr = read(0, buf, sizeof buf); if (nr == 0) exit(0); printf("\nread %d bytes:", nr); for (i = 0; i < nr; ++i) printf(" %02x", (unsigned char)buf[i]); printf("\n"); } } Run this and type `1^D' where ^D is the eof character for the tty. The read should return 1, but in telnet LINEMODE it doesn't return. The eol character is similarly broken (when set). The eol2 character works. Bruce From owner-freebsd-hackers Sun Dec 8 00:35:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA02018 for hackers-outgoing; Sun, 8 Dec 1996 00:35:19 -0800 (PST) Received: from cedb.dpcsys.com (cedb.DPCSYS.COM [165.90.143.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA02012 for ; Sun, 8 Dec 1996 00:35:17 -0800 (PST) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.2/8.8.2) with SMTP id IAA20447; Sun, 8 Dec 1996 08:29:12 GMT Date: Sun, 8 Dec 1996 00:29:11 -0800 (PST) From: Dan Busarow To: Jake Hamby cc: hackers@freebsd.org Subject: Re: Help, I've been SCOed! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 7 Dec 1996, Jake Hamby wrote: > high as you imply, then that's not a good choice for them either. About > how much would an upgrade from OpenServer 5 to UnixWare cost? Price sensitivity depends on the situation. UnixWare licenses are cheap compared to HP/UX or AIX or ... Base license (5 user) is somewhere around $800. Really not that bad if that's all you need. But we use Unix on our clients too (F* MS) and 800 per client is a little too much :) SCO's upgrade policy isn't that great so I'd look at presenting your client with the cost of a new license (there is no upgrade at the moment anyway) but you could also point out that the new prooduct (UnixWare/Gemini) really is the best there is in the commercial x86 market and is winning performance awards left and right. It really is good stuff and we run our server side stuff on it, the VxFS (journaling file system) is really bullet proof, we haven't lost anything from power outages or lightning or stupid janitors. That's pretty important to retailers and isn't there yet in FreBSD. But for the client side (cash registers for us) FreeBSD shines. Not just the price, but that I can build a mini kernel that does just what we need in as little RAM as possible. Only folks who buy into WinTel say that bloat is OK cause RAM is cheap :) > Also, glad to see you're shipping your product for FreeBSD! So am I :) Dan -- Dan Busarow 714 443 4172 DPC Systems dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Sun Dec 8 00:53:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA02470 for hackers-outgoing; Sun, 8 Dec 1996 00:53:30 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA02446 for ; Sun, 8 Dec 1996 00:53:26 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA01532 for ; Sun, 8 Dec 1996 09:53:24 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA02464 for freebsd-hackers@freebsd.org; Sun, 8 Dec 1996 09:53:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA29189 for freebsd-hackers@freebsd.org; Sun, 8 Dec 1996 09:49:53 +0100 (MET) From: J Wunsch Message-Id: <199612080849.JAA29189@uriah.heep.sax.de> Subject: Re: ppp+alias -auto &spurious dialups. To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 8 Dec 1996 09:49:53 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612080005.SAA14181@bonkers.taronga.com> from Peter da Silva at "Dec 7, 96 06:05:48 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter da Silva wrote: > >Sheesh. sendmail is our default MTA. It's not an ISP-only thing, > >even local mail is being passed to sendmail: > > Yeh, but that'll work without the "sendmail -bd". All that does is provide > SMTP service. If you're getting your mail via POP3 or something you don't > need a sendmail daemon running. Anyway, if the sendmail isn't configured correctly, it will still dialout to the Internet, even for local delivery only. And _that_'s been the question here. (If you are less concerned about this, but are e.g. about security, i fully agree with you.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Dec 8 01:23:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA03064 for hackers-outgoing; Sun, 8 Dec 1996 01:23:38 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA03056 for ; Sun, 8 Dec 1996 01:23:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA02011 for ; Sun, 8 Dec 1996 10:23:25 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA02934 for freebsd-hackers@freebsd.org; Sun, 8 Dec 1996 10:23:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA29310 for freebsd-hackers@freebsd.org; Sun, 8 Dec 1996 09:51:35 +0100 (MET) From: J Wunsch Message-Id: <199612080851.JAA29310@uriah.heep.sax.de> Subject: Re: possible bug in comconsole code... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 8 Dec 1996 09:51:35 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from John-Mark Gurney at "Dec 7, 96 07:13:55 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John-Mark Gurney wrote: > > sio devices are being probed. (Even this doesn't happen with a > > modem-control insensitive terminal however.) > > hmmm... is tip sensitive to it? thanks for the advice though... ttyl.. Maybe, if the line isn't declared to be `clocal'. (I don't have much clues about tip, i've never used it myself.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Dec 8 01:24:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA03092 for hackers-outgoing; Sun, 8 Dec 1996 01:24:08 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA03087; Sun, 8 Dec 1996 01:24:03 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA02015; Sun, 8 Dec 1996 10:23:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA02936; Sun, 8 Dec 1996 10:23:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA29486; Sun, 8 Dec 1996 10:20:40 +0100 (MET) From: J Wunsch Message-Id: <199612080920.KAA29486@uriah.heep.sax.de> Subject: Re: bug in 2.2-alpha loopback (?) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 8 Dec 1996 10:20:39 +0100 (MET) Cc: mbarkah@hemi.com (Ade Barkah), wollman@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612080034.RAA27465@hemi.com> from Ade Barkah at "Dec 7, 96 05:34:49 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Ade Barkah wrote: > Sorry, I wasn't very careful considering all the variables. This > might be a "telnet" problem instead of a loop interface problem > (My 2.2 machine is located remotely, so that's why I noticed it.) > I have been telnetting into the 2.2 machine, "telnet localhost > 2000", then close the first telnet. > > The problem occurs when I telnet into a FreeBSD machine, _then_ > telnet again to port 2000, issue the escape character, and > close the connection. > > So, we have: > > Machine A ---telnet---> Machine B ---telnet---> Machine C Hmm, now i can reproduce it. It's another problem with telnet linemode handling. Though i'm not sure whether it is OK by the telnet RFC's or not. (It looks as if this is in violation.) If you set the connection between Machine B and Machine C to character-at-a-time mode, it works correctly. Note that this is a little tricky since you gotta issue the telnet escape character twice, so you can type ``mode char'' at the second telnet prompt. Since the network server on Machine C is not a telnet server, linemode negotiation should IMHO not occur, and the connection should rather remain in character-at-a-time mode anyway, but i better leave the actual interpretation to the telnet gurus. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Dec 8 04:04:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA06982 for hackers-outgoing; Sun, 8 Dec 1996 04:04:24 -0800 (PST) Received: from odie.physik2.uni-rostock.de (odie.physik2.uni-rostock.de [139.30.40.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA06977; Sun, 8 Dec 1996 04:04:19 -0800 (PST) Received: from odie.physik2.uni-rostock.de (localhost [127.0.0.1]) by odie.physik2.uni-rostock.de (8.8.3/8.7.3) with ESMTP id NAA16093; Sun, 8 Dec 1996 13:04:10 +0100 (MET) Message-Id: <199612081204.NAA16093@odie.physik2.uni-rostock.de> X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-questions@freefall.FreeBSD.org, freebsd-hackers@freefall.FreeBSD.org cc: Lars_Koeller@odie.physik2.uni-rostock.de Subject: SKIP for FreeBSD, anyone working on it? X-Face: nLQGe[[K51[{{[C\,BiQm[7]u1m{N>_\%nLBo4t@)CoZ}hK[W7DwX&V=}Wf#Qb,j:Jpj[(12r=b~:dYmh]fDf\, ]_frt6eM Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -------- Hi! Is there anybody working on a port of Sun's IP layer encryption implementation for FreeBSD? A US-only version for 2.1.5 is available on www.skip.com. When will it be available to ALL FreeBSDles? Thanks Lars -- ------------------------------------------------------------------------ Internet: | Lars Koeller Lars_Koeller@odie.physik2.Uni-Rostock.DE | Department of Physics ftp://odie.physik2.uni-rostock.de | University of Rostock PGP-key: | Germany http://www.nic.surfnet.nl/pgp/pks-toplev.html | ----------- FreeBSD, what else? ---- http://www.freebsd.org ------------ From owner-freebsd-hackers Sun Dec 8 04:46:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA08203 for hackers-outgoing; Sun, 8 Dec 1996 04:46:04 -0800 (PST) Received: from superior.truenorth.org (ppp023-sm2.sirius.com [205.134.231.23]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA08198; Sun, 8 Dec 1996 04:45:48 -0800 (PST) Received: (from jgrosch@localhost) by superior.truenorth.org (8.7.5/8.7.3) id EAA00753; Sun, 8 Dec 1996 04:40:58 -0800 (PST) From: Josef Grosch Message-Id: <199612081240.EAA00753@superior.truenorth.org> Subject: Re: SKIP for FreeBSD, anyone working on it? In-Reply-To: <199612081204.NAA16093@odie.physik2.uni-rostock.de> from Lars Koeller at "Dec 8, 96 01:04:10 pm" To: lkoeller@odie.physik2.uni-rostock.de (Lars Koeller) Date: Sun, 8 Dec 1996 04:40:57 -0800 (PST) Cc: freebsd-questions@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org, Lars_Koeller@odie.physik2.uni-rostock.de Reply-To: jgrosch@sirius.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >-------- > > Hi! > > Is there anybody working on a port of Sun's IP layer encryption > implementation for FreeBSD? A US-only version for 2.1.5 is available on > www.skip.com. When will it be available to ALL FreeBSDles? > > Thanks > > Lars The URL has changed. Try ; http://skip.incog.com Josef -- Josef Grosch | Laugh while you can, monkey boy ! | FreeBSD 2.1.6 jgrosch@sirius.com | - John Warfin - | UNIX for the masses From owner-freebsd-hackers Sun Dec 8 05:43:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA09350 for hackers-outgoing; Sun, 8 Dec 1996 05:43:04 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA09344 for ; Sun, 8 Dec 1996 05:43:01 -0800 (PST) Message-Id: <199612081343.FAA09344@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA089932551; Mon, 9 Dec 1996 00:42:31 +1100 From: Darren Reed Subject: Re: truss, trace ?? To: proff@suburbia.net Date: Mon, 9 Dec 1996 00:42:31 +1100 (EDT) Cc: avalon@coombs.anu.edu.au, hackers@freebsd.org In-Reply-To: <19961208072846.9917.qmail@suburbia.net> from "proff@suburbia.net" at Dec 8, 96 06:28:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from proff@suburbia.net, sie said: > > > > > Be nice if there was an option for it to output (immeadiately) to stdout > > > > rather than ktrace.out. > > > > > > I'm afraid that the kernel risks to stall if you get it to write the > > > trace into a FIFO. But perhaps it's not too difficult to have > > > kdump(8) doing some `tail -f' like magic? This should effectively > > > yield you a similar behaviour. > > ktrace ./foo & kdump -l and make sure you don't fill your filesystem.... Darren From owner-freebsd-hackers Sun Dec 8 05:46:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA09504 for hackers-outgoing; Sun, 8 Dec 1996 05:46:31 -0800 (PST) Received: from squirrel.tgsoft.com (sdts3-10.znet.com [207.167.65.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA09481 for ; Sun, 8 Dec 1996 05:46:02 -0800 (PST) Received: (from thompson@localhost) by squirrel.tgsoft.com (8.8.3/8.6.12) id FAA24231; Sun, 8 Dec 1996 05:42:38 -0800 (PST) Date: Sun, 8 Dec 1996 05:42:38 -0800 (PST) Message-Id: <199612081342.FAA24231@squirrel.tgsoft.com> From: mark thompson To: joerg_wunsch@uriah.heep.sax.de CC: freebsd-hackers@freebsd.org In-reply-to: <199612072204.XAA23284@uriah.heep.sax.de> (message from J Wunsch on Sat, 7 Dec 1996 23:04:18 +0100 (MET)) Subject: Re: trying to upgrade to 2.2 Reply-to: thompson@znet.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: J Wunsch Date: Sat, 7 Dec 1996 23:04:18 +0100 (MET) As mark thompson wrote: > My question is: > 1) is '../../contrib' a new idea in 2.2? Yes. Basically, /usr/src/contrib contains the unmodified original distribution files (mostly), while local changes are maintained where they belong to. The make process never descends into the `contrib' directory, but the files there are rather being used by .PATH and -I../../contrib/ stuff in the real Makefiles. Ah. Well, that clears it right up. contrib was not in my cvsup file. Is there an 'official' or 'sample' cvsup file for boneheads like me somewhere, and I simply didn't find it? Or is creating one a sort of intelligence test (obviously, i got only partial credit)? -mark p.s. I do like the 'contrib' idea. I just wish that it was clearer what has to be done to upgrade. From owner-freebsd-hackers Sun Dec 8 05:47:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA09555 for hackers-outgoing; Sun, 8 Dec 1996 05:47:38 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA09550 for ; Sun, 8 Dec 1996 05:47:33 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id OAA16494; Sun, 8 Dec 1996 14:49:09 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id PAA03555; Sun, 8 Dec 1996 15:01:18 +0100 (MET) From: Christoph Kukulies Message-Id: <199612081401.PAA03555@gilberto.physik.rwth-aachen.de> Subject: Re: Amd (K5) 586 /133 In-Reply-To: <199612080358.WAA27217@oscar.cc.gatech.edu> from Carlos Ugarte at "Dec 7, 96 10:58:52 pm" To: cau@cc.gatech.edu (Carlos Ugarte) Date: Sun, 8 Dec 1996 15:01:18 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I bought an A-Star (i430VX) mainboard and put in an Amd (K5) 133 MHz CPU. > > dmesg tells me 100.23 MHz. Who's cheating? > > No one, really. I'm pretty sure AMD uses a similar "rating" > scale to Cyrix - the particular chip you have is called something > like a K5-PR133, where PR stands for Pentium Rating (or something > similar). It actually runs at 100 MHz, but its performance was > found to be "equivalent" to a Pentium 133 MHz. > > How does it run? Any problems? It requires I586_CPU in the kernel config file and it seems to work fine. I will send worldstones later when I have solved my ccd problem. > > Carlos > > -- > Carlos A. Ugarte cau@cc.gatech.edu > Author of PageMage, a virtual desktop util for OS/2 > http://www.cc.gatech.edu/people/home/cau/ > If you understand what you're doing, you are not learning anything > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sun Dec 8 06:05:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA10414 for hackers-outgoing; Sun, 8 Dec 1996 06:05:10 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA10402 for ; Sun, 8 Dec 1996 06:05:06 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id GAA16612 for ; Sun, 8 Dec 1996 06:05:34 -0800 (PST) Received: (qmail 3455 invoked by uid 110); 8 Dec 1996 14:04:51 -0000 Message-ID: <19961208140451.3454.qmail@suburbia.net> Subject: Re: truss, trace ?? In-Reply-To: from Darren Reed at "Dec 9, 96 00:42:31 am" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Mon, 9 Dec 1996 01:04:51 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In some mail from proff@suburbia.net, sie said: > > > > > > > Be nice if there was an option for it to output (immeadiately) to stdout > > > > > rather than ktrace.out. > > > > > > > > I'm afraid that the kernel risks to stall if you get it to write the > > > > trace into a FIFO. But perhaps it's not too difficult to have > > > > kdump(8) doing some `tail -f' like magic? This should effectively > > > > yield you a similar behaviour. > > > > ktrace ./foo & kdump -l > > and make sure you don't fill your filesystem.... > > Darren Yeah, the cyclic file type is (stupidly) missing from unix. From owner-freebsd-hackers Sun Dec 8 06:23:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA11644 for hackers-outgoing; Sun, 8 Dec 1996 06:23:13 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA11628 for ; Sun, 8 Dec 1996 06:23:07 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA07278; Sun, 8 Dec 1996 15:22:47 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA08207; Sun, 8 Dec 1996 15:22:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id PAA16674; Sun, 8 Dec 1996 15:01:29 +0100 (MET) From: J Wunsch Message-Id: <199612081401.PAA16674@uriah.heep.sax.de> Subject: Re: trying to upgrade to 2.2 To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sun, 8 Dec 1996 15:01:28 +0100 (MET) Cc: thompson@znet.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612081342.FAA24231@squirrel.tgsoft.com> from mark thompson at "Dec 8, 96 05:42:38 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As mark thompson wrote: > Ah. Well, that clears it right up. contrib was not in my cvsup file. Is > there an 'official' or 'sample' cvsup file for boneheads like me > somewhere, and I simply didn't find it? Wasn't there something in /usr/share/examples/? (I still you CTM, i can't tell you.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Dec 8 07:03:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA13932 for hackers-outgoing; Sun, 8 Dec 1996 07:03:29 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA13927 for ; Sun, 8 Dec 1996 07:03:26 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id QAA01358; Sun, 8 Dec 1996 16:00:25 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.8.4/8.8.2) with SMTP id PAA01265; Sun, 8 Dec 1996 15:47:24 +0100 (MET) Date: Sun, 8 Dec 1996 15:47:24 +0100 (MET) From: Andreas Klemm To: thompson@znet.com cc: freebsd-hackers@FreeBSD.org Subject: Re: trying to upgrade to 2.2 In-Reply-To: <199612081342.FAA24231@squirrel.tgsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 8 Dec 1996, mark thompson wrote: > Ah. Well, that clears it right up. contrib was not in my cvsup file. Is > there an 'official' or 'sample' cvsup file for boneheads like me > somewhere, and I simply didn't find it? Or is creating one a sort of > intelligence test (obviously, i got only partial credit)? src-base release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-bin release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-contrib release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-etc release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-games release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-gnu release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-include release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-lib release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-libexec release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-sbin release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-share release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-sys release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-usrbin release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress src-usrsbin release=cvs host=cvsup.FreeBSD.org hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress ports-all release=cvs host=cvsup.FreeBSD.ORG hostbase=/home base=/usr prefix=/local/CVS delete old use-rel-suffix compress I removed eBones and secure from the list. You only have to change some paths ... > p.s. I do like the 'contrib' idea. I just wish that it was clearer what > has to be done to upgrade. Did you read the FreeBSD handbook ? Part 4: Advanced topics 15. Staying current with FreeBSD 15.1. What is FreeBSD-current? 15.2. Who needs FreeBSD-current? 15.3. What is FreeBSD-current NOT? 15.4. Using FreeBSD-current 16. Staying stable with FreeBSD 16.1. What is FreeBSD-stable? 16.2. Who needs FreeBSD-stable? 16.3. Using FreeBSD-stable I think you'll find some info on that topic there. You only have to change the supfiles to the format of cvsup ... The cvsup package has some info on that ... I managed that as well without ``pain in the ass'' some months ago. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Sun Dec 8 08:03:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA15254 for hackers-outgoing; Sun, 8 Dec 1996 08:03:37 -0800 (PST) Received: from whale.gu.kiev.ua (whale.gu.net [194.93.190.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA15248 for ; Sun, 8 Dec 1996 08:03:32 -0800 (PST) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [194.93.190.3]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id SAA11542; Sun, 8 Dec 1996 18:02:43 +0200 Date: Sun, 8 Dec 1996 18:02:43 +0200 (EET) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: "Serge A. Babkin" cc: hackers@freebsd.org Subject: Re: Help, I've been SCOed! In-Reply-To: <199612080540.KAA25708@hq.icb.chel.su> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 8 Dec 1996, Serge A. Babkin wrote: > > I don't know about AIX but HP-UX has really nice SAM program. After Sam has a friend from AIX , who's name is Smit :-) -- Best, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-hackers Sun Dec 8 08:45:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16812 for hackers-outgoing; Sun, 8 Dec 1996 08:45:03 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA16778 for ; Sun, 8 Dec 1996 08:44:30 -0800 (PST) Received: (from davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) id DAA07909; Mon, 9 Dec 1996 03:42:26 +1100 (EST) Message-ID: Date: Mon, 9 Dec 1996 03:42:25 +1100 From: davidn@sdev.usn.blaze.net.au (David Nugent) To: angio@aros.net (Dave Andersen) Cc: mbarkah@hemi.com (Ade Barkah), imb@scgt.oz.au (michael butler), jfesler@calweb.com, hackers@FreeBSD.ORG Subject: Re: Apache and huge numbers of IP's.. References: <199612080242.TAA01291@hemi.com> <199612080408.VAA07389@fluffy.aros.net> X-Mailer: Mutt 0.50 Mime-Version: 1.0 In-Reply-To: <199612080408.VAA07389@fluffy.aros.net>; from Dave Andersen on Dec 7, 1996 21:08:06 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dave Andersen writes: > > > options "CHILD_MAX=512" > > > options "OPEN_MAX=512" > > > > Is this sufficient ? You still have: > > > > #ifndef FD_SETSIZE > > #define FD_SETSIZE 256 > > #endif > > > > in /usr/include/sys/types.h. FD_SETSIZE ultimately limits the > > At the beginning of your program, before ALL other #includes, say: > > #define FD_SETSIZE 512 Examining the source for the kernel implementation of select(2) in sys/kern/sys_generic.c suggests that this won't help. The kernel would also needs to understand the new FD_SETSIZE for fd's >= FD_SETSIZE to be seen at that level. Modifying the define in sys/sys/types.h directly would seem to be the only way, after which a kernel build/install and make world would be necessary. And probably rebuild any ports and extras that use select() as well. Perhaps FD_SETSIZE should be set higher by default? I'm also wondering if this might cause transition problems. :-( A more reasonable default would be 1024 (imho) - this is after all only 128 bytes in an fd_set block. The problem with virtual domains is becoming increasingly common and 256 is definitely too small a value. Regards, David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn From owner-freebsd-hackers Sun Dec 8 09:38:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA18600 for hackers-outgoing; Sun, 8 Dec 1996 09:38:03 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA18594 for ; Sun, 8 Dec 1996 09:37:58 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id SAA09139 for ; Sun, 8 Dec 1996 18:37:52 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id SAA14292 for freebsd-hackers@freebsd.org; Sun, 8 Dec 1996 18:37:39 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id SAA05376; Sun, 8 Dec 1996 18:37:27 +0100 (CET) Message-ID: Date: Sun, 8 Dec 1996 18:37:26 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-hackers@freebsd.org Subject: Re: truss, trace ?? References: <199612080433.UAA11953@kithrup.com> X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 In-Reply-To: <199612080433.UAA11953@kithrup.com>; from Sean Eric Fagan on Dec 7, 1996 20:33:11 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Sean Eric Fagan: > I recently posted the main part of my EP truss program to the net, to show > what it would look like. Where did you post it please ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-hackers Sun Dec 8 10:00:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19185 for hackers-outgoing; Sun, 8 Dec 1996 10:00:08 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA19126 for ; Sun, 8 Dec 1996 09:59:56 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id TAA18560 for ; Sun, 8 Dec 1996 19:01:32 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id TAA04313 for freebsd-hackers@freefall.cdrom.com; Sun, 8 Dec 1996 19:13:45 +0100 (MET) Date: Sun, 8 Dec 1996 19:13:45 +0100 (MET) From: Christoph Kukulies Message-Id: <199612081813.TAA04313@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: ccd - help needed Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I can't get my ccd working. ccdconfig -C always says ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format This is my /etc/ccd.conf: # # /etc/ccd.conf # Configuration file for concateneated disk devices # # ccd ileave flags component devices ccd0 16 none /dev/sd0c /dev/sd1c dmesg: npx0: INT 16 interface ccd0-3: Concatenated disk drivers I tried with a 'true partition entry' as well as with a raw partition (or whatever this is called when you choose a partition entry 'being incompatible with future operating systems' :-). It is 3.0-current. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sun Dec 8 11:56:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA21829 for hackers-outgoing; Sun, 8 Dec 1996 11:56:27 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA21824 for ; Sun, 8 Dec 1996 11:56:24 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id LAA05920; Sun, 8 Dec 1996 11:56:15 -0800 (PST) To: Andreas Klemm cc: thompson@znet.com, freebsd-hackers@FreeBSD.org Subject: Re: trying to upgrade to 2.2 In-reply-to: Your message of "Sun, 08 Dec 1996 15:47:24 +0100." Date: Sun, 08 Dec 1996 11:56:14 -0800 Message-ID: <5917.850074974@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Sun, 8 Dec 1996, mark thompson wrote: > > > Ah. Well, that clears it right up. contrib was not in my cvsup file. Is > > there an 'official' or 'sample' cvsup file for boneheads like me > > somewhere, and I simply didn't find it? Or is creating one a sort of > > intelligence test (obviously, i got only partial credit)? Also, it's John Polstra's intention (which he's working on now) to make the cvsup files themselves a CVS collection which you'll grab by default, so the files will be self-updating at some point and totally brainless to maintain. Jordan From owner-freebsd-hackers Sun Dec 8 12:13:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA22320 for hackers-outgoing; Sun, 8 Dec 1996 12:13:30 -0800 (PST) Received: from ican.net (ican.net [198.133.36.9]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA22315 for ; Sun, 8 Dec 1996 12:13:26 -0800 (PST) Received: from gate.ican.net(really [198.133.36.2]) by ican.net via sendmail with esmtp id for ; Sun, 8 Dec 1996 15:13:17 -0500 (EST) (Smail-3.2 1996-Jul-4 #1 built 1996-Jul-10) Received: (from smap@localhost) by gate.ican.net (8.7.5/8.7.3) id PAA02597 for ; Sun, 8 Dec 1996 15:10:10 -0500 (EST) Received: from nap.io.org(10.1.1.3) by gate.ican.net via smap (V1.3) id sma002595; Sun Dec 8 15:10:03 1996 Received: from localhost (taob@localhost) by nap.io.org (8.7.5/8.7.3) with SMTP id PAA16999 for ; Sun, 8 Dec 1996 15:07:15 -0500 (EST) X-Authentication-Warning: nap.io.org: taob owned process doing -bs Date: Sun, 8 Dec 1996 15:07:15 -0500 (EST) From: Brian Tao To: FREEBSD-HACKERS-L Subject: Odd booting problems with 2.2-ALPHA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently installed 2.2-ALPHA on a handful of new workstations around the office, and noticed problems related to the boot procedure. The hardware is an Intel P166 on a Gigabyte 430VX motherboard: FreeBSD 2.2-ALPHA #0: Mon Nov 25 17:40:00 EST 1996 mattp@schmooze.io.org:/usr/local/src/sys/compile/SCHMOOZE Calibrating clock(s) relative to mc146818A clock ... i586 clock: 167066126 Hz, i8254 clock: 1193331 Hz CPU: Pentium (167.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63856640 (62360K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 3 on pci0:8 ahc0 rev 0 int a irq 11 on pci0:9 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs (ahc0:1:0): "SEAGATE ST31051N 0284" type 0 fixed SCSI 2 sd0(ahc0:1:0): Direct-Access 1010MB (2069860 512 byte sectors) sd0(ahc0:1:0): with 4177 cyls, 4 heads, and an average 123 sectors/track (ahc0:4:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 cd0(ahc0:4:0): CD-ROM cd present [216888 x 2048 byte records] de0 rev 17 int a irq 9 on pci0:10 de0: DC21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:cf:73:f2 [...] All the machines have experienced one of the two problems I want to describe. On random occasions when rebooting, the machine will simply freeze just after the initial kernel load message and before it prints the BIOS memory size check (the first line printed in bright white with the syscons driver). This can happen from power-on, coming from a DOS session, or rebooting from FreeBSD. The second problem happened to my machine today. I switched to a vty from the xdm console in order to login and shutdown the machine. The machine froze when it should have given me the "Password:" prompt. I didn't catch any kernel messages (couldn't switch to vty0), and it rebooted itself. The boot cycle stopped at the "WARNING: / was not properly dismounted." kernel message. There was no disk or screen activity from the expected fsck. Hard resets and power cycles do not cure the problem. Booting into single-user mode hangs at the same place. I haven't had a chance to pull out the drive and mount it on another machine yet, so there may be some critical filesystem corruption going on in /etc or /bin that I haven't found yet. There was no activity to the mounted DOS filesystems. Any ideas why the boot process might hang at the point it should be running /etc/rc, without any sort of error messages or diagnostics? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" From owner-freebsd-hackers Sun Dec 8 13:05:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23618 for hackers-outgoing; Sun, 8 Dec 1996 13:05:16 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23612 for ; Sun, 8 Dec 1996 13:05:08 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA29392; Sun, 8 Dec 1996 13:44:03 -0700 From: Terry Lambert Message-Id: <199612082044.NAA29392@phaeton.artisoft.com> Subject: Re: Help, I've been SCOed! To: jehamby@lightside.com Date: Sun, 8 Dec 1996 13:44:03 -0700 (MST) Cc: hackers@freebsd.org, jkh@time.cdrom.com In-Reply-To: from "Jake Hamby" at Dec 7, 96 08:37:17 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone have background info on these old XENIX binaries? Yes. > Will FreeBSD or Linux run them? No. For FreeBSD, this would take another execution class. Luckily Xenix didn't support shared libraries, so all it would take is the execution class, and nearly nothing else. You would need a Xenix system to be able to deal with it. Many Xenix programs opened directories and read the directory data from the directory into user space struct direct/dirent's. You would need to differentiate a read of a directory from that of a non-directory, and fake up the data (SVR4 does this, assuming the binary wants the data in SVR3 S51k format). The "select" or "poll" system calls introduced with the Xenix ODT (*yes* it *was* first released on Xenix... it even ran about 1.6 times faster before they went to SVR3 for the AFCAC 451 and Desktop III federal systems bids) are a bit odd. They are afterthougts, not device entry points, and if this behaviour is depended upon, then it will require some intricate faking. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Dec 8 13:13:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23896 for hackers-outgoing; Sun, 8 Dec 1996 13:13:54 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA23890 for ; Sun, 8 Dec 1996 13:13:51 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id NAA00379; Sun, 8 Dec 1996 13:12:27 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Sun, 8 Dec 1996 13:12:26 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: Terry Lambert cc: hackers@freebsd.org, jkh@time.cdrom.com Subject: Re: Help, I've been SCOed! In-Reply-To: <199612082044.NAA29392@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 8 Dec 1996, Terry Lambert wrote: > > Does anyone have background info on these old XENIX binaries? > > Yes. > > > Will FreeBSD or Linux run them? > > No. > > [description of XENIX format deleted] Thanks for the info, but for your information, I just downloaded the latest iBCS package for Linux and it does claim Beta-level support for Xenix binaries (and alpha support for Xenix-286 binaries!). It also had freely distributable versions of the common ELF shared libraries, which will be useful if we get SVR4 compatibility. FWIW, Linux ran the programs I was interested in (FoxPro and something called MView) perfectly, but those were COFF binaries. But I won't tell my client to switch to Linux because it doesn't provide any sort of long-term solution for their database (moving it to something real like Oracle). Right now they want to move over to Windows NT, with NT Workstation on all the clients, accessing the database through a VB front-end, probably. The only alternative I could see is running UnixWare on the server, which claims excellent Oracle tpm/C ratings, which should also have enough SCO compatibility to run FoxPro in the meantime. Either way they'd be using NT on the clients because they also want to run some Windows software (Goldmine). The only problem with that is the high price of UnixWare, the lack of upgrade pricing from OpenServer, and the feeling among the company that they've been burned once by SCO already. -- Jake From owner-freebsd-hackers Sun Dec 8 13:41:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24947 for hackers-outgoing; Sun, 8 Dec 1996 13:41:11 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA24941 for ; Sun, 8 Dec 1996 13:41:07 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id NAA00452 for ; Sun, 8 Dec 1996 13:41:14 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Sun, 8 Dec 1996 13:41:13 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: hackers@freebsd.org Subject: How do I diagnose user-mode PPP coredumps? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I use the user-mode PPP daemon extensively on my FreeBSD-current box, and often, after a number of HDLC errors, it will coredump. The ppp.log looks like: 12-08 13:30:21 [143] HDLC errors -> FCS: 5 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:31:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:32:21 [143] HDLC errors -> FCS: 4 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:33:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:35:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] Signal 11, core dump. The weird thing is that process 143 is still alive, and I must manually "kill -9" it, in order for the phone line to hang up. The other problem is that I don't get a core file anywhere, because it seems to be trapping the SIGSEGV. Does anyone else have this problem? What steps should I follow to start tracing it? I don't know why I'm getting the HDLC errors in the first place, but I have seen CRC errors using PPP with other OS's, so it's possible there's a dirty connection on my ISP's end, or on mine. Any help will be greatly appreciated, and I will post a send-pr when I've found the culprit. -- Jake From owner-freebsd-hackers Sun Dec 8 14:23:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA26841 for hackers-outgoing; Sun, 8 Dec 1996 14:23:31 -0800 (PST) Received: from netrover.com (ottawa24.netrover.com [205.209.19.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA26835 for ; Sun, 8 Dec 1996 14:23:16 -0800 (PST) Received: (from brianc@localhost) by netrover.com (8.8.2/8.8.2) id RAA00265; Sun, 8 Dec 1996 17:22:16 -0500 (EST) Message-ID: Date: Sun, 8 Dec 1996 17:22:15 -0500 From: brianc@netrover.com (Brian Campbell) To: freebsd-hackers@freebsd.org (FREEBSD-HACKERS-L) Subject: Re: Odd booting problems with 2.2-ALPHA References: X-Mailer: Mutt 0.51 Mime-Version: 1.0 Reply-to: brianc@pobox.com In-Reply-To: ; from Brian Tao on Dec 8, 1996 15:07:15 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Tao writes: > I recently installed 2.2-ALPHA on a handful of new workstations > around the office, and noticed problems related to the boot procedure. > The hardware is an Intel P166 on a Gigabyte 430VX motherboard: > > ... > > All the machines have experienced one of the two problems I want > to describe. On random occasions when rebooting, the machine will > simply freeze just after the initial kernel load message and before it > prints the BIOS memory size check (the first line printed in bright > white with the syscons driver). This can happen from power-on, coming > from a DOS session, or rebooting from FreeBSD. My Dell P166 running 2.2-alpha has done this too on occasion. However I haven't been able to find a repeatable set of circumstances under which it happens. However, if it happens, it's usually right after powerup and the floppy light is still on from the bios "probes". Perhaps it's an unexpected interrupt. From owner-freebsd-hackers Sun Dec 8 15:12:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA28916 for hackers-outgoing; Sun, 8 Dec 1996 15:12:41 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA28911 for ; Sun, 8 Dec 1996 15:12:38 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id XAA100434 for ; Sun, 8 Dec 1996 23:12:37 GMT Message-Id: <199612082312.XAA100434@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-243-66.va.us.ibm.net(166.72.243.66) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaYK0Dmb; Sun Dec 8 23:11:21 1996 Reply-To: From: "Steve Sims" To: Subject: Re: trying to upgrade to 2.2 Date: Sun, 8 Dec 1996 18:11:16 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk mark thompson said: > > build /u/build2.2/Root, using dump/restore to copy my (working) > 2.1.6.1 system (/, /var, /usr). > > cvsupped 12/6 (release=cvs host=cvsup.freebsd.org) > > extracted with: > cvs -d /home/ncvs $QUIET -r checkout -r RELENG_2_2 -d `pwd`/src src and this reminded me of a question that's been rattling around in the back of my brain for some time: Where is the definitive listing of tags that cvsup can use to pull code sets from the cvs repository? Stated another way, how would an idjit (me) know what tag names in cvs correspond to what versions (I presume all the way back to 2.0.something. On the machine that I use to track -CURRENT, 'tag=.', so that's a no-brainer, but what if I wanted to track, say, 2.2? Inquiring minds want to know. (Yes, I've R'd TFM). ...sjs... From owner-freebsd-hackers Sun Dec 8 19:21:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA17088 for hackers-outgoing; Sun, 8 Dec 1996 19:21:35 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA17071 for ; Sun, 8 Dec 1996 19:21:30 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id OAA12973; Mon, 9 Dec 1996 14:19:33 +1100 Date: Mon, 9 Dec 1996 14:19:33 +1100 From: Bruce Evans Message-Id: <199612090319.OAA12973@godzilla.zeta.org.au> To: hackers@freebsd.org, proff@suburbia.net Subject: Re: strange problems with recent current Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Dec 8 02:37:59 evil /kernel: cy15: 5 more silo overflows (total 3876) >Dec 8 02:38:00 evil /kernel: cy8: 1 more silo overflow (total 7) >... >This has crept in sometime during the past few days. On what hardware? The PCI cy driver doesn't use a "fast" interrupt handler yet, so silo overflows are quite likely for it. E.g., updating the keyboard LEDs takes a few msec, so a few fifos full of input may be dropped on each port whenever you hit caps lock (the fifo fills up in 1 msec at 115200 bps). >Previously cy.c >would suffer silo overflows far more rarely (once every 10-30 seconds >on average) and overflows quantities were never over 2 or 3. One per day is too many. >Response time generally has suffered, even with a very low load. Feels >like some kind of excessive context switching delay. I haven't noticed any new problems here on a lightly loaded 486/33 system. Bruce From owner-freebsd-hackers Sun Dec 8 20:04:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA21613 for hackers-outgoing; Sun, 8 Dec 1996 20:04:06 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA21593 for ; Sun, 8 Dec 1996 20:04:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA13347; Sun, 8 Dec 1996 20:03:36 -0800 (PST) Message-Id: <199612090403.UAA13347@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Bruce Evans cc: hackers@freebsd.org, proff@suburbia.net Subject: Re: strange problems with recent current In-reply-to: Your message of "Mon, 09 Dec 1996 14:19:33 +1100." <199612090319.OAA12973@godzilla.zeta.org.au> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Dec 1996 20:03:36 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Dec 8 02:37:59 evil /kernel: cy15: 5 more silo overflows (total 3876) >>Dec 8 02:38:00 evil /kernel: cy8: 1 more silo overflow (total 7) >>... >>This has crept in sometime during the past few days. > >On what hardware? The PCI cy driver doesn't use a "fast" interrupt >handler yet, so silo overflows are quite likely for it. E.g., updating >the keyboard LEDs takes a few msec, so a few fifos full of input may >be dropped on each port whenever you hit caps lock (the fifo fills up >in 1 msec at 115200 bps). If you are using the PCI cy adapter, you might want to get the "cytest" program from the Cyclades ftp site and change the memory mapping mode to >1MB. When the card is mapped into the <1MB region, the shared memory operates much slower on some motherboards (Triton chipset, perhaps others). It's actually 50% slower than ISA in this case. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Dec 8 20:05:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA21869 for hackers-outgoing; Sun, 8 Dec 1996 20:05:45 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA21852 for ; Sun, 8 Dec 1996 20:05:42 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA28225 for ; Sun, 8 Dec 1996 20:06:00 -0800 (PST) Received: (qmail 4549 invoked by uid 110); 9 Dec 1996 04:05:15 -0000 Message-ID: <19961209040514.4547.qmail@suburbia.net> Subject: Re: strange problems with recent current In-Reply-To: <199612090319.OAA12973@godzilla.zeta.org.au> from Bruce Evans at "Dec 9, 96 02:19:33 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 9 Dec 1996 15:05:14 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Dec 8 02:37:59 evil /kernel: cy15: 5 more silo overflows (total 3876) > >Dec 8 02:38:00 evil /kernel: cy8: 1 more silo overflow (total 7) > >... > >This has crept in sometime during the past few days. > > On what hardware? The PCI cy driver doesn't use a "fast" interrupt > handler yet, so silo overflows are quite likely for it. E.g., updating > the keyboard LEDs takes a few msec, so a few fifos full of input may > be dropped on each port whenever you hit caps lock (the fifo fills up > in 1 msec at 115200 bps). P100/Triton mother board. 4 Triton/mb IDE drives, two scsi (ISA adaptec), average 120 procs, 72Mb swap used (striped over the 4 ide drives). This configuration hasn't changed, and I don't use the console keyboard, infact..the console keyboard has been unplugged (could this have any effect?) > >Previously cy.c > >would suffer silo overflows far more rarely (once every 10-30 seconds > >on average) and overflows quantities were never over 2 or 3. > > One per day is too many. cy15 is often going at 57.6k in both directions, the others are more sporadic typical dial-up-user traffic (at 38.4). I moved cy15 onto sio1 (on board 16550A uart) Dec 9 14:58:16 suburbia /kernel: sio1: 1 more silo overflow (total 17190) Dec 9 14:58:21 suburbia /kernel: cy0: 2 more silo overflows (total 220) Dec 9 14:58:21 suburbia /kernel: sio1: 1 more silo overflow (total 17191) Dec 9 14:58:29 suburbia /kernel: sio1: 1 more silo overflow (total 17192) Dec 9 14:58:38 suburbia /kernel: sio1: 1 more silo overflow (total 17193) (uptime 16 hours) This is actually quite a bit better than the cyclades (could just be the 12 vs 15 byte byffer) but still worse than the cyclades before the "slow down". > >Response time generally has suffered, even with a very low load. Feels > >like some kind of excessive context switching delay. > > I haven't noticed any new problems here on a lightly loaded 486/33 system. > > Bruce > Load average is typically around 0.16 Cheers, Julian. From owner-freebsd-hackers Sun Dec 8 20:12:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA22715 for hackers-outgoing; Sun, 8 Dec 1996 20:12:53 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA22696 for ; Sun, 8 Dec 1996 20:12:44 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id OAA06894; Mon, 9 Dec 1996 14:42:19 +1030 (CST) From: Michael Smith Message-Id: <199612090412.OAA06894@genesis.atrad.adelaide.edu.au> Subject: Re: Amd (K5) 586 /133 In-Reply-To: <199612080358.WAA27217@oscar.cc.gatech.edu> from Carlos Ugarte at "Dec 7, 96 10:58:52 pm" To: cau@cc.gatech.edu (Carlos Ugarte) Date: Mon, 9 Dec 1996 14:42:18 +1030 (CST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Carlos Ugarte stands accused of saying: > > > I bought an A-Star (i430VX) mainboard and put in an Amd (K5) 133 MHz CPU. > > dmesg tells me 100.23 MHz. Who's cheating? You probably have the motherboard jumpers set wrong. > No one, really. I'm pretty sure AMD uses a similar "rating" > scale to Cyrix - the particular chip you have is called something > like a K5-PR133, where PR stands for Pentium Rating (or something > similar). It actually runs at 100 MHz, but its performance was > found to be "equivalent" to a Pentium 133 MHz. I don't think so. This is a 2.2 system with an AMD K5-PR100 : Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100252689 Hz, i8254 clock: 1193485 Hz CPU: AMD Unknown (100.23-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x501 > How does it run? Any problems? These guys seem to run pretty well; certainly they're P100-feel. 8) > Carlos A. Ugarte cau@cc.gatech.edu -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 8 20:20:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA23521 for hackers-outgoing; Sun, 8 Dec 1996 20:20:22 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA23506 for ; Sun, 8 Dec 1996 20:20:18 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id OAA06973 for hackers@freebsd.org; Mon, 9 Dec 1996 14:50:15 +1030 (CST) From: Michael Smith Message-Id: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au> Subject: VX-aware PCI probe To: hackers@freebsd.org Date: Mon, 9 Dec 1996 14:50:14 +1030 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can someone with a VX-chipset motherboard confirm that this patch correctly identifies their chipset before I commit it? (beware snarf-n-barf damage). What was the consensus on codenames? I notice that the old "Triton" comments have gone, but some of the others are still there. Any interest in a general PCI device ID/name mapping registry? I'd be happy to collect all the intelligence scattered among the files in sys/pci and write a small lookup function to return it appropriately. --- pcisupport.c.old Mon Dec 9 14:44:18 1996 +++ pcisupport.c Mon Dec 9 14:45:19 1996 @@ -132,6 +132,8 @@ return ("Intel 82434LX (Mercury) PCI cache memory controller"); case 0x122d8086: return ("Intel 82437FX PCI cache memory controller"); + case 0x70308086: + return ("Intel 82437VX PCI cache memory controller"); case 0x122e8086: return ("Intel 82371FB PCI-ISA bridge"); case 0x12308086: -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 8 20:32:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA24884 for hackers-outgoing; Sun, 8 Dec 1996 20:32:45 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA24879 for ; Sun, 8 Dec 1996 20:32:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id UAA05550; Sun, 8 Dec 1996 20:25:04 -0800 (PST) Message-Id: <199612090425.UAA05550@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: hackers@freebsd.org Subject: Re: VX-aware PCI probe Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 08 Dec 1996 20:25:04 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996 14:50:14 +1030 (CST) Michael Smith wrote: > Any interest in a general PCI device ID/name mapping registry? I'd be > happy to collect all the intelligence scattered among the files in > sys/pci and write a small lookup function to return it appropriately. Take a look at pci_devinfo(), in NetBSD's PCI code (sys/dev/pci). There's also a collection if PCI device IDs there. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Sun Dec 8 20:32:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA24928 for hackers-outgoing; Sun, 8 Dec 1996 20:32:53 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA24909 for ; Sun, 8 Dec 1996 20:32:51 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id VAA11231; Sun, 8 Dec 1996 21:32:47 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id VAA10071; Sun, 8 Dec 1996 21:32:16 -0700 (MST) Date: Sun, 8 Dec 1996 21:32:15 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: Jake Hamby cc: hackers@freebsd.org Subject: Re: How do I diagnose user-mode PPP coredumps? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk While I can't comment on the problem, one possible reason why it doesn't core dump is that it is running setuid. ppp installs its own signal handler for various signals, including SEGV. What it does is clean things up, then (in the case of sig 11) call abort(3). abort would dump core, except for the fact that the program is setuid. You should (or might; you can on 2.1.5, there have been some changes made in that are in -current, but I don't _think_ this should be one) be able to get around this by running ppp as root. As to the reason why it doesn't exit by itself, it is probably getting hung up somewhere in the signal handler trying to close the line and terminate the connection; if you wait long enough, it may sort itself out. On Sun, 8 Dec 1996, Jake Hamby wrote: > I use the user-mode PPP daemon extensively on my FreeBSD-current box, and > often, after a number of HDLC errors, it will coredump. The ppp.log looks > like: > > 12-08 13:30:21 [143] HDLC errors -> FCS: 5 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:31:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:32:21 [143] HDLC errors -> FCS: 4 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:33:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:35:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:36:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 > 12-08 13:36:21 [143] Signal 11, core dump. > > The weird thing is that process 143 is still alive, and I must manually > "kill -9" it, in order for the phone line to hang up. The other problem > is that I don't get a core file anywhere, because it seems to be trapping > the SIGSEGV. Does anyone else have this problem? What steps should I > follow to start tracing it? I don't know why I'm getting the HDLC errors > in the first place, but I have seen CRC errors using PPP with other OS's, > so it's possible there's a dirty connection on my ISP's end, or on mine. > Any help will be greatly appreciated, and I will post a send-pr when I've > found the culprit. > > -- Jake > From owner-freebsd-hackers Sun Dec 8 20:45:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA26444 for hackers-outgoing; Sun, 8 Dec 1996 20:45:48 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA26437 for ; Sun, 8 Dec 1996 20:45:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA20757; Sun, 8 Dec 1996 20:45:13 -0800 (PST) Message-Id: <199612090445.UAA20757@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: proff@suburbia.net cc: bde@zeta.org.au (Bruce Evans), hackers@freebsd.org Subject: Re: strange problems with recent current In-reply-to: Your message of "Mon, 09 Dec 1996 15:05:14 +1100." <19961209040514.4547.qmail@suburbia.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Dec 1996 20:45:13 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Dec 8 02:37:59 evil /kernel: cy15: 5 more silo overflows (total 3876) >> >Dec 8 02:38:00 evil /kernel: cy8: 1 more silo overflow (total 7) >> >... >> >This has crept in sometime during the past few days. >> >> On what hardware? The PCI cy driver doesn't use a "fast" interrupt ...> >P100/Triton mother board. 4 Triton/mb IDE drives, two scsi (ISA >adaptec), average 120 procs, 72Mb swap used (striped over the 4 Bruce means: Are you using the ISA Cyclades board or the PCI Cyclades board? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Dec 8 20:54:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27418 for hackers-outgoing; Sun, 8 Dec 1996 20:54:33 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27410 for ; Sun, 8 Dec 1996 20:54:30 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id UAA28826 for ; Sun, 8 Dec 1996 20:54:59 -0800 (PST) Received: (qmail 5229 invoked by uid 110); 9 Dec 1996 04:54:08 -0000 Message-ID: <19961209045408.5228.qmail@suburbia.net> Subject: Re: strange problems with recent current In-Reply-To: <199612090445.UAA20757@root.com> from David Greenman at "Dec 8, 96 08:45:13 pm" To: dg@root.com Date: Mon, 9 Dec 1996 15:54:08 +1100 (EST) Cc: hackers@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Bruce means: Are you using the ISA Cyclades board or the PCI Cyclades > board? > > -DG PCI From owner-freebsd-hackers Sun Dec 8 20:56:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27695 for hackers-outgoing; Sun, 8 Dec 1996 20:56:03 -0800 (PST) Received: from netrover.com (ottawa24.netrover.com [205.209.19.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27682 for ; Sun, 8 Dec 1996 20:56:00 -0800 (PST) Received: (from brianc@localhost) by netrover.com (8.8.2/8.8.2) id XAA02109; Sun, 8 Dec 1996 23:55:24 -0500 (EST) Message-ID: Date: Sun, 8 Dec 1996 23:55:23 -0500 From: brianc@netrover.com (Brian Campbell) To: hackers@FreeBSD.org Subject: Re: VX-aware PCI probe References: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.51 Mime-Version: 1.0 Reply-to: brianc@pobox.com In-Reply-To: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au>; from Michael Smith on Dec 9, 1996 14:50:14 +1030 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > Can someone with a VX-chipset motherboard confirm that this patch correctly > identifies their chipset before I commit it? (beware snarf-n-barf damage). That's exactly the code I've been using for the last several revisions. It detects my VX reliably. Is there a similar "patch" in chipset_attach? How about the same two patches for the 82371FB IDE interface on the Triton IIs? From owner-freebsd-hackers Sun Dec 8 20:58:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA28003 for hackers-outgoing; Sun, 8 Dec 1996 20:58:30 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27982; Sun, 8 Dec 1996 20:58:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA21328; Sun, 8 Dec 1996 20:57:56 -0800 (PST) Message-Id: <199612090457.UAA21328@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: proff@suburbia.net cc: hackers@freebsd.org, current@freebsd.org Subject: Re: strange problems with recent current In-reply-to: Your message of "Mon, 09 Dec 1996 15:54:08 +1100." <19961209045408.5228.qmail@suburbia.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Dec 1996 20:57:56 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Bruce means: Are you using the ISA Cyclades board or the PCI Cyclades >> board? >> >> -DG > >PCI Okay, then you definately want to get "cytest" and change the shared memory mapping address to >1MB. That should make the accesses to the card several times faster than they are now. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Dec 8 21:36:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA02460 for hackers-outgoing; Sun, 8 Dec 1996 21:36:14 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA02447 for ; Sun, 8 Dec 1996 21:36:07 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA17144; Mon, 9 Dec 1996 16:33:49 +1100 Date: Mon, 9 Dec 1996 16:33:49 +1100 From: Bruce Evans Message-Id: <199612090533.QAA17144@godzilla.zeta.org.au> To: bde@zeta.org.au, proff@suburbia.net Subject: Re: strange problems with recent current Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >P100/Triton mother board. 4 Triton/mb IDE drives, two scsi (ISA >adaptec), average 120 procs, 72Mb swap used (striped over the 4 >ide drives). This configuration hasn't changed, and I don't use the >console keyboard, infact..the console keyboard has been unplugged >(could this have any effect?) Not using the keyboard can only help. All those IDE drives are bad for the non-fast-interrupt (PCI) cy driver, at least if multi-mode is enabled. It takes 0.5 ms to transfer a typical 8K multi-block at 16MB/sec. Any more than that will cause silo overflows. Active drives on both controllers can certainly cause more than that, and very fast drives may be able to hog the cpu for any number of transfers. >> One per day is too many. > >cy15 is often going at 57.6k in both directions, the others are more >sporadic typical dial-up-user traffic (at 38.4). I moved cy15 onto sio1 >(on board 16550A uart) I would expect it to work up to 16 * 57.6k going in both directions. In raw mode, this takes about 70% overhead on a 486/33, about 40% of which is bus i/o overhead, 20% interrupt overhead, and 40% software overhead. Cooked mode has a much larger software overhead (5-10 times). A P100 should be enough faster to run some lines in cooked mode and actually do something besides serial i/o. However, if the PCI bus interface is 50% slower like David mentioned, then the bus i/o alone will take 60% of a P100 instead of only 40% :-]. >Dec 9 14:58:16 suburbia /kernel: sio1: 1 more silo overflow (total 17190) >Dec 9 14:58:21 suburbia /kernel: cy0: 2 more silo overflows (total 220) Not good. >This is actually quite a bit better than the cyclades (could just be the >12 vs 15 byte byffer) but still worse than the cyclades before the >"slow down". sio actually only uses 2 or 3 bytes of buffering above the interrupt threshold (the threshold is 14), while cy uses 6 bytes (the threshold is 6). The source must be edited to change the thresholds. >Load average is typically around 0.16 Load average doesn't show interrupt load. Use systat to see interrupt load for non-fast-interrupt handlers. Nothing shows the load for fast-interrupt handlers properly. Bruce From owner-freebsd-hackers Sun Dec 8 21:38:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA02824 for hackers-outgoing; Sun, 8 Dec 1996 21:38:25 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA02795 for ; Sun, 8 Dec 1996 21:38:16 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id QAA07561; Mon, 9 Dec 1996 16:07:49 +1030 (CST) From: Michael Smith Message-Id: <199612090537.QAA07561@genesis.atrad.adelaide.edu.au> Subject: Re: Driver help In-Reply-To: <199612031744.LAA13076@jake.lodgenet.com> from "Eric L. Hernes" at "Dec 3, 96 11:44:34 am" To: erich@lodgenet.com (Eric L. Hernes) Date: Mon, 9 Dec 1996 16:07:48 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, tony@nlanr.net, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Eric L. Hernes stands accused of saying: > > > IMHO, using copyin/out in drivers is bogus in most cases. > > I agree, but people porting drivers from a sysV derrivative, may want > to have a driver that will compile and work on either machine. I've > used a set of macros tucked away in the ifdef section like: ... This implies that SysV doesn't provide the readv/writev interface, correct? > I've also done similar things with the dma kernel support functions. > Usually, the driver ends up looking more BSDish than SCOish, but > isn't that how God intended? ;-) *grins* Now, is this documented in the DDWG? > erich@lodgenet.com -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 8 22:30:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA08398 for hackers-outgoing; Sun, 8 Dec 1996 22:30:39 -0800 (PST) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA08389 for ; Sun, 8 Dec 1996 22:30:37 -0800 (PST) Received: from harlie (bastion.bfd.com [204.160.242.2]) by horst.bfd.com (8.7.6/8.7.3) with SMTP id WAA29531; Sun, 8 Dec 1996 22:30:08 -0800 (PST) Date: Sun, 8 Dec 1996 22:30:08 -0800 (PST) From: "Eric J. Schwertfeger" X-Sender: ejs@harlie To: Michael Smith cc: Carlos Ugarte , kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Subject: Re: Amd (K5) 586 /133 In-Reply-To: <199612090412.OAA06894@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, Michael Smith wrote: > Carlos Ugarte stands accused of saying: > > > > > I bought an A-Star (i430VX) mainboard and put in an Amd (K5) 133 MHz CPU. > > > dmesg tells me 100.23 MHz. Who's cheating? > > > No one, really. I'm pretty sure AMD uses a similar "rating" > > scale to Cyrix - the particular chip you have is called something > > like a K5-PR133, where PR stands for Pentium Rating (or something > > similar). It actually runs at 100 MHz, but its performance was > > found to be "equivalent" to a Pentium 133 MHz. > > I don't think so. This is a 2.2 system with an AMD K5-PR100 : > > Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100252689 Hz, i8254 clock: 1193485 Hz > CPU: AMD Unknown (100.23-MHz 586-class CPU) The K5-PR100 and K5-PR133 are both 100Mhz CPU's, the PR133 just has a more efficient pipelining/microcoding/etc. From owner-freebsd-hackers Sun Dec 8 23:06:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA10760 for hackers-outgoing; Sun, 8 Dec 1996 23:06:44 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA10725 for ; Sun, 8 Dec 1996 23:06:27 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA28636; Mon, 9 Dec 1996 08:08:02 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id IAA06380; Mon, 9 Dec 1996 08:20:27 +0100 (MET) From: Christoph Kukulies Message-Id: <199612090720.IAA06380@gilberto.physik.rwth-aachen.de> Subject: Re: Amd (K5) 586 /133 In-Reply-To: from "Eric J. Schwertfeger" at "Dec 8, 96 10:30:08 pm" To: ejs@bfd.com (Eric J. Schwertfeger) Date: Mon, 9 Dec 1996 08:20:27 +0100 (MET) Cc: msmith@atrad.adelaide.edu.au, cau@cc.gatech.edu, kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > On Mon, 9 Dec 1996, Michael Smith wrote: > > > Carlos Ugarte stands accused of saying: > > > > > > > I bought an A-Star (i430VX) mainboard and put in an Amd (K5) 133 MHz CPU. > > > > dmesg tells me 100.23 MHz. Who's cheating? > > > > > No one, really. I'm pretty sure AMD uses a similar "rating" > > > scale to Cyrix - the particular chip you have is called something > > > like a K5-PR133, where PR stands for Pentium Rating (or something > > > similar). It actually runs at 100 MHz, but its performance was > > > found to be "equivalent" to a Pentium 133 MHz. > > > > I don't think so. This is a 2.2 system with an AMD K5-PR100 : > > > > Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100252689 Hz, i8254 clock: 1193485 Hz > > CPU: AMD Unknown (100.23-MHz 586-class CPU) > > The K5-PR100 and K5-PR133 are both 100Mhz CPU's, the PR133 just has a more > efficient pipelining/microcoding/etc. Aha, PR=Pentium Rating > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Mon Dec 9 00:11:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA16034 for hackers-outgoing; Mon, 9 Dec 1996 00:11:24 -0800 (PST) Received: from ns.instrumatic.ch (ns.instrumatic.ch [194.206.238.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA16004 for ; Mon, 9 Dec 1996 00:11:17 -0800 (PST) Received: by ns.instrumatic.ch (8.7.5/5.4/960822-ast) id JAA10506; Mon, 9 Dec 1996 09:07:14 +0100 (MET) Received: by rainbird.marabu.ch (8.7.5/8.6.12-960822/ast) id JAA22860; Mon, 9 Dec 1996 09:06:20 +0100 (MET) Received: by marabu.marabu.ch (8.7.5/960822-ast-7.3) id JAA24571; Mon, 9 Dec 1996 09:02:00 +0100 (CET) Message-Id: <199612090802.JAA24571@marabu.marabu.ch> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Adrian Steinmann Date: Mon, 9 Dec 96 09:01:59 +0100 To: hackers@freefall.freebsd.org Subject: Badblock scan at 2.1.5 install time renders disk unbootable ? References: <199612090404.UAA21632@freefall.freebsd.org> X-Organization: Steinmann Consulting, Apollostrasse 21, 8032 Zurich X-Phone-Numbers: Switzerland, Tel +41 1 380 30 83 Fax +41 1 380 30 85 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I was installing FreeBSD 2.1.5 minimal on a 325MB IDE drive in a Compaq Prolinea 466. The first install went great (I used the full disk including block 1, i.e., losing "compatibility with other OSs"). When I booted, I saw badblack messages and so I said, OOOPs, lets reinstall using that "scan for bad blocks option" in the disklabel menu. The scan worked - it found two bad blocks and entered them in the maintenance blocks, the install went fine again, but when I rebooted, the system hung right after the "Boot:" prompt with a never ending stream of "Error: Cyl 616 Hd: ?? Sector: ??". So I installed (with badblock scan) again with the first block "Compatible with other operating Systems" and the FreeBSD BootBlockManager. This time, the never ending loop was the infamous "Default F?" disk geometry problem (I had used 324/32/64). Finally, I decided to reinstall as I had done first: no bad block scan at install time, but then rebooted to the Fixit floppy and did the "bad144" from there, after which the system came up fine. So, does bad block scanning at boot time currupt the disklabel? BTW, the bad blocks were somewhere in the last third, that is, not in the label nor in the maintenance blocks. Adrian _________________________________________________________________________ Dr. Adrian Steinmann Steinmann Consulting Apollostrasse 21 8032 Zurich Tel +41 1 380 30 83 Fax +41 1 380 30 85 Mailto:ast@marabu.ch From owner-freebsd-hackers Mon Dec 9 01:27:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA22665 for hackers-outgoing; Mon, 9 Dec 1996 01:27:48 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-166.rdcy01.pacbell.net [206.170.5.166]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA22659; Mon, 9 Dec 1996 01:27:42 -0800 (PST) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id BAA00316; Mon, 9 Dec 1996 01:27:37 -0800 (PST) Message-Id: <199612090927.BAA00316@precipice.shockwave.com> To: nate@freebsd.org, hackers@freebsd.org Subject: need help with a PC CARD NE2000 clone... Date: Mon, 09 Dec 1996 01:27:36 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm at IETF and I've just brought up -current on my laptop and am running into a bit of a jam. pccardd is recognising my card and configuration, but then giving me an allocation error. Sigh. 2 days getting FreeBSD installed and now my brain is totally fried. Can you/anyone shed some light? My .conf files reads: card "PMX " "PE-200" config 0x1 "ed0" 11 ether 0xff0 insert echo PMX PE-200 Ethernet inserted insert /etc/pccard_ether ed0 remove echo PMX PE-200 Ethernet removed remove /etc/pccard_ether ed0 delete Card manuf PMX , vers PE-200 Configuration entries: Index code = 0x1, driver name = ed0 Insert commands are: echo PMX PE-200 Ethernet inserted /etc/pccard_ether ed0 Remove commands are: echo PMX PE-200 Ethernet removed /sbin/ifconfig ed0 delete When I insert the card: Code 240 not found Code 240 not found code Unknown ignored Ether=00:20:e0:0e:25:02 cardd: Resource allocation failure for PMX I've set up ed0 and ed1 in my kernel config as follows (just in case the card wanted to be at fixed places or have fixed irq's): ed0 @ 300, irq 11 ed1 @ 310, irq 5 Here's what pccardc's dumpcis says. Unfortunately, I don't know how to interpret it. Code 240 not found Code 240 not found code Unknown ignored Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: dc 03 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 100nS, Memory block size = 32Kb, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 53 01 ff Attribute memory device information: Device number 1, type FLASH EEPROM, WPS = OFF Speed = 150nS, Memory block size = 2Kb, 1 units Tuple #3, code = 0x21 (Functional ID), length = 2 000: 06 03 Network/LAN adapter - POST initialize - Card has ROM Tuple #4, code = 0x15 (Version 1 info), length = 30 000: 04 01 50 4d 58 20 20 20 00 50 45 2d 32 30 30 00 010: 45 54 48 45 52 4e 45 54 00 52 30 31 00 ff Version = 4.1, Manuf = [PMX ],card vers = [PE-200] Addit. info = [ETHERNET],[R01] Tuple #5, code = 0x1a (Configuration map), length = 5 000: 01 01 00 01 01 Reg len = 2, config register addr = 0x100, last config = 0x1 Registers: X------- Tuple #6, code = 0x1b (Configuration entry), length = 25 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 010: 00 00 40 0d 40 40 00 40 0d Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x10 I/O address # 2: block start = 0x310 block length = 0x10 IRQ modes: Level IRQs: 4 5 10 11 12 13 14 15 Memory descriptor 1 blk length = 0x400 card addr = 0x000 host addr = 0xd4000 Memory descriptor 2 blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 Tuple #7, code = 0x0 (Null tuple), length = 9 000: 57 42 20 4c 41 4e 20 20 ff Tuple #8, code = 0x14 (No link), length = 0 Tuple #9, code = 0xff (Terminator), length = 0 2 slots found From owner-freebsd-hackers Mon Dec 9 01:59:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA25304 for hackers-outgoing; Mon, 9 Dec 1996 01:59:38 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-166.rdcy01.pacbell.net [206.170.5.166]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA25296; Mon, 9 Dec 1996 01:59:34 -0800 (PST) Received: (from pst@localhost) by precipice.shockwave.com (8.8.4/8.7.3) id BAA00393; Mon, 9 Dec 1996 01:59:28 -0800 (PST) Date: Mon, 9 Dec 1996 01:59:28 -0800 (PST) From: Paul Traina Message-Id: <199612090959.BAA00393@precipice.shockwave.com> To: nate@freebsd.org Subject: followup on pccardd problems... Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's a memory allocation problem, but this stuff is driving me bonkers. /etc/sysconfig has pccard memory set to default (d0000). /etc/pccardd has pccard blocks at default (d4000 96k). the ed0 driver has had iomem set to d4000 (was d8000). We're failing inside assign_io, specificly in allocate_memory. We're asking for 1024 / MEMUNIT memory, which means the count being passed in to alloc_mem() is 0. Is this sane? Paul From owner-freebsd-hackers Mon Dec 9 02:03:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA25609 for hackers-outgoing; Mon, 9 Dec 1996 02:03:50 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA25604 for ; Mon, 9 Dec 1996 02:03:47 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.3/8.7.3) id CAA15644; Mon, 9 Dec 1996 02:51:24 -0700 (MST) From: Ade Barkah Message-Id: <199612090951.CAA15644@hemi.com> Subject: Re: bug in 2.2-alpha loopback (?) To: bde@zeta.org.au (Bruce Evans) Date: Mon, 9 Dec 1996 02:51:24 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org In-Reply-To: <199612080824.TAA19537@godzilla.zeta.org.au> from "Bruce Evans" at Dec 8, 96 07:24:22 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > >Sorry, I wasn't very careful considering all the variables. This > >might be a "telnet" problem instead of a loop interface problem > > See another thread in freebsd-bugs about bugs in telnet LINEMODE. [...program deleted...] > Run this and type `1^D' where ^D is the eof character for the tty. The > read should return 1, but in telnet LINEMODE it doesn't return. The > eol character is similarly broken (when set). The eol2 character works. Yeah... it fails to process the EOF unless it's the first character of the line. =-( J Wunsch wrote: > Since the network server on Machine C is not a telnet server, linemode > negotiation should IMHO not occur, and the connection should rather > remain in character-at-a-time mode anyway, but i better leave the > actual interpretation to the telnet gurus. :) I think it is fine for the telnet client to default in LINEMODE. In fact, I think Unix telnet has always defaulted to linemode since "way back when" (VMS ones stay in character mode.) I've seen many naive servers on the net (muds, chatlines, etc.) depend on the client starting in LINEMODE. The question is then, when the input tty is closed, should the client send an actual EOF character to the server or simply close the output connection ? Currently telnet forces out an EOF character by doing: (from sys_bsd.c:) [...up here somewhere basically (c = read (tin... ))...] | /* EOF detection for line mode!!!! */ | if ((c == 0) && MODE_LOCAL_CHARS(globalmode) && isatty(tin)) { | /* must be an EOF... */ | *ttyiring.supply = termEofChar; | c = 1; | } If I #ifdef out the above lines, things then work as I expect (erm, as I want, I mean.) In the mean time I'll check for an explicit EOF character in my programs. Thanks for all the replies, -Ade ps. Is David Borman the correct person to bug ? ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Mon Dec 9 02:47:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27759 for hackers-outgoing; Mon, 9 Dec 1996 02:47:45 -0800 (PST) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27748 for ; Mon, 9 Dec 1996 02:47:40 -0800 (PST) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id LAA06976; Mon, 9 Dec 1996 11:46:59 +0100 (MET) Date: Mon, 9 Dec 1996 11:46:58 +0100 (MET) From: Andrzej Bialecki To: Jake Hamby cc: hackers@freebsd.org, jkh@time.cdrom.com Subject: Re: Help, I've been SCOed! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 7 Dec 1996, Jake Hamby wrote: > 3) Start thinking about a custom help system like scohelp, which would > combine man pages and HTML through a custom HTTP server that could be > accessed remotely. Everyone is moving to HTML (or SGML) anyway, including > our own FreeBSD Handbook. We just need to make things more approachable > for new users. > > All of these have been discussed recently in hackers, so I thought I'd > post this as a summary of how one vendor has done things. I wish I had > some more insightful comments, but I hope that repeating what they've done > wrong should show us what we can do better. > > I hope you found these comments useful and relevant. Overall, I'd say > FreeBSD has done as good (and often better) job than many commercial UNIX > vendors have done, as my experience today proved! BTW, now I know that if > I had spent $10 on "Free SCO", it would've been wasted money. Rather to > find that out with someone else paying me, than vice versa! :-) Now, when > Free UnixWare comes out, that I might think about buying. Comments? > > -- Jake > +-------------------------------------------------------------------------+ Andrzej Bialecki _) _) _)_) _)_)_) _) _) --------------------------------------- _)_) _) _) _) _)_) _)_) Research and Academic Network in Poland _) _)_) _)_)_)_) _) _) _) Bartycka 18, 00-716 Warsaw, Poland _) _) _) _) _)_)_) _) _) +-------------------------------------------------------------------------+ From owner-freebsd-hackers Mon Dec 9 06:28:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA05344 for hackers-outgoing; Mon, 9 Dec 1996 06:28:54 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA05336 for ; Mon, 9 Dec 1996 06:28:51 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA03110; Mon, 9 Dec 1996 08:28:00 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma003100; Mon Dec 9 08:27:48 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA01829; Mon, 9 Dec 1996 08:28:01 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id IAA25901; Mon, 9 Dec 1996 08:28:12 -0600 (CST) Message-Id: <199612091428.IAA25901@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Michael Smith cc: erich@lodgenet.com (Eric L. Hernes), hackers@freebsd.org Subject: Re: Driver help In-reply-to: Your message of "Mon, 09 Dec 1996 16:07:48 +1030." <199612090537.QAA07561@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 08:28:12 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > >This implies that SysV doesn't provide the readv/writev interface, correct? Yup, I should have probably said SVR3. I can't figure out whether or not SVR4 has readv/writev, but the Magic Garden book indicates it has uiomove, so that point is probably moot. > >> I've also done similar things with the dma kernel support functions. >> Usually, the driver ends up looking more BSDish than SCOish, but >> isn't that how God intended? ;-) > >*grins* Now, is this documented in the DDWG? > naw, but the whole thing is (still) due for updating. My little stint with propagating userconfig changes to arbitrary kernels learned me up enough to fill in more pages ;-), now just for the time :( >> erich@lodgenet.com > >-- >]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ >]] Genesis Software genesis@gsoft.com.au [[ >]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ >]] realtime instrument control. (ph) +61-8-8267-3493 [[ >]] Unix hardware collector. "Where are your PEZ?" The Tick [[ eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Mon Dec 9 07:29:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA10018 for hackers-outgoing; Mon, 9 Dec 1996 07:29:33 -0800 (PST) Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA10010 for ; Mon, 9 Dec 1996 07:29:26 -0800 (PST) Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id KAA15167 for ; Mon, 9 Dec 1996 10:29:23 -0500 Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma015083; Mon Dec 9 10:28:21 1996 Received: from thoth.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA02074; Mon, 9 Dec 96 10:34:25 EST Received: from thoth (localhost [127.0.0.1]) by thoth.ctron.com (8.6.12/8.6.12) with SMTP id KAA02511 for ; Mon, 9 Dec 1996 10:29:55 -0500 Message-Id: <32AC3071.5C1B@ctron.com> Date: Mon, 09 Dec 1996 10:29:53 -0500 From: Alexander Seth Jones Organization: Cabletron Systems, Inc. X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: hackers@freebsd.org Subject: FreeBSD doesn't see my modem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm trying to install a modem on my FreeBSD box (486-66) running 2.1.5, but can't seem to get FreeBSD to see the card. I have tried configuring the card at both COM3 and COM4, but no luck...The BIOS does see the card, however... I've enabled all of the sio drivers (1-4)...What am I not doing? or doing wrong for that matter? -- Alex Jones | ajones@ctron.com Cabletron Systems, Inc. Durham, NH USA 03824 From owner-freebsd-hackers Mon Dec 9 08:34:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13927 for hackers-outgoing; Mon, 9 Dec 1996 08:34:01 -0800 (PST) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA13916 for ; Mon, 9 Dec 1996 08:33:55 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.8.4/8.8.4) with SMTP id LAA20712; Mon, 9 Dec 1996 11:32:55 -0500 Message-ID: <32AC3FBB.41C67EA6@aristar.com> Date: Mon, 09 Dec 1996 11:35:07 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: Alexander Seth Jones CC: hackers Subject: Re: FreeBSD doesn't see my modem References: <32AC3071.5C1B@ctron.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alexander Seth Jones wrote: > > Hello, > > I'm trying to install a modem on my FreeBSD box (486-66) running > 2.1.5, but can't seem to get FreeBSD to see the card. I have tried > configuring the card at both COM3 and COM4, but no luck...The BIOS does > see the card, however... > > I've enabled all of the sio drivers (1-4)...What am I not doing? or > doing wrong for that matter? > > -- > Alex Jones | ajones@ctron.com > Cabletron Systems, Inc. > Durham, NH USA 03824 Tell us more! Did you enable all those drivers in the kernel with the right IRQ's? Did you set anything up in /etc/rc.serial? Did you set everything up in UserConfig (-c from Boot: prompt)? Thanks -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Mon Dec 9 09:00:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA15422 for hackers-outgoing; Mon, 9 Dec 1996 09:00:37 -0800 (PST) Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA15417 for ; Mon, 9 Dec 1996 09:00:33 -0800 (PST) Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id MAA23156; Mon, 9 Dec 1996 12:00:08 -0500 Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma023019; Mon Dec 9 11:58:25 1996 Received: from thoth.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA12232; Mon, 9 Dec 96 12:04:21 EST Received: from thoth (localhost [127.0.0.1]) by thoth.ctron.com (8.6.12/8.6.12) with SMTP id LAA03636; Mon, 9 Dec 1996 11:59:51 -0500 Message-Id: <32AC4586.5772@ctron.com> Date: Mon, 09 Dec 1996 11:59:50 -0500 From: Alexander Seth Jones Organization: Cabletron Systems, Inc. X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: "Matthew A. Gessner" Cc: hackers Subject: Re: FreeBSD doesn't see my modem References: <32AC3071.5C1B@ctron.com> <32AC3FBB.41C67EA6@aristar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Matthew A. Gessner wrote: > > Alexander Seth Jones wrote: > > > > Hello, > > > > I'm trying to install a modem on my FreeBSD box (486-66) running > > 2.1.5, but can't seem to get FreeBSD to see the card. I have tried > > configuring the card at both COM3 and COM4, but no luck...The BIOS does > > see the card, however... > > > > I've enabled all of the sio drivers (1-4)...What am I not doing? or > > doing wrong for that matter? > > > > -- > > Alex Jones | ajones@ctron.com > > Cabletron Systems, Inc. > > Durham, NH USA 03824 > > Tell us more! Did you enable all those drivers in the kernel with the > right IRQ's? Did you set anything up in /etc/rc.serial? Did you set > everything up in UserConfig (-c from Boot: prompt)? > > Thanks Yes, the IRQs are configured correctly. I didn't touch /etc/rc.serial, nor did I do anything from UserConfig. Here's what I did: (1) set jumpers on the card for COM3 irq 5 (2) rebuilt the kernel to use sio[0-3] (for COM3) (3) installed new kernel and rebooted I have COM2, 3, and 4 open but FreeBSD didn't see the card at any of them > -- > Matthew Gessner, Computer Scientist, > Aristar, Inc. > 302 N. Cleveland-Massillon Rd. > Akron, OH 44333 > Voice (330) 668-2267, Fax (330) 668-2961 -- Alex Jones | ajones@ctron.com Cabletron Systems, Inc. Durham, NH USA 03824 From owner-freebsd-hackers Mon Dec 9 09:19:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA15992 for hackers-outgoing; Mon, 9 Dec 1996 09:19:09 -0800 (PST) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA15986 for ; Mon, 9 Dec 1996 09:19:06 -0800 (PST) Received: from crocodile.vale.com (crocodile [204.117.217.147]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id LAA02762; Mon, 9 Dec 1996 11:18:56 -0600 (CST) Received: from jaguar (jaguar.vale.com [204.117.217.146]) by crocodile.vale.com (8.8.3/8.7.3) with SMTP id LAA22883; Mon, 9 Dec 1996 11:18:53 -0600 (CST) Message-ID: <32AC49FF.72E4@vailsys.com> Date: Mon, 09 Dec 1996 11:18:55 -0600 From: Hal Snyder Reply-To: hal@vailsys.com Organization: Vail Systems, Inc. X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: Jake Hamby CC: hackers@freebsd.org Subject: Re: Help, I've been SCOed! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk SCO's html-ization of the docs is a good idea. But, I have never been able to get their cgi-bin man script to work with 3rd party browsers (you know, obscure browsers like NS 3.0 and IE 3.0), only the local client. Reminds me of the wretched toy browser on the Cisco doc CD. Where I work, we are stuck using SCO on systems where we need SQL servers and run Dialogic boards. It's a royal pain to work with, but unlike NT, it does not crash. 24x7. From owner-freebsd-hackers Mon Dec 9 09:20:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA16181 for hackers-outgoing; Mon, 9 Dec 1996 09:20:56 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA16173 for ; Mon, 9 Dec 1996 09:20:54 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA11376; Mon, 9 Dec 1996 12:20:18 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 9 Dec 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id HAA12205; Mon, 9 Dec 1996 07:50:22 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id HAA18033; Mon, 9 Dec 1996 07:52:43 -0500 (EST) Date: Mon, 9 Dec 1996 07:52:43 -0500 (EST) From: Thomas David Rivers Message-Id: <199612091252.HAA18033@lakes.water.net> To: spaz@u.washington.edu, ponds!lambert.org!terry Subject: Re: Chairs! Was: FreeBSD/Alpha (was Re: COMDEX trip report) Cc: ponds!FreeBSD.org!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Guys and gals; > > On Sun, 1 Dec 1996, Terry Lambert wrote: > > > It's on track. I've been off track from my injury. I have to get > > orthopedic furniture to let me sit hunched over for hours over a > > PC any more. My chair at home is a government surplus offic chair > > and just doesn't cut it for my back any more. 8-(. > > Office Depot has the OfficeStar ergonomic chair in maroon or blue > for us$179.00. I strongly reccommended it. We bought them at work, and > they are so damn good i got one for home. I had a 13 hour CMOS marathon > ( peed twice ) and i never even got stiff. > > All of u under 30's...if u like this line of work, get the ergo > chair and the keyboard now! and stack that monitor on top of 5 intel data > books! It is well worth the 225 bucks or so, believe me! Bad backs suck! > > > no, i have no financial interest in ofiice depot, just a profound interest > in all of you people staying productive..... > I can only echo and add to these sentiments... Last year, I spent the entire month of October lying in bed; mostly drugged up [I'm just now getting around to rewriting the code I wrote in that narcotic state :-) ] It is quite a demoralizing situation to be 33 years old and totally overcome by pain. Should it ever happen to you, my recommendation is physical therapy - and fast. The first time I had problems (I was 25) it took a year to get better. This last round took a month; which I attribute to my physical therapist. We are fortunate, here in Raleigh, NC - we've got a store that specializes in nothing but bad-back paraphenalia. I imagine, with all the computer industry in the area, they have an ample supply of customers. Please, oh please - if you're under thirty and seriously get into this type of work, go get a good chair - better yet; stand up every 15 minutes and stretch... Actually, one of the more clever things I've seen lately is this new NEC M700 monitor I've got - it will pop up a "health tip" every 15 minutes to encourage you to stand up... - Dave Rivers - From owner-freebsd-hackers Mon Dec 9 09:21:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA16206 for hackers-outgoing; Mon, 9 Dec 1996 09:21:06 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA16191 for ; Mon, 9 Dec 1996 09:20:58 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA11405; Mon, 9 Dec 1996 12:20:23 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 9 Dec 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id IAA15321; Mon, 9 Dec 1996 08:58:09 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id JAA18180; Mon, 9 Dec 1996 09:00:27 -0500 (EST) Date: Mon, 9 Dec 1996 09:00:27 -0500 (EST) From: Thomas David Rivers Message-Id: <199612091400.JAA18180@lakes.water.net> To: aqe2255@is2.nyu.edu, ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: FreeBSD on Laptop Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I want to buy a laptop that will work well with FreeBSD. I'm thinking > specifically of the ACER Light Note series. Do you have any information > on FreeBSD compatability with ACER and other laptops? > > As it so happens, I run FreeBSD 2.1.5 on an Acer Note (Not the "light" version) laptop.. Pentium 75, 8meg ram, 810meg hard disk, dual-scan display, PS/2 mouse, serial port... It runs just fine there - recognizes the sound card and everything. In fact, its one of my easier machines to handle. I do have a problem using the mouse-pad on very humid days; so I always carry a PS/2 mouse along with me. The only "real" problem I've encountered is the PCMCIA port - I haven't successfully gotten my no-name NE2000 card recognized yet. I wouldn't expect that to be a problem of the Acer though; but more likely the PCMCIA support in FreeBSD 2.1.5 (it's "beta" quality there.) - Dave Rivers - From owner-freebsd-hackers Mon Dec 9 09:39:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA17507 for hackers-outgoing; Mon, 9 Dec 1996 09:39:35 -0800 (PST) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA17486 for ; Mon, 9 Dec 1996 09:39:18 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.8.4/8.8.4) with SMTP id MAA21111; Mon, 9 Dec 1996 12:38:56 -0500 Message-ID: <32AC4F34.167EB0E7@aristar.com> Date: Mon, 09 Dec 1996 12:41:08 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: Alexander Seth Jones CC: hackers Subject: Re: FreeBSD doesn't see my modem References: <32AC3071.5C1B@ctron.com> <32AC3FBB.41C67EA6@aristar.com> <32AC4586.5772@ctron.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alexander Seth Jones wrote: > > Matthew A. Gessner wrote: > > > > Alexander Seth Jones wrote: > > > > > > Hello, > > > > > > I'm trying to install a modem on my FreeBSD box (486-66) running > > > 2.1.5, but can't seem to get FreeBSD to see the card. I have tried > > > configuring the card at both COM3 and COM4, but no luck...The BIOS does > > > see the card, however... > > > > > > I've enabled all of the sio drivers (1-4)...What am I not doing? or > > > doing wrong for that matter? > > > > > > -- > > > Alex Jones | ajones@ctron.com > > > Cabletron Systems, Inc. > > > Durham, NH USA 03824 > > > > Tell us more! Did you enable all those drivers in the kernel with the > > right IRQ's? Did you set anything up in /etc/rc.serial? Did you set > > everything up in UserConfig (-c from Boot: prompt)? > > > > Thanks > > Yes, the IRQs are configured correctly. > > I didn't touch /etc/rc.serial, nor did I do anything from UserConfig. > > Here's what I did: > > (1) set jumpers on the card for COM3 irq 5 > (2) rebuilt the kernel to use sio[0-3] (for COM3) > (3) installed new kernel and rebooted > > I have COM2, 3, and 4 open but FreeBSD didn't see the card at any > of them OK. When you get the boot prompt, do -c. When the prompt appears, type in 'visual' and go to the Communications section. Enable sio2 or whatever, then set up your addresses and irq's. That should do it. Matt -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Mon Dec 9 10:03:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18617 for hackers-outgoing; Mon, 9 Dec 1996 10:03:27 -0800 (PST) Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA18611 for ; Mon, 9 Dec 1996 10:03:24 -0800 (PST) Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id NAA28126; Mon, 9 Dec 1996 13:03:20 -0500 Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma027974; Mon Dec 9 13:01:37 1996 Received: from thoth.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA18051; Mon, 9 Dec 96 13:07:40 EST Received: from thoth (localhost [127.0.0.1]) by thoth.ctron.com (8.6.12/8.6.12) with SMTP id NAA04091; Mon, 9 Dec 1996 13:03:11 -0500 Message-Id: <32AC545E.475E@ctron.com> Date: Mon, 09 Dec 1996 13:03:11 -0500 From: Alexander Seth Jones Organization: Cabletron Systems, Inc. X-Mailer: Mozilla 3.0Gold (X11; I; SunOS 5.4 sun4m) Mime-Version: 1.0 To: "Matthew A. Gessner" Cc: hackers Subject: Re: FreeBSD doesn't see my modem References: <32AC3071.5C1B@ctron.com> <32AC3FBB.41C67EA6@aristar.com> <32AC4586.5772@ctron.com> <32AC4F34.167EB0E7@aristar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Matthew A. Gessner wrote: > > > OK. When you get the boot prompt, do -c. > When the prompt appears, type in 'visual' and go to the Communications > section. > > Enable sio2 or whatever, then set up your addresses and irq's. > > That should do it. > > Matt > -- > Matthew Gessner, Computer Scientist, > Aristar, Inc. > 302 N. Cleveland-Massillon Rd. > Akron, OH 44333 > Voice (330) 668-2267, Fax (330) 668-2961 OK, now I'm confused... (1) Why do I have to do a UserConfig if I've added the device to my config file? (2) When I did the UserConfig it was already enabled, I booted, and FreeBSD didn't see it... (3) When I did a UserConfig "visual" it was also already enabled, so I exited, booted, and FreeBSD saw it... In neither case did I make any changes... What's going on? -- Alex Jones | ajones@ctron.com Cabletron Systems, Inc. Durham, NH USA 03824 From owner-freebsd-hackers Mon Dec 9 10:05:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18755 for hackers-outgoing; Mon, 9 Dec 1996 10:05:13 -0800 (PST) Received: from gluon.mep.ruhr-uni-bochum.de (gluon.mep.ruhr-uni-bochum.de [134.147.160.165]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA18725 for ; Mon, 9 Dec 1996 10:04:44 -0800 (PST) Received: (from roberte@localhost) by gluon.mep.ruhr-uni-bochum.de (8.6.12/8.6.12) id TAA00339; Mon, 9 Dec 1996 19:01:42 +0100 From: Robert Eckardt Message-Id: <199612091801.TAA00339@gluon.mep.ruhr-uni-bochum.de> Subject: Re: Amd (K5) 586 /133 In-Reply-To: <199612090720.IAA06380@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "9. Dec. 96 8:20:11" To: kuku@gilberto.physik.RWTH-Aachen.DE Date: Mon, 9 Dec 1996 19:01:42 +0100 (MET) Cc: ejs@bfd.com, msmith@atrad.adelaide.edu.au, cau@cc.gatech.edu, kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100252689 Hz, i8254 clock: 1193485 Hz > > > CPU: AMD Unknown (100.23-MHz 586-class CPU) > > > > The K5-PR100 and K5-PR133 are both 100Mhz CPU's, the PR133 just has a more > > efficient pipelining/microcoding/etc. > > Aha, PR=Pentium Rating No, PR = Public Relations > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Robert -- Robert Eckardt ( Ruhr-Universitaet Bochum, Inst.f.Theor.Physik, NB6/169 ) Universitaetsstrasse 150, D-44780 Bochum, Germany ----X---8---- Telefon: +49 234 700-3709, Telefax: +49 234 7094-574 8 E-Mail: RobertE@MEP.Ruhr-Uni-Bochum.de --------8---- URL: http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte >>> To be successful one needs friends, <<< >>> To be very successful one needs enemies. <<< From owner-freebsd-hackers Mon Dec 9 10:11:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19397 for hackers-outgoing; Mon, 9 Dec 1996 10:11:30 -0800 (PST) Received: from super-g.inch.com (spork@super-g.com [204.178.32.161]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA19390 for ; Mon, 9 Dec 1996 10:11:26 -0800 (PST) Received: from localhost (spork@localhost) by super-g.inch.com (8.7.6/8.6.9) with SMTP id NAA02193; Mon, 9 Dec 1996 13:04:06 -0500 Date: Mon, 9 Dec 1996 12:04:05 -0600 (CST) From: "S(pork)" X-Sender: spork@super-g.inch.com To: michael butler cc: Jason Fesler , hackers@freebsd.org Subject: Re: Apache and huge numbers of IP's.. In-Reply-To: <199612080202.NAA26188@asstdc.scgt.oz.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is an interesting question; a while back I posted something similar and everyone agreed "maxusers" set to a high value would take care of max processes and max open files... However, in setting up a medium duty (2G/Day) dedicated webserver, I was running out of processes with maxusers at 200. When I re-compiled the kernel with params like those below, all was well. Could someone clarify? I'll be building another big machine (news) soon, and I will be dealing with the same issue. Thanks, Charles On Sun, 8 Dec 1996, michael butler wrote: > The number of file handles available is related to the maxusers config > parameter. If you wish to alter that without affecting the other table > sizes, you can add something like this to your config file .. > > options "CHILD_MAX=512" > options "OPEN_MAX=512" [snip] > michael > From owner-freebsd-hackers Mon Dec 9 10:17:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19619 for hackers-outgoing; Mon, 9 Dec 1996 10:17:25 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA19599; Mon, 9 Dec 1996 10:17:05 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-206.rdcy01.pacbell.net) by mail.crl.com with SMTP id AA21591 (5.65c/IDA-1.5); Mon, 9 Dec 1996 10:17:31 -0800 Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id KAA01333; Mon, 9 Dec 1996 10:04:26 -0800 (PST) Message-Id: <199612091804.KAA01333@precipice.shockwave.com> To: Michael Smith , Andrew.Gordon@net-tel.co.uk, nate@freebsd.org Cc: mobile@freebsd.org, hackers@freebsd.org, pst@jnx.com Subject: Re: need help with a PC CARD NE2000 clone... Date: Mon, 09 Dec 1996 10:04:26 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [This is a response to Michael and Andrew's suggestions (thanks) with a comprehensive debugging session and some observations about the dumpcis output at the end.] > Are you using stock -current. or have you added the PAO patches over the top? -current > Try removing the "ether" line if you are running stock -current. This > tells the PAO code to look in the CIS for the hardware address, while > my modifications to the 'ed' driver dig it out from the normal > location hung off the 8390 as per the NE-2000. Tried both ways. > > Code 240 not found > I've never seen this message before. Try paring your /etc/pccardd.conf > file right down to the bone, in case this is a syntax error there. Tried it. > > I've set up ed0 and ed1 in my kernel config as follows (just in case the > > card wanted to be at fixed places or have fixed irq's): > > As long as you have a message coming up after the 'ed0' signon saying > "pccard driver ed0 added", there's a free 'ed' device for the card probe to > attach to. Yep, that's OK. It seems to be bailing out long before we even play driver games. > I can't find an "allocate_memory" in any of the -current pccard-related > sources, so I have to assume that you've applied the PAO patches. No, I did /not/. Sorry, gdb trace will explain all > Note that if this really is an NE2000 clone, it doesn't need any > memory address space (the on-card RAM is driven by i/o) - unlike some > of the other cards supported by the ed driver. Yeah, I agree. Why does it have two blocks of memory? > On the other hand, the card claims to have memory on it (from dumpcis). > Perhaps its an "enhanced" NE2000 which can be memory-addressed in > some proprietary way? This could cause confusion, where pccardd > knows the card has memory and that ed usually wants to use memory, > but in this case has probed it as an NE2000 and decided that it > doesn't need any. I agree with you, but it's bailing long before it even decides to play ed0 games (I think). It's failing in assign_io() which is calling the memory alloc block check routine with 1024 bytes, which is smaller than MEMUNIT. urk? Here are all the details.... I did some more debugging on my ethernet card problem. It looks like we're failing long before we even start to play driver games. To recap, here's the data, plus a gdb trace: # cat /etc/pccard.conf # Sample PCCARD configuration file # # Removing all IRQ conflicts from this file can't be done because of some # IRQ-selfish PC-cards. So if you want to use some of these cards in # your machine, you will be forced to modify their IRQ parameters from # the following list. # # IRQ == 0 means "allocate free IRQ from IRQ pool" # IRQ == 16 means "do not use IRQ (e.g. PIO mode)" # # $Id: pccard.conf.sample,v 1.4 1996/06/19 01:28:07 nate Exp $ # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 3 5 10 11 13 15 # Available memory slots memory 0xd0000 96k (I've tried this at d4000) card "PMX " "PE-200" config 0x1 "ed0" 11 # ether 0xff0 (I've tried it with & without) insert echo PMX PE-200 Ethernet inserted insert /etc/pccard_ether ed0 remove echo PMX PE-200 Ethernet removed remove /sbin/ifconfig ed0 delete dmesg: Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-961208-SNAP #1: Mon Dec 9 00:40:47 1996 root@foo.shockwave.com:/usr/src/sys/compile/LAP Calibrating clock(s) relative to mc146818A clock ... i8254 clock: 1193312 Hz CPU: i486DX (486-class CPU) real memory = 8388608 (8192K bytes) FreeBSD Kernel Configuration Utility - Version 1.1 Type "help" for help or "visual" to go to the visual configuration interface (requires MGA/VGA display or serial terminal capable of displaying ANSI graphics). config> ls Device port irq drq iomem iosize unit flags enabled fdc0 0x3f0 6 2 0x0 0 0 0x0 Yes wdc0 0x1f0 14 -1 0x0 0 0 0x80ff80ff Yes sc0 0x60 1 -1 0x0 0 0 0x0 Yes sio0 0x3f8 4 -1 0x0 0 0 0x0 Yes sio1 0x2f8 3 -1 0x0 0 1 0x0 Yes pca0 0x40 -1 -1 0x0 0 0 0x0 Yes lpt0 0xffffffff 7 -1 0x0 0 0 0x0 Yes psm0 0x60 12 -1 0x0 0 0 0x0 Yes ed0 0x300 11 -1 0xd8000 0 0 0x0 Yes ed1 0x310 5 -1 0xd8000 0 1 0x0 Yes npx0 0xf0 13 -1 0x0 0 0 0x0 Yes apm0 0x0 -1 -1 0x0 0 0 0x0 Yes config> iomem ed0 0xd4000 config> ls Device port irq drq iomem iosize unit flags enabled fdc0 0x3f0 6 2 0x0 0 0 0x0 Yes wdc0 0x1f0 14 -1 0x0 0 0 0x80ff80ff Yes sc0 0x60 1 -1 0x0 0 0 0x0 Yes sio0 0x3f8 4 -1 0x0 0 0 0x0 Yes sio1 0x2f8 3 -1 0x0 0 1 0x0 Yes pca0 0x40 -1 -1 0x0 0 0 0x0 Yes lpt0 0xffffffff 7 -1 0x0 0 0 0x0 Yes psm0 0x60 12 -1 0x0 0 0 0x0 Yes ed0 0x300 11 -1 0xd4000 0 0 0x0 Yes ed1 0x310 5 -1 0xd8000 0 1 0x0 Yes npx0 0xf0 13 -1 0x0 0 0 0x0 Yes apm0 0x0 -1 -1 0x0 0 0 0x0 Yes config> q avail memory = 6819840 (6660K bytes) PC-Card Intel 82365 (5 mem & 2 I/O windows) pcic: controller irq 3 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> pccard driver ed added ed0 not found at 0x300 ed1: disabled, not probed. pccard driver sio added sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 not found at 0x2f8 pca0 on motherboard pca0: PC speaker audio driver lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 2 buttons? fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , multi-block-16 wd0: 516MB (1058400 sectors), 1050 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 Card inserted, slot 1 # cat /etc/motd FreeBSD 2.2-961208-SNAP (LAP) #1: Mon Dec 9 00:40:47 1996 (-current as of yesterday, no PAO patches) # gdb pccardd GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc... (gdb) break assign_io Breakpoint 1 at 0x1b39: file cardd.c, line 464. (gdb) run -d -v Starting program: /usr/src/usr.sbin/pccard/pccardd/pccardd -d -v Card manuf PMX , vers PE-200 Configuration entries: Index code = 0x1, driver name = ed0 Insert commands are: echo PMX PE-200 Ethernet inserted /etc/pccard_ether ed0 Remove commands are: echo PMX PE-200 Ethernet removed /sbin/ifconfig ed0 delete Code 240 not found Code 240 not found code Unknown ignored Breakpoint 1, assign_io (sp=0x19100) at cardd.c:464 464 cis = sp->cis; (gdb) n 465 defconf = cis->def_config; (gdb) print *cis $1 = {tlist = 0x18160, manuf = "PMX ", '\000' , vers = "PE-200", '\000' , add_info1 = "ETHERNET", '\000' , add_info2 = "R01", '\000' , maj_v = 4 '\004', min_v = 1 '\001', last_config = 1 '\001', ccrs = 1 '\001', reg_addr = 256, attr_mem = {valid = 1 '\001', type = 5 '\005', speed = 3 '\003', wps = 0 '\000', addr = 0 '\000', units = 1 '\001'}, common_mem = { valid = 1 '\001', type = 13 '\r', speed = 4 '\004', wps = 1 '\001', addr = 0 '\000', units = 3 '\003'}, def_config = 0x1d080, conf = 0x1d080} (gdb) n 466 for (cisconf = cis->conf; cisconf; cisconf = cisconf->next) (gdb) n 467 if (cisconf->id == sp->config->index) (gdb) print *cisconf $2 = {next = 0x0, pwr = 0, timing = 0, iospace = 1, irq = 1, memspace = 1, misc_valid = 0, id = 1 '\001', io_blks = 2 '\002', io_addr = 10 '\n', io_bus = 2 '\002', io = 0x1a1c0, irqlevel = 0 '\000', irq_flags = 48 '0', irq_mask = 48892, memwins = 2 '\002', mem = 0x1a1e0, misc = 0 '\000'} (gdb) print *sp $3 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, card_config = 0x0, devname = '\000' , eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, irq = 0} (gdb) print *sp->config $4 = {next = 0x0, index = 1 '\001', driver = 0x180e0, irq = 11, flags = 0, inuse = 1 '\001'} (gdb) n 469 if (cisconf == 0) (gdb) n 471 sp->card_config = cisconf; (gdb) n 477 if (cisconf->memspace || (defconf && defconf->memspace)) { (gdb) n 480 mp = cisconf->mem; (gdb) print cisconf->memspace $5 = 1 (gdb) print defconf $6 = (struct cis_config *) 0x1d080 (gdb) print defconf->memspace $7 = 1 (gdb) print cisconf $8 = (struct cis_config *) 0x1d080 NOTE: cisconf and defconf are the same??? (gdb) n 481 if (!cisconf->memspace) (gdb) n 483 sp->mem.size = mp->length; (gdb) n 484 sp->mem.cardaddr = mp->address; (gdb) n 487 sp->mem.addr = sp->config->driver->mem; (gdb) n 492 if (sp->mem.size && sp->mem.addr == 0) { (gdb) print *sp $9 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, card_config = 0x1d080, devname = '\000' , eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 1024, flags = 0, cardaddr = 0}, irq = 0} NOTE: why is sp->mem.size == 1024? <---------------------------- (gdb) n 493 sp->mem.addr = alloc_memory(mp->length); (gdb) s alloc_memory (size=-272639028) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); (gdb) print *mem_avail @200 (oops, should have just printed 12 bytes) $10 = {"\000\000\000\000\000\000\000\000\000\000\000\000\000PMX \000\000\000\000\000\000\000\000\000\000PE-200\000\000\000\000\000\000\000\000\000\000ed0", '\000' , "ed", '\000' , "\220 \001\000\000P\001", '\000' , " \201\001\000\000\000\000\000\000\000\000\0000 \001\000@P\001", '\000' , "@\201\001\000\000\000\000\000\000\000\000\000/dev/card0\000\000\000\000\000\000/dev/card1\000\000\000\000\000\000\000!\001\000\001\000\000\000\003\000\000\000p \001\000\\003\000\000\000\000"} (gdb) s bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:106 106 int found = 0; (gdb) where #0 bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:106 #1 0x341f in alloc_memory (size=1024) at util.c:125 #2 0x1bb6 in assign_io (sp=0x19100) at cardd.c:493 #3 0x18b5 in card_inserted (sp=0x19100) at cardd.c:323 #4 0x1696 in slot_change (sp=0x19100) at cardd.c:246 #5 0x15ec in readslots () at cardd.c:216 #6 0x1257 in main (argc=3, argv=0xefbfdd04) at cardd.c:105 (gdb) up #1 0x341f in alloc_memory (size=1024) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); (gdb) print size $12 = 1024 (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print nbits $13 = 96 (gdb) n 109 if (bit_test(nm, i)) { (gdb) print 96 / 8 $14 = 12 (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print i $15 = 0 (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print i $16 = 6 (gdb) fin Run till exit from #0 bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:108 0x341f in alloc_memory (size=1024) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); Value returned is $17 = -1 (gdb) n 126 if (i < 0) (gdb) n 127 return (0); (gdb) n 130 } (gdb) n assign_io (sp=0x19100) at cardd.c:494 494 if (sp->mem.addr == 0) (gdb) print sp->mem.addr $18 = 0 (gdb) n 536 return (-1); (gdb) c Continuing. cardd: Resource allocation failure for PMX Here's the pccardc dumpcis output again (look where I put arrows): Code 240 not found Code 240 not found code Unknown ignored Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: dc 03 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 100nS, Memory block size = 32Kb, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 53 01 ff Attribute memory device information: Device number 1, type FLASH EEPROM, WPS = OFF Speed = 150nS, Memory block size = 2Kb, 1 units Tuple #3, code = 0x21 (Functional ID), length = 2 000: 06 03 Network/LAN adapter - POST initialize - Card has ROM Tuple #4, code = 0x15 (Version 1 info), length = 30 000: 04 01 50 4d 58 20 20 20 00 50 45 2d 32 30 30 00 010: 45 54 48 45 52 4e 45 54 00 52 30 31 00 ff Version = 4.1, Manuf = [PMX ],card vers = [PE-200] Addit. info = [ETHERNET],[R01] Tuple #5, code = 0x1a (Configuration map), length = 5 000: 01 01 00 01 01 Reg len = 2, config register addr = 0x100, last config = 0x1 Registers: X------- Tuple #6, code = 0x1b (Configuration entry), length = 25 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 010: 00 00 40 0d 40 40 00 40 0d Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x10 I/O address # 2: block start = 0x310 block length = 0x10 IRQ modes: Level IRQs: 4 5 10 11 12 13 14 15 -> why? what could this be for? It's 1k long? -> Memory descriptor 1 -> blk length = 0x400 card addr = 0x000 host addr = 0xd4000 Memory descriptor 2 blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 Tuple #7, code = 0x0 (Null tuple), length = 9 000: 57 42 20 4c 41 4e 20 20 ff Tuple #8, code = 0x14 (No link), length = 0 Tuple #9, code = 0xff (Terminator), length = 0 2 slots found From owner-freebsd-hackers Mon Dec 9 10:19:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19722 for hackers-outgoing; Mon, 9 Dec 1996 10:19:17 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA19715 for ; Mon, 9 Dec 1996 10:19:15 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA00914; Mon, 9 Dec 1996 10:58:32 -0700 From: Terry Lambert Message-Id: <199612091758.KAA00914@phaeton.artisoft.com> Subject: Re: trying to upgrade to 2.2 To: SimsS@IBM.Net Date: Mon, 9 Dec 1996 10:58:32 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199612082312.XAA100434@smtp-gw01.ny.us.ibm.net> from "Steve Sims" at Dec 8, 96 06:11:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > build /u/build2.2/Root, using dump/restore to copy my (working) > > 2.1.6.1 system (/, /var, /usr). > > > > cvsupped 12/6 (release=cvs host=cvsup.freebsd.org) > > > > extracted with: > > cvs -d /home/ncvs $QUIET -r checkout -r RELENG_2_2 -d `pwd`/src src > > and this reminded me of a question that's been rattling around in the back > of my brain for some time: Where is the definitive listing of tags that > cvsup can use to pull code sets from the cvs repository? Stated another > way, how would an idjit (me) know what tag names in cvs correspond to what > versions (I presume all the way back to 2.0.something. > > On the machine that I use to track -CURRENT, 'tag=.', so that's a > no-brainer, but what if I wanted to track, say, 2.2? > > Inquiring minds want to know. (Yes, I've R'd TFM). Actually, there should have been a list checked in at the top level so that you could check out the list, then check out the tag branch. You would, of course, reset the tags on the tag list file each time you checked it out... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Dec 9 11:10:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22464 for hackers-outgoing; Mon, 9 Dec 1996 11:10:29 -0800 (PST) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22457 for ; Mon, 9 Dec 1996 11:10:27 -0800 (PST) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id LAA02529 for hackers@freebsd.org; Mon, 9 Dec 1996 11:10:26 -0800 Date: Mon, 9 Dec 1996 11:10:26 -0800 From: "Jin Guojun[ITG]" Message-Id: <199612091910.LAA02529@george.lbl.gov> To: hackers@freebsd.org Subject: Q for loadable network driver Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a question in writing a loadable network driver. How is the PCI device table is load into pcidevice_set list -- pcidevice_set.ls_items That is, what is the mechanism to replace these lines : struct pci_device xyz_device = { OEM_DRVNAME, xyz_probe, xyz_attach, &xyz_count, xyz_shutdown }; DATA_SET(pcidevice_set, xyz_device); Thanks, -Jin From owner-freebsd-hackers Mon Dec 9 11:13:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22702 for hackers-outgoing; Mon, 9 Dec 1996 11:13:00 -0800 (PST) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA22691 for ; Mon, 9 Dec 1996 11:12:54 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA14156; Mon, 9 Dec 1996 11:12:17 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma014154; Mon Dec 9 11:12:03 1996 Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id LAA08117; Mon, 9 Dec 1996 11:12:03 -0800 (PST) From: Archie Cobbs Message-Id: <199612091912.LAA08117@bubba.whistle.com> Subject: Re: FreeBSD doesn't see my modem In-Reply-To: <32AC545E.475E@ctron.com> from Alexander Seth Jones at "Dec 9, 96 01:03:11 pm" To: ajones@ctron.com (Alexander Seth Jones) Date: Mon, 9 Dec 1996 11:12:02 -0800 (PST) Cc: mgessner@aristar.com, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > OK, now I'm confused... > > (1) Why do I have to do a UserConfig if I've added the device to my > config file? > > (2) When I did the UserConfig it was already enabled, I booted, and > FreeBSD didn't see it... > > (3) When I did a UserConfig "visual" it was also already enabled, so > I exited, booted, and FreeBSD saw it... > > In neither case did I make any changes... > > What's going on? > > -- > Alex Jones | ajones@ctron.com > Cabletron Systems, Inc. > Durham, NH USA 03824 We have had some trouble in the past getting FreeBSD to recognize certain modems. Cardinal comes to mind. What kind of modem are you using? The solution was to increase some of the DELAY() calls in sioprobe(). If you go into user config, and set the flags to 0x80, you'll see which test the probe is failing at. If this is the problem, you may need to edit /usr/src/sys/i386/isa/sio.c Look for the comment /* EXTRA DELAY? */ in the function sioprobe() :-) This of course may not be your particular situation but it's worth a try. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Mon Dec 9 13:22:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01327 for hackers-outgoing; Mon, 9 Dec 1996 13:22:54 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA01316 for ; Mon, 9 Dec 1996 13:22:51 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id QAA24122 for freebsd-hackers@freebsd.org; Mon, 9 Dec 1996 16:22:40 -0500 (EST) From: Charles Henrich Message-Id: <199612092122.QAA24122@crh.cl.msu.edu> Subject: Any suggestions? DG? To: freebsd-hackers@freebsd.org Date: Mon, 9 Dec 1996 16:22:40 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Im about to bring up a ALR PentiumPro system w/ 256mb of ram and 12 2gb Fast/Wide 7200 RPM Quantum's on 4 Adaptec 2940 controllers w/ an additional 4gb 7200 rpm disk for the OS for a news server. I will be using FreeBSD 2.2-WHATEVER w/ INN 1.5.1, anyone have any suggestions as to kernel tweaks I might want to make, other than the standard out-of-box rebuild that I might to? What special was done to ftp.cdrom.com, anything? Is it running 2.2? Thanks! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Mon Dec 9 13:23:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01362 for hackers-outgoing; Mon, 9 Dec 1996 13:23:05 -0800 (PST) Received: from mira.net.au (eplet.mira.net.au [203.9.190.17]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA01355 for ; Mon, 9 Dec 1996 13:23:01 -0800 (PST) Received: (qmail 10833 invoked from network); 9 Dec 1996 21:22:50 -0000 Received: from melb.werple.net.au (203.9.190.18) by eplet.mira.net.au with SMTP; 9 Dec 1996 21:22:50 -0000 Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id IAA04223 for hackers@FreeBSD.org; Tue, 10 Dec 1996 08:15:06 +1100 (EST) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id IAA10527 for hackers@FreeBSD.org; Tue, 10 Dec 1996 08:18:04 +1100 (EST) From: John Birrell Message-Id: <199612092118.IAA10527@freebsd1.cimlogic.com.au> Subject: poll(2) To: hackers@FreeBSD.org Date: Tue, 10 Dec 1996 08:18:03 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk G'day, There are a few things that NetBSD has added recently that belong (IMHO) in FreeBSD too. One of them is poll(2), which gives an alternative to select(2) that does not suffer from the FD_SETSIZE "feature". Anyone planning to add this? -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au; jb@netbsd.org 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Mon Dec 9 13:24:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01514 for hackers-outgoing; Mon, 9 Dec 1996 13:24:19 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA01508 for ; Mon, 9 Dec 1996 13:24:13 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id PAA02930; Mon, 9 Dec 1996 15:22:51 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma002925; Mon Dec 9 15:22:40 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id PAA11734; Mon, 9 Dec 1996 15:22:53 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id PAA13091; Mon, 9 Dec 1996 15:22:54 -0600 (CST) Message-Id: <199612092122.PAA13091@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Jin Guojun[ITG]" cc: hackers@freebsd.org Subject: Re: Q for loadable network driver In-reply-to: Your message of "Mon, 09 Dec 1996 11:10:26 PST." <199612091910.LAA02529@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 15:22:53 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jin Guojun[ITG]" writes: >I have a question in writing a loadable network driver. >How is the PCI device table is load into pcidevice_set list -- > pcidevice_set.ls_items it's a linker set, see the archives for Terry's good explanation of what these are and how they work. >That is, what is the mechanism to replace these lines : > >struct pci_device xyz_device = { > OEM_DRVNAME, > xyz_probe, > xyz_attach, > &xyz_count, > xyz_shutdown >}; > >DATA_SET(pcidevice_set, xyz_device); I believe that they're only used during the autoconf phase of the pci bus. The pci subsystem gets a signature of all devices on the bus; then asks each driver in the pcidevice_set, `hey is this your device?' by calling the probe/attach members. I think they can savely be #ifdef'ed out for the lkm case, because you're not autoconf'ing. Then lkm equivalent is done in the xyz_load call. You might be able to peruse a pci data structure that has a list of `found but not claimed' devices where you should find your device's signature, or you may be able to play with /usr/bin/pciconf to determine if your device exists before attempting the modload. > > >Thanks, > >-Jin > > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Mon Dec 9 13:30:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01812 for hackers-outgoing; Mon, 9 Dec 1996 13:30:41 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA01802 for ; Mon, 9 Dec 1996 13:30:29 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-10.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA09378 (5.67b/IDA-1.5 for ); Mon, 9 Dec 1996 22:29:44 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id QAA17337; Mon, 9 Dec 1996 16:02:15 +0100 (CET) Message-Id: Date: Mon, 9 Dec 1996 16:00:54 +0100 From: se@FreeBSD.org (Stefan Esser) To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hackers@FreeBSD.org Subject: Re: VX-aware PCI probe References: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au>; from Michael Smith on Dec 9, 1996 14:50:14 +1030 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Dec 9, msmith@atrad.adelaide.edu.au (Michael Smith) wrote: > > Can someone with a VX-chipset motherboard confirm that this patch correctly > identifies their chipset before I commit it? (beware snarf-n-barf damage). Can't check that, but it doesn't look completely wrong :) > What was the consensus on codenames? I notice that the old "Triton" > comments have gone, but some of the others are still there. There is a problem with using "Triton" in Germany, since some French company got "Tricon" as a registered trademark, and some lawyer is suing anybody violating that trademark ... (That lawyer made a special agreement with Microsoft, BTW, which allows them to identify the Triton chip-set under Win/95. But a lot of motherboards used to print Triton in the boot message, and the dealers had to stop selling them, and to pay $1000 to $7000i ...) > Any interest in a general PCI device ID/name mapping registry? I'd be > happy to collect all the intelligence scattered among the files in > sys/pci and write a small lookup function to return it appropriately. I'm planning to remove most of the verbose PCI probe messages, and have a (easily configurable) user-land program know much more about the different PCI chips, than you'd ever want to put into the kernel. Only information that might be useful for debugging in case of a boot failure should be printed by the probe/attach code, IMHO. This will remove some 7KB from the kernel binary, and will add a few tens of KB to the disk space requirements, if in fact lots more vendors and devices will be known to that code ... > + case 0x70308086: > + return ("Intel 82437VX PCI cache memory controller"); Regards, STefan From owner-freebsd-hackers Mon Dec 9 13:54:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03816 for hackers-outgoing; Mon, 9 Dec 1996 13:54:15 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA03809 for ; Mon, 9 Dec 1996 13:54:13 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id VAA151683; Mon, 9 Dec 1996 21:54:05 GMT Message-Id: <199612092154.VAA151683@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-141.va.us.ibm.net(166.72.229.141) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaHQsDe7; Mon Dec 9 21:53:34 1996 Reply-To: From: "Steve Sims" To: <34lz5ap@cmuvm.csv.cmich.edu> Cc: , Subject: FreeBSD & Compaq Aero - sio question Date: Mon, 9 Dec 1996 16:52:38 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In your installation of FreeBSD on your Compaq Aero, were you successful in getting the internal serial port to probe correctly? I've tried a GENERIC kernel from 2.1.6 and 2.2-ALPHA, as well as Hosokawa's PAO-enabled boot floppy and none of them probe the internal port successfully, regardless of the CMOS configuration (com1: or com2:) of the hardware (set though Compaq's diagnostic / setup floppy). This is similar to a problem that I had with FreeBSD on a Compaq LTE-Elite; while the OS ran fine, neither sio0 or sio1 ever did probe correctly (even with some extended delay added to sio.c). I ran this problem by Nate and Bruce, but never really delved under the covers and sorted it out. Apparently our friends at Compaq do something goofy with their hardware, but I haven't a clue as to what. I assume you have had some success???? ...sjs... From owner-freebsd-hackers Mon Dec 9 14:01:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA04402 for hackers-outgoing; Mon, 9 Dec 1996 14:01:23 -0800 (PST) Received: from CMUVM.CSV.CMICH.EDU (SMTP@cmuvm.csv.cmich.edu [141.209.1.16]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA04397 for ; Mon, 9 Dec 1996 14:01:21 -0800 (PST) Received: from em3101.emmons.cmich.edu by CMUVM.CSV.CMICH.EDU (IBM VM SMTP V2R2) with TCP; Mon, 09 Dec 96 16:59:37 EST Received: by em3101.emmons.cmich.edu with Microsoft Mail id <01BBE5F2.F524DA20@em3101.emmons.cmich.edu>; Mon, 9 Dec 1996 17:03:54 -0500 Message-ID: <01BBE5F2.F524DA20@em3101.emmons.cmich.edu> From: John David Steffes <34lz5ap@cmuvm.csv.cmich.edu> To: "'Steve Sims'" Cc: "hackers@FreeBSD.ORG" , "aero@aisb.org" Subject: RE: FreeBSD & Compaq Aero - sio question Date: Mon, 9 Dec 1996 17:03:52 -0500 Encoding: 28 TEXT Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To be honest, I never have used my Serial Port on my Aero. I don't even know if it works. But I will try after I write this letter. JDS ---------- From: Steve Sims[SMTP:SimsS@ibm.net] Sent: Monday, December 09, 1996 4:53 PM To: 34lz5ap@cmuvm.csv.cmich.edu Cc: hackers@FreeBSD.ORG; aero@aisb.org Subject: FreeBSD & Compaq Aero - sio question In your installation of FreeBSD on your Compaq Aero, were you successful in getting the internal serial port to probe correctly? I've tried a GENERIC kernel from 2.1.6 and 2.2-ALPHA, as well as Hosokawa's PAO-enabled boot floppy and none of them probe the internal port successfully, regardless of the CMOS configuration (com1: or com2:) of the hardware (set though Compaq's diagnostic / setup floppy). This is similar to a problem that I had with FreeBSD on a Compaq LTE-Elite; while the OS ran fine, neither sio0 or sio1 ever did probe correctly (even with some extended delay added to sio.c). I ran this problem by Nate and Bruce, but never really delved under the covers and sorted it out. Apparently our friends at Compaq do something goofy with their hardware, but I haven't a clue as to what. I assume you have had some success???? ...sjs... From owner-freebsd-hackers Mon Dec 9 15:00:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08028 for hackers-outgoing; Mon, 9 Dec 1996 15:00:55 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA08021 for ; Mon, 9 Dec 1996 15:00:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02008; Mon, 9 Dec 1996 15:40:03 -0700 From: Terry Lambert Message-Id: <199612092240.PAA02008@phaeton.artisoft.com> Subject: Re: poll(2) To: jb@cimlogic.com.au (John Birrell) Date: Mon, 9 Dec 1996 15:40:03 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199612092118.IAA10527@freebsd1.cimlogic.com.au> from "John Birrell" at Dec 10, 96 08:18:03 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There are a few things that NetBSD has added recently that belong (IMHO) > in FreeBSD too. One of them is poll(2), which gives an alternative to > select(2) that does not suffer from the FD_SETSIZE "feature". > > Anyone planning to add this? It's relatively trivial to build a poll() using select() (ie: library wrapper). If someone decides to add poll, note: the tiemout is only good to 1ms theoretical (argument resolution) or 10ms actual (system clock update frequency), so it isn't suitable for doing a lot of things that select() *is* suitable for doing... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Dec 9 15:06:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08293 for hackers-outgoing; Mon, 9 Dec 1996 15:06:08 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08287 for ; Mon, 9 Dec 1996 15:06:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.7.6/8.6.12) with SMTP id SAA01955; Mon, 9 Dec 1996 18:05:53 -0500 (EST) Message-Id: <199612092305.SAA01955@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: Host localhost [127.0.0.1] didn't use HELO protocol To: John Birrell Cc: hackers@freebsd.org Subject: Re: poll(2) In-reply-to: Your message of "Tue, 10 Dec 1996 08:18:03 +1100." <199612092118.IAA10527@freebsd1.cimlogic.com.au> Date: Mon, 09 Dec 1996 18:05:53 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > There are a few things that NetBSD has added recently that belong (IMHO) > in FreeBSD too. One of them is poll(2), which gives an alternative to > select(2) that does not suffer from the FD_SETSIZE "feature". Note that the 2.2 kernel does not have this limitation (kern/sys_generic.c:select() allocates space as necessary for the three bitstrings). You can compile user programs with FD_SETSIZE different from the default of 256. You can even use different size bitstrings in the same program in different select() calls but you have to cast fd_mask* to fd_set* There are other reasons why poll() can be preferable to select(): - it does not overwrite the input arguments - it is more efficient when the fd set being tested is a small subset of the total fds in use. - fds are not serviced from the lowest numbered fd to the highest. (servicing by the increasing fd number implicitly favors the lower numbered fds.) - more conditions per fd can be tested. From owner-freebsd-hackers Mon Dec 9 15:13:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA08667 for hackers-outgoing; Mon, 9 Dec 1996 15:13:24 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA08661 for ; Mon, 9 Dec 1996 15:13:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id PAA11079; Mon, 9 Dec 1996 15:04:22 -0800 (PST) Message-Id: <199612092304.PAA11079@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert Cc: jb@cimlogic.com.au (John Birrell), hackers@freebsd.org Subject: Re: poll(2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 09 Dec 1996 15:04:22 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996 15:40:03 -0700 (MST) Terry Lambert wrote: > It's relatively trivial to build a poll() using select() (ie: library > wrapper). ...indeed. I did that once (in 1994), so that I could compile some SVR4 sources under NetBSD/hp300. However, doing that limits poll() to select()'s functionality. > If someone decides to add poll, note: the tiemout is only good to 1ms > theoretical (argument resolution) or 10ms actual (system clock update > frequency), so it isn't suitable for doing a lot of things that select() > *is* suitable for doing... I'd like to see a upoll(2), as well... an extension, that gives the funtionality of poll, but takes a more reasonable timeout (like, probably a struct timespec). Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Mon Dec 9 15:26:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA09664 for hackers-outgoing; Mon, 9 Dec 1996 15:26:42 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA09656 for ; Mon, 9 Dec 1996 15:26:40 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id XAA21936; Mon, 9 Dec 1996 23:26:33 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA009343992; Mon, 9 Dec 1996 23:26:32 GMT Message-Id: <32ACA091.2EFB@fsl.noaa.gov> Date: Mon, 09 Dec 1996 16:28:17 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: Bakul Shah Cc: John Birrell , hackers@freebsd.org Subject: Re: poll(2) References: <199612092305.SAA01955@chai.plexuscom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bakul Shah wrote: > [about the advantages of poll] Nice though it is, it's a terrible name for a system call. You use it to avoid polling ... and yet it's called "poll". (Of course, the reminder of SysV doesn't help much either. :-) -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Mon Dec 9 15:29:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA09985 for hackers-outgoing; Mon, 9 Dec 1996 15:29:40 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA09979 for ; Mon, 9 Dec 1996 15:29:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id PAA11225; Mon, 9 Dec 1996 15:20:43 -0800 (PST) Message-Id: <199612092320.PAA11225@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert , jb@cimlogic.com.au (John Birrell), hackers@freebsd.org Subject: Re: poll(2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 09 Dec 1996 15:20:42 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 09 Dec 1996 15:04:22 -0800 Jason Thorpe wrote: > I'd like to see a upoll(2), as well... an extension, that gives the > funtionality of poll, but takes a more reasonable timeout (like, > probably a struct timespec). Of course, I meant nanopoll(2) for timespec, or upoll(2) for timeval. *duh* Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Mon Dec 9 15:40:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11827 for hackers-outgoing; Mon, 9 Dec 1996 15:40:33 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA11811 for ; Mon, 9 Dec 1996 15:40:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id PAA06159; Mon, 9 Dec 1996 15:40:04 -0800 (PST) Message-Id: <199612092340.PAA06159@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: John Birrell cc: hackers@freebsd.org Subject: Re: poll(2) In-reply-to: Your message of "Tue, 10 Dec 1996 08:18:03 +1100." <199612092118.IAA10527@freebsd1.cimlogic.com.au> From: David Greenman Reply-To: dg@root.com Date: Mon, 09 Dec 1996 15:40:03 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >There are a few things that NetBSD has added recently that belong (IMHO) >in FreeBSD too. One of them is poll(2), which gives an alternative to >select(2) that does not suffer from the FD_SETSIZE "feature". > >Anyone planning to add this? We've been talking about it. BTW, select() in FreeBSD should no longer have the size limit. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Dec 9 15:41:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12075 for hackers-outgoing; Mon, 9 Dec 1996 15:41:46 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA12055 for ; Mon, 9 Dec 1996 15:41:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.7.6/8.6.12) with SMTP id SAA02068; Mon, 9 Dec 1996 18:41:37 -0500 (EST) Message-Id: <199612092341.SAA02068@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Sean Kelly Cc: hackers@freebsd.org Subject: Re: poll(2) In-reply-to: Your message of "Mon, 09 Dec 1996 16:28:17 MST." <32ACA091.2EFB@fsl.noaa.gov> Date: Mon, 09 Dec 1996 18:41:37 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Nice though it is, it's a terrible name for a system call. You use it > to avoid polling ... and yet it's called "poll". (Of course, the > reminder of SysV doesn't help much either. :-) Well, your program _is_ polling; it is polling a whole bunch of file descriptors all at once! It is avoiding busy-waiting (a strange phrase) but that is just an implementation detail! And yes, please do not remind us of sysV :-) From owner-freebsd-hackers Mon Dec 9 16:06:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA16996 for hackers-outgoing; Mon, 9 Dec 1996 16:06:06 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-206.rdcy01.pacbell.net [206.170.5.206]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA16973; Mon, 9 Dec 1996 16:05:56 -0800 (PST) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id QAA02009; Mon, 9 Dec 1996 16:04:56 -0800 (PST) Message-Id: <199612100004.QAA02009@precipice.shockwave.com> To: Michael Smith , Andrew.Gordon@net-tel.co.uk, nate@freebsd.org cc: mobile@freebsd.org, hackers@freebsd.org, pst@jnx.com Subject: Re: need help with a PC CARD NE2000 clone... Date: Mon, 09 Dec 1996 16:04:56 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Appologies if this never made it out. I never received a copy at work and got no responses, so I'll try again. ------- Forwarded Message [This is a response to Michael and Andrew's suggestions (thanks) with a comprehensive debugging session and some observations about the dumpcis output at the end.] > Are you using stock -current. or have you added the PAO patches over the top? -current > Try removing the "ether" line if you are running stock -current. This > tells the PAO code to look in the CIS for the hardware address, while > my modifications to the 'ed' driver dig it out from the normal > location hung off the 8390 as per the NE-2000. Tried both ways. > > Code 240 not found > I've never seen this message before. Try paring your /etc/pccardd.conf > file right down to the bone, in case this is a syntax error there. Tried it. > > I've set up ed0 and ed1 in my kernel config as follows (just in case the > > card wanted to be at fixed places or have fixed irq's): > > As long as you have a message coming up after the 'ed0' signon saying > "pccard driver ed0 added", there's a free 'ed' device for the card probe to > attach to. Yep, that's OK. It seems to be bailing out long before we even play driver games. > I can't find an "allocate_memory" in any of the -current pccard-related > sources, so I have to assume that you've applied the PAO patches. No, I did /not/. Sorry, gdb trace will explain all > Note that if this really is an NE2000 clone, it doesn't need any > memory address space (the on-card RAM is driven by i/o) - unlike some > of the other cards supported by the ed driver. Yeah, I agree. Why does it have two blocks of memory? > On the other hand, the card claims to have memory on it (from dumpcis). > Perhaps its an "enhanced" NE2000 which can be memory-addressed in > some proprietary way? This could cause confusion, where pccardd > knows the card has memory and that ed usually wants to use memory, > but in this case has probed it as an NE2000 and decided that it > doesn't need any. I agree with you, but it's bailing long before it even decides to play ed0 games (I think). It's failing in assign_io() which is calling the memory alloc block check routine with 1024 bytes, which is smaller than MEMUNIT. urk? Here are all the details.... I did some more debugging on my ethernet card problem. It looks like we're failing long before we even start to play driver games. To recap, here's the data, plus a gdb trace: # cat /etc/pccard.conf # Sample PCCARD configuration file # # Removing all IRQ conflicts from this file can't be done because of some # IRQ-selfish PC-cards. So if you want to use some of these cards in # your machine, you will be forced to modify their IRQ parameters from # the following list. # # IRQ == 0 means "allocate free IRQ from IRQ pool" # IRQ == 16 means "do not use IRQ (e.g. PIO mode)" # # $Id: pccard.conf.sample,v 1.4 1996/06/19 01:28:07 nate Exp $ # Generally available IO ports io 0x240-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 3 5 10 11 13 15 # Available memory slots memory 0xd0000 96k (I've tried this at d4000) card "PMX " "PE-200" config 0x1 "ed0" 11 # ether 0xff0 (I've tried it with & without) insert echo PMX PE-200 Ethernet inserted insert /etc/pccard_ether ed0 remove echo PMX PE-200 Ethernet removed remove /sbin/ifconfig ed0 delete dmesg: Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-961208-SNAP #1: Mon Dec 9 00:40:47 1996 root@foo.shockwave.com:/usr/src/sys/compile/LAP Calibrating clock(s) relative to mc146818A clock ... i8254 clock: 1193312 Hz CPU: i486DX (486-class CPU) real memory = 8388608 (8192K bytes) FreeBSD Kernel Configuration Utility - Version 1.1 Type "help" for help or "visual" to go to the visual configuration interface (requires MGA/VGA display or serial terminal capable of displaying ANSI graphics). config> ls Device port irq drq iomem iosize unit flags enabled fdc0 0x3f0 6 2 0x0 0 0 0x0 Yes wdc0 0x1f0 14 -1 0x0 0 0 0x80ff80ff Yes sc0 0x60 1 -1 0x0 0 0 0x0 Yes sio0 0x3f8 4 -1 0x0 0 0 0x0 Yes sio1 0x2f8 3 -1 0x0 0 1 0x0 Yes pca0 0x40 -1 -1 0x0 0 0 0x0 Yes lpt0 0xffffffff 7 -1 0x0 0 0 0x0 Yes psm0 0x60 12 -1 0x0 0 0 0x0 Yes ed0 0x300 11 -1 0xd8000 0 0 0x0 Yes ed1 0x310 5 -1 0xd8000 0 1 0x0 Yes npx0 0xf0 13 -1 0x0 0 0 0x0 Yes apm0 0x0 -1 -1 0x0 0 0 0x0 Yes config> iomem ed0 0xd4000 config> ls Device port irq drq iomem iosize unit flags enabled fdc0 0x3f0 6 2 0x0 0 0 0x0 Yes wdc0 0x1f0 14 -1 0x0 0 0 0x80ff80ff Yes sc0 0x60 1 -1 0x0 0 0 0x0 Yes sio0 0x3f8 4 -1 0x0 0 0 0x0 Yes sio1 0x2f8 3 -1 0x0 0 1 0x0 Yes pca0 0x40 -1 -1 0x0 0 0 0x0 Yes lpt0 0xffffffff 7 -1 0x0 0 0 0x0 Yes psm0 0x60 12 -1 0x0 0 0 0x0 Yes ed0 0x300 11 -1 0xd4000 0 0 0x0 Yes ed1 0x310 5 -1 0xd8000 0 1 0x0 Yes npx0 0xf0 13 -1 0x0 0 0 0x0 Yes apm0 0x0 -1 -1 0x0 0 0 0x0 Yes config> q avail memory = 6819840 (6660K bytes) PC-Card Intel 82365 (5 mem & 2 I/O windows) pcic: controller irq 3 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> pccard driver ed added ed0 not found at 0x300 ed1: disabled, not probed. pccard driver sio added sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 not found at 0x2f8 pca0 on motherboard pca0: PC speaker audio driver lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 2 buttons? fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , multi-block-16 wd0: 516MB (1058400 sectors), 1050 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 Card inserted, slot 1 # cat /etc/motd FreeBSD 2.2-961208-SNAP (LAP) #1: Mon Dec 9 00:40:47 1996 (-current as of yesterday, no PAO patches) # gdb pccardd GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc... (gdb) break assign_io Breakpoint 1 at 0x1b39: file cardd.c, line 464. (gdb) run -d -v Starting program: /usr/src/usr.sbin/pccard/pccardd/pccardd -d -v Card manuf PMX , vers PE-200 Configuration entries: Index code = 0x1, driver name = ed0 Insert commands are: echo PMX PE-200 Ethernet inserted /etc/pccard_ether ed0 Remove commands are: echo PMX PE-200 Ethernet removed /sbin/ifconfig ed0 delete Code 240 not found Code 240 not found code Unknown ignored Breakpoint 1, assign_io (sp=0x19100) at cardd.c:464 464 cis = sp->cis; (gdb) n 465 defconf = cis->def_config; (gdb) print *cis $1 = {tlist = 0x18160, manuf = "PMX ", '\000' , vers = "PE-200", '\000' , add_info1 = "ETHERNET", '\000' , add_info2 = "R01", '\000' , maj_v = 4 '\004', min_v = 1 '\001', last_config = 1 '\001', ccrs = 1 '\001', reg_addr = 256, attr_mem = {valid = 1 '\001', type = 5 '\005', speed = 3 '\003', wps = 0 '\000', addr = 0 '\000', units = 1 '\001'}, common_mem = { valid = 1 '\001', type = 13 '\r', speed = 4 '\004', wps = 1 '\001', addr = 0 '\000', units = 3 '\003'}, def_config = 0x1d080, conf = 0x1d080} (gdb) n 466 for (cisconf = cis->conf; cisconf; cisconf = cisconf->next) (gdb) n 467 if (cisconf->id == sp->config->index) (gdb) print *cisconf $2 = {next = 0x0, pwr = 0, timing = 0, iospace = 1, irq = 1, memspace = 1, misc_valid = 0, id = 1 '\001', io_blks = 2 '\002', io_addr = 10 '\n', io_bus = 2 '\002', io = 0x1a1c0, irqlevel = 0 '\000', irq_flags = 48 '0', irq_mask = 48892, memwins = 2 '\002', mem = 0x1a1e0, misc = 0 '\000'} (gdb) print *sp $3 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, card_config = 0x0, devname = '\000' , eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, irq = 0} (gdb) print *sp->config $4 = {next = 0x0, index = 1 '\001', driver = 0x180e0, irq = 11, flags = 0, inuse = 1 '\001'} (gdb) n 469 if (cisconf == 0) (gdb) n 471 sp->card_config = cisconf; (gdb) n 477 if (cisconf->memspace || (defconf && defconf->memspace)) { (gdb) n 480 mp = cisconf->mem; (gdb) print cisconf->memspace $5 = 1 (gdb) print defconf $6 = (struct cis_config *) 0x1d080 (gdb) print defconf->memspace $7 = 1 (gdb) print cisconf $8 = (struct cis_config *) 0x1d080 NOTE: cisconf and defconf are the same??? (gdb) n 481 if (!cisconf->memspace) (gdb) n 483 sp->mem.size = mp->length; (gdb) n 484 sp->mem.cardaddr = mp->address; (gdb) n 487 sp->mem.addr = sp->config->driver->mem; (gdb) n 492 if (sp->mem.size && sp->mem.addr == 0) { (gdb) print *sp $9 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, card_config = 0x1d080, devname = '\000' , eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 1024, flags = 0, cardaddr = 0}, irq = 0} NOTE: why is sp->mem.size == 1024? <---------------------------- (gdb) n 493 sp->mem.addr = alloc_memory(mp->length); (gdb) s alloc_memory (size=-272639028) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); (gdb) print *mem_avail @200 (oops, should have just printed 12 bytes) $10 = {"\000\000\000\000\000\000ÿÿÿ\000\000\000\000\000\000\000PMX \000\000\000\ 000\000\000\000\000\000\000PE-200\000\000\000\000\000\000\000\000\000\000ed0", '\000' , "ed", '\000' , "\220 \001\000\000Ð\0 01", '\000' , " \201\001\000\000\000\000\000\000\000\000\000° \ 001\000@Ð\001", '\000' , "@\201\001\000\000\000\000\000\000\00 0\000\000/dev/card0\000\000\000\000\000\000/dev/card1\000\000\000\000\000\000\0 00¡\001\000\001\000\000\000\003\000\000\000ð \001\000Ü\003ÿ\000\000\000\000"} (gdb) s bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:106 106 int found = 0; (gdb) where #0 bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:106 #1 0x341f in alloc_memory (size=1024) at util.c:125 #2 0x1bb6 in assign_io (sp=0x19100) at cardd.c:493 #3 0x18b5 in card_inserted (sp=0x19100) at cardd.c:323 #4 0x1696 in slot_change (sp=0x19100) at cardd.c:246 #5 0x15ec in readslots () at cardd.c:216 #6 0x1257 in main (argc=3, argv=0xefbfdd04) at cardd.c:105 (gdb) up #1 0x341f in alloc_memory (size=1024) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); (gdb) print size $12 = 1024 (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print nbits $13 = 96 (gdb) n 109 if (bit_test(nm, i)) { (gdb) print 96 / 8 $14 = 12 (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print i $15 = 0 (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) n 109 if (bit_test(nm, i)) { (gdb) n 113 found = 0; (gdb) n 108 for (i = 0; i < nbits; i++) (gdb) print i $16 = 6 (gdb) fin Run till exit from #0 bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:108 0x341f in alloc_memory (size=1024) at util.c:125 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); Value returned is $17 = -1 (gdb) n 126 if (i < 0) (gdb) n 127 return (0); (gdb) n 130 } (gdb) n assign_io (sp=0x19100) at cardd.c:494 494 if (sp->mem.addr == 0) (gdb) print sp->mem.addr $18 = 0 (gdb) n 536 return (-1); (gdb) c Continuing. cardd: Resource allocation failure for PMX Here's the pccardc dumpcis output again (look where I put arrows): Code 240 not found Code 240 not found code Unknown ignored Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: dc 03 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 100nS, Memory block size = 32Kb, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 000: 53 01 ff Attribute memory device information: Device number 1, type FLASH EEPROM, WPS = OFF Speed = 150nS, Memory block size = 2Kb, 1 units Tuple #3, code = 0x21 (Functional ID), length = 2 000: 06 03 Network/LAN adapter - POST initialize - Card has ROM Tuple #4, code = 0x15 (Version 1 info), length = 30 000: 04 01 50 4d 58 20 20 20 00 50 45 2d 32 30 30 00 010: 45 54 48 45 52 4e 45 54 00 52 30 31 00 ff Version = 4.1, Manuf = [PMX ],card vers = [PE-200] Addit. info = [ETHERNET],[R01] Tuple #5, code = 0x1a (Configuration map), length = 5 000: 01 01 00 01 01 Reg len = 2, config register addr = 0x100, last config = 0x1 Registers: X------- Tuple #6, code = 0x1b (Configuration entry), length = 25 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 010: 00 00 40 0d 40 40 00 40 0d Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x10 I/O address # 2: block start = 0x310 block length = 0x10 IRQ modes: Level IRQs: 4 5 10 11 12 13 14 15 -> why? what could this be for? It's 1k long? -> Memory descriptor 1 -> blk length = 0x400 card addr = 0x000 host addr = 0xd4000 Memory descriptor 2 blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 Tuple #7, code = 0x0 (Null tuple), length = 9 000: 57 42 20 4c 41 4e 20 20 ff Tuple #8, code = 0x14 (No link), length = 0 Tuple #9, code = 0xff (Terminator), length = 0 2 slots found ------- End of Forwarded Message From owner-freebsd-hackers Mon Dec 9 16:07:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17271 for hackers-outgoing; Mon, 9 Dec 1996 16:07:57 -0800 (PST) Received: from mira.net.au (eplet.mira.net.au [203.9.190.17]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA17254 for ; Mon, 9 Dec 1996 16:07:54 -0800 (PST) Received: (qmail 20084 invoked from network); 10 Dec 1996 00:07:52 -0000 Received: from melb.werple.net.au (203.9.190.18) by eplet.mira.net.au with SMTP; 10 Dec 1996 00:07:52 -0000 Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id KAA16020; Tue, 10 Dec 1996 10:57:00 +1100 (EST) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id KAA10842; Tue, 10 Dec 1996 10:41:41 +1100 (EST) From: John Birrell Message-Id: <199612092341.KAA10842@freebsd1.cimlogic.com.au> Subject: Re: poll(2) To: thorpej@nas.nasa.gov Date: Tue, 10 Dec 1996 10:41:40 +1100 (EST) Cc: terry@lambert.org, jb@cimlogic.com.au, hackers@freebsd.org In-Reply-To: <199612092304.PAA11079@lestat.nas.nasa.gov> from Jason Thorpe at "Dec 9, 96 03:04:22 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe wrote: > ...indeed. I did that once (in 1994), so that I could compile some > SVR4 sources under NetBSD/hp300. However, doing that limits poll() > to select()'s functionality. I was just replacing code in the thread kernel that used select to use poll as the hidden syscall. > I'd like to see a upoll(2), as well... an extension, that gives the > funtionality of poll, but takes a more reasonable timeout (like, > probably a struct timespec). npoll(2) for timespec? Or nanopoll(2) like nanosleep? I prefer poll_nsec(2), though. 8-) > > Jason R. Thorpe thorpej@nas.nasa.gov Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au; jb@netbsd.org 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Mon Dec 9 16:29:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA18842 for hackers-outgoing; Mon, 9 Dec 1996 16:29:55 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA18835 for ; Mon, 9 Dec 1996 16:29:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id QAA11620; Mon, 9 Dec 1996 16:20:59 -0800 (PST) Message-Id: <199612100020.QAA11620@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: John Birrell Cc: terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: poll(2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 09 Dec 1996 16:20:58 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just wanted to get tech-kern@netbsd.org on this thread, too :-) "Discuss." :-) On Tue, 10 Dec 1996 10:41:40 +1100 (EST) John Birrell wrote: > Jason Thorpe wrote: > > ...indeed. I did that once (in 1994), so that I could compile some > > SVR4 sources under NetBSD/hp300. However, doing that limits poll() > > to select()'s functionality. > > I was just replacing code in the thread kernel that used select to use > poll as the hidden syscall. > > > I'd like to see a upoll(2), as well... an extension, that gives the > > funtionality of poll, but takes a more reasonable timeout (like, > > probably a struct timespec). > > npoll(2) for timespec? Or nanopoll(2) like nanosleep? > I prefer poll_nsec(2), though. 8-) > > > > > Jason R. Thorpe thorpej@nas.nasa.gov > > Regards, > > -- > John Birrell CIMlogic Pty Ltd > jb@cimlogic.com.au; jb@netbsd.org 119 Cecil Street > Ph +61 3 9690 6900 South Melbourne Vic 3205 > Fax +61 3 9690 6650 Australia > Mob +61 18 353 137 Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Mon Dec 9 16:56:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA20441 for hackers-outgoing; Mon, 9 Dec 1996 16:56:17 -0800 (PST) Received: from hub.org (root@hub.org [207.107.138.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA20436 for ; Mon, 9 Dec 1996 16:56:14 -0800 (PST) Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id TAA26789 for ; Mon, 9 Dec 1996 19:56:20 -0500 (EST) Date: Mon, 9 Dec 1996 19:56:16 -0500 (EST) From: "Marc G. Fournier" To: hackers@freebsd.org Subject: Multiple Buffer allocation of Shared Memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just starting to play with shared memory, and have hit a wall that I don't know if its too be expected, or if I've screwed something up... Basically, I'm setting up the shared memory as: ---- int shmid[MAXBUF]; /* shared memory pointers */ Mesg *mesgptr[MAXBUF]; /* data cells */ for(ii = 0; ii < MAXBUF; ii++) { if((shmid[ii] = shmget(SHMKEY + ii, sizeof(Mesg), PERMS | IPC_CREAT)) < 0) { fprintf(stderr, "cannot initialize shared memory buffer #%d\n", ii); exit(-1); } if((mesgptr[ii] = (Mesg *)shmat(shmid[ii], (char *)0, 0)) == (Mesg *)-1) { printf("%s\n", strerror(errno)); fprintf(stderr, "cannot attach shared mem segment #%d\n", ii); exit(-1); } } ---- Where MAXBUf == 100, and Mesg is: ---- #define MAXMESGDATA 2048 typedef struct { int mesg_len; char mesg_data[MAXMESGDATA]; } Mesg; ---- The problem seems to be when 'ii == 8', the shmget() is working, but the shmat() is failing with 'strerror()' returning with: ---- hub> ./client Too many open files cannot initialize mesgptr #8 ---- I've tried doing an 'unlimit' before running, same results... I don't know enough about shared memory yet, but figure that I should be able to get further then allocating ~20k for shared memory, no? Without anything special needed in the kernel config? I would have assumed that if I had screwed up my syntax, it would be failing at ii == 0, which it isn't. limit shows: descriptors 1064 which is the only one that I would think is appropriate to the situation...unless its a kernel config problem... As I'm pretty much using the example straight out of "Unix Network Programming", pg 165...if anyone can point out the error of my ways, it would be much appreciated... Thanks in advance... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-hackers Mon Dec 9 17:11:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA21483 for hackers-outgoing; Mon, 9 Dec 1996 17:11:25 -0800 (PST) Received: from Pescadero.DSG.Stanford.EDU (Pescadero.DSG.Stanford.EDU [171.64.79.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA21478 for ; Mon, 9 Dec 1996 17:11:23 -0800 (PST) Received: from Cup.DSG.Stanford.EDU (Cup.DSG.Stanford.EDU [171.64.79.91]) by Pescadero.DSG.Stanford.EDU (8.7.4/8.6.9) with SMTP id RAA04353; Mon, 9 Dec 1996 17:09:58 -0800 Message-Id: <199612100109.RAA04353@Pescadero.DSG.Stanford.EDU> X-Authentication-Warning: Pescadero.DSG.Stanford.EDU: Host Cup.DSG.Stanford.EDU [171.64.79.91] didn't use HELO protocol To: Jason Thorpe Cc: John Birrell Cc: terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: poll(2) Date: Mon, 09 Dec 1996 17:09:57 -0800 From: Jonathan Stone Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just wanted to get tech-kern@netbsd.org on this thread, too :-) > >"Discuss." :-) Uh, well, then.... AFAIK, there aren't yet any NetBSD ports with significantly better than millisecond time-of-day-clock (and thus forced process- scheduling) resolution. So milliseconds are currently as good as you'll get. You can add a syscall specifying a nanosecond interval, but anyone thinking they're going to get _nano_second-level wakeups is, currently, deluding themselves. (I still get ~4usec syscall times on a 200MHz P6.) Clearly we should add a nano-second resolution poll interface. Once we do so, regardless of the actualy in-kernel resolution, poll(2) and upoll(3) become poll(3) and upoll(3). Re naming, npoll() is more consistent with the sleep()/usleep() usage. Does POSIX have anything to say here? If we did this _now_ we could, perhaps, reuse the existing syscall number, since AFAIK poll(2) has never been in an official NetBSD release. From owner-freebsd-hackers Mon Dec 9 17:34:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22614 for hackers-outgoing; Mon, 9 Dec 1996 17:34:44 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA22573; Mon, 9 Dec 1996 17:34:30 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA11963; Tue, 10 Dec 1996 12:04:00 +1030 (CST) From: Michael Smith Message-Id: <199612100134.MAA11963@genesis.atrad.adelaide.edu.au> Subject: Re: need help with a PC CARD NE2000 clone... In-Reply-To: <199612091804.KAA01333@precipice.shockwave.com> from Paul Traina at "Dec 9, 96 10:04:26 am" To: pst@shockwave.com (Paul Traina) Date: Tue, 10 Dec 1996 12:03:59 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org, pst@jnx.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by freefall.freebsd.org id RAA22586 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (It made it OK Paul, I just had to go to sleep at some point 8) > > Note that if this really is an NE2000 clone, it doesn't need any > > memory address space (the on-card RAM is driven by i/o) - unlike some > > of the other cards supported by the ed driver. > > Yeah, I agree. Why does it have two blocks of memory? Not entirely sure. It looks like the card might have a boot ROM on it; I can't find any other justification for this, which is a write-protected 32K region : > Tuple #1, code = 0x1 (Common memory descriptor), length = 3 > 000: dc 03 ff > Common memory device information: > Device number 1, type Function specific, WPS = ON > Speed = 100nS, Memory block size = 32Kb, 1 units I can only assume that pccardd is trying to DTRT and map this in somewhere. > # cat /etc/pccard.conf ... > # Generally available IO ports > io 0x240-0x360 > # Generally available IRQs (Built-in sound-card owners remove 5) > irq 3 5 10 11 13 15 Does your notebook really have all these resources available? (Lots have onboard peripherals scattered around. I'd have expected the PCIC to be given IRQ 3...) > # Available memory slots > memory 0xd0000 96k (I've tried this at d4000) Should be plenty of space anyway. > PC-Card Intel 82365 (5 mem & 2 I/O windows) > pcic: controller irq 3 As I thought, the PCIC is getting IRQ 3. You will want to remove this from the list of available IRQs (no, I know this isn't your problem). > Code 240 not found > Code 240 not found > code Unknown ignored There's a tuple in the card with an unknown (0xf0) code; no idea what it's supposed to be. > Breakpoint 1, assign_io (sp=0x19100) at cardd.c:464 > 464 cis = sp->cis; > (gdb) n > 465 defconf = cis->def_config; > (gdb) print *cis > $1 = {tlist = 0x18160, manuf = "PMX ", '\000' , > vers = "PE-200", '\000' , > add_info1 = "ETHERNET", '\000' , > add_info2 = "R01", '\000' , maj_v = 4 '\004', > min_v = 1 '\001', last_config = 1 '\001', ccrs = 1 '\001', reg_addr = 256, > attr_mem = {valid = 1 '\001', type = 5 '\005', speed = 3 '\003', > wps = 0 '\000', addr = 0 '\000', units = 1 '\001'}, common_mem = { > valid = 1 '\001', type = 13 '\r', speed = 4 '\004', wps = 1 '\001', > addr = 0 '\000', units = 3 '\003'}, def_config = 0x1d080, conf = 0x1d080} > (gdb) n > 466 for (cisconf = cis->conf; cisconf; cisconf = cisconf->next) > (gdb) n > 467 if (cisconf->id == sp->config->index) > (gdb) print *cisconf > $2 = {next = 0x0, pwr = 0, timing = 0, iospace = 1, irq = 1, memspace = 1, > misc_valid = 0, id = 1 '\001', io_blks = 2 '\002', io_addr = 10 '\n', > io_bus = 2 '\002', io = 0x1a1c0, irqlevel = 0 '\000', irq_flags = 48 '0', > irq_mask = 48892, memwins = 2 '\002', mem = 0x1a1e0, misc = 0 '\000'} > (gdb) print *sp > $3 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", > state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, > card_config = 0x0, devname = '\000' , > eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, > flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 0, > flags = 0, cardaddr = 0}, irq = 0} > (gdb) print *sp->config > $4 = {next = 0x0, index = 1 '\001', driver = 0x180e0, irq = 11, flags = 0, > inuse = 1 '\001'} > (gdb) n > 469 if (cisconf == 0) > (gdb) n > 471 sp->card_config = cisconf; > (gdb) n > 477 if (cisconf->memspace || (defconf && defconf->memspace)) { > (gdb) n > 480 mp = cisconf->mem; > (gdb) print cisconf->memspace > $5 = 1 > (gdb) print defconf > $6 = (struct cis_config *) 0x1d080 > (gdb) print defconf->memspace > $7 = 1 > (gdb) print cisconf > $8 = (struct cis_config *) 0x1d080 > > NOTE: cisconf and defconf are the same??? Some cards have more than one Configuration Entry tuple; one can be nominated as the 'default' in the card, but this can be overridden with an explicit index entry in the /etc/pccard.conf file. > (gdb) n > 481 if (!cisconf->memspace) > (gdb) n > 483 sp->mem.size = mp->length; > (gdb) n > 484 sp->mem.cardaddr = mp->address; > (gdb) n > 487 sp->mem.addr = sp->config->driver->mem; > (gdb) n > 492 if (sp->mem.size && sp->mem.addr == 0) { > (gdb) print *sp > $9 = {next = 0x19080, fd = 8, mask = 0, slot = 1, name = 0x1a0d0 "/dev/card1", > state = filled, cis = 0x19180, card = 0x180a0, config = 0x180c0, > card_config = 0x1d080, devname = '\000' , > eaddr = "\000\000\000\000\000", io = {next = 0x0, addr = 0, size = 0, > flags = 0, cardaddr = 0}, mem = {next = 0x0, addr = 0, size = 1024, > flags = 0, cardaddr = 0}, irq = 0} > > NOTE: why is sp->mem.size == 1024? <---------------------------- It's trying to allocate a mapping for the EEPROM (tuple #2, aka memory region 1). > (gdb) n > 493 sp->mem.addr = alloc_memory(mp->length); > (gdb) s > alloc_memory (size=-272639028) at util.c:125 > 125 i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); > > (gdb) print *mem_avail @200 (oops, should have just printed 12 bytes) > > $10 = {"\000\000\000\000\000\000\000\000\000 Ok. Looks like you have some memory there. > (gdb) s > bit_fns (nm=0x1a030 "", nbits=96, count=0) at util.c:106 And there's your problem; alloc_memory should be rounding 'size' up to MEMUNIT, as bit_fns can't handle a request for an allocation of 0. unsigned long alloc_memory(int size) { int i; /* Add Me */ if (size < MEMUNIT) size = MEMUNIT; i = bit_fns(mem_avail, MEMBLKS, size / MEMUNIT); if (i < 0) return (0); bit_nclear(mem_avail, i, size / MEMUNIT); return (BIT2MEM(i)); } (commentary on your CIS follows) > Configuration data for card in slot 1 > Tuple #1, code = 0x1 (Common memory descriptor), length = 3 > 000: dc 03 ff > Common memory device information: > Device number 1, type Function specific, WPS = ON > Speed = 100nS, Memory block size = 32Kb, 1 units > Tuple #2, code = 0x17 (Attribute memory descriptor), length = 3 > 000: 53 01 ff > Attribute memory device information: > Device number 1, type FLASH EEPROM, WPS = OFF > Speed = 150nS, Memory block size = 2Kb, 1 units > Tuple #3, code = 0x21 (Functional ID), length = 2 > 000: 06 03 > Network/LAN adapter - POST initialize - Card has ROM > Tuple #4, code = 0x15 (Version 1 info), length = 30 > 000: 04 01 50 4d 58 20 20 20 00 50 45 2d 32 30 30 00 > 010: 45 54 48 45 52 4e 45 54 00 52 30 31 00 ff > Version = 4.1, Manuf = [PMX ],card vers = [PE-200] > Addit. info = [ETHERNET],[R01] > Tuple #5, code = 0x1a (Configuration map), length = 5 > 000: 01 01 00 01 01 > Reg len = 2, config register addr = 0x100, last config = 0x1 > Registers: X------- > Tuple #6, code = 0x1b (Configuration entry), length = 25 > 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 > 010: 00 00 40 0d 40 40 00 40 0d > Config index = 0x1(default) > Interface byte = 0x81 (I/O) wait signal supported > Card decodes 10 address lines, limited 8/16 Bit I/O > I/O address # 1: block start = 0x300 block length = 0x10 > I/O address # 2: block start = 0x310 block length = 0x10 > IRQ modes: Level > IRQs: 4 5 10 11 12 13 14 15 > -> why? what could this be for? It's 1k long? > -> Memory descriptor 1 > -> blk length = 0x400 card addr = 0x000 host addr = 0xd4000 Not entirely sure. This may match tuple #2, the flash EEPROM. > Memory descriptor 2 > blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 This almost certainly matches tuple #1. It's interesting to note that the sizes of both of these mismatch; it appears that the spec doesn't provide for 1K or 16K as legitimate values for memory regions. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 9 17:37:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22790 for hackers-outgoing; Mon, 9 Dec 1996 17:37:42 -0800 (PST) Received: from auchentoshan.pdl.cs.cmu.edu (AUCHENTOSHAN.PDL.CS.CMU.EDU [128.2.189.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA22785 for ; Mon, 9 Dec 1996 17:37:39 -0800 (PST) Received: from localhost by auchentoshan.pdl.cs.cmu.edu id aa03127; 9 Dec 96 20:36 EST To: Jonathan Stone cc: Jason Thorpe , John Birrell , terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: poll(2) In-reply-to: Your message of "Mon, 09 Dec 1996 17:09:57 PST." <199612100109.RAA04353@Pescadero.DSG.Stanford.EDU> Date: Mon, 09 Dec 1996 20:35:44 -0500 Message-ID: <18951.850181744@auchentoshan.pdl.cs.cmu.edu> From: Chris G Demetriou Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > AFAIK, there aren't yet any NetBSD ports with significantly > better than millisecond time-of-day-clock (and thus forced process- > scheduling) resolution. So milliseconds are currently as good as > you'll get. On a single-processor alpha, you can sanely get down-to-the-cycle time of day clock resolution. You can't schedule on it, but you can get it e.g. for microtime(), etc. I implemented that in NetBSD/alpha (along with a memory mapped clock that provided the same resolution), then yanked it because i didn't want to create an interface which would be more or less impossible to provide on MP systems. Granted, that doesn't change what you're saying re: scheduling, but when you add in the fact that the Alpha uses a 1024Hz real time clock interrupt rate, which could be easily increased, well, you're still in microseconds for scheduling, but are getting closer. It's just a matter of time. 8-) chris From owner-freebsd-hackers Mon Dec 9 17:37:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22826 for hackers-outgoing; Mon, 9 Dec 1996 17:37:57 -0800 (PST) Received: from mira.net.au (eplet.mira.net.au [203.9.190.17]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA22816 for ; Mon, 9 Dec 1996 17:37:53 -0800 (PST) Received: (qmail 26629 invoked from network); 10 Dec 1996 01:37:51 -0000 Received: from melb.werple.net.au (203.9.190.18) by eplet.mira.net.au with SMTP; 10 Dec 1996 01:37:51 -0000 Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id MAA22457; Tue, 10 Dec 1996 12:23:43 +1100 (EST) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id MAA11043; Tue, 10 Dec 1996 12:15:59 +1100 (EST) From: John Birrell Message-Id: <199612100115.MAA11043@freebsd1.cimlogic.com.au> Subject: Re: poll(2) To: thorpej@nas.nasa.gov Date: Tue, 10 Dec 1996 12:15:58 +1100 (EST) Cc: jb@cimlogic.com.au, terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: <199612100020.QAA11620@lestat.nas.nasa.gov> from Jason Thorpe at "Dec 9, 96 04:20:58 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe wrote: > Just wanted to get tech-kern@netbsd.org on this thread, too :-) The "thread kernel" for a user-thread implementation (in libpthread or libc_r in FreeBSD-current) is in user space. *Nothing* in the "real kernel" is affected => tech-user@netbsd.org? 8-) The user-thread implementation just uses the best that the real kernel has to offer. That way, the implementation doesn't get in the way of a kernel thread implementation later on. > > "Discuss." :-) If NetBSD's kernel is moving towards everything being done in timespecs, then the best that the real kernel *should* offer would be a nanopoll syscall with a timespec argument. Then libc could provide wrappers for poll(2) and upoll(2). > Jason R. Thorpe thorpej@nas.nasa.gov Regards, -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au; jb@netbsd.org 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Mon Dec 9 17:55:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA23689 for hackers-outgoing; Mon, 9 Dec 1996 17:55:20 -0800 (PST) Received: from Pescadero.DSG.Stanford.EDU (Pescadero.DSG.Stanford.EDU [171.64.79.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA23684 for ; Mon, 9 Dec 1996 17:55:15 -0800 (PST) Received: from Cup.DSG.Stanford.EDU (Cup.DSG.Stanford.EDU [171.64.79.91]) by Pescadero.DSG.Stanford.EDU (8.7.4/8.6.9) with SMTP id RAA04644; Mon, 9 Dec 1996 17:53:55 -0800 Message-Id: <199612100153.RAA04644@Pescadero.DSG.Stanford.EDU> X-Authentication-Warning: Pescadero.DSG.Stanford.EDU: Host Cup.DSG.Stanford.EDU [171.64.79.91] didn't use HELO protocol To: Chris G Demetriou cc: Jason Thorpe , John Birrell , terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: poll(2) Subject: i386 priority levels Date: Mon, 09 Dec 1996 17:53:54 -0800 From: Jonathan Stone Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [alpha references snipped; the 2^10-Hz alpha clock-tick "hz" was why I referred to millisecond accuracy] Quoting cgd: >Granted, that doesn't change what you're saying re: scheduling, but >when you add in the fact that the Alpha uses a 1024Hz real time clock >interrupt rate, which could be easily increased, well, you're still in >microseconds for scheduling, but are getting closer. It's just a >matter of time. 8-) Uh, ``of course.''. That's why i also said: >Clearly we should add a nano-second resolution poll interface. >Once we do so, regardless of the actualy in-kernel resolution, >poll(2) and upoll(3) become poll(3) and upoll(3). (the "y" is a typo.) In case it's not clear, the reason for adding nanosecond resolution is that NetBSD has acquired POSIX .12(?)-compatible syscalls with nanosecond resolution, and if we're going to change poll(2) to higher resolution, I'm saying move it to nanoseconds _now_, for consistency with other nanosecond-granularity syscalls, even if the internal implementation doesn't offer better than millisecond (or 100s of microsecond) resolution for some time to come. From owner-freebsd-hackers Mon Dec 9 17:57:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA23897 for hackers-outgoing; Mon, 9 Dec 1996 17:57:06 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA23868 for ; Mon, 9 Dec 1996 17:56:55 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id TAA23705; Mon, 9 Dec 1996 19:56:13 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma023699; Mon Dec 9 19:55:43 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id TAA16187; Mon, 9 Dec 1996 19:55:56 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id TAA00658; Mon, 9 Dec 1996 19:56:17 -0600 (CST) Message-Id: <199612100156.TAA00658@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Marc G. Fournier" cc: hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Mon, 09 Dec 1996 19:56:16 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Dec 1996 19:56:17 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" writes: > >Hi... > > Just starting to play with shared memory, and have hit a wall >that I don't know if its too be expected, or if I've screwed something >up... Shared memory is cool, SysV symantics for shared memory *suck*, if at all possible use mmap(). BSDi uses libc wrappers around mmap() for it's SysV shm stuff, but there's caveats... I'd like the wrappers, but have the real ones available too. > > Basically, I'm setting up the shared memory as: > > > The problem seems to be when 'ii == 8', the shmget() is working, >but the shmat() is failing with 'strerror()' returning with: > >---- >hub> ./client >Too many open files >cannot initialize mesgptr #8 >---- yup, from /sys/conf/param.h: #ifndef SHMSEG #define SHMSEG 8 #endif you can only have 8 shm segments by default, you can override it with: `options "SHMSEG=32"' or something similar in your config file. I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. > > which is the only one that I would think is appropriate to the >situation...unless its a kernel config problem... > You got it. > >Thanks in advance... > >Marc G. Fournier scrappy@hub.org >Systems Administrator @ hub.org scrappy@freebsd.org > > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Mon Dec 9 18:08:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA24883 for hackers-outgoing; Mon, 9 Dec 1996 18:08:12 -0800 (PST) Received: from mira.net.au (eplet.mira.net.au [203.9.190.17]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA24850 for ; Mon, 9 Dec 1996 18:08:05 -0800 (PST) Received: (qmail 28749 invoked from network); 10 Dec 1996 02:07:56 -0000 Received: from melb.werple.net.au (203.9.190.18) by eplet.mira.net.au with SMTP; 10 Dec 1996 02:07:56 -0000 Received: (from uucp@localhost) by melb.werple.net.au (8.7.6/8.7.3/2) with UUCP id MAA25091; Tue, 10 Dec 1996 12:56:55 +1100 (EST) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.7.5/8.7.3) id MAA11100; Tue, 10 Dec 1996 12:36:44 +1100 (EST) From: John Birrell Message-Id: <199612100136.MAA11100@freebsd1.cimlogic.com.au> Subject: Re: poll(2) To: jonathan@DSG.Stanford.EDU (Jonathan Stone) Date: Tue, 10 Dec 1996 12:36:43 +1100 (EST) Cc: thorpej@nas.nasa.gov, jb@cimlogic.com.au, terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: <199612100109.RAA04353@Pescadero.DSG.Stanford.EDU> from Jonathan Stone at "Dec 9, 96 05:09:57 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Stone wrote: > Re naming, npoll() is more consistent with the sleep()/usleep() usage. > Does POSIX have anything to say here? nanopoll() is more consistent with the sleep()/nanosleep() usage which are defined in POSIX 1003.1b. usleep() is not POSIX AFAIK. -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au; jb@netbsd.org 119 Cecil Street Ph +61 3 9690 6900 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137 From owner-freebsd-hackers Mon Dec 9 18:34:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA27078 for hackers-outgoing; Mon, 9 Dec 1996 18:34:17 -0800 (PST) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA27039; Mon, 9 Dec 1996 18:34:08 -0800 (PST) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.8.3/8.8.3) with ESMTP id SAA17179; Mon, 9 Dec 1996 18:33:37 -0800 (PST) Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id SAA00372; Mon, 9 Dec 1996 18:33:37 -0800 (PST) Message-Id: <199612100233.SAA00372@base.jnx.com> To: Michael Smith cc: Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org Subject: Re: need help with a PC CARD NE2000 clone... In-reply-to: Your message of "Tue, 10 Dec 1996 12:03:59 +1030." <199612100134.MAA11963@genesis.atrad.adelaide.edu.au> Date: Mon, 09 Dec 1996 18:33:37 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for all the help. Sorry if I sounded rather frantic, I'm desparately trying to get this laptop working for a conference and then two weeks holiday. I'll fix the pcic irq address. On the memory stuff, I think your change is good, but I think it should actually be: units = (size + MEMUNITS - 1) / MEMUNITS; and do the rest with units. because of the 16k allocation blocks too. This will cause us to always round up properly. I wonder why my card is so weird? :-( From owner-freebsd-hackers Mon Dec 9 18:39:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA27483 for hackers-outgoing; Mon, 9 Dec 1996 18:39:22 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA27470 for ; Mon, 9 Dec 1996 18:39:17 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id VAA27569; Mon, 9 Dec 1996 21:38:50 -0500 (EST) From: "John S. Dyson" Message-Id: <199612100238.VAA27569@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Mon, 9 Dec 1996 21:38:50 -0500 (EST) Cc: scrappy@hub.org, hackers@FreeBSD.ORG In-Reply-To: <199612100156.TAA00658@jake.lodgenet.com> from "Eric L. Hernes" at Dec 9, 96 07:56:17 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Shared memory is cool, SysV symantics for shared memory *suck*, if at all > possible use mmap(). BSDi uses libc wrappers around mmap() for > it's SysV shm stuff, but there's caveats... I'd like the wrappers, > but have the real ones available too. > FreeBSD, NetBSD, and OpenBSD have a low level implementation of the SYSVSHM stuff (not based on mmap, but on some of the low level kernel primatives that are also used to implement mmap.) > > you can only have 8 shm segments by default, you can override > it with: `options "SHMSEG=32"' or something similar in your config file. > I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. > The limits on FreeBSD are totally administrative, and so if you need to increase SHMMAXPGS or somesuch, there is little cost. John dyson@freebsd.org From owner-freebsd-hackers Mon Dec 9 18:42:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA27870 for hackers-outgoing; Mon, 9 Dec 1996 18:42:57 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA27859; Mon, 9 Dec 1996 18:42:49 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA12469; Tue, 10 Dec 1996 13:12:27 +1030 (CST) From: Michael Smith Message-Id: <199612100242.NAA12469@genesis.atrad.adelaide.edu.au> Subject: Re: need help with a PC CARD NE2000 clone... In-Reply-To: <199612100233.SAA00372@base.jnx.com> from Paul Traina at "Dec 9, 96 06:33:37 pm" To: pst@jnx.com (Paul Traina) Date: Tue, 10 Dec 1996 13:12:26 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina stands accused of saying: > Thanks for all the help. Sorry if I sounded rather frantic, I'm > desparately trying to get this laptop working for a conference and > then two weeks holiday. That's OK; I understand franticity entirely 8) > On the memory stuff, I think your change is good, but I think it should > actually be: > > units = (size + MEMUNITS - 1) / MEMUNITS; > > and do the rest with units. Of course; it was stupid of me to assume that any allocation over 4K would be a multiple of 4K. > I wonder why my card is so weird? :-( I don't necessarily think that it is; you're just coming into contact with PC hardware again 8) Please to be keeping us informed! -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 9 19:21:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA01188 for hackers-outgoing; Mon, 9 Dec 1996 19:21:11 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA01183 for ; Mon, 9 Dec 1996 19:21:09 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id WAA25837 for freebsd-hackers@freebsd.org; Mon, 9 Dec 1996 22:21:08 -0500 (EST) From: Charles Henrich Message-Id: <199612100321.WAA25837@crh.cl.msu.edu> Subject: Intelligent source IP's in multinet singlephysicalnet connections? To: freebsd-hackers@freebsd.org Date: Mon, 9 Dec 1996 22:21:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I posted this some months ago, but the suggested "I just fixed it" apparently didnt. On a FreeBSD box with multiple IP addresses, shouldnt FreeBSD pick the source IP of a packet of the net that the destination IP address is for (if possible?) That is, in my case I have an IP address on a standard network class C address, as well as an alias in the non-routed 10.x.x.x range. I have a default route for both networks: e.g. 10 link#1 UCSc 11 0 CLASSC link#1 UC 0 0 When I send any packets to the 10. addresses, I want my source IP to be my aliased 10. Address. In all other cases I want it to be my normal address. This is because I have a bunch of devices hanging on the 10. network that I want to talk to, and who can only communicate to other devices on the 10. network. The kicker is this works under Win95 if I define multiple networks for myself.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Mon Dec 9 19:36:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA02491 for hackers-outgoing; Mon, 9 Dec 1996 19:36:53 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA02486 for ; Mon, 9 Dec 1996 19:36:50 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id DAA22147; Tue, 10 Dec 1996 03:36:35 GMT Date: Tue, 10 Dec 1996 12:36:35 +0900 (JST) From: Michael Hancock To: Jake Hamby cc: Terry Lambert , hackers@FreeBSD.org, jkh@time.cdrom.com Subject: Re: Help, I've been SCOed! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 8 Dec 1996, Jake Hamby wrote: > But I won't tell my client to switch to Linux because it doesn't provide > any sort of long-term solution for their database (moving it to something > real like Oracle). Right now they want to move over to Windows NT, with > NT Workstation on all the clients, accessing the database through a VB > front-end, probably. The only alternative I could see is running UnixWare > on the server, which claims excellent Oracle tpm/C ratings, which should > also have enough SCO compatibility to run FoxPro in the meantime. Either > way they'd be using NT on the clients because they also want to run some > Windows software (Goldmine). The only problem with that is the high price > of UnixWare, the lack of upgrade pricing from OpenServer, and the feeling > among the company that they've been burned once by SCO already. If you want to recommend a Unix solution over NT you might want to consider that UnixWare is sold by user licenses. This means that you can get the 5-user version, install a 5 user Oracle workgroup server, and use a Web to SQL gateway. Oracle is licensed by concurrent use so the web2SQL gateway will keep the concurrent connections down. With this solution you don't need to install SQL*Net on each client PC, you just use a browser. If you need a lot of user email accounts then use FreeBSD for mail. The UnixWare Oracle server will only need a couple of administrative accounts. There is a Japanese company, run by foreigners and some former NCSA engineers, that has a pretty cool product called Zolar. It works with CGI variables and communicates with SQL databases such as Oracle and SQL Server. It uses .zsql files in the cgi-bin directory as a template for accepting cgi variables and binding them to a query. Here's an example .zsql file: INSERT INTO Emp VALUES ([Number?{Number}:NULL], [Name?'{Name}':NULL], [Job?'{Job}':NULL], [Manager?{Manager}:NULL], [HiredateToday? SYSDATE : TO_DATE('{HiredateMonth}-{HiredateDay}-{HiredateYear}','MM-DD-YY')], [Salary?{Salary}:NULL], [Commission?{Commission}:NULL], [Department?{Department}:NULL]) The {} are for cgi variables from HTML forms. Unfortunately, these guys only support Solaris, HP-UX, and NT and don't have an English version yet. Their are some English examples on their web pages, http://isr.co.jp/zolar. Their US office is http://www.isrusa.com. Their Japanese NT version does run on English WinNT, though it is not supported. FreeBSD could be brought into the picture for the Web server side if Oracle's SCO version of SQL*Net version runs and if ISR did an SCO port that could run on FreeBSD. Regards, Mike Hancock From owner-freebsd-hackers Mon Dec 9 20:00:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA04729 for hackers-outgoing; Mon, 9 Dec 1996 20:00:06 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA04721 for ; Mon, 9 Dec 1996 20:00:02 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id UAA29391 for ; Mon, 9 Dec 1996 20:00:00 -0800 (PST) Message-Id: <199612100400.UAA29391@austin.polstra.com> To: freebsd-hackers@freebsd.org Subject: Attention CVSup users! Date: Mon, 09 Dec 1996 19:59:59 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If you have started to get messages like these when you do your CVSup updates: Unknown release "current" for "src-eBones" Unknown release "current" for "src-secure" Unknown release "stable" for "src-eBones" Unknown release "stable" for "src-secure" it's because your cvsupfile isn't correct. To get the "current" release, you should have this in your supfile: release=cvs tag=. To get the "stable" release, you should have this: release=cvs tag=RELENG_2_1_0 I am only seeing this in the logs for the src-eBones and src-secure collections, and I think I know why. You probably started with a sample supfile that had those two releases commented out. Then you ran supconv on it. Then, later, you uncommented the lines for the above collections. Since supconv doesn't touch comments, those lines never got converted properly. It used to accidentally work if you had "release=current" or "release=stable", but it didn't work efficiently. Now it doesn't work at all, so you'll have to fix your cvsupfiles. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Dec 9 20:09:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA05741 for hackers-outgoing; Mon, 9 Dec 1996 20:09:53 -0800 (PST) Received: from tdc.on.ca (tdc.on.ca [204.92.242.39]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA05727 for ; Mon, 9 Dec 1996 20:09:49 -0800 (PST) Received: (from martin@localhost) by tdc.on.ca (8.7.5/8.6.6) id XAA29044 for freebsd-hackers@freebsd.org; Mon, 9 Dec 1996 23:09:56 -0500 (EST) From: Martin Renters Message-Id: <199612100409.XAA29044@tdc.on.ca> Subject: PPP with network address translation To: freebsd-hackers@freebsd.org Date: Mon, 9 Dec 1996 23:09:56 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've merged Charles Mott's PPP with packet aliasing code into the -current PPP code and added a 'set nat on' command so that it can be turned on or off. The default is off which keeps the existing PPP behaviour. If no one is violently opposed to this feature, I'll commit it later this week. It certainly seems useful. Martin From owner-freebsd-hackers Mon Dec 9 20:17:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA06423 for hackers-outgoing; Mon, 9 Dec 1996 20:17:41 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA06411 for ; Mon, 9 Dec 1996 20:17:36 -0800 (PST) Received: from misery.sdf.com ([204.244.213.33]) by misery.sdf.com with SMTP id <1774-211>; Mon, 9 Dec 1996 20:18:27 -0800 Date: Mon, 9 Dec 1996 20:18:25 -0800 (PST) From: Tom Samplonius To: "S(pork)" cc: michael butler , Jason Fesler , hackers@freebsd.org Subject: Re: Apache and huge numbers of IP's.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, S(pork) wrote: > > This is an interesting question; a while back I posted something similar > and everyone agreed "maxusers" set to a high value would take care of max > processes and max open files... However, in setting up a medium duty > (2G/Day) dedicated webserver, I was running out of processes with maxusers > at 200. When I re-compiled the kernel with params like those below, all > was well. Could someone clarify? I'll be building another big machine > (news) soon, and I will be dealing with the same issue. > > Thanks, > > Charles Not exactly. Increasing maxusers only increases the size of system wide descriptor table. OPEN_MAX chanes the max number of open files per uid. open files per uid never changes via maxusers. CHILD_MAX sets the total number of processes per uid. You will notice that Apache runs and all its related processes run under a single uid, so you will hit the default limit of 40 processes and 64 files per uid quite quickly. The defaults are intended for a general purpose machine where you do not want users using more than their share of the processes and files. Tom > On Sun, 8 Dec 1996, michael butler wrote: > > > The number of file handles available is related to the maxusers config > > parameter. If you wish to alter that without affecting the other table > > sizes, you can add something like this to your config file .. > > > > options "CHILD_MAX=512" > > options "OPEN_MAX=512" > [snip] > > michael > > > > From owner-freebsd-hackers Mon Dec 9 21:07:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA11127 for hackers-outgoing; Mon, 9 Dec 1996 21:07:33 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA11118 for ; Mon, 9 Dec 1996 21:07:29 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA05817; Mon, 9 Dec 1996 22:07:22 -0700 (MST) Date: Mon, 9 Dec 1996 22:07:22 -0700 (MST) Message-Id: <199612100507.WAA05817@rocky.mt.sri.com> From: Nate Williams To: Martin Renters Cc: freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-Reply-To: <199612100409.XAA29044@tdc.on.ca> References: <199612100409.XAA29044@tdc.on.ca> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've merged Charles Mott's PPP with packet aliasing code into the > -current PPP code and added a 'set nat on' command so that it can > be turned on or off. The default is off which keeps the existing PPP > behaviour. Wow, there are now *3* differnent folks working on this. Brian Somers is working with the code that Charles sent me and has added some new stuff to it. He wants to commit the code himself, so I've held off doing anything with it (and also because I'm on a business trip meaning I can't test it fully). > If no one is violently opposed to this feature, I'll commit it later > this week. It certainly seems useful. Hold off just a bit longer if you would please. I won't go into 2.2 anyway, so there's no big rush. Nate From owner-freebsd-hackers Mon Dec 9 21:39:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA14231 for hackers-outgoing; Mon, 9 Dec 1996 21:39:31 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA14224 for ; Mon, 9 Dec 1996 21:39:27 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id AAA20044; Tue, 10 Dec 1996 00:38:44 -0500 (EST) Date: Tue, 10 Dec 1996 00:38:44 -0500 (EST) From: Mark Mayo To: Nate Williams cc: Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-Reply-To: <199612100507.WAA05817@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, Nate Williams wrote: > > I've merged Charles Mott's PPP with packet aliasing code into the > > -current PPP code and added a 'set nat on' command so that it can > > be turned on or off. The default is off which keeps the existing PPP > > behaviour. > > Wow, there are now *3* differnent folks working on this. Brian Somers > is working with the code that Charles sent me and has added some new > stuff to it. He wants to commit the code himself, so I've held off > doing anything with it (and also because I'm on a business trip meaning > I can't test it fully). > > > If no one is violently opposed to this feature, I'll commit it later > > this week. It certainly seems useful. > > Hold off just a bit longer if you would please. I won't go into 2.2 > anyway, so there's no big rush. > Really? Darn... guess I won't be able to stick with 2.2 after all... I was hoping this would make it in. I usually run -CURRENT, but was sort of looking forward to running a "stable" 2.2 system for a while and not playing the make world game for a few months at least. Oh well, NAT is just too useful, so I guess I'll be 3.0 after all :-) Out of curiosity, when is 2.2-RELEASE going to happen? Is the early Jan. 97 estimate still on target? I have a few friends that I've convinced to run FreeBSD, but I've been telling them to hold off for a few weeks for 2.2 :-) cya, -Mark > > Nate > --------------------------------------------------- | Mark Mayo mark@quickweb.com | | RingZero Comp. vinyl.quickweb.com/mark | --------------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch From owner-freebsd-hackers Mon Dec 9 21:42:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA14906 for hackers-outgoing; Mon, 9 Dec 1996 21:42:35 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA14894 for ; Mon, 9 Dec 1996 21:42:31 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id VAA21649; Mon, 9 Dec 1996 21:42:22 -0800 (PST) To: John Birrell cc: hackers@freebsd.org Subject: Re: poll(2) In-reply-to: Your message of "Tue, 10 Dec 1996 08:18:03 +1100." <199612092118.IAA10527@freebsd1.cimlogic.com.au> Date: Mon, 09 Dec 1996 21:42:22 -0800 Message-ID: <21645.850196542@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > There are a few things that NetBSD has added recently that belong (IMHO) > in FreeBSD too. One of them is poll(2), which gives an alternative to > select(2) that does not suffer from the FD_SETSIZE "feature". > > Anyone planning to add this? If you get no answer to this, trying a second time with a PR containing unidiffs might just be what it takes to get it in. :-) Failing that, if you are going to make a habit of looking through both code bases, commit privileges to FreeBSD might be an even more effective solution if you're into it. Jordan From owner-freebsd-hackers Mon Dec 9 22:04:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA17047 for hackers-outgoing; Mon, 9 Dec 1996 22:04:25 -0800 (PST) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA17024 for ; Mon, 9 Dec 1996 22:04:06 -0800 (PST) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id LAA17340; Tue, 10 Dec 1996 11:01:18 +0500 (ESK) From: "Serge A. Babkin" Message-Id: <199612100601.LAA17340@hq.icb.chel.su> Subject: Re: Help, I've been SCOed! To: jehamby@lightside.com (Jake Hamby) Date: Tue, 10 Dec 1996 11:01:17 +0500 (ESK) Cc: terry@lambert.org, hackers@freebsd.org, jkh@time.cdrom.com In-Reply-To: from "Jake Hamby" at Dec 8, 96 01:12:26 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > But I won't tell my client to switch to Linux because it doesn't provide > any sort of long-term solution for their database (moving it to something > real like Oracle). Right now they want to move over to Windows NT, with Linux _can_ run Oracle7. You just need to take a SCO system, install Oracle there and then move the installed version to your Linux system. If your client already has a SCO license this is possible to do. We run Oracle 7.2.2 under Linux for more than half a year and did not noticed any problems (except the "cross-installation"). -SB From owner-freebsd-hackers Mon Dec 9 22:10:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA17588 for hackers-outgoing; Mon, 9 Dec 1996 22:10:55 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA17583 for ; Mon, 9 Dec 1996 22:10:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id WAA07044; Mon, 9 Dec 1996 22:10:24 -0800 (PST) Message-Id: <199612100610.WAA07044@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Mark Mayo cc: Nate Williams , Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-reply-to: Your message of "Tue, 10 Dec 1996 00:38:44 EST." From: David Greenman Reply-To: dg@root.com Date: Mon, 09 Dec 1996 22:10:24 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Out of curiosity, when is 2.2-RELEASE going to happen? Is the early Jan. >97 estimate still on target? I have a few friends that I've convinced to >run FreeBSD, but I've been telling them to hold off for a few weeks for >2.2 :-) Yes, early January. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Dec 9 23:36:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25189 for hackers-outgoing; Mon, 9 Dec 1996 23:36:45 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25183 for ; Mon, 9 Dec 1996 23:36:43 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id XAA22924; Mon, 9 Dec 1996 23:36:40 -0800 (PST) To: Martin Renters cc: freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-reply-to: Your message of "Mon, 09 Dec 1996 23:09:56 EST." <199612100409.XAA29044@tdc.on.ca> Date: Mon, 09 Dec 1996 23:36:40 -0800 Message-ID: <22920.850203400@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Argh. I already did all this. ;-( I just have a command-line switch called '-alias' for enabling it in the variant I did. One man's NAT is another man's IP aliasing. ;-) The only reason I haven't committed it yet is that I'm trying to improve ppp.8 to the point where it actually *describes* the feature to someone who doesn't necessarily understand what NAT is all about. You, erm, wouldn't have already attacked the documentation in your version, would you? ;-) Perhaps we can/should compare notes. Jordan > I've merged Charles Mott's PPP with packet aliasing code into the > -current PPP code and added a 'set nat on' command so that it can > be turned on or off. The default is off which keeps the existing PPP > behaviour. > > If no one is violently opposed to this feature, I'll commit it later > this week. It certainly seems useful. > > Martin From owner-freebsd-hackers Mon Dec 9 23:40:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25570 for hackers-outgoing; Mon, 9 Dec 1996 23:40:57 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25565 for ; Mon, 9 Dec 1996 23:40:55 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id XAA22953; Mon, 9 Dec 1996 23:40:49 -0800 (PST) To: Nate Williams cc: Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-reply-to: Your message of "Mon, 09 Dec 1996 22:07:22 MST." <199612100507.WAA05817@rocky.mt.sri.com> Date: Mon, 09 Dec 1996 23:40:49 -0800 Message-ID: <22949.850203649@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Wow, there are now *3* differnent folks working on this. Brian Somers > is working with the code that Charles sent me and has added some new > stuff to it. He wants to commit the code himself, so I've held off > doing anything with it (and also because I'm on a business trip meaning > I can't test it fully). Yeargh.. :-) Well, in the interest of trying to minimize confusion, here's the version I have waiting to commit: time.cdrom.com:~ftp/pub/new-ppp.tar.gz If there are a few more features in the pipeline that I din't know about or one of you has done more to improve the docs (I only added one paragraph), let me know! So, who's the coordinator of this now, anyway? It doesn't have to be me, but it should be *one* of us! :-) Jordan From owner-freebsd-hackers Mon Dec 9 23:41:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25600 for hackers-outgoing; Mon, 9 Dec 1996 23:41:18 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25590 for ; Mon, 9 Dec 1996 23:41:14 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id XAA01555; Mon, 9 Dec 1996 23:38:57 -0800 (PST) Message-ID: <32AD136C.41C67EA6@whistle.com> Date: Mon, 09 Dec 1996 23:38:20 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Martin Renters CC: hackers@freebsd.org Subject: Re: PPP with network address translation References: <199612100409.XAA29044@tdc.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Martin Renters wrote: > > I've merged Charles Mott's PPP with packet aliasing code into the > -current PPP code and added a 'set nat on' command so that it can > be turned on or off. The default is off which keeps the existing PPP > behaviour. > > If no one is violently opposed to this feature, I'll commit it later > this week. It certainly seems useful. > > Martin YES! though check with nate too From owner-freebsd-hackers Mon Dec 9 23:41:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25651 for hackers-outgoing; Mon, 9 Dec 1996 23:41:56 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25646 for ; Mon, 9 Dec 1996 23:41:54 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id XAA22968; Mon, 9 Dec 1996 23:41:41 -0800 (PST) To: Mark Mayo cc: Nate Williams , Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-reply-to: Your message of "Tue, 10 Dec 1996 00:38:44 EST." Date: Mon, 09 Dec 1996 23:41:41 -0800 Message-ID: <22965.850203701@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Out of curiosity, when is 2.2-RELEASE going to happen? Is the early Jan. > 97 estimate still on target? I have a few friends that I've convinced to Yes. Jordan From owner-freebsd-hackers Mon Dec 9 23:51:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA26300 for hackers-outgoing; Mon, 9 Dec 1996 23:51:33 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA26294 for ; Mon, 9 Dec 1996 23:51:27 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.3/8.7.3) id IAA05036; Tue, 10 Dec 1996 08:54:52 +0100 (MET) Message-Id: <199612100754.IAA05036@ravenock.cybercity.dk> Subject: Re: PPP with network address translation In-Reply-To: <199612100507.WAA05817@rocky.mt.sri.com> from Nate Williams at "Dec 9, 96 10:07:22 pm" To: nate@mt.sri.com (Nate Williams) Date: Tue, 10 Dec 1996 08:54:51 +0100 (MET) Cc: martin@tdc.on.ca, freebsd-hackers@freebsd.org From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Nate Williams who wrote: > > I've merged Charles Mott's PPP with packet aliasing code into the > > -current PPP code and added a 'set nat on' command so that it can > > be turned on or off. The default is off which keeps the existing PPP > > behaviour. > > Wow, there are now *3* differnent folks working on this. Brian Somers > is working with the code that Charles sent me and has added some new > stuff to it. He wants to commit the code himself, so I've held off > doing anything with it (and also because I'm on a business trip meaning > I can't test it fully). Hi, hi, I know of 4 now (I'm not the fourth, I have an unreleaseable kernel NAT).... > > If no one is violently opposed to this feature, I'll commit it later > > this week. It certainly seems useful. > > Hold off just a bit longer if you would please. I won't go into 2.2 > anyway, so there's no big rush. Hmm, I'd like it to be in 2.2, and I know that charles's code works pretty decently for a couble of my users here... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Tue Dec 10 00:00:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA26953 for hackers-outgoing; Tue, 10 Dec 1996 00:00:35 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-197.rdcy01.pacbell.net [206.170.5.197]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA26943; Tue, 10 Dec 1996 00:00:28 -0800 (PST) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id AAA00750; Tue, 10 Dec 1996 00:00:02 -0800 (PST) Message-Id: <199612100800.AAA00750@precipice.shockwave.com> To: Michael Smith cc: Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org Subject: Re: need help with a PC CARD NE2000 clone... In-reply-to: Your message of "Tue, 10 Dec 1996 12:03:59 +1030." <199612100134.MAA11963@genesis.atrad.adelaide.edu.au> Date: Tue, 10 Dec 1996 00:00:01 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, the good news is that fixing the logic to round up did fix my allocation problems. Now pccardd sets up the card and calls the ed driver to initialize. Unfortunately, at this point, the system hangs (seting a breakpoint at edinit shows the call occuring). My next step will be to remote-gdb the kernel... or I could just get a big hammer and smash this cruddy ethernet card into pieces. I should have known $100 for a PCMCIA ethernet card last xmas was too good to be true. :-) I'm thinking of going out and getting one of the 3COM 3c589 cards and a Megahertz 3811 cellular modem, but the combo is /not/ cheap. I noticed that Fry's is selling IBM's old 14.4k modem+Ethernet cards for $69. I'm going to yell at the manufacturer of my ethernet card, as I noticed even they needed a special driver under w95 for this card. Maybe they'll cough up some dirt on how it differs. Paul From owner-freebsd-hackers Tue Dec 10 00:04:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA27139 for hackers-outgoing; Tue, 10 Dec 1996 00:04:01 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA27125; Tue, 10 Dec 1996 00:03:56 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id SAA14925; Tue, 10 Dec 1996 18:33:41 +1030 (CST) From: Michael Smith Message-Id: <199612100803.SAA14925@genesis.atrad.adelaide.edu.au> Subject: Re: need help with a PC CARD NE2000 clone... In-Reply-To: <199612100800.AAA00750@precipice.shockwave.com> from Paul Traina at "Dec 10, 96 00:00:01 am" To: pst@shockwave.com (Paul Traina) Date: Tue, 10 Dec 1996 18:33:40 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina stands accused of saying: > Well, the good news is that fixing the logic to round up did fix my > allocation problems. Now pccardd sets up the card and calls the ed > driver to initialize. > > Unfortunately, at this point, the system hangs (seting a breakpoint > at edinit shows the call occuring). My next step will be to > remote-gdb the kernel... or I could just get a big hammer and > smash this cruddy ethernet card into pieces. I should have known > $100 for a PCMCIA ethernet card last xmas was too good to be true. :-) Hmm. Great, even. 8( > I'm thinking of going out and getting one of the 3COM 3c589 cards > and a Megahertz 3811 cellular modem, but the combo is /not/ cheap. I would strongly advise against the 3c589 if stress is not your friend; see Greg Lehey's current running battle for reference there. I can assue you that the Accton EN2216 card _does_ work, and it shouldn't bust the bank. Accton should be available in your neck of the woods. > I'm going to yell at the manufacturer of my ethernet card, as I noticed > even they needed a special driver under w95 for this card. Maybe they'll > cough up some dirt on how it differs. Heh. Hopeful 8( > Paul -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Dec 10 00:31:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA28100 for hackers-outgoing; Tue, 10 Dec 1996 00:31:27 -0800 (PST) Received: from precipice.shockwave.com (ppp-206-170-5-197.rdcy01.pacbell.net [206.170.5.197]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA28093; Tue, 10 Dec 1996 00:31:21 -0800 (PST) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.8.4/8.7.3) with ESMTP id AAA00864; Tue, 10 Dec 1996 00:24:52 -0800 (PST) Message-Id: <199612100824.AAA00864@precipice.shockwave.com> To: Michael Smith cc: Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org Subject: Re: need help with a PC CARD NE2000 clone... In-reply-to: Your message of "Tue, 10 Dec 1996 18:33:40 +1030." <199612100803.SAA14925@genesis.atrad.adelaide.edu.au> Date: Tue, 10 Dec 1996 00:24:52 -0800 From: Paul Traina Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: Michael Smith Subject: Re: need help with a PC CARD NE2000 clone... I can assue you that the Accton EN2216 card _does_ work, and it shouldn't bust the bank. Accton should be available in your neck of the woods. Yes, I saw them, and disregarded them because I didn't want to get stung by another dinky vendor. However, the only problem is getting support, so if it already works, then I'm golden. Thanks. Does anyone have any opinions about the Megahertz combo or modem-only cards? I have yet to see anyone say they have the combo-ether/modem card working, so I'm thinking of just doing a Megahertz modem card. Cellular One was kind enough to send me a Megahertz<->Nokia cable for my nokia 2160 cellphone for free (Megahertz is putting on a promo). So, I'm kinda leaning towards a Megahertz modem (unless I can find a better modem card with cellular capability for less than the cost of purchasing a cable for real). From owner-freebsd-hackers Tue Dec 10 00:40:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA28392 for hackers-outgoing; Tue, 10 Dec 1996 00:40:46 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA28387; Tue, 10 Dec 1996 00:40:43 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA12555; Tue, 10 Dec 1996 00:33:17 -0800 (PST) To: Paul Traina cc: Michael Smith , Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org Subject: Re: need help with a PC CARD NE2000 clone... In-reply-to: Your message of "Tue, 10 Dec 1996 00:00:01 PST." <199612100800.AAA00750@precipice.shockwave.com> Date: Tue, 10 Dec 1996 00:33:16 -0800 Message-ID: <12551.850206796@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm thinking of going out and getting one of the 3COM 3c589 cards > and a Megahertz 3811 cellular modem, but the combo is /not/ cheap. I've had excellent luck with National's "InfoMover" card, though it's probably years out of date by now. Jordan From owner-freebsd-hackers Tue Dec 10 00:46:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA28540 for hackers-outgoing; Tue, 10 Dec 1996 00:46:17 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA28535; Tue, 10 Dec 1996 00:46:13 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA15232; Tue, 10 Dec 1996 19:09:44 +1030 (CST) From: Michael Smith Message-Id: <199612100839.TAA15232@genesis.atrad.adelaide.edu.au> Subject: Re: need help with a PC CARD NE2000 clone... In-Reply-To: <199612100824.AAA00864@precipice.shockwave.com> from Paul Traina at "Dec 10, 96 00:24:52 am" To: pst@shockwave.com (Paul Traina) Date: Tue, 10 Dec 1996 19:09:43 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina stands accused of saying: > > I can assue you that the Accton EN2216 card _does_ work, and it shouldn't > bust the bank. Accton should be available in your neck of the woods. > > Yes, I saw them, and disregarded them because I didn't want to get stung > by another dinky vendor. However, the only problem is getting support, so > if it already works, then I'm golden. Yup. I've beaten on the one here for the last 6 months or so, and we bought a few more to go with some more systems less than three weeks ago, so I'm confident that they work OK. > I have yet to see anyone say they have the combo-ether/modem card working, > so I'm thinking of just doing a Megahertz modem card. There are problems with sharing interrupts on a single card; you would definitely require more hackery. 8( -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Dec 10 01:04:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA29209 for hackers-outgoing; Tue, 10 Dec 1996 01:04:16 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA29204 for ; Tue, 10 Dec 1996 01:04:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id AAA16434; Tue, 10 Dec 1996 00:54:01 -0800 (PST) Message-Id: <199612100854.AAA16434@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: Jonathan Stone Cc: John Birrell , terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: poll(2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 10 Dec 1996 00:53:56 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 09 Dec 1996 17:09:57 -0800 Jonathan Stone wrote: > Re naming, npoll() is more consistent with the sleep()/usleep() usage. > Does POSIX have anything to say here? nanosleep() (right?) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Tue Dec 10 01:38:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA00617 for hackers-outgoing; Tue, 10 Dec 1996 01:38:02 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA00612 for ; Tue, 10 Dec 1996 01:38:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id BAA17083; Tue, 10 Dec 1996 01:30:19 -0800 (PST) Message-Id: <199612100930.BAA17083@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" Cc: John Birrell , hackers@freebsd.org Subject: Re: poll(2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 10 Dec 1996 01:30:19 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 09 Dec 1996 21:42:22 -0800 "Jordan K. Hubbard" wrote: > If you get no answer to this, trying a second time with a PR > containing unidiffs might just be what it takes to get it in. :-) So, it's worth noting, you have to change every driver that has a select() entry point... Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Tue Dec 10 02:14:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA02045 for hackers-outgoing; Tue, 10 Dec 1996 02:14:27 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA02040 for ; Tue, 10 Dec 1996 02:14:23 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id KAA24985; Tue, 10 Dec 1996 10:13:43 GMT Date: Tue, 10 Dec 1996 19:13:42 +0900 (JST) From: Michael Hancock To: Bakul Shah cc: Terry Lambert , freebsd-hackers@freebsd.org Subject: Re: clone()/rfork()/threads (Re: Inferno for FreeBSD) In-Reply-To: <199612062111.QAA22343@chai.plexuscom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 6 Dec 1996, Bakul Shah wrote: > BTW, you may wish to browse the NBS thread (a different kind of > thread) on comp.os.research. NBS may be something worth using > (instead of mutexs and locks) in the MP version of FreeBSD. Also > read Greenwald and Cheriton's "The Synergy Between Non-blocking > Synchronization and Operating System Structure" (accessible via > http://www-dsg.stanford.edu/Publications.html) This is pretty interesting. Here's a quote from one of Greenwald's postings: "Blocking synchronization commits you to allowing the first person to acquire the lock to finish, and everyone else is blocked. Non-blocking synchronization allows you to reconsider who the "lock-owner" should be at any point during the operation." Regards, Mike Hancock From owner-freebsd-hackers Tue Dec 10 06:08:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA01387 for hackers-outgoing; Tue, 10 Dec 1996 06:08:05 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA01344; Tue, 10 Dec 1996 06:07:59 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA10994; Tue, 10 Dec 1996 08:07:21 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma010985; Tue Dec 10 08:07:06 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA22801; Tue, 10 Dec 1996 08:07:19 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id IAA05255; Tue, 10 Dec 1996 08:07:39 -0600 (CST) Message-Id: <199612101407.IAA05255@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: dyson@FreeBSD.ORG cc: erich@lodgenet.com (Eric L. Hernes), scrappy@hub.org, hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Mon, 09 Dec 1996 21:38:50 EST." <199612100238.VAA27569@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Dec 1996 08:07:39 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" writes: >> >> Shared memory is cool, SysV symantics for shared memory *suck*, if at all >> possible use mmap(). BSDi uses libc wrappers around mmap() for >> it's SysV shm stuff, but there's caveats... I'd like the wrappers, >> but have the real ones available too. >> >FreeBSD, NetBSD, and OpenBSD have a low level implementation of the >SYSVSHM stuff (not based on mmap, but on some of the low level kernel primativ >es >that are also used to implement mmap.) > yea, I know that, but there are some programs (gimp) that use gobs of shared memory, at some point you'll run out and have to build a new kernel. The right answer is to get the authors to fix their program. A slightly uglier solution would be to #include a hacked up and that would use a wrapper to mmap, then it's only a application re-compile instead of a kernel/reboot. Another thing I'd be mildly interested in is /kern/sysv/shm/ that is mmap()able. Although I don't think that would gain any functionality, it might even be wandering close to something linux would try... but you could get the equivalent of `ipcs' from `ls /kern/sysv/*' >> >> you can only have 8 shm segments by default, you can override >> it with: `options "SHMSEG=32"' or something similar in your config file. >> I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. >> >The limits on FreeBSD are totally administrative, and so if you need to >increase SHMMAXPGS or somesuch, there is little cost. > Are there any big obstacles to making this totally dynamic? >John >dyson@freebsd.org eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Dec 10 06:24:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA03470 for hackers-outgoing; Tue, 10 Dec 1996 06:24:31 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA03457; Tue, 10 Dec 1996 06:24:27 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id JAA06928; Tue, 10 Dec 1996 09:24:21 -0500 (EST) From: "John S. Dyson" Message-Id: <199612101424.JAA06928@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 10 Dec 1996 09:24:21 -0500 (EST) Cc: dyson@FreeBSD.ORG, erich@lodgenet.com, scrappy@hub.org, hackers@FreeBSD.ORG In-Reply-To: <199612101407.IAA05255@jake.lodgenet.com> from "Eric L. Hernes" at Dec 10, 96 08:07:39 am X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >The limits on FreeBSD are totally administrative, and so if you need to > >increase SHMMAXPGS or somesuch, there is little cost. > > > > Are there any big obstacles to making this totally dynamic? > None that I know of. Mapping the shared memory into kva space seperately from process space (like the original code) is of no use, and takes KVA space. When it takes KVA space, there becomes a problem with KVA space allocation. The only limitation(s) on FreeBSD, other than administative are (I think) process size, and swap space. FreeBSD has used the NetBSD code since the 4.4-lite re-do. When we had users complain about the shared memory size limits, I was suprised that the code was implemented to use KVA space?!?!? The mods aren't that hard to fix it. There are some other nits that I have about the code, and I have it partially rewritten (smaller) from scratch. But, it isn't my highest priority right now, and the current code in FreeBSD (modified NetBSD code) works ok. John From owner-freebsd-hackers Tue Dec 10 08:25:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA10977 for hackers-outgoing; Tue, 10 Dec 1996 08:25:43 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA10972 for ; Tue, 10 Dec 1996 08:25:41 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id QAA154080; Tue, 10 Dec 1996 16:22:52 GMT Message-Id: <199612101622.QAA154080@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-94.va.us.ibm.net(166.72.229.94) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaPVwDFW; Tue Dec 10 16:22:25 1996 Reply-To: From: "Steve Sims" To: "Martin Renters" , "Jordan K. Hubbard" , "Nate Williams" Cc: Subject: Re: PPP with network address translation Date: Tue, 10 Dec 1996 11:21:28 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, Enough! I'm out of the pool. Here's what I ask: 1) Somebody point me at the code that we intend to merge into 2.2. (I, for one, would like to see this in 2.2-RELEASE. It's cool, seems to be stable, and is trivial to set up. 2) Tell me who the maintainer-du-jour is; I'll work with him, his release notes ;-) and his code to work up the docs. 3) Settle for once and all whether it's Jordan's '-alias' flag in the command line or Martin's 'set nat on|off' (Which I think is more elegant, at least in theory). I'll do testing and documentation if someone will show me the Release Candidate code that I can hammer on for a while. ....sjs... ---------- > From: Jordan K. Hubbard > To: Martin Renters > Cc: freebsd-hackers@freebsd.org > Subject: Re: PPP with network address translation > Date: Tuesday, December 10, 1996 2:36 AM > > Argh. I already did all this. ;-( > > I just have a command-line switch called '-alias' for enabling > it in the variant I did. One man's NAT is another man's IP aliasing. ;-) > > The only reason I haven't committed it yet is that I'm trying to > improve ppp.8 to the point where it actually *describes* the feature > to someone who doesn't necessarily understand what NAT is all about. > > You, erm, wouldn't have already attacked the documentation in your > version, would you? ;-) Perhaps we can/should compare notes. > > Jordan > > > I've merged Charles Mott's PPP with packet aliasing code into the > > -current PPP code and added a 'set nat on' command so that it can > > be turned on or off. The default is off which keeps the existing PPP > > behaviour. > > > > If no one is violently opposed to this feature, I'll commit it later > > this week. It certainly seems useful. > > > > Martin > From owner-freebsd-hackers Tue Dec 10 08:36:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11358 for hackers-outgoing; Tue, 10 Dec 1996 08:36:54 -0800 (PST) Received: from tdc.on.ca (tdc.on.ca [204.92.242.39]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA11344 for ; Tue, 10 Dec 1996 08:36:50 -0800 (PST) Received: (from martin@localhost) by tdc.on.ca (8.7.5/8.6.6) id LAA00216; Tue, 10 Dec 1996 11:34:11 -0500 (EST) From: Martin Renters Message-Id: <199612101634.LAA00216@tdc.on.ca> Subject: Re: PPP with network address translation To: SimsS@IBM.Net Date: Tue, 10 Dec 1996 11:34:10 -0500 (EST) Cc: jkh@time.cdrom.com, nate@mt.sri.com, freebsd-hackers@freebsd.org In-Reply-To: <199612101622.QAA154080@smtp-gw01.ny.us.ibm.net> from "Steve Sims" at Dec 10, 96 11:21:28 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 1) Somebody point me at the code that we intend to merge into 2.2. (I, for > one, would like to see this in 2.2-RELEASE. It's cool, seems to be stable, > and is trivial to set up. I haven't really done much more than merge Charles' code (which changes very little in the base ppp code) and add the 'set nat' code. I understand Brian may have made some further enhancements but I don't have that code yet. > 3) Settle for once and all whether it's Jordan's '-alias' flag in the command > line or Martin's 'set nat on|off' (Which I think is more elegant, at least in > theory). Actually, I like Jordan's idea of a command line switch for the simple reason that the 'set nat on|off' *could* be turned on and off at any time which would certainly confuse the clients/servers involved. It seems to be you'd want it either on or off for the whole session which the command line switch accomplishes well. > I'll do testing and documentation if someone will show me the Release > Candidate code that I can hammer on for a while. Martin From owner-freebsd-hackers Tue Dec 10 08:44:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11978 for hackers-outgoing; Tue, 10 Dec 1996 08:44:43 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA11973 for ; Tue, 10 Dec 1996 08:44:41 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.7.3) id KAA29064 for freebsd-hackers@freefall.cdrom.com; Tue, 10 Dec 1996 10:44:27 -0600 (CST) From: Bob Willcox Message-Id: <199612101644.KAA29064@luke.pmr.com> Subject: Dump "short read error" on a Micropolis disk To: freebsd-hackers@freefall.FreeBSD.org (freebsd-hackers) Date: Tue, 10 Dec 1996 10:44:27 -0600 (CST) Reply-To: bob@luke.pmr.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have this Micropolis disk that the dump program doesn't seem to like. I continually get the following kinds of errors when dumping it: DUMP: Date of this level 0 dump: Tue Dec 10 10:00:12 1996 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd6a (/usr3) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 951885 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.27% done, finished in 0:39 DUMP: 23.46% done, finished in 0:32 DUMP: 35.43% done, finished in 0:27 DUMP: short read error from /dev/rsd6a: [block -670977536]: count=3072, got=0 DUMP: short read error from /dev/rsd6a: [sector -670977536]: count=512, got=0 DUMP: short read error from /dev/rsd6a: [sector -670977535]: count=512, got=0 ... Conincident with the dump errors I get the following system messages: Debugger("Slice code got negative blocknumber") called. Which lead me to be suspect that I had some kind of partition/label problem. But, alas, I have re-partitioned and re-labeled this disk a couple of times with no effect. The SCSI probe messages for this driver are: ahc2: target 0 Tagged Queuing Device (ahc2:0:0): "MICROP 2217-15MZ1001901 HZ30" type 0 fixed SCSI 2 sd6(ahc2:0:0): Direct-Access 1685MB (3450902 512 byte sectors) I have also included the disks partition and label info below. Thanks for any help you can give, Bob Willcox ******* Working on device /dev/rsd6 ******* parameters extracted from in-core disklabel are: cylinders=421 heads=256 sectors/track=32 (8192 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=421 heads=256 sectors/track=32 (8192 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 3448800 (1683 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 420/ sector 32/ head 255 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: # /dev/rsd6c: type: SCSI disk: MICROP label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 256 sectors/cylinder: 8192 cylinders: 420 sectors/unit: 3448800 rpm: 5400 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 3448800 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 420*) c: 3448800 0 unused 0 0 # (Cyl. 0 - 420*) -- Bob Willcox politics, n: bob@luke.pmr.com A strife of interests masquerading as a contest of Austin, TX principles. The conduct of public affairs for private advantage. -- Ambrose Bierce From owner-freebsd-hackers Tue Dec 10 09:10:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA13963 for hackers-outgoing; Tue, 10 Dec 1996 09:10:51 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA13957 for ; Tue, 10 Dec 1996 09:10:46 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA07888; Tue, 10 Dec 1996 10:10:34 -0700 (MST) Date: Tue, 10 Dec 1996 10:10:34 -0700 (MST) Message-Id: <199612101710.KAA07888@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Nate Williams , Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-Reply-To: <22949.850203649@time.cdrom.com> References: <199612100507.WAA05817@rocky.mt.sri.com> <22949.850203649@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Wow, there are now *3* differnent folks working on this. Brian Somers > > is working with the code that Charles sent me and has added some new > > stuff to it. He wants to commit the code himself, so I've held off > > doing anything with it (and also because I'm on a business trip meaning > > I can't test it fully). > > Yeargh.. :-) > > Well, in the interest of trying to minimize confusion, here's the > version I have waiting to commit: > > time.cdrom.com:~ftp/pub/new-ppp.tar.gz > > If there are a few more features in the pipeline that I din't know > about or one of you has done more to improve the docs (I only added > one paragraph), let me know! Charles fixed the manpages with the code Brian and I have, so again let's try and stick with the version I have. > So, who's the coordinator of this now, anyway? It doesn't have to be > me, but it should be *one* of us! :-) I volunteered two weeks ago to do this, but I didn't get Charles code until last week and then I sent the code to Brian late last week to play with/test. Do you want it in 2.2? If so, I'll speed up my testing as soon as I get home. Nate From owner-freebsd-hackers Tue Dec 10 09:12:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14181 for hackers-outgoing; Tue, 10 Dec 1996 09:12:28 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA14155; Tue, 10 Dec 1996 09:12:15 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA07927; Tue, 10 Dec 1996 10:11:44 -0700 (MST) Date: Tue, 10 Dec 1996 10:11:44 -0700 (MST) Message-Id: <199612101711.KAA07927@rocky.mt.sri.com> From: Nate Williams To: Paul Traina Cc: Michael Smith , Andrew.Gordon@net-tel.co.uk, nate@freebsd.org, mobile@freebsd.org, hackers@freebsd.org Subject: Re: need help with a PC CARD NE2000 clone... In-Reply-To: <199612100824.AAA00864@precipice.shockwave.com> References: <199612100803.SAA14925@genesis.atrad.adelaide.edu.au> <199612100824.AAA00864@precipice.shockwave.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone have any opinions about the Megahertz combo or modem-only cards? Combo cards currently don't work under FreeBSD. > Cellular One was kind enough to send me a Megahertz<->Nokia cable for > my nokia 2160 cellphone for free (Megahertz is putting on a promo). So, > I'm kinda leaning towards a Megahertz modem (unless I can find a better > modem card with cellular capability for less than the cost of > purchasing a cable for real). From owner-freebsd-hackers Tue Dec 10 09:16:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14581 for hackers-outgoing; Tue, 10 Dec 1996 09:16:13 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA14565 for ; Tue, 10 Dec 1996 09:16:09 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA07954; Tue, 10 Dec 1996 10:15:52 -0700 (MST) Date: Tue, 10 Dec 1996 10:15:52 -0700 (MST) Message-Id: <199612101715.KAA07954@rocky.mt.sri.com> From: Nate Williams To: Cc: "Martin Renters" , "Jordan K. Hubbard" , "Nate Williams" , Subject: Re: PPP with network address translation In-Reply-To: <199612101622.QAA154080@smtp-gw01.ny.us.ibm.net> References: <199612101622.QAA154080@smtp-gw01.ny.us.ibm.net> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Here's what I ask: > > 1) Somebody point me at the code that we intend to merge into 2.2. (I, for > one, would like to see this in 2.2-RELEASE. It's cool, seems to be stable, > and is trivial to set up. I'm leaning toward the code Brian has right now. > 2) Tell me who the maintainer-du-jour is; I'll work with him, his release > notes ;-) and his code to work up the docs. That'd be me or Brian. > 3) Settle for once and all whether it's Jordan's '-alias' flag in the command > line or Martin's 'set nat on|off' (Which I think is more elegant, at least in > theory). I'm going for the former since turning it on/off should be a one-time deal. And, it's not really NAT, although it acts alot like it. (I think Charles had code to toggle the functionality on/off in the ppp.conf file as well). > I'll do testing and documentation if someone will show me the Release > Candidate code that I can hammer on for a while. > It should be documented well. Nate From owner-freebsd-hackers Tue Dec 10 09:20:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA15182 for hackers-outgoing; Tue, 10 Dec 1996 09:20:46 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA15168 for ; Tue, 10 Dec 1996 09:20:38 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22167; Tue, 10 Dec 1996 12:20:04 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 10 Dec 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id MAA08158 for ; Tue, 10 Dec 1996 12:14:37 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id MAA00609 for freebsd-hackers@freefall.cdrom.com; Tue, 10 Dec 1996 12:16:47 -0500 (EST) Date: Tue, 10 Dec 1996 12:16:47 -0500 (EST) From: Thomas David Rivers Message-Id: <199612101716.MAA00609@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Daily panics (I'm back.) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - After a short hiatus for Thanksgiving and other holidays, and after deleting my backlog'd 5000+ messages :-) I'm ready to dive in on the daily panic problems. Just F.Y.I. - the problem still occurs, and at least one other person has reported it as well. I'm running 2.1.5-S as of Oct. 17th - I had dowloaded 2.1.6-RELEASE to set up and see if the problem went away; but as soon as I got it home, the 2.1.6.1 release came out - so I have to start over. My questions at this point are: 1) Since I was running a late version of 2.1.5-S, there is little hope that 2.1.6.1 will actually address this - right? 2) Assuming 1) is true - how do we proceed on figuring this out? 3) Would it be better to suffer through this for now, and wait for a more stable 2.2 version to try out (presumably _before_ 2.2-RELEASE was sent out.) - Dave Rivers - From owner-freebsd-hackers Tue Dec 10 09:24:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA15789 for hackers-outgoing; Tue, 10 Dec 1996 09:24:10 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA15752 for ; Tue, 10 Dec 1996 09:24:03 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id JAA00576; Tue, 10 Dec 1996 09:23:37 -0800 (PST) To: Nate Williams cc: Martin Renters , freebsd-hackers@freebsd.org Subject: Re: PPP with network address translation In-reply-to: Your message of "Tue, 10 Dec 1996 10:10:34 MST." <199612101710.KAA07888@rocky.mt.sri.com> Date: Tue, 10 Dec 1996 09:23:36 -0800 Message-ID: <572.850238616@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Do you want it in 2.2? If so, I'll speed up my testing as soon as I get > home. Yes. OK, Nate, you're it - your version will be the definitive one. And yes, I think this should be part of 2.2's ppp, assuming that we can get through all this with a working ppp implementation at the end. :-) Jordan From owner-freebsd-hackers Tue Dec 10 10:20:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19342 for hackers-outgoing; Tue, 10 Dec 1996 10:20:18 -0800 (PST) Received: from hub.org (root@hub.org [207.107.138.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA19337 for ; Tue, 10 Dec 1996 10:20:16 -0800 (PST) Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id NAA01152; Tue, 10 Dec 1996 13:20:06 -0500 (EST) Date: Tue, 10 Dec 1996 13:20:06 -0500 (EST) From: "Marc G. Fournier" To: "Eric L. Hernes" cc: hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: <199612100156.TAA00658@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, Eric L. Hernes wrote: > "Marc G. Fournier" writes: > > > >Hi... > > > > Just starting to play with shared memory, and have hit a wall > >that I don't know if its too be expected, or if I've screwed something > >up... > > Shared memory is cool, SysV symantics for shared memory *suck*, if at all > possible use mmap(). BSDi uses libc wrappers around mmap() for > it's SysV shm stuff, but there's caveats... I'd like the wrappers, > but have the real ones available too. > Okay...maybe I'm missing something as far as mmap() is concerned, but what I want to be able to do is allocated X bytes of memory to be shared amongst several processes. After the memory is allocated, I will *then* want to fill the memory (ie. with data read from a socket). From reading the mmap() man page (any good reference/textbooks that I might want to pick up?), mmap() allocates and fills the memory space at the same time, based on a previously opened, already existing, file (fd). Is there something I'm missing? With shared memory, this isn't a problem, or, at least, from what I've read, won't be a problem... > #ifndef SHMSEG > #define SHMSEG 8 > #endif > > you can only have 8 shm segments by default, you can override > it with: `options "SHMSEG=32"' or something similar in your config file. > I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. > Did this, got this: ----- hub> ./client No space left on device cannot initialize shared memory buffer #29 ----- At least I'm getting 28 buffers created now, instead of just 8 :) Now, am I understanding what I've configured correctly? With SHMSEG=128 and SHMMAXPGS=4096, I should be able to allocate up to 128 pages of 4096k each? I actually set SHMSEG to 256, mind you...just in case. options SYSVSHM options SYSVSEM options SYSVMSG options "SHMSEG=256" options "SHMMAXPGS=4096" Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-hackers Tue Dec 10 10:25:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA19638 for hackers-outgoing; Tue, 10 Dec 1996 10:25:13 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA19633 for ; Tue, 10 Dec 1996 10:25:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04496; Tue, 10 Dec 1996 11:03:26 -0700 From: Terry Lambert Message-Id: <199612101803.LAA04496@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: scrappy@hub.org (Marc G. Fournier) Date: Tue, 10 Dec 1996 11:03:25 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at Dec 9, 96 07:56:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > that I don't know if its too be expected, or if I've screwed something > up... Administrative limit because of address space crowding... just like the limit on segment size. You can override as necessary, and rebuild a kernel. However, I would suggest you use mmap instead, if possible. > ---- > #define MAXMESGDATA 2048 > > typedef struct { > int mesg_len; > char mesg_data[MAXMESGDATA]; > } Mesg; > ---- WARNING! When you map a shared memory region or file into an address space, the cache unification and the x86 page protection mechanism forces the mapping to be in chunks of 4k. This basically means that you are overlapping your regions here. The first region, if it starts on a 4k boundry (which it will, according to your code) will map the first 4k page at the start address. The second will map 8k, since it spans a 4k boundry: the first 4k, followed by the next 4k. It will be mapped at a different address. And so on, based on crossing conditions of 4k boundries. It would be much better to mmap a contiguous area, where each message fills up exactly 4k (even if you need pad to do it) and make sure the messages are on 4k boundries to ensure seperate protection domains. This is true, even if you use SVR4 primitives... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 10:43:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21051 for hackers-outgoing; Tue, 10 Dec 1996 10:43:32 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21039 for ; Tue, 10 Dec 1996 10:43:27 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04523; Tue, 10 Dec 1996 11:20:55 -0700 From: Terry Lambert Message-Id: <199612101820.LAA04523@phaeton.artisoft.com> Subject: Re: poll(2) To: jonathan@DSG.Stanford.EDU (Jonathan Stone) Date: Tue, 10 Dec 1996 11:20:55 -0700 (MST) Cc: thorpej@nas.nasa.gov, jb@cimlogic.com.au, terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: <199612100109.RAA04353@Pescadero.DSG.Stanford.EDU> from "Jonathan Stone" at Dec 9, 96 05:09:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Just wanted to get tech-kern@netbsd.org on this thread, too :-) > > > >"Discuss." :-) > > Uh, well, then.... > > AFAIK, there aren't yet any NetBSD ports with significantly > better than millisecond time-of-day-clock (and thus forced process- > scheduling) resolution. So milliseconds are currently as good as > you'll get. > > You can add a syscall specifying a nanosecond interval, but anyone > thinking they're going to get _nano_second-level wakeups is, > currently, deluding themselves. (I still get ~4usec syscall times on > a 200MHz P6.) The Sun SPARCServer 2 also has a timer resoloution of ~4uS; this was tested with itimers + gettimeofday() after timer firing, so it does include significant system call overhead. I think the scheduling limitation of 100Hz limits the guaranteee resoloution to 10ms, at best (gettimeofday() value update frequency for the SVR4 scheduler module... SVID specifies system clock update frequency... SVR4 is not SVID compliant). If a process consumes it's entire quantum, it will not switch for 10ms without kernel preemption based on a timer event being capable of forcing a kernel-level context switch. Practically, this becomes a maximum of: 10ms + min( 10ms, timer_duration) - 1 If the process in line before the timer expiry process consumes its full quantum. This assumes that timer expiry events result in the process moving to the head of the scheduler queue. Really, good timers is the province of kernel preemption -- and extension for RT scheduling support. When I make an setitimer/getitimer call, I am *truly* interfacing into the RT services (which is why they are listed in section "(RT)" in SVID III). > Clearly we should add a nano-second resolution poll interface. > Once we do so, regardless of the actualy in-kernel resolution, > poll(2) and upoll(3) become poll(3) and upoll(3). Yes. This is a good idea in general; it shows good future planning. A 550MHz PPC processor is said to be shipping next year... as we approach GHz speds, nS resoloution becomes likely. At the very least, we are talking sub-uS resoloution, which requires those units be used in any case. > Re naming, npoll() is more consistent with the sleep()/usleep() usage. > Does POSIX have anything to say here? No. All of POSIX is permitted to be implemented in libc as nothing more than wrappers. VMS is POSIX compliant, for instance, if you have the VAX C Runtime Environment (well, except the record seek pointer is not advanced after the implied carriage control from a record has been implied into the input stream -- but that's another story). > If we did this _now_ we could, perhaps, reuse the existing syscall > number, since AFAIK poll(2) has never been in an official NetBSD release. Yes. The only conflict is call gate for ABI with some other OS that does poll with which you want binary compatability. Solaris might be one example. It really depends on whether execution classes imply system call interfaces, or not (they should, meaning no conflict). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 10:43:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21075 for hackers-outgoing; Tue, 10 Dec 1996 10:43:39 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21068 for ; Tue, 10 Dec 1996 10:43:37 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04533; Tue, 10 Dec 1996 11:22:25 -0700 From: Terry Lambert Message-Id: <199612101822.LAA04533@phaeton.artisoft.com> Subject: Re: poll(2) To: jb@cimlogic.com.au (John Birrell) Date: Tue, 10 Dec 1996 11:22:25 -0700 (MST) Cc: thorpej@nas.nasa.gov, jb@cimlogic.com.au, terry@lambert.org, hackers@freebsd.org, tech-kern@netbsd.org In-Reply-To: <199612100115.MAA11043@freebsd1.cimlogic.com.au> from "John Birrell" at Dec 10, 96 12:15:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > "Discuss." :-) > > If NetBSD's kernel is moving towards everything being done in timespecs, > then the best that the real kernel *should* offer would be a nanopoll > syscall with a timespec argument. Then libc could provide wrappers for > poll(2) and upoll(2). poll(3) and upoll(2). also select(3) and nselect(3). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 10:54:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA21685 for hackers-outgoing; Tue, 10 Dec 1996 10:54:28 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA21680 for ; Tue, 10 Dec 1996 10:54:22 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id SAA149597; Tue, 10 Dec 1996 18:54:05 GMT Message-Id: <199612101854.SAA149597@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-68.va.us.ibm.net(166.72.229.68) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smauREDmb; Tue Dec 10 18:53:52 1996 Reply-To: From: "Steve Sims" To: "Martin Renters" Cc: , , Subject: Re: PPP with network address translation Date: Tue, 10 Dec 1996 13:52:48 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Martin Renters is on the record: > > > 3) Settle for once and all whether it's Jordan's '-alias' flag in the command > > line or Martin's 'set nat on|off' (Which I think is more elegant, at least in > > theory). > > Actually, I like Jordan's idea of a command line switch for the simple > reason that the 'set nat on|off' *could* be turned on and off at any time > which would certainly confuse the clients/servers involved. It seems to > be you'd want it either on or off for the whole session which the command > line switch accomplishes well. > I find the 'set nat on|off' a little more flexible. Say I have two configurations defined: One for AT&T (which gives me 5 hours a month for *free*) and one for IBM that's all-you-can-eat. Not that this could *actually* happen or anything ;-) but let's say IBM's local POP is hosed for some reason. I'd like to be able to `ppp -auto ATT` (which had `set nat off` in /etc/ppp/ppp.conf) to provide dial-on-demand for mail queue processing, DNS zone transfers and other administrivia for the local machine, but prevent the P2P link from being up full-time (or close to) by the unwashed masses on my local net (who know full well the value of free access!) When the hosed IBM POP got squared away, I'd slay the ATT configuration and load 'ppp -auto IBM' (which, of course, has 'set nat on' in /etc/ppp/ppp.conf). Local network nodes would have restored gatewaying to the world. Just like I can have different levels of debug, different login scripts, different LCP params, I think that different modes of NAT should be supported in the ppp.conf file and, thereby, associated with remote connections rather than the command line arguments used to start ppp. I take your point that this could be specified with an -alias argument when starting ppp, but embedding the setting in the ppp.conf file tends to consolidate remote-side considerations with per-connection settings, rather than per-instances of ppp. Comments? ...sjs... From owner-freebsd-hackers Tue Dec 10 11:05:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22267 for hackers-outgoing; Tue, 10 Dec 1996 11:05:25 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22261 for ; Tue, 10 Dec 1996 11:05:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA04595; Tue, 10 Dec 1996 11:43:36 -0700 From: Terry Lambert Message-Id: <199612101843.LAA04595@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: scrappy@hub.org (Marc G. Fournier) Date: Tue, 10 Dec 1996 11:43:36 -0700 (MST) Cc: erich@lodgenet.com, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Dec 10, 96 01:20:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Okay...maybe I'm missing something as far as mmap() is concerned, > but what I want to be able to do is allocated X bytes of memory to be > shared amongst several processes. After the memory is allocated, I will > *then* want to fill the memory (ie. with data read from a socket). > > From reading the mmap() man page (any good reference/textbooks that > I might want to pick up?), mmap() allocates and fills the memory space at > the same time, based on a previously opened, already existing, file (fd). > > Is there something I'm missing? With shared memory, this isn't a > problem, or, at least, from what I've read, won't be a problem... OK. The cannonically "correct" kludge for this is to mmap() an fd opened on /dev/zero in order to get your anonymous pages. This works because the /dev/zero mapping entry point knows to make an anonymous zero-filled region attacked to an open vnode that does not have an FS name space entry. This is different that mapping /dev/zero copy-on-write, since it means that there is a shared copy of the zero-filled pages, and that the shared copy is seperate. Then you pass the fd to the other processes using a POSIX (UNIX) domain socket. Same fd == same mapping region. I have no idea if this actually works in FreeBSD, like it's supposed to; my gut feeling is that it would not, since a lot of people just ignore FS interaction details, and they get lost in the cracks (this is an FS implementation detail; if you don't believe me, I can explain in great gory detail about struct fileops and character device nodes, like /dev/zero). John? How does mmap'ing /dev/zero work? In any case, if this does not work for you, you *can* write out an empty file for the region size, map it instead, and then once all mappings exist, unlink the file (and pass the fd around with a UNIX domain socket). If you do this method, then the mapping can be non-copy-on-write and still not run into problems (since multiple programs doing this same thing would not crap on /dev/zero itself). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 11:08:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22432 for hackers-outgoing; Tue, 10 Dec 1996 11:08:20 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA22347 for ; Tue, 10 Dec 1996 11:06:49 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id UAA23586 for ; Tue, 10 Dec 1996 20:06:22 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vXXVN-0001zWC; Tue, 10 Dec 96 20:06 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA193564746; Tue, 10 Dec 1996 20:05:46 +0100 From: "Hr.Ladavac" Message-Id: <199612101905.AA193564746@ws2301.gud.siemens.co.at> Subject: Re: Multiple Buffer allocation of Shared Memory To: scrappy@hub.org (Marc G. Fournier) Date: Tue, 10 Dec 1996 20:05:46 +0100 (MEZ) Cc: erich@lodgenet.com, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Dec 10, 96 01:20:06 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Marc G. Fournier contained: > On Mon, 9 Dec 1996, Eric L. Hernes wrote: > > > "Marc G. Fournier" writes: > > > > > >Hi... > > > > > > Just starting to play with shared memory, and have hit a wall > > >that I don't know if its too be expected, or if I've screwed something > > >up... > > > > Shared memory is cool, SysV symantics for shared memory *suck*, if at all > > possible use mmap(). BSDi uses libc wrappers around mmap() for > > it's SysV shm stuff, but there's caveats... I'd like the wrappers, > > but have the real ones available too. > > > > Okay...maybe I'm missing something as far as mmap() is concerned, > but what I want to be able to do is allocated X bytes of memory to be > shared amongst several processes. After the memory is allocated, I will > *then* want to fill the memory (ie. with data read from a socket). > > From reading the mmap() man page (any good reference/textbooks that > I might want to pick up?), mmap() allocates and fills the memory space at > the same time, based on a previously opened, already existing, file (fd). mmap with MAP_SHARED will "propagate" the writes among all processes who map is as shared. You can map with MAP_ANON as well which ignores the contents of the fd (but you still have to have it opened; /dev/null comes in handy :) /Marino > > Is there something I'm missing? With shared memory, this isn't a > problem, or, at least, from what I've read, won't be a problem... > > > #ifndef SHMSEG > > #define SHMSEG 8 > > #endif > > > > you can only have 8 shm segments by default, you can override > > it with: `options "SHMSEG=32"' or something similar in your config file. > > I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. > > > > Did this, got this: > > ----- > hub> ./client > No space left on device > cannot initialize shared memory buffer #29 > ----- > > At least I'm getting 28 buffers created now, instead of just > 8 :) > > Now, am I understanding what I've configured correctly? With > SHMSEG=128 and SHMMAXPGS=4096, I should be able to allocate up to 128 > pages of 4096k each? I actually set SHMSEG to 256, mind you...just in case. > > options SYSVSHM > options SYSVSEM > options SYSVMSG > options "SHMSEG=256" > options "SHMMAXPGS=4096" > > Marc G. Fournier scrappy@hub.org > Systems Administrator @ hub.org scrappy@freebsd.org > > From owner-freebsd-hackers Tue Dec 10 11:20:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23082 for hackers-outgoing; Tue, 10 Dec 1996 11:20:59 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA23076 for ; Tue, 10 Dec 1996 11:20:55 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id OAA00466; Tue, 10 Dec 1996 14:19:26 -0500 (EST) From: John Dyson Message-Id: <199612101919.OAA00466@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: terry@lambert.org (Terry Lambert) Date: Tue, 10 Dec 1996 14:19:26 -0500 (EST) Cc: scrappy@hub.org, hackers@FreeBSD.ORG In-Reply-To: <199612101803.LAA04496@phaeton.artisoft.com> from "Terry Lambert" at Dec 10, 96 11:03:25 am Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Administrative limit because of address space crowding... just like > the limit on segment size. You can override as necessary, and > rebuild a kernel. However, I would suggest you use mmap instead, > if possible. > SYSVSHM isn't that different from mmap, but it has a different namespace. > > It would be much better to mmap a contiguous area, where each message > fills up exactly 4k (even if you need pad to do it) and make sure the > messages are on 4k boundries to ensure seperate protection domains. > This is true, even if you use SVR4 primitives... > I agree with this -- the larger the number of seperate mappings, the more OS overhead there will be. John From owner-freebsd-hackers Tue Dec 10 11:26:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23322 for hackers-outgoing; Tue, 10 Dec 1996 11:26:05 -0800 (PST) Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA23317 for ; Tue, 10 Dec 1996 11:26:01 -0800 (PST) Received: (from tinguely@localhost) by plains.nodak.edu (8.8.3/8.8.3) id NAA19261 for freebsd-hackers@FreeBSD.ORG; Tue, 10 Dec 1996 13:25:53 -0600 (CST) Date: Tue, 10 Dec 1996 13:25:53 -0600 (CST) From: Mark Tinguely Message-Id: <199612101925.NAA19261@plains.nodak.edu> To: freebsd-hackers@FreeBSD.ORG Subject: Re: PPP with network address translation Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk nate says: > And, it's not really NAT, although it acts alot like it. (I > think Charles had code to toggle the functionality on/off in the > ppp.conf file as well). what does it do with applications like ftp? NAT in IP Filter requires a ftp proxie such as those found in FWTK. --mark. From owner-freebsd-hackers Tue Dec 10 11:36:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA24105 for hackers-outgoing; Tue, 10 Dec 1996 11:36:21 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA24089 for ; Tue, 10 Dec 1996 11:36:07 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id NAA27665; Tue, 10 Dec 1996 13:35:26 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma027646; Tue Dec 10 13:34:57 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id NAA30011; Tue, 10 Dec 1996 13:35:10 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id NAA16873; Tue, 10 Dec 1996 13:35:25 -0600 (CST) Message-Id: <199612101935.NAA16873@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Marc G. Fournier" cc: "Eric L. Hernes" , hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Tue, 10 Dec 1996 13:20:06 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Dec 1996 13:35:24 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" writes: > > Okay...maybe I'm missing something as far as mmap() is concerned, >but what I want to be able to do is allocated X bytes of memory to be >shared amongst several processes. After the memory is allocated, I will >*then* want to fill the memory (ie. with data read from a socket). > > From reading the mmap() man page (any good reference/textbooks that >I might want to pick up?), mmap() allocates and fills the memory space at >the same time, based on a previously opened, already existing, file (fd). > Yup, * The Design and Implemenatation of the 4.4BSD Operating System ~page 139 * UNIX Internals The New Frontiers ~page 440 One way, is to open a (previously agreed upon) named file that will be used to share data, ftruncate() it to the size you want, then mmap() it. Other processes can open and mmap() this same file to get at the data. After the mmap(), you've got a pointer to the data, you can cast it to whatever you like, just like with shmat(). The biggest problem here is that all programs will have to agree on the named file, but if you use the SysV stuff, they all have to agree on the shmid, so it's not a showstopper. Terry has already outlined a solution that avoids this problem. In a nutshell, open()/mmap() are roughly analogous to shmget()/shmat(), and munmap()/unlink() are roughly analogous to shmget()/shmctl(). One thing that named files and mmap() can buy you is persistance of data across a reboot(), whether that is good or bad is up to you. > >----- >hub> ./client >No space left on device >cannot initialize shared memory buffer #29 >----- > > At least I'm getting 28 buffers created now, instead of just >8 :) > > Now, am I understanding what I've configured correctly? With >SHMSEG=128 and SHMMAXPGS=4096, I should be able to allocate up to 128 >pages of 4096k each? I actually set SHMSEG to 256, mind you...just in case. SHMMAXPGS is in pages, so its 4096*4096, or 16Meg. I think that 16Meg is the global shared mem pool, and the 128 segments are taken out of it. As John has pointed out, the numbers are purely administrative, you may be able to remove the checks in kern/sysv_shm.c and just grant the requests, but you'll have to check the return from the lower (vm) layer that acutally returns the mapping. > >Marc G. Fournier scrappy@hub.org >Systems Administrator @ hub.org scrappy@freebsd.org > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Dec 10 11:58:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA25387 for hackers-outgoing; Tue, 10 Dec 1996 11:58:58 -0800 (PST) Received: from odie.physik2.uni-rostock.de (odie.physik2.uni-rostock.de [139.30.40.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA25345; Tue, 10 Dec 1996 11:58:11 -0800 (PST) Received: from odie.physik2.uni-rostock.de (localhost [127.0.0.1]) by odie.physik2.uni-rostock.de (8.8.3/8.7.3) with ESMTP id UAA11105; Tue, 10 Dec 1996 20:57:44 +0100 (MET) Message-Id: <199612101957.UAA11105@odie.physik2.uni-rostock.de> X-Mailer: exmh version 1.6.7 5/3/96 To: jgrosch@sirius.com Cc: freebsd-questions@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org, Lars_Koeller@odie.physik2.uni-rostock.de Subject: Re: SKIP for FreeBSD, anyone working on it? In-Reply-To: jgrosch's message of Sun, 08 Dec 1996 04:40:57 -0800. <199612081240.EAA00753@superior.truenorth.org> X-Face: nLQGe[[K51[{{[C\,BiQm[7]u1m{N>_\%nLBo4t@)CoZ}hK[W7DwX&V=}Wf#Qb,j:Jpj[(12r=b~:dYmh]fDf\, ]_frt6eM Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Content-Type: text/plain; charset=us-ascii In message <199612081240.EAA00753@superior.truenorth.org>, Josef Grosch writes: >>-------- >> >> Hi! >> >> Is there anybody working on a port of Sun's IP layer encryption >> implementation for FreeBSD? A US-only version for 2.1.5 is available on >> www.skip.com. When will it be available to ALL FreeBSDles? >> >> Thanks >> >> Lars > >The URL has changed. Try ; > > http://skip.incog.com > Hello! Yes, you are right. Thanks! But is there really nobody who is working on such a famous thing? I know of somone who trys to make it on a LINUX box. - ----------------------------------------------------------------------------- I just wanted to let everyone know that I'm working on ENskip for Linux (localhost is already successfully talking to localhost, encrypted ;-) My approach is somewhat different from IPSEC, however it requires a kernel patch. Hopefully I will have some code ready next week for everyone to test. Robert muchsel@acm.org - ----------------------------------------------------------------------------- Sorry, but I have not enough time to participate! Regards Lars - -- - ------------------------------------------------------------------------ Internet: | Lars Koeller Lars_Koeller@odie.physik2.Uni-Rostock.DE | Department of Physics ftp://odie.physik2.uni-rostock.de | University of Rostock PGP-key: | Germany http://www.nic.surfnet.nl/pgp/pks-toplev.html | - ----------- FreeBSD, what else? ---- http://www.freebsd.org ------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQEVAwUBMq3AtFU+EqI/D/51AQGSEwgAitqAiRJ/QBbqjdzSTXzkzG7pWgtUJbJc 8yIlfp5NpgmPxcYF9UFr1Rn4Q7cW+pG0TYL9CFxDctaDd89YOxzISAKe7m4rgd5H 9TqvzCly2maOfLd0Yd55yCOcJF0Uh8hKegJIKVwQ5ch9RnVsb+l3ZficG8+OpJ1Q fWd1YDwkT3+/Btu7sz0QcifZfz97CURSKn31eRGQnjjCMjlxGaIfZjwbSLP1OB6P L55hdlhcsCfgW+/beyh7xfDu7vmKj2bVWcbSZ6nhBF32Zr7DNekLWgYZ6d5a6CnI 9+2dBjcZIem79coKiTsZhGR6q7l9uW7ZZKRkCT9x0WYbWx+nkHInnQ== =PzJo -----END PGP SIGNATURE----- From owner-freebsd-hackers Tue Dec 10 12:00:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA25545 for hackers-outgoing; Tue, 10 Dec 1996 12:00:03 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA25499 for ; Tue, 10 Dec 1996 12:00:00 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id TAA27414; Tue, 10 Dec 1996 19:59:58 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA151297997; Tue, 10 Dec 1996 19:59:57 GMT Message-Id: <32ADC1A9.3832@fsl.noaa.gov> Date: Tue, 10 Dec 1996 13:01:45 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: "Eric L. Hernes" Cc: "Marc G. Fournier" , hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory References: <199612101935.NAA16873@jake.lodgenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Eric L. Hernes wrote: > One way, is to open a (previously agreed upon) named file that > will be used to share data, ftruncate() it to the size you want, > then mmap() it. Other processes can open and mmap() this same file > to get at the data. But bear in mind where the file is located. If it's on a UFS, then your system will have to do physical I/O to update the file on disk as processes mmap'ing it make updates. That's why it's often better to locate mmap'd files used for IPC on an MFS filesystem. Sample /etc/fstab entries to mount MFS on /tmp: /dev/sd0s4b none swap sw 0 0 /dev/sd0s4b /tmp mfs rw 0 0 Of course, if you need the file's contents to be persistent across reboots, then MFS isn't such a bad idea. > and mmap() can buy you is persistance of data across a reboot(), whether > that is good or bad is up to you. Hey, that's what I just said! ;-) -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ From owner-freebsd-hackers Tue Dec 10 12:10:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26246 for hackers-outgoing; Tue, 10 Dec 1996 12:10:17 -0800 (PST) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA26241 for ; Tue, 10 Dec 1996 12:10:14 -0800 (PST) Received: (from tony@localhost) by nlanr.net (8.7.3/8.7.3) id MAA28642 for hackers@FreeBSD.ORG; Tue, 10 Dec 1996 12:10:07 -0800 (PST) From: Tony Sterrett Message-Id: <199612102010.MAA28642@nlanr.net> Subject: (no subject given) To: hackers@FreeBSD.ORG Date: Tue, 10 Dec 1996 12:10:05 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello everybody I am trying to install a test driver I wrote. The driver is simple it just returns a 0 when opened. My test code only openeds the driver. I performed all the steps in the FreeBSD tutorial on installing driver and my kernel recompiles clean. However when I run I get a strange error: fd = -1 tst: Unknown error: -266382256 Details follow: The Test code: main() { int fd; fd = open("/dev/tst", O_RDONLY); if (fd < 0) { printf ("fd = %d \n",fd); perror("tst"); } } and the driver code is : tstopen(dev_t dev, int flag, int type, struct proc *p) { return (1); } and here is a log of my install steps: in /usr/src/sys/i386/conf/files.i386 - /local/src/tst.c optional tst device-driver in usr/src/sys/i386/i386/conf.c #include "tst.h" #if NTST > 0 d_open_t tstopen; d_close_t tstclose; d_rdwr_t tstread; d_ioctl_t tstioctl; #else #define tstopen nxopen #define tstclose nxclose #define tstread nxread #define tstioctl nxioctl #endif and { tstopen, tstclose, tstread, nowrite, /*76*/ tstioctl, nostop, nullreset, nodevtotty,/*test */ noselect, nommap, NULL}, for the struct cdevsw cdevsw[] value. in GENERIC the config file pseudo-device tst and I mknod c 76 0 76 is the cdevsw element Any ideas. Thanks in advance. Tony From owner-freebsd-hackers Tue Dec 10 12:21:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA26783 for hackers-outgoing; Tue, 10 Dec 1996 12:21:20 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA26771 for ; Tue, 10 Dec 1996 12:21:08 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id OAA00154; Tue, 10 Dec 1996 14:20:21 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma000144; Tue Dec 10 14:20:05 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id OAA30897; Tue, 10 Dec 1996 14:20:18 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id OAA17243; Tue, 10 Dec 1996 14:20:37 -0600 (CST) Message-Id: <199612102020.OAA17243@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Sean Kelly cc: "Eric L. Hernes" , "Marc G. Fournier" , hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Tue, 10 Dec 1996 13:01:45 MST." <32ADC1A9.3832@fsl.noaa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Dec 1996 14:20:37 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sean Kelly writes: >Eric L. Hernes wrote: > >> One way, is to open a (previously agreed upon) named file that >> will be used to share data, ftruncate() it to the size you want, >> then mmap() it. Other processes can open and mmap() this same file >> to get at the data. > >But bear in mind where the file is located. If it's on a UFS, then your >system will have to do physical I/O to update the file on disk as >processes mmap'ing it make updates. That's why it's often better to >locate mmap'd files used for IPC on an MFS filesystem. > correct me if I'm wrong here, but doesn't MFS allocate backing store in swap, so it could be paged out via physical I/O too. In either case the physical IO appears async -- the physio won't happen until the system needs ram, or the pages are inactive. If you've got enough ram, the mmap'ed file won't be flushed out no matter what the underlying FS is. Or do I just have too much faith in the VM system? ;-) > >-- >Sean Kelly >NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov >Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/ eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Dec 10 12:30:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27361 for hackers-outgoing; Tue, 10 Dec 1996 12:30:06 -0800 (PST) Received: from hub.org (root@hub.org [207.107.138.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA27353 for ; Tue, 10 Dec 1996 12:30:02 -0800 (PST) Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id PAA11583; Tue, 10 Dec 1996 15:29:56 -0500 (EST) Date: Tue, 10 Dec 1996 15:29:54 -0500 (EST) From: "Marc G. Fournier" To: "Eric L. Hernes" cc: hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: <199612101935.NAA16873@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 10 Dec 1996, Eric L. Hernes wrote: > Yup, > * The Design and Implemenatation of the 4.4BSD Operating System > ~page 139 > * UNIX Internals The New Frontiers > ~page 440 > Will hit the store this afternoon...thanks... > One way, is to open a (previously agreed upon) named file that > will be used to share data, ftruncate() it to the size you want, > then mmap() it. Other processes can open and mmap() this same file > to get at the data. After the mmap(), you've got a pointer to the > data, you can cast it to whatever you like, just like with shmat(). > The biggest problem here is that all programs will have to agree > on the named file, but if you use the SysV stuff, they all have to agree > on the shmid, so it's not a showstopper. Terry has already outlined > a solution that avoids this problem. In a nutshell, open()/mmap() > are roughly analogous to shmget()/shmat(), and munmap()/unlink() > are roughly analogous to shmget()/shmctl(). One thing that named files > and mmap() can buy you is persistance of data across a reboot(), whether > that is good or bad is up to you. > Okay...this makes a bit of sense (this is new to me, its got to click into place first to make perfect sense *sigh*)... So, if I where to be getting a frame of data from a remote end using sockets, I'd want to do something like: get size of frame open named file ftruncate() named file to size of frame mmap named file write frame to mmap'd region Does that make sense? Now, "child" processes accessing that MMAP'd area...Terry (I believe?) mentioned passing the file descriptor through a socket from the parent to the child, which, to me, sounds okay if you have few children reading the mmap()'d region...but what I'm working on is going to require 1000's of child processes reading that mmap()'d region, and having 1 socket open for each child doesn't sound very efficient. You mention a named file in your example, so each frame could be called '001', '002'...'999', with the child processes accessing them sequentially, as they exist...but at that point, I may as well just write the date to 001, and have the child process open, read, close... I think what I'm still missing is that the way mmap() is being described is that it requires a file to work off of, and all that the benefit is is that each child can share the data from the same memory region...what I'm *trying* to accomplish is a completely "in memory" solution, without using something like MFS to get off of the physical device. I know that I'm currently missing something that is totally obvious to those that have a better understanding of mmap/shm...thanks for the patience... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-hackers Tue Dec 10 12:34:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA27864 for hackers-outgoing; Tue, 10 Dec 1996 12:34:45 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA27859 for ; Tue, 10 Dec 1996 12:34:42 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id PAA00573; Tue, 10 Dec 1996 15:33:11 -0500 (EST) From: John Dyson Message-Id: <199612102033.PAA00573@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: terry@lambert.org (Terry Lambert) Date: Tue, 10 Dec 1996 15:33:11 -0500 (EST) Cc: scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612101843.LAA04595@phaeton.artisoft.com> from "Terry Lambert" at Dec 10, 96 11:43:36 am Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > John? How does mmap'ing /dev/zero work? > It was hacked in, as it has not previously existed in BSD. (MAP_ANON is the canonically correct way in BSD.) Does POSIX require /dev/zero? John From owner-freebsd-hackers Tue Dec 10 13:09:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA00919 for hackers-outgoing; Tue, 10 Dec 1996 13:09:23 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA00914 for ; Tue, 10 Dec 1996 13:09:20 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id QAA00660; Tue, 10 Dec 1996 16:09:06 -0500 (EST) From: John Dyson Message-Id: <199612102109.QAA00660@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 10 Dec 1996 16:09:06 -0500 (EST) Cc: kelly@fsl.noaa.gov, erich@lodgenet.com, scrappy@hub.org, hackers@freebsd.org In-Reply-To: <199612102020.OAA17243@jake.lodgenet.com> from "Eric L. Hernes" at Dec 10, 96 02:20:37 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > correct me if I'm wrong here, but doesn't MFS allocate backing store > in swap, so it could be paged out via physical I/O too. In either case > the physical IO appears async -- the physio won't happen until > the system needs ram, or the pages are inactive. If you've got enough > ram, the mmap'ed file won't be flushed out no matter what the underlying > FS is. Or do I just have too much faith in the VM system? ;-) > It is flushed on msync paged out when memory gets scarce. I think that the update process also syncs the mmaped regions (with vnode backing.) John From owner-freebsd-hackers Tue Dec 10 13:17:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01507 for hackers-outgoing; Tue, 10 Dec 1996 13:17:06 -0800 (PST) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA01497 for ; Tue, 10 Dec 1996 13:17:03 -0800 (PST) Received: (from tony@localhost) by nlanr.net (8.7.3/8.7.3) id NAA22696 for hackers@FreeBSD.ORG; Tue, 10 Dec 1996 13:17:02 -0800 (PST) From: Tony Sterrett Message-Id: <199612102117.NAA22696@nlanr.net> Subject: Driver installation To: hackers@FreeBSD.ORG Date: Tue, 10 Dec 1996 13:17:02 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is reposted with a subject Hello everybody I am trying to install a test driver I wrote. The driver is simple it just returns a 0 when opened. My test code only openeds the driver. I performed all the steps in the FreeBSD tutorial on installing driver and my kernel recompiles clean. However when I run I get a strange error: fd = -1 tst: Unknown error: -266382256 Details follow: The Test code: main() { int fd; fd = open("/dev/tst", O_RDONLY); if (fd < 0) { printf ("fd = %d \n",fd); perror("tst"); } } and the driver code is : tstopen(dev_t dev, int flag, int type, struct proc *p) { return (1); } and here is a log of my install steps: in /usr/src/sys/i386/conf/files.i386 - /local/src/tst.c optional tst device-driver in usr/src/sys/i386/i386/conf.c #include "tst.h" #if NTST > 0 d_open_t tstopen; d_close_t tstclose; d_rdwr_t tstread; d_ioctl_t tstioctl; #else #define tstopen nxopen #define tstclose nxclose #define tstread nxread #define tstioctl nxioctl #endif and { tstopen, tstclose, tstread, nowrite, /*76*/ tstioctl, nostop, nullreset, nodevtotty,/*test */ noselect, nommap, NULL}, for the struct cdevsw cdevsw[] value. in GENERIC the config file pseudo-device tst and I mknod c 76 0 76 is the cdevsw element Any ideas. Thanks in advance. Tony From owner-freebsd-hackers Tue Dec 10 13:24:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02105 for hackers-outgoing; Tue, 10 Dec 1996 13:24:01 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA02070 for ; Tue, 10 Dec 1996 13:23:56 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id WAA25618 for ; Tue, 10 Dec 1996 22:23:27 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vXZe2-0001zWC; Tue, 10 Dec 96 22:23 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA197322970; Tue, 10 Dec 1996 22:22:50 +0100 From: "Hr.Ladavac" Message-Id: <199612102122.AA197322970@ws2301.gud.siemens.co.at> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 10 Dec 1996 22:22:50 +0100 (MEZ) Cc: kelly@fsl.noaa.gov, erich@lodgenet.com, scrappy@hub.org, hackers@freebsd.org In-Reply-To: <199612102020.OAA17243@jake.lodgenet.com> from "Eric L. Hernes" at Dec 10, 96 02:20:37 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from Eric L. Hernes contained: > Sean Kelly writes: > >Eric L. Hernes wrote: > > > >> One way, is to open a (previously agreed upon) named file that > >> will be used to share data, ftruncate() it to the size you want, > >> then mmap() it. Other processes can open and mmap() this same file > >> to get at the data. > > > >But bear in mind where the file is located. If it's on a UFS, then your > >system will have to do physical I/O to update the file on disk as > >processes mmap'ing it make updates. That's why it's often better to > >locate mmap'd files used for IPC on an MFS filesystem. > > > > correct me if I'm wrong here, but doesn't MFS allocate backing store > in swap, so it could be paged out via physical I/O too. In either case > the physical IO appears async -- the physio won't happen until > the system needs ram, or the pages are inactive. If you've got enough > ram, the mmap'ed file won't be flushed out no matter what the underlying > FS is. Or do I just have too much faith in the VM system? ;-) This should be irrelevant, as mmapped files should not get written to until msync, or perhaps pageout (I don't know what POSIX draft says about it). AFAIK, they need to be updated on close, though. I don't know what should be the right thing for files mapped as MAP_PRIVATE. /Marino From owner-freebsd-hackers Tue Dec 10 13:26:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA02293 for hackers-outgoing; Tue, 10 Dec 1996 13:26:03 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA02280 for ; Tue, 10 Dec 1996 13:25:56 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id PAA03537; Tue, 10 Dec 1996 15:25:10 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma003527; Tue Dec 10 15:24:43 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id PAA32524; Tue, 10 Dec 1996 15:24:57 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id PAA17784; Tue, 10 Dec 1996 15:25:16 -0600 (CST) Message-Id: <199612102125.PAA17784@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Marc G. Fournier" cc: "Eric L. Hernes" , hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Tue, 10 Dec 1996 15:29:54 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Dec 1996 15:25:15 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" writes: > Okay...this makes a bit of sense (this is new to me, its got to >click into place first to make perfect sense *sigh*)... > > So, if I where to be getting a frame of data from a remote end using >sockets, I'd want to do something like: > > get size of frame > open named file > ftruncate() named file to size of frame > mmap named file > write frame to mmap'd region > > > Does that make sense? > > Now, "child" processes accessing that MMAP'd area...Terry (I believe?) Again it depends on the application... If you've got a parent that gets data, and a child that processes it, you can `share' memory with just a fork and no exec. The instant after the fork, both process are sharing all of the memory, except for one page that has the fork return value, and the proc/user structures. The problem here is that the neither process can share modifications, they can only read it. Any modifications by one process will not be seen by the other (copy on write). To get around this, you can mmap an anonymous region that is *not* associated with a file at all (with MAP_ANON and -1 for the file descriptor), and you can arrange to have the mapping preserved across exec (with MAP_INHERIT). For this example, mmap is like an extended malloc: someptr=mmap(0, sizeof_frame, PROT_READ|PROT_WRITE, MAP_ANON|MAP_INHERIT|MAP_SHARED, -1, 0); read(socket, someptr, sizeof_frame); if (pid=fork()) { ...parent stuff... } else { ... exec someother prog that will know what to do with the data that is at someptr, which is still a valid address ... } you can even ask mmap() to use absolute address for the mapping, such that your well known filenames are now well known addresses, providing that they don't conflict with other regions of text/data/stack/bss. Someone, Ron Minnich (?) posted a set of library routines that provided a malloc using mmap instead of brk/sbrk, they should be in the archives if they're still around. >mentioned passing the file descriptor through a socket from the parent to >the child, which, to me, sounds okay if you have few children reading the >mmap()'d region...but what I'm working on is going to require 1000's of >child processes reading that mmap()'d region, and having 1 socket open for >each child doesn't sound very efficient. > The correct answer for everything is `it depends' ;-) If you can arrange for the parent to open the file before fork'ing, the children will inherit it, but if you can do that, you can also mmap with MAP_SHARED before forking and the child will automatically get the shared memory with no added effort. *But* if you have a child that needs access to a memory segment that the parent doesn't allocate until after the fork, you'll need something like Terry's fd passing trick, or the well known file trick in order to get the memory. > You mention a named file in your example, so each frame could be >called '001', '002'...'999', with the child processes accessing them sequentially, as they exist...but at that point, I may as well just write >the date to 001, and have the child process open, read, close... > In theory yes, but mmap is much faster than open/read/close, for one reason, there's fewer system calls. For another, the work of mmap is done through the VM system, which may or may not read the information from disk, although in theory the buffer cache should prevent the read() from going to disk too. > I think what I'm still missing is that the way mmap() is being >described is that it requires a file to work off of, and all that the >benefit is is that each child can share the data from the same memory >region...what I'm *trying* to accomplish is a completely "in memory" >solution, without using something like MFS to get off of the physical >device. See above. In BSD, and in Unix in general, you've always got the disk involved, whether implicitly as backing store for malloc/mmap or explicitly as in open/read/write/close. If you buy that, then even though mmap may seem like it uses a file, it doesn't anymore than any other memory operation. > >Marc G. Fournier scrappy@hub.org >Systems Administrator @ hub.org scrappy@freebsd.org > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Tue Dec 10 13:36:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03044 for hackers-outgoing; Tue, 10 Dec 1996 13:36:31 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA03039 for ; Tue, 10 Dec 1996 13:36:28 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04855; Tue, 10 Dec 1996 14:14:44 -0700 From: Terry Lambert Message-Id: <199612102114.OAA04855@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: scrappy@hub.org (Marc G. Fournier) Date: Tue, 10 Dec 1996 14:14:43 -0700 (MST) Cc: erich@lodgenet.com, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Dec 10, 96 03:29:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Now, "child" processes accessing that MMAP'd area...Terry (I believe?) > mentioned passing the file descriptor through a socket from the parent to > the child, which, to me, sounds okay if you have few children reading the > mmap()'d region...but what I'm working on is going to require 1000's of > child processes reading that mmap()'d region, and having 1 socket open for > each child doesn't sound very efficient. If it's a child process, just unmark "close on exec" with fcntl() and the child will have the fd available anyway. > You mention a named file in your example, so each frame could be > called '001', '002'...'999', with the child processes accessing them > sequentially, as they exist...but at that point, I may as well just write > the date to 001, and have the child process open, read, close... Better to have a file 999 * sizeof(frame) in length and map it once. > I think what I'm still missing is that the way mmap() is being > described is that it requires a file to work off of, and all that the > benefit is is that each child can share the data from the same memory > region...what I'm *trying* to accomplish is a completely "in memory" > solution, without using something like MFS to get off of the physical > device. > > I know that I'm currently missing something that is totally > obvious to those that have a better understanding of mmap/shm...thanks > for the patience... All a file is is a FS name space name for a memory region. The difference betweem shm/mmap mappings is that, in the limit, the shm mappings use the swap area for swap store ("swap pager") and the mmap mappings use the file space for swap store ("vnode pager"). Because of the VM/cache unification, there is no real difference between one or the other (except you have to preallocate swap as swap store, but you can dynamically allocate and deallocate file space as swap store). Practically, the shm stuff is mapped in KVM space and the mmap stuff is not. This is an implemenation detail (it's worse to implement address space mappings in the KVM space because it's already so limited and has paging restrictions because of the processor protect bits -- but it's possible and likely for this to fixed in a future rev of FreeBSD). Bottom line: using mmap keeps you from bumping up against compile time limits. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 13:38:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03207 for hackers-outgoing; Tue, 10 Dec 1996 13:38:22 -0800 (PST) Received: from eterna.com.au (mhri-10.mhri.edu.au [203.3.164.25]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA03192 for ; Tue, 10 Dec 1996 13:38:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by eterna.com.au (8.8.4/8.8.3) with SMTP id IAA23198; Wed, 11 Dec 1996 08:35:45 +1100 (EST) Message-Id: <199612102135.IAA23198@eterna.com.au> X-Authentication-Warning: splode.eterna.com.au: localhost [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: thorpej@nas.nasa.gov, jb@cimlogic.com.au, hackers@freebsd.org, tech-kern@netbsd.org, jonathan@dsg.stanford.edu (Jonathan Stone) From: matthew green Subject: Re: poll(2) In-reply-to: Your message of "Tue, 10 Dec 1996 11:20:55 PDT." <199612101820.LAA04523@phaeton.artisoft.com> Date: Wed, 11 Dec 1996 08:35:18 +1100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If we did this _now_ we could, perhaps, reuse the existing syscall > number, since AFAIK poll(2) has never been in an official NetBSD release. Yes. The only conflict is call gate for ABI with some other OS that does poll with which you want binary compatability. Solaris might be one example. It really depends on whether execution classes imply system call interfaces, or not (they should, meaning no conflict). netbsd uses separate a system call table for each emulation (what you call an `execution class'). From owner-freebsd-hackers Tue Dec 10 13:40:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03429 for hackers-outgoing; Tue, 10 Dec 1996 13:40:52 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA03422; Tue, 10 Dec 1996 13:40:45 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA04884; Tue, 10 Dec 1996 14:19:42 -0700 From: Terry Lambert Message-Id: <199612102119.OAA04884@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: dyson@freebsd.org Date: Tue, 10 Dec 1996 14:19:42 -0700 (MST) Cc: terry@lambert.org, scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612102033.PAA00573@dyson.iquest.net> from "John Dyson" at Dec 10, 96 03:33:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > John? How does mmap'ing /dev/zero work? > > It was hacked in, as it has not previously existed in BSD. (MAP_ANON > is the canonically correct way in BSD.) Does POSIX require /dev/zero? No... I don't think so, anyway. It's a SystemV'ism; but then again, POSIX is mostly a codification of SystemV semantics, so it might. I think it's outside the name space, though, like truncating files to be larger. The reason I mentioned it was that the fd is usable as a key to get the same area mapped into multiple processes without them needing to be parent/child, with the mapping preeestablished in the parent. I'm not clear on how I get several processes using the same region in the MAP_ANON case... is it even possible? The man page says a non -1 fd "is used for naming"... how does that work? Is it an index, or is it just an ID? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 13:42:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA03613 for hackers-outgoing; Tue, 10 Dec 1996 13:42:42 -0800 (PST) Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA03607 for ; Tue, 10 Dec 1996 13:42:39 -0800 (PST) Received: (from uucp@localhost) by smtp-gw01.ny.us.ibm.net (8.6.9/8.6.9) id VAA131193; Tue, 10 Dec 1996 21:42:35 GMT Message-Id: <199612102142.VAA131193@smtp-gw01.ny.us.ibm.net> Received: from slip166-72-229-141.va.us.ibm.net(166.72.229.141) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr) id smaVjEGrx; Tue Dec 10 21:42:26 1996 Reply-To: From: "Steve Sims" To: "Mark Tinguely" , Subject: Re: PPP with network address translation Date: Tue, 10 Dec 1996 16:42:12 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There's special case handling in the (new) alias* code for FTP. It simply works, Look, ma! No proxies. ...sjs... ---------- > From: Mark Tinguely > To: freebsd-hackers@FreeBSD.ORG > Subject: Re: PPP with network address translation > Date: Tuesday, December 10, 1996 2:25 PM > > nate says: > > > And, it's not really NAT, although it acts alot like it. (I > > think Charles had code to toggle the functionality on/off in the > > ppp.conf file as well). > > what does it do with applications like ftp? NAT in IP Filter requires > a ftp proxie such as those found in FWTK. > > --mark. From owner-freebsd-hackers Tue Dec 10 13:54:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA04391 for hackers-outgoing; Tue, 10 Dec 1996 13:54:14 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA04377; Tue, 10 Dec 1996 13:53:56 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id QAA00743; Tue, 10 Dec 1996 16:53:07 -0500 (EST) From: John Dyson Message-Id: <199612102153.QAA00743@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: terry@lambert.org (Terry Lambert) Date: Tue, 10 Dec 1996 16:53:07 -0500 (EST) Cc: dyson@freebsd.org, terry@lambert.org, scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612102119.OAA04884@phaeton.artisoft.com> from "Terry Lambert" at Dec 10, 96 02:19:42 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm not clear on how I get several processes using the same region > in the MAP_ANON case... is it even possible? The man page says a > non -1 fd "is used for naming"... how does that work? Is it an index, > or is it just an ID? > I am not clear on what it is supposed to do either. What would the protection attributes of such an entity be? At least SYSVSHM defines them. John From owner-freebsd-hackers Tue Dec 10 14:01:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05373 for hackers-outgoing; Tue, 10 Dec 1996 14:01:40 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA05365 for ; Tue, 10 Dec 1996 14:01:26 -0800 (PST) Received: (from mgessner@localhost) by phoenix.aristar.com (8.6.12/8.6.12) id RAA00245 for hackers@freebsd.org; Tue, 10 Dec 1996 17:03:49 -0500 Message-Id: <199612102203.RAA00245@phoenix.aristar.com> Subject: Out of swap space -- now what??? To: hackers@freebsd.org (FreeBSD Hackers) Date: Tue, 10 Dec 1996 17:03:48 -0500 (EST) From: Matthew Gessner Organization: Aristar Software Development, Inc. Reply-To: mgessner@aristar.com X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, all, I keep getting the messages "Killed" and "Out of swap space" on my 2.1.5 machine. What can I do to increase the size of my swap space? I use heavy memory programs like Netscape, so maybe that's part of it. What else can I do?? TIA, Matt From owner-freebsd-hackers Tue Dec 10 14:05:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA05690 for hackers-outgoing; Tue, 10 Dec 1996 14:05:45 -0800 (PST) Received: from fps.biblos.unal.edu.co ([168.176.37.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA05659; Tue, 10 Dec 1996 14:05:25 -0800 (PST) From: pgiffuni@fps.biblos.unal.edu.co Received: from localhost by fps.biblos.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA03404; Tue, 10 Dec 1996 17:11:12 -0500 Date: Tue, 10 Dec 1996 17:11:12 -0500 (EST) To: freebsd-fs@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Interest in other Filesystems ? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have a bit of information about FAT with long names, HPFS (they can be mounted by NT and OS2) and about sysv-fs (you may already have that one). I sent the information I had to the maintainer of this url: http://www.teleport.com/~sabre It should be available there soon, but if someone is interested, drop me a line. Pedro. pgiffuni@fps.biblos.unal.edu.co From owner-freebsd-hackers Tue Dec 10 14:28:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07177 for hackers-outgoing; Tue, 10 Dec 1996 14:28:41 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07172; Tue, 10 Dec 1996 14:28:32 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA05053; Tue, 10 Dec 1996 15:07:22 -0700 From: Terry Lambert Message-Id: <199612102207.PAA05053@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: dyson@freebsd.org Date: Tue, 10 Dec 1996 15:07:22 -0700 (MST) Cc: terry@lambert.org, scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612102153.QAA00743@dyson.iquest.net> from "John Dyson" at Dec 10, 96 04:53:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm not clear on how I get several processes using the same region > > in the MAP_ANON case... is it even possible? The man page says a > > non -1 fd "is used for naming"... how does that work? Is it an index, > > or is it just an ID? > > I am not clear on what it is supposed to do either. What would the > protection attributes of such an entity be? At least SYSVSHM defines > them. Maybe: P1: fd = open key file mmap( ... fd ... MAP_ANON ... yada yada ...) P2: fd = open key file mmap( ... fd ... MAP_ANON ... yada yada ...) So the key file would be used to create a unique identifier. In this case, I would expect the protection attributes to match the key file. NOTE: Since the MAP_ANON is used, the key file is *NOT* the backing store for the region; however, since the is generated from the key file (dev_t and inode_t?) and uniquified that way, I don't think you could have both an anonymous and a non-anonymaous mapping for the same file... ie: you can't map a key file if it is being used as a key for an anon region, since the mapping will return the first mapping... the MAP_ANON... and the second mapping would fail. This may be scary at this point, since you *could* have both in different processes, *IF* the VM and cache were not unified, but not otherwise. OR you could take MAP_ANON as part of the key generation and end up with a structure that pointed to the anon vnode that was not the fd vnode, but was in the list of key indices. This would imply that you would need to indirect the key references (they are currently direct, it looks like). My hunch is that using and fd as a key would make that file the backing store; at the very least, you would be in danger, since you would not get protection if you used the fd index instead of the FS object (it wouldn't be very portable between processes otherwise, either). In other words, the cache unification would now cause some wierd behaviour about whose buffer is written on a page write fault from user space. I guess we could quit postulating and write test code... NAW! 8-) 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 14:36:34 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA07611 for hackers-outgoing; Tue, 10 Dec 1996 14:36:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA07604 for ; Tue, 10 Dec 1996 14:36:31 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA05068; Tue, 10 Dec 1996 15:12:00 -0700 From: Terry Lambert Message-Id: <199612102212.PAA05068@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Tue, 10 Dec 1996 15:11:59 -0700 (MST) Cc: scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612102125.PAA17784@jake.lodgenet.com> from "Eric L. Hernes" at Dec 10, 96 03:25:15 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > *But* if you have a child that > needs access to a memory segment that the parent doesn't allocate until > after the fork, you'll need something like Terry's fd passing trick, or > the well known file trick in order to get the memory. I was worried about the "nothing to inherit case", where one process accessing the segment wasn't in the same process group or hierarchically related in any way to the process that created the segment. > In theory yes, but mmap is much faster than open/read/close, for one > reason, there's fewer system calls. For another, the work of mmap > is done through the VM system, which may or may not read the information > from disk, although in theory the buffer cache should prevent the read() > from going to disk too. Also a socket write of an mmap'ed space avoids the bmap() translation on systems without a unified VM/cache. Since the mapping already exists, the translation can be done statically... the kernel space address and user space address don't need the checking. We used this on SVR4 all the time to avoid lots of copies for user space servers for net clients (http, NetWare, and AppleTalk). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Dec 10 15:39:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11889 for hackers-outgoing; Tue, 10 Dec 1996 15:39:21 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA11875 for ; Tue, 10 Dec 1996 15:39:19 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2) with ESMTP id RAA25528 for ; Tue, 10 Dec 1996 17:39:15 -0600 (CST) Received: from Jupiter.Mcs.Net (root@Jupiter.mcs.net [192.160.127.88]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id RAA12769; Tue, 10 Dec 1996 17:39:06 -0600 (CST) Received: (from jonas@localhost) by Jupiter.Mcs.Net (8.8.2/8.8.2) id RAA04997; Tue, 10 Dec 1996 17:32:27 -0600 (CST) From: Lars Jonas Olsson Message-Id: <199612102332.RAA04997@Jupiter.Mcs.Net> Subject: dga and page fault in kernel mode To: hackers@freebsd.org Date: Tue, 10 Dec 1996 17:32:27 -0600 (CST) Cc: jonas@mcs.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to get a DGA based system to run with current FreeBSD and X11. The FreeBSD is current sup'ed today. The X11 is XFree86 3.2 running on #9 Motion 771. Both my program and the dga program (/usr/X11R6/bin/dga) make FreeBSD panic during the XF86DGADirectVideo(display, screen, 0) call to go from DGA mode to normal X mode. Using COMCONSOLE I get the following: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf3488ffd fault code = supervisor write, page not present instruction pointer = 0x8:0xf01b08f3 stack pointer = 0x10:0xefbffed8 frame pointer = 0x10:0xefbffef4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 203 (dga) interrupt mask = panic: page fault syncing disks... 40 40 37 33 14 2 done Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cu: Got hangup signal Any ideas what to do? What's the next step in debugging? My config file has the following. The only odd thing is the large amount of shared memory. The machine is a Texas Microsystems PV5000HX SBC with 128 MB EDO parity RAM (Samsung KMM5368105BKG-6), 512 kB cache, Triton II. Cards are Boca IO650 (2 serial ports), Matrox Meteor RGB, NE2000 clone, Number 9 FX Motion 771. Using 1GB Quantum IDE, no SCSI devices. machine "i386" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 10 options COMCONSOLE #prefer serial console to video console options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SHMMAXPGS=8192 options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 # A single entry for any of these controllers (ncr, ahb, ahc) is sufficient # for any number of installed devices. controller ahb0 controller ahc0 options "AHC_FORCE_PIO" # Some motherboards choke on MemI/O, # so use PIO in the ahc driver in the # generic kernel. controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr options METEOR_ALLOC_PAGES=450 device meteor0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing From owner-freebsd-hackers Tue Dec 10 15:52:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA12779 for hackers-outgoing; Tue, 10 Dec 1996 15:52:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA12747 for ; Tue, 10 Dec 1996 15:51:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA19061; Wed, 11 Dec 1996 00:50:41 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA04923; Wed, 11 Dec 1996 00:50:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA01765; Wed, 11 Dec 1996 00:39:32 +0100 (MET) From: J Wunsch Message-Id: <199612102339.AAA01765@uriah.heep.sax.de> Subject: Re: Driver installation To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 11 Dec 1996 00:39:32 +0100 (MET) Cc: tony@nlanr.net (Tony Sterrett) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612102117.NAA22696@nlanr.net> from Tony Sterrett at "Dec 10, 96 01:17:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tony Sterrett wrote: > tstopen(dev_t dev, int flag, int type, struct proc *p) > { > return (1); > > } Return value 0 is success, everything else is interpreted as an errno. > in usr/src/sys/i386/i386/conf.c Uh, which version of FreeBSD are you using? This file has long since gone in the development system. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Dec 10 15:57:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA13332 for hackers-outgoing; Tue, 10 Dec 1996 15:57:30 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA13311 for ; Tue, 10 Dec 1996 15:57:23 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA19046; Wed, 11 Dec 1996 00:50:37 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA04914; Wed, 11 Dec 1996 00:50:37 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA01785; Wed, 11 Dec 1996 00:41:22 +0100 (MET) From: J Wunsch Message-Id: <199612102341.AAA01785@uriah.heep.sax.de> Subject: Re: Dump "short read error" on a Micropolis disk To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 11 Dec 1996 00:41:21 +0100 (MET) Cc: bob@luke.pmr.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612101644.KAA29064@luke.pmr.com> from Bob Willcox at "Dec 10, 96 10:44:27 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bob Willcox wrote: > DUMP: short read error from /dev/rsd6a: [block -670977536]: count=3072, got=0 > DUMP: short read error from /dev/rsd6a: [sector -670977536]: count=512, got=0 > DUMP: short read error from /dev/rsd6a: [sector -670977535]: count=512, got=0 > ahc2: target 0 Tagged Queuing Device > (ahc2:0:0): "MICROP 2217-15MZ1001901 HZ30" type 0 fixed SCSI 2 > sd6(ahc2:0:0): Direct-Access 1685MB (3450902 512 byte sectors) Are you sure the filesystem is okay? The block numbers are way out of range, which should normally only happen if the filesystem is clobbered. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Dec 10 16:14:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15021 for hackers-outgoing; Tue, 10 Dec 1996 16:14:52 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA15015 for ; Tue, 10 Dec 1996 16:14:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA19053; Wed, 11 Dec 1996 00:50:39 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA04915; Wed, 11 Dec 1996 00:50:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA01672; Wed, 11 Dec 1996 00:30:44 +0100 (MET) From: J Wunsch Message-Id: <199612102330.AAA01672@uriah.heep.sax.de> Subject: Re: Out of swap space -- now what??? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 11 Dec 1996 00:30:44 +0100 (MET) Cc: mgessner@aristar.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612102203.RAA00245@phoenix.aristar.com> from Matthew Gessner at "Dec 10, 96 05:03:48 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Matthew Gessner wrote: > I keep getting the messages "Killed" and "Out of swap space" on my 2.1.5 > machine. What can I do to increase the size of my swap space? Well, add more of it! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Dec 10 16:21:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15412 for hackers-outgoing; Tue, 10 Dec 1996 16:21:06 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA15362 for ; Tue, 10 Dec 1996 16:20:51 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id LAA12445; Wed, 11 Dec 1996 11:24:26 +1100 (EST) Date: Wed, 11 Dec 1996 11:24:26 +1100 (EST) From: "Daniel O'Callaghan" To: Steve Sims cc: Mark Tinguely , freebsd-hackers@FreeBSD.ORG Subject: Re: PPP with network address translation In-Reply-To: <199612102142.VAA131193@smtp-gw01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Next question with the PPP Nat, is: who is going to hack this to work with divert(4) sockets, so we can have a NAT box on ethernet, without the need for a PPP link? Danny From owner-freebsd-hackers Tue Dec 10 17:06:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA18130 for hackers-outgoing; Tue, 10 Dec 1996 17:06:35 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA18107 for ; Tue, 10 Dec 1996 17:06:32 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.7.3) id SAA03678; Tue, 10 Dec 1996 18:55:47 -0600 (CST) From: Bob Willcox Message-Id: <199612110055.SAA03678@luke.pmr.com> Subject: Re: Dump "short read error" on a Micropolis disk In-Reply-To: <199612102341.AAA01785@uriah.heep.sax.de> from J Wunsch at "Dec 11, 96 00:41:21 am" To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 10 Dec 1996 18:55:47 -0600 (CST) Cc: freebsd-hackers@freebsd.org Reply-To: bob@luke.pmr.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > As Bob Willcox wrote: > > > DUMP: short read error from /dev/rsd6a: [block -670977536]: count=3072, got=0 > > DUMP: short read error from /dev/rsd6a: [sector -670977536]: count=512, got=0 > > DUMP: short read error from /dev/rsd6a: [sector -670977535]: count=512, got=0 > > > ahc2: target 0 Tagged Queuing Device > > (ahc2:0:0): "MICROP 2217-15MZ1001901 HZ30" type 0 fixed SCSI 2 > > sd6(ahc2:0:0): Direct-Access 1685MB (3450902 512 byte sectors) > > Are you sure the filesystem is okay? The block numbers are way out of > range, which should normally only happen if the filesystem is > clobbered. Well, it fsck's just fine. It was newly newfs'd and loaded with data and I see no other errors. It just seems that dump does not like any filesystem that I try to build on that disk. (I've had a couple of others in a previous layout before I fdisk'd and relabeled it today...I was hoping that that would fix it :-() Thanks, -- Bob Willcox politics, n: bob@luke.pmr.com A strife of interests masquerading as a contest of Austin, TX principles. The conduct of public affairs for private advantage. -- Ambrose Bierce From owner-freebsd-hackers Tue Dec 10 18:42:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA29607 for hackers-outgoing; Tue, 10 Dec 1996 18:42:22 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA29598 for ; Tue, 10 Dec 1996 18:42:20 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Tue, 10 Dec 1996 19:41:46 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Tue, 10 Dec 1996 19:41:22 -0700 From: Darren Davis To: hackers@freebsd.org Subject: Marimba for FreeBSD... Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I went out to Marimba (http://www.marimba.com) and got their unsupported version of Castanet tuner for FreeBSD. It also has version 1.0.2 of the JDK. I was able to get the javac they ported to work, but get the following problems when I try to run the java emulator (I also get this same problem when I try to run the tuner). I have tried this with both stable and current. Has anybody got this stuff to work? Thanks, Darren R. Davis ======= SIGSEGV 11* segmentation violation sig 11, code 12 or 0xc, sc 0xefbfb964, addr 0x93d9fff stackbase=0xefbfd828, stackpointer=0xefbfd674 Full thread dump: "Finalizer thread" (TID:0x85623b0, sys_thread_t:0x9366f28) prio=1 "Async Garbage Collector" (TID:0x8562368, sys_thread_t:0x9345f28) prio=1 "Idle thread" (TID:0x8562320, sys_thread_t:0x9324f28) prio=0 "clock handler" (TID:0x85621f8, sys_thread_t:0x9303f28) prio=11 "main" (TID:0x85620a0, sys_thread_t:0x168300) prio=5 *current thread* sun.awt.motif.MToolkit.(MToolkit.java:49) java.awt.Toolkit.getDefaultToolkit(Toolkit.java:199) sun.applet.AppletCopyright.(AppletCopyright.java:41) sun.applet.AppletViewer.mainInit(AppletViewer.java:869) sun.applet.AppletViewer.main(AppletViewer.java:878) Monitor Cache Dump: sun.awt.motif.MToolkit@8563AB8/859D2D0 (key=0x8563ab8): monitor owner: "main" java.lang.Class@85639B8/1B0900 (key=0x85639b8): monitor owner: "main" Registered Monitor Dump: Finalize me queue lock: unowned Thread queue lock: unowned Class lock: unowned Java stack lock: unowned Code rewrite lock: unowned Heap lock: unowned Has finalization queue lock: unowned Monitor IO lock: unowned Child death monitor: unowned Event monitor: unowned I/O monitor: unowned Alarm monitor: unowned Waiting to be notified: "clock handler" Monitor cache lock: unowned Monitor registry: monitor owner: "main" Thread Alarm Q: Abort trap (core dumped) From owner-freebsd-hackers Tue Dec 10 19:33:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA04485 for hackers-outgoing; Tue, 10 Dec 1996 19:33:07 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA04479 for ; Tue, 10 Dec 1996 19:33:03 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id WAA01277; Tue, 10 Dec 1996 22:31:27 -0500 (EST) From: "John S. Dyson" Message-Id: <199612110331.WAA01277@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: terry@lambert.org (Terry Lambert) Date: Tue, 10 Dec 1996 22:31:27 -0500 (EST) Cc: scrappy@hub.org, erich@lodgenet.com, hackers@freebsd.org In-Reply-To: <199612102114.OAA04855@phaeton.artisoft.com> from "Terry Lambert" at Dec 10, 96 02:14:43 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Practically, the shm stuff is mapped in KVM space and the mmap stuff > is not. > I fixed that brokenness in 2.2 and 3.0 a long time ago. > > This is an implemenation detail (it's worse to implement > address space mappings in the KVM space because it's already so > limited and has paging restrictions because of the processor protect > bits -- but it's possible and likely for this to fixed in a future > rev of FreeBSD). > It is fixed :-). We are very very KVA space conservative (or getting more so with larger and larger systems looming.) John From owner-freebsd-hackers Tue Dec 10 21:20:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA14695 for hackers-outgoing; Tue, 10 Dec 1996 21:20:40 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA14676 for ; Tue, 10 Dec 1996 21:20:36 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22981; Wed, 11 Dec 1996 00:20:05 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 11 Dec 1996 00:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id UAA17692; Tue, 10 Dec 1996 20:05:35 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id UAA01275; Tue, 10 Dec 1996 20:07:46 -0500 (EST) Date: Tue, 10 Dec 1996 20:07:46 -0500 (EST) From: Thomas David Rivers Message-Id: <199612110107.UAA01275@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!quickweb.com!mark Subject: Re: Daily panics (I'm back.) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Tue, 10 Dec 1996, Thomas David Rivers wrote: > > > > > Ok - > [SNIP] > > 3) Would it be better to suffer through this for now, > > and wait for a more stable 2.2 version to try out > > (presumably _before_ 2.2-RELEASE was sent out.) > > You can try out "2.2-ALPHA" - it's the precursor to the 2.2 release, which > is suppose to happen in early Jan. If you use CVSup, just add > "tag=RELENG_2_2" and you'll get the 2.2 Alpha. It's been quite solid for > me, although I haven't have as much time as I'd like to pound away at it > harder... > > Have fun, > -mark Thanks for the suggestion - but I run on a (basically) uucp site; my network connectivity is, shall we say, lacking... So, I don't get use CTM or CVSup. What I'm thinking of doing is ordering the latest 2.2-SNAP from Walnut Creek... but, it may be too old... Also, if 2.1.5 binaries run fine on a 2.2 kernel (what about ps, et. al?), I could just try the kernel... - Dave R. - From owner-freebsd-hackers Tue Dec 10 21:47:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA17233 for hackers-outgoing; Tue, 10 Dec 1996 21:47:55 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA17227 for ; Tue, 10 Dec 1996 21:47:52 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id VAA17462; Tue, 10 Dec 1996 21:44:13 -0800 (PST) Message-ID: <32AE4A07.167EB0E7@whistle.com> Date: Tue, 10 Dec 1996 21:43:35 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Daniel O'Callaghan" CC: Steve Sims , Mark Tinguely , freebsd-hackers@FreeBSD.ORG Subject: Re: PPP with network address translation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel O'Callaghan wrote: > > Next question with the PPP Nat, is: who is going to hack this to work > with divert(4) sockets, so we can have a NAT box on ethernet, without the > need for a PPP link? > > Danny that's what we do here.. (why we wrote divert sockets actually) but it;s inherrently kinked with the proprietary part of our system so we can't just give it away. (we'd like to however). but it really is a simple job. we're hoping someone just 'does it' as our hands are tied on this one.. sos BTW has a purely in-kernel version of NAT (or is it HAT?) ours is a process that works on packets that come up via the divert sockets. From owner-freebsd-hackers Tue Dec 10 21:57:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA18208 for hackers-outgoing; Tue, 10 Dec 1996 21:57:45 -0800 (PST) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA18203 for ; Tue, 10 Dec 1996 21:57:43 -0800 (PST) Received: from localhost (brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) with SMTP id WAA10611; Tue, 10 Dec 1996 22:57:57 -0700 (MST) Date: Tue, 10 Dec 1996 22:57:57 -0700 (MST) From: Brandon Gillespie To: Mark Taylor cc: hackers@freebsd.org Subject: RE: Help! Turning off DTR on a serial device In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 6 Dec 1996, Mark Taylor wrote: > On 18:25:06 Brandon Gillespie wrote: > >I'm writing some software to use the serial device in FreeBSD (and > >Unixware in the long run). I need to know if I can turn off DTR. The > >supplied software with this program is for DOS, and manages to turn off > >DTR from the software end--but I have never been able to figure out if I > >can do this from a unix perspective? Can I? help? > > > >-Brandon Gillespie > > There is an IOCTL for it. > Look in /usr/include/sys/ttycom.h for TIOCSDTR (set DTR) and TIOCCDTR (clear > DTR). > > The only problem youu will find with it is that the DTR is set when you change > your > baud rate. There is an 'if' statement in the baud changing code in the > kernel's sio > driver which checks if the baud is non-zero, then the DTR will be set. > > So, you can set your baud rate, turn off your DTR, but don't chang your baud > rate > again! It will turn ON the DTR (if the new baud rate is not zero). How portable is this? I'm developing the software in FreeBSD but it will be running on a Unixware server. Anybody familiar with unixware? -Brandon Gillespie From owner-freebsd-hackers Tue Dec 10 21:59:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA18305 for hackers-outgoing; Tue, 10 Dec 1996 21:59:46 -0800 (PST) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA18298 for ; Tue, 10 Dec 1996 21:59:41 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.2) with UUCP id GAA05502; Wed, 11 Dec 1996 06:59:31 +0100 (MET) Received: (from elrond@localhost) by phoe.netdev.net (8.7.5/8.7.3/phoe-1.0002) id EAA00601; Wed, 11 Dec 1996 04:09:33 +0100 (MET) Date: Wed, 11 Dec 1996 04:09:33 +0100 (MET) Message-Id: <199612110309.EAA00601@phoe.netdev.net> From: Bertrand Petit To: ettrich@informatik.uni-tuebingen.de, freebsd-hackers@freebsd.org Subject: LyX troubles report on FreeBSD Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Note: a copy of this mail was sent to the FreeBSD hackers mailing list, be sure to use a group reply] Hello, I've just compiled installed and tested LyX version 0.10.7 on a FreeBSD 2.2-960501-SNAP under a XFree86 3.12 X11 server with the help of teTeX 0.4. With this setup LyX runs fine for some time (variable) then in reply to a GUI interaction (moving main window, popping the styles list) it crashes the system. I don't know exactly what's appening because there is a hard reset: it looks like a kernel panic. Have you ever heard of similar reactions on other systems. I hope this will help you harden LyX that seems very interesting from the little the crashs allowed me to see. [Note: I just tweaked the sendmail.cf file, it should be ok but in case of bad From: header, use this adresse to reply: elrond@phoe.frmug.org]. From owner-freebsd-hackers Tue Dec 10 23:12:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA23132 for hackers-outgoing; Tue, 10 Dec 1996 23:12:09 -0800 (PST) Received: (from hsu@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA23125; Tue, 10 Dec 1996 23:12:04 -0800 (PST) Date: Tue, 10 Dec 1996 23:12:04 -0800 (PST) From: Jeffrey Hsu Message-Id: <199612110712.XAA23125@freefall.freebsd.org> To: DARREND@novell.com Subject: Re: Marimba for FreeBSD... Cc: hackers Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Did you set your LD_LIBRARY_PATH as described in the README? From owner-freebsd-hackers Tue Dec 10 23:37:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA24320 for hackers-outgoing; Tue, 10 Dec 1996 23:37:01 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA24314 for ; Tue, 10 Dec 1996 23:36:59 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id XAA06839 for ; Tue, 10 Dec 1996 23:37:19 -0800 (PST) Received: (qmail 8100 invoked by uid 110); 11 Dec 1996 07:36:26 -0000 Message-ID: <19961211073626.8099.qmail@suburbia.net> Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: from "Marc G. Fournier" at "Dec 10, 96 03:29:54 pm" To: scrappy@hub.org (Marc G. Fournier) Date: Wed, 11 Dec 1996 18:36:26 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Now, "child" processes accessing that MMAP'd area...Terry (I believe?) > mentioned passing the file descriptor through a socket from the parent to > the child, which, to me, sounds okay if you have few children reading the > mmap()'d region...but what I'm working on is going to require 1000's of > child processes reading that mmap()'d region, and having 1 socket open for > each child doesn't sound very efficient. Consider using rfork() (freebsd) and clone() (linux). If you want something more portable, or you (or your libraries) use static variables (and you can't easily change their mappings). Then I advise you to examine the solution I implemented in nntpcache: 1. parent maps file/anonymous region with MAP_SHARED 2. children fork off and automatically have this shared region in their memory space There are a few caveats. 1. growth of the mmaped region can only be made by the parent and is only reflected in newly born children. You can circumvent this by simply mapping very large regions initially (there is almost no overhead for unused pages, although many unix's will stupidly insist that map_size Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA25555 for hackers-outgoing; Wed, 11 Dec 1996 00:07:56 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA25543 for ; Wed, 11 Dec 1996 00:07:54 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0vXjhj-0008wVC; Wed, 11 Dec 96 00:07 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: PC CARD stuff To: hackers@freefall.freebsd.org Date: Wed, 11 Dec 1996 00:07:47 -0800 (PST) Cc: pst@shockwave.com In-Reply-To: <199612101408.GAA01396@freefall.freebsd.org> from "owner-hackers-digest@freefall.freebsd.org" at Dec 10, 96 06:08:07 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Paul Traina > Date: Tue, 10 Dec 1996 00:00:01 -0800 > Subject: Re: need help with a PC CARD NE2000 clone... > > I'm thinking of going out and getting one of the 3COM 3c589 cards > and a Megahertz 3811 cellular modem, but the combo is /not/ cheap. I got the 3com 3c589 to use in a Toshiba 115cs as a cheap portable net monitor. Lo, it won't go into promiscuous mode, so it's not a very useful net monitor. It also seems to have performance problems, but I haven't characterized them, so can't say if that's real or not. When I get back, I'll be looking for a card that is more suitable. For modem, I'm using a Motorola Montana ("named after the state with no speed limits") card right now; I got the one with the cable for my Motorola cell phone just in time for my trip to IETF (you've been trying to get your net working here, and I've been trying to get the modem working, with about the same luck :-) ). I'm using it under Windoze so I can get my mail, but via land line, as I don't want to experiment with the cellular link at $1/min roaming charges... pccard seems to want to put it at 2e8, and I only have sio0/1 configured in, so my next attempt will be to build the kernel with sio0-3 and see if that helps. Also, I notice that it's truncating the card identifier (damn, no !grep /etc/pccard here!, so no example till I get back home), though ktrace shows it's getting the whole thing. BTW, I'll probably be in rtfm and rps tomorrow; then I head back to Portland... perhaps we'll run into each other? -- Alan Batie ______ batie@agora.rdrop.com \ / Assimilate this! +1 503 452-0960 \ / --Worf, First Contact DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-hackers Wed Dec 11 01:00:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA27611 for hackers-outgoing; Wed, 11 Dec 1996 01:00:36 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA27357 for ; Wed, 11 Dec 1996 00:55:07 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA03686; Wed, 11 Dec 1996 09:51:11 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA10912; Wed, 11 Dec 1996 09:51:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA05056; Wed, 11 Dec 1996 09:34:40 +0100 (MET) From: J Wunsch Message-Id: <199612110834.JAA05056@uriah.heep.sax.de> Subject: Re: Daily panics (I'm back.) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 11 Dec 1996 09:34:40 +0100 (MET) Cc: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612110107.UAA01275@lakes.water.net> from Thomas David Rivers at "Dec 10, 96 08:07:46 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > Thanks for the suggestion - but I run on a (basically) uucp site; > my network connectivity is, shall we say, lacking... > > So, I don't get use CTM or CVSup. I still get all my CTM deltas via UUCP, either. It's probably less load than the -hackers list. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Dec 11 01:49:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA00118 for hackers-outgoing; Wed, 11 Dec 1996 01:49:13 -0800 (PST) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA00105; Wed, 11 Dec 1996 01:49:08 -0800 (PST) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.3/8.8.3) with UUCP id JAA03771; Wed, 11 Dec 1996 09:33:57 GMT Date: Wed, 11 Dec 1996 09:20:26 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 11 Dec 1996 09:20:26 GMT X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: postmaster@freebsd.org From: rb@gid.co.uk (Bob Bishop) Subject: Deja Vu Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, This morning I've been receiving repeats (in 3's) of old messages, via an unusual route; the following is typical: >Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by >isbalham.ist.co.uk (8.8.3/8.8.3) with SMTP id CAA02908 for ; >Wed, 11 Dec 1996 02:05:13 GMT >Received: by sovcom.kiae.su id AA16826 > (5.65.kiae-1 for rb@gid.co.uk); Wed, 11 Dec 1996 04:24:31 +0300 >Received: by sovcom.KIAE.su (UUMAIL/2.0); Wed, 11 Dec 96 04:24:31 +0300 >Received: by p5.f434.n5020.z2.ftn (Smail3.1.28.1 #8) > id m0vWuzm-0003oca; Mon, 9 Dec 96 03:59 EET >Received: from f434.n5020.z2.fidonet.org by p5.f434.n5020.z2.fidonet.org > with FTN (ifmail v.2.5) id AA27739; Mon, 09 Dec 96 03:59:00 +0200 >Received: (from uucp@localhost) by anka.frog.org (8.8.3/8.8.3) with UUCP >id FAA09359 for bsdlst@anka.da.mtelecom.ru; Sat, 7 Dec 1996 05:28:43 +0300 >(MSK) >Received: from ns.mtelecom.ru (ns.mtelecom.ru [194.226.115.1]) by >sev.mtelecom.ru (8.8.3/8.8.3) with ESMTP id EAA03055 for >; Sat, 7 Dec 1996 04:29:08 +0300 (MSK) >Received: from zit1.zit.th-darmstadt.de (zit1.zit.th-darmstadt.de >[130.83.63.1]) by ns.mtelecom.ru (8.8.3/8.8.3) with ESMTP id EAA24654 for >; Sat, 7 Dec 1996 04:28:20 +0300 (MSK) >Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.18]) >by zit1.zit.th-darmstadt.de (8.7.6/8.6.9) with ESMTP id CAA29390; Sat, 7 >Dec 1996 02:08:48 +0100 (MET) >Received: from localhost (daemon@localhost) > by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA21704; > Fri, 6 Dec 1996 17:03:40 -0800 (PST) >Received: (from root@localhost) > by freefall.freebsd.org (8.8.4/8.8.4) id RAA21693 > for hackers-outgoing; Fri, 6 Dec 1996 17:03:38 -0800 (PST) >Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) > by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA21684 > for ; Fri, 6 Dec 1996 17:03:36 -0800 (PST) >Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id >RAA24762; Fri, 6 Dec 1996 17:43:29 -0700 -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Wed Dec 11 02:01:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA00812 for hackers-outgoing; Wed, 11 Dec 1996 02:01:55 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA00795 for ; Wed, 11 Dec 1996 02:01:51 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id CAA15105 for ; Wed, 11 Dec 1996 02:01:25 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA03686; Wed, 11 Dec 1996 09:51:11 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA10912; Wed, 11 Dec 1996 09:51:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id JAA05056; Wed, 11 Dec 1996 09:34:40 +0100 (MET) From: J Wunsch Message-Id: <199612110834.JAA05056@uriah.heep.sax.de> Subject: Re: Daily panics (I'm back.) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 11 Dec 1996 09:34:40 +0100 (MET) Cc: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612110107.UAA01275@lakes.water.net> from Thomas David Rivers at "Dec 10, 96 08:07:46 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Thomas David Rivers wrote: > Thanks for the suggestion - but I run on a (basically) uucp site; > my network connectivity is, shall we say, lacking... > > So, I don't get use CTM or CVSup. I still get all my CTM deltas via UUCP, either. It's probably less load than the -hackers list. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Dec 11 02:15:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA01909 for hackers-outgoing; Wed, 11 Dec 1996 02:15:06 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA01903 for ; Wed, 11 Dec 1996 02:15:00 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id LAA00657 for ; Wed, 11 Dec 1996 11:15:47 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id LAA20003 for freebsd-hackers@freefall.cdrom.com; Wed, 11 Dec 1996 11:28:21 +0100 (MET) Date: Wed, 11 Dec 1996 11:28:21 +0100 (MET) From: Christoph Kukulies Message-Id: <199612111028.LAA20003@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: ccd - partitioning Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I still have no luck getting ccd working here with 2 SCSI disks and two controllers . I partitioned several times with various options. Presently the picture is like this: Disk name: sd0 FDISK Partition Editor DISK Geometry: 3067 cyls/64 heads/32 sectors Offset Size End Name PType Desc Subtype Flags 0 32 31 - 6 unused 0 32 6281184 6281215 sd0s1 3 freebsd 165 C> 6281216 640 6281855 - 6 unused 0 > The following commands are supported (in upper or lower case): A = Use Entire Disk B = Bad Block Scan C = Create Partition D = Delete Partition G = Set Drive Geometry S = Set Bootable U = Undo All Changes Q = Finish W = Write Changes Use F1 or ? to get more help, arrow keys to select. Dito for sd1. # /dev/rsd1c: type: SCSI disk: sd1s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 3066 sectors/unit: 6281184 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) # # /dev/rsd0c: type: SCSI disk: sd0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 3066 sectors/unit: 6281184 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) # # # /etc/ccd.conf # Configuration file for concatenated disk devices # # ccd ileave flags component devices ccd0 16 none /dev/sd0e /dev/sd1e # ccdconfig -C ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format ^^^^^^^^^^^^^^^^^ This remains the key problem ^^^^^^^^^^^^^^^^^ I tried with or without tabs, with linefeed at the end. No luck. I did this all with a 2.2-ALPHA install. The kernel being 3.0, hope the latter not being a problem. # fdisk sd0 ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 6281184 (3066 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 32/ head 63 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: # # fdisk sd1 ******* Working on device /dev/rsd1 ******* parameters extracted from in-core disklabel are: cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 6281184 (3066 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 32/ head 63 The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: # # dmesg Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Dec 8 16:23:36 MET 1996 kuku@bach.physik.rwth-aachen.de:/usr/src/sys/compile/DUKE Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100248720 Hz, i8254 clock: 1193437 Hz CPU: AMD Unknown (100.23-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x511 real memory = 33554432 (32768K bytes) avail memory = 30928896 (30204K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ncr0 rev 17 int a irq 11 on pci0:8 ncr0 waiting for scsi devices to settle (ncr0:0:0): "QUANTUM FIREBALL_TM3200S 300N" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 3067MB (6281856 512 byte sectors) ncr1 rev 17 int a irq 10 on pci0:11 ncr1 waiting for scsi devices to settle (ncr1:0:0): "QUANTUM FIREBALL_TM3200S 300N" type 0 fixed SCSI 2 sd1(ncr1:0:0): Direct-Access sd1(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 3067MB (6281856 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: MDA/hercules <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:bd:8a:16, type WD8003E (8 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wd0: 124MB (254592 sectors), 936 cyls, 16 heads, 17 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers # # ls -l /dev/*ccd* brw-r----- 1 root wheel 21, 0 Dec 9 01:02 /dev/ccd0a brw-r----- 1 root wheel 21, 1 Dec 9 01:02 /dev/ccd0b brw-r----- 1 root wheel 21, 2 Dec 9 01:02 /dev/ccd0c brw-r----- 1 root wheel 21, 3 Dec 9 01:02 /dev/ccd0d brw-r----- 1 root wheel 21, 4 Dec 9 01:02 /dev/ccd0e brw-r----- 1 root wheel 21, 5 Dec 9 01:02 /dev/ccd0f brw-r----- 1 root wheel 21, 6 Dec 9 01:02 /dev/ccd0g brw-r----- 1 root wheel 21, 7 Dec 9 01:02 /dev/ccd0h crw------- 1 root wheel 74, 0x20000000 Dec 11 04:47 /dev/rccd0.ctl crw-r----- 1 root wheel 74, 0 Dec 9 01:02 /dev/rccd0a crw-r----- 1 root wheel 74, 1 Dec 9 01:02 /dev/rccd0b crw-r----- 1 root wheel 74, 2 Dec 9 01:02 /dev/rccd0c crw-r----- 1 root wheel 74, 3 Dec 9 01:02 /dev/rccd0d crw-r----- 1 root wheel 74, 4 Dec 9 01:02 /dev/rccd0e crw-r----- 1 root wheel 74, 5 Dec 9 01:02 /dev/rccd0f crw-r----- 1 root wheel 74, 6 Dec 9 01:02 /dev/rccd0g crw-r----- 1 root wheel 74, 7 Dec 9 01:02 /dev/rccd0h # Is there something special to partitioning? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Wed Dec 11 02:26:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA02628 for hackers-outgoing; Wed, 11 Dec 1996 02:26:53 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA02615 for ; Wed, 11 Dec 1996 02:26:46 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.3/8.7.3) id LAA05791; Wed, 11 Dec 1996 11:28:43 +0100 (MET) Message-Id: <199612111028.LAA05791@ravenock.cybercity.dk> Subject: Re: PPP with network address translation In-Reply-To: <32AE4A07.167EB0E7@whistle.com> from Julian Elischer at "Dec 10, 96 09:43:35 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 11 Dec 1996 11:28:42 +0100 (MET) Cc: danny@panda.hilink.com.au, SimsS@IBM.Net, tinguely@plains.nodak.edu, freebsd-hackers@FreeBSD.ORG From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Julian Elischer who wrote: > Daniel O'Callaghan wrote: > > > > Next question with the PPP Nat, is: who is going to hack this to work > > with divert(4) sockets, so we can have a NAT box on ethernet, without the > > need for a PPP link? > > > > Danny > > that's what we do here.. > (why we wrote divert sockets actually) > but it;s inherrently kinked with the proprietary part of our system > so we can't just give it away. (we'd like to however). > but it really is a simple job. we're hoping someone just 'does it' > as our hands are tied on this one.. > > sos BTW has a purely in-kernel version of NAT (or is it HAT?) > ours is a process that works on packets that come up via the > divert sockets. HAT?? And yes I have a NAT implementation that runs entirely in kernel land, and it does all the footwork on ip, udp, tcp, ftp, irc, realaudio etc etc. It soon will support multible ip# to multible ip# and other fancy stuff. The problem is that the code is now proprietary as well, so I cannot release it either. However its not difficult to do as julian states, and I still think it should be in the kernel (or at least its needed in the apps where its used here). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Dec 11 03:05:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA03986 for hackers-outgoing; Wed, 11 Dec 1996 03:05:13 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA03981 for ; Wed, 11 Dec 1996 03:05:10 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id EAA14701 for hackers@freebsd.org; Wed, 11 Dec 1996 04:05:04 -0700 (MST) From: Ade Barkah Message-Id: <199612111105.EAA14701@hemi.com> Subject: cron's log files location To: hackers@freebsd.org Date: Wed, 11 Dec 1996 04:05:03 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm just wondering why cron's log files are in /var/cron instead of /var/log with everything else (besides "historical reason.") Any reason they can't be moved to /var/log ? Regards, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Wed Dec 11 07:07:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA14735 for hackers-outgoing; Wed, 11 Dec 1996 07:07:16 -0800 (PST) Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA14727 for ; Wed, 11 Dec 1996 07:07:09 -0800 (PST) Received: by atena.eurocontrol.fr; (5.65v3.2/1.3/10May95) id AA25035; Wed, 11 Dec 1996 16:07:00 +0100 Received: from caerdonn.eurocontrol.fr by eurocontrol.fr with ESMTP (1.37.109.16/16.2) id AA122876578; Wed, 11 Dec 1996 16:02:58 +0100 Received: (from roberto@localhost) by caerdonn.eurocontrol.fr (8.8.4/8.8.2/caerdonn-1.1) id QAA16495; Wed, 11 Dec 1996 16:02:58 +0100 (MET) Message-Id: Date: Wed, 11 Dec 1996 16:02:58 +0100 From: roberto@eurocontrol.fr (Ollivier Robert) To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers' list) Subject: Fwd: CVSup with SSH X-Mailer: Mutt 0.53 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [I sent this to -hubs which is probably not the right list] Hi, I'm behind a firewall and I can't use SOCKS. I'd like to use the port forwarding features of SSH (the 22 port is open) with CVSup. Has anyone tried the same setup ? I've tried ssh -L 5999:freefall.freebsd.org:5999 -L 5998:freefall.freebsd.org:5998 freefall.freebsd.org and cvsup -L 1 -g -p 5999 -P - cvs-supfile.cvsup but it still tries to connect to freefall directly: cvsup 13841 roberto 4u inet 0xf2471900 0t0 TCP localhost.eurocontrol.fr:2480->localhost.eurocontrol.fr:5999 cvsup 13841 roberto 5u inet 0xf242ee00 0t0 TCP caerdonn.eurocontrol.fr:2481->freefall.FreeBSD.ORG:4798 Thanks for any answer. -- Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr From owner-freebsd-hackers Wed Dec 11 07:24:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15690 for hackers-outgoing; Wed, 11 Dec 1996 07:24:20 -0800 (PST) Received: from home.winc.com (root@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA15679 for ; Wed, 11 Dec 1996 07:24:12 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by home.winc.com (8.8.4/8.8.4) with SMTP id KAA05199; Wed, 11 Dec 1996 10:23:57 -0500 Message-ID: <32AED2A1.41C67EA6@aristar.com> Date: Wed, 11 Dec 1996 10:26:25 -0500 From: "Matthew A. Gessner" Organization: Aristar, Inc. X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: ftp and cwd 'messages' Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, all, I've noticed that some ftp servers will print messages when you cd to a directory. How do you control this behaviour (I'm running 2.1.5)? I don't see anything in the man page for ftpd or the FAQ or the handbook covering this. TIA -- Matthew Gessner, Computer Scientist, Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 Voice (330) 668-2267, Fax (330) 668-2961 From owner-freebsd-hackers Wed Dec 11 07:27:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA16011 for hackers-outgoing; Wed, 11 Dec 1996 07:27:18 -0800 (PST) Received: from rocket.comtrol.com (rocket.comtrol.com [204.73.219.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA16003 for ; Wed, 11 Dec 1996 07:27:15 -0800 (PST) Received: from amirpc (amir [204.73.219.82]) by rocket.comtrol.com (8.6.9/8.6.9) with SMTP id JAA23157 for ; Wed, 11 Dec 1996 09:26:39 -0600 Date: Wed, 11 Dec 1996 09:26:39 -0600 Message-Id: <199612111526.JAA23157@rocket.comtrol.com> X-Sender: amir@comtrol.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: amir@comtrol.com (Amir Farah) Subject: driver problems Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a problem and a general question. problem: I have a serial port driver which works fine with modems. I can make PPP connections and all is well. The problem is "cu". The first time I run cu on a callout port it runs fine. When I quit it drops DTR and exits normally. Next time I start cu on the same port it just hangs until I either turn off the modem and turn it back on or remove the port cable from the modem for a second. Everything then works fine. It starts taking at commands and ~. to quit. I can enter cu again and it will work. Just that each time I quit I have to turn off the modem. What remains hanging when the driver closes the port to cause this problem?? general question: How can you set tty speed for 64K bits/sec or 56K bits/sec for data transfer over ISDN?? Thanks amir From owner-freebsd-hackers Wed Dec 11 07:33:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA16536 for hackers-outgoing; Wed, 11 Dec 1996 07:33:44 -0800 (PST) Received: from seine.cs.umd.edu (10862@seine.cs.umd.edu [128.8.128.59]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA16531 for ; Wed, 11 Dec 1996 07:33:42 -0800 (PST) Received: by seine.cs.umd.edu (8.8.4/UMIACS-0.9/04-05-88) id KAA06210; Wed, 11 Dec 1996 10:33:39 -0500 (EST) Date: Wed, 11 Dec 1996 10:33:39 -0500 (EST) From: rohit@cs.umd.edu (Rohit Dube) Message-Id: <199612111533.KAA06210@seine.cs.umd.edu> To: freebsd-hackers@freebsd.org Subject: Sendmail question for Gurus Cc: rohit@cs.umd.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, My ISP did both primary and secondary DNS for me and I had sendmail running on my machine which delivered mail fine. Then we acquired a new domain name for which the same machine does Primary DNS. The ISP does secondary. I wanted sendmail on the machine to deliver mail for both the domain names. What is the cleanest/easiest way to achieve this? NOTE: Both the old domain name and the new domain name point to the same IP address. I am running FreeBSD 2.x, named 4.9.x and sendmail 8.7.x From owner-freebsd-hackers Wed Dec 11 08:04:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA18494 for hackers-outgoing; Wed, 11 Dec 1996 08:04:04 -0800 (PST) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA18456 for ; Wed, 11 Dec 1996 08:04:01 -0800 (PST) Received: from harlie (bastion.bfd.com [204.160.242.2]) by horst.bfd.com (8.7.6/8.7.3) with SMTP id IAA15107; Wed, 11 Dec 1996 08:03:56 -0800 (PST) Date: Wed, 11 Dec 1996 08:03:56 -0800 (PST) From: "Eric J. Schwertfeger" X-Sender: ejs@harlie To: Rohit Dube cc: freebsd-hackers@freebsd.org Subject: Re: Sendmail question for Gurus In-Reply-To: <199612111533.KAA06210@seine.cs.umd.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Rohit Dube wrote: > I wanted sendmail on the machine to deliver mail for both > the domain names. What is the cleanest/easiest way to achieve > this? If the userlist is the same for both domains (ie webmaster@domain1.com is the same as webaster@domain2.com), then all you need do is add the new domain to /etc/sendmail.cw. If you need to be able to seperate out the two, then check out http://cybernut.com/guides/virtual.html (http://pandora.bfd.com/guides/virtual.html if that doesn't work). It has a cookbook solution to virtualizing sendmail far enough to let the same name at two different domains route to two different mailboxes, without needing a sendmail recompile (at least under 2.1.5 and later). From owner-freebsd-hackers Wed Dec 11 08:07:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA18729 for hackers-outgoing; Wed, 11 Dec 1996 08:07:51 -0800 (PST) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA18719 for ; Wed, 11 Dec 1996 08:07:45 -0800 (PST) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 10579 on Wed, 11 Dec 1996 16:51:14 +0100; id QAA10579 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.7.5/8.7.3) with ESMTP id QAA19134; Wed, 11 Dec 1996 16:51:32 +0100 (MET) Message-Id: <199612111551.QAA19134@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: roberto@eurocontrol.fr (Ollivier Robert) cc: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers' list) Subject: Re: Fwd: CVSup with SSH In-reply-to: roberto's message of Wed, 11 Dec 1996 16:02:58 +0100. Date: Wed, 11 Dec 1996 16:51:31 +0100 From: Marc van Kempen Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [I sent this to -hubs which is probably not the right list] > > Hi, > > I'm behind a firewall and I can't use SOCKS. I'd like to use the port > forwarding features of SSH (the 22 port is open) with CVSup. Has anyone > tried the same setup ? > > I've tried > > ssh -L 5999:freefall.freebsd.org:5999 -L 5998:freefall.freebsd.org:5998 > freefall.freebsd.org > > and > > cvsup -L 1 -g -p 5999 -P - cvs-supfile.cvsup > > but it still tries to connect to freefall directly: > > cvsup 13841 roberto 4u inet 0xf2471900 0t0 TCP localhost.eurocontrol.fr:2480->localhost.eurocontrol.fr:5999 > cvsup 13841 roberto 5u inet 0xf242ee00 0t0 TCP caerdonn.eurocontrol.fr:2481->freefall.FreeBSD.ORG:4798 > Did you try the plug-gw from the fwtk from TIS? You can use this to forward a port/ip-no from your internal network to a port/ip-no on the Internet. Then you should point cvsup at your firewall as being the cvsup server. If you want details, mail me. Regards, Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Wed Dec 11 08:23:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA19618 for hackers-outgoing; Wed, 11 Dec 1996 08:23:12 -0800 (PST) Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA19612 for ; Wed, 11 Dec 1996 08:23:08 -0800 (PST) Received: by atena.eurocontrol.fr; (5.65v3.2/1.3/10May95) id AA26067; Wed, 11 Dec 1996 17:22:03 +0100 Received: from caerdonn.eurocontrol.fr by eurocontrol.fr with ESMTP (1.37.109.16/16.2) id AA153961047; Wed, 11 Dec 1996 17:17:27 +0100 Received: (from roberto@localhost) by caerdonn.eurocontrol.fr (8.8.4/8.8.2/caerdonn-1.1) id RAA16860; Wed, 11 Dec 1996 17:17:27 +0100 (MET) Message-Id: Date: Wed, 11 Dec 1996 17:17:27 +0100 From: roberto@eurocontrol.fr (Ollivier Robert) To: marc@bowtie.nl (Marc van Kempen) Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers' list) Subject: Re: Fwd: CVSup with SSH References: <199612111551.QAA19134@nietzsche.bowtie.nl> X-Mailer: Mutt 0.53 Mime-Version: 1.0 In-Reply-To: <199612111551.QAA19134@nietzsche.bowtie.nl>; from Marc van Kempen on Dec 11, 1996 16:51:31 +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Marc van Kempen: > Did you try the plug-gw from the fwtk from TIS? You can use this > to forward a port/ip-no from your internal network to a port/ip-no I can't use but SSH should be able to do the same thing as plug-gw (except it can forward multiple port whereas plug-gw can't). The problem is that CVSup tries to connect to freefall "directly" because I can't seem to force CVSup to use the port I decided. What I want is a way to tell CVSup : use these two ports on localhost where the ports have been magically redirected to ports on freefall by SSH. -- Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr From owner-freebsd-hackers Wed Dec 11 08:25:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA19807 for hackers-outgoing; Wed, 11 Dec 1996 08:25:12 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA19802 for ; Wed, 11 Dec 1996 08:25:10 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Wed, 11 Dec 1996 09:24:26 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 11 Dec 1996 09:24:00 -0700 From: Darren Davis To: mtaylor@cybernet.com, brandon@glacier.cold.org Cc: hackers@freebsd.org Subject: RE: Help! Turning off DTR on a serial device -Reply Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, actually, I was the Developer Support Engineer for UnixWare at Univel/Novell. I suspect that you will find that there are some differences. In looking at man termio(7), you want to look at TIOCM_DTR. Darren From owner-freebsd-hackers Wed Dec 11 08:44:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA21058 for hackers-outgoing; Wed, 11 Dec 1996 08:44:05 -0800 (PST) Received: from trem.cnt.org.br (desvio.cnt.org.br [200.19.123.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA21032 for ; Wed, 11 Dec 1996 08:43:58 -0800 (PST) Received: by trem.cnt.org.br (AIX 3.2/UCB 5.64/4.03) id AA13674; Wed, 11 Dec 1996 14:40:27 -0300 From: ormonde@trem.cnt.org.br (Rodrigo Ormonde) Message-Id: <9612111740.AA13674@trem.cnt.org.br> Subject: Discovering network interfaces To: hackers@freebsd.org Date: Wed, 11 Dec 1996 14:40:27 -0300 (GRNLNDST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Helo. I have to write a program to show the user the names of the currently configured network interfaces. (something like netstat -in) The problem is that I have no idea how this could be done inside a C program (I don't want to execute a external program like netstat to do this. It'd be nice if I could do it inside my C program). Does anybody know a function/system call which can be used to list the network interfaces ? Any help will be apreciated. Please send answers to me, I'm not on the list. Thanks in advance. -- Rodrigo de La Rocque Ormonde e-mail: ormonde@cnt.org.br PGP Public key: finger ormonde@cnt.org.br From owner-freebsd-hackers Wed Dec 11 08:44:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA21102 for hackers-outgoing; Wed, 11 Dec 1996 08:44:13 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA21085 for ; Wed, 11 Dec 1996 08:44:09 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id KAA02338; Wed, 11 Dec 1996 10:43:54 -0600 (CST) Message-Id: <199612111643.KAA02338@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Christoph Kukulies cc: freebsd-hackers@freefall.freebsd.org Subject: Re: ccd - partitioning In-reply-to: Your message of Wed, 11 Dec 1996 11:28:21 +0100. <199612111028.LAA20003@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Dec 1996 10:43:54 -0600 From: Chris Csanady Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I still have no luck getting ccd working here with 2 SCSI disks and >two controllers . I think that the problem is that the fstype in the disklabel is unused. Try changing both e's to 4.2BSD, and see what that does. Also, I noticed in disklabel.h there is a disk type "CCD". I'm not sure if changing the type to this value is significant or not though. --Chris Csanady >I partitioned several times with various options. Presently the picture is >like this: > >Disk name: sd0 FDISK Partition Editor >DISK Geometry: 3067 cyls/64 heads/32 sectors > > Offset Size End Name PType Desc Subtype Flags > > 0 32 31 - 6 unused 0 > 32 6281184 6281215 sd0s1 3 freebsd 165 C> > 6281216 640 6281855 - 6 unused 0 > > > > > > > >The following commands are supported (in upper or lower case): > >A = Use Entire Disk B = Bad Block Scan C = Create Partition >D = Delete Partition G = Set Drive Geometry S = Set Bootable >U = Undo All Changes Q = Finish W = Write Changes > > >Use F1 or ? to get more help, arrow keys to select. > > >Dito for sd1. > ># /dev/rsd1c: >type: SCSI >disk: sd1s1 >label: >flags: >bytes/sector: 512 >sectors/track: 32 >tracks/cylinder: 64 >sectors/cylinder: 2048 >cylinders: 3066 >sectors/unit: 6281184 >rpm: 3600 >interleave: 1 >trackskew: 0 >cylinderskew: 0 >headswitch: 0 # milliseconds >track-to-track seek: 0 # milliseconds >drivedata: 0 > >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > c: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) > e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) ^^^^^^ ># ># /dev/rsd0c: >type: SCSI >disk: sd0s1 >label: >flags: >bytes/sector: 512 >sectors/track: 32 >tracks/cylinder: 64 >sectors/cylinder: 2048 >cylinders: 3066 >sectors/unit: 6281184 >rpm: 3600 >interleave: 1 >trackskew: 0 >cylinderskew: 0 >headswitch: 0 # milliseconds >track-to-track seek: 0 # milliseconds >drivedata: 0 > >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > c: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) > e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) ^^^^^^ ># > ># ># /etc/ccd.conf ># Configuration file for concatenated disk devices ># ># ccd ileave flags component devices >ccd0 16 none /dev/sd0e /dev/sd1e > > ># ccdconfig -C >ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format >^^^^^^^^^^^^^^^^^ This remains the key problem ^^^^^^^^^^^^^^^^^ > >I tried with or without tabs, with linefeed at the end. No luck. > >I did this all with a 2.2-ALPHA install. The kernel being 3.0, >hope the latter not being a problem. > ># >fdisk sd0 >******* Working on device /dev/rsd0 ******* >parameters extracted from in-core disklabel are: >cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 >parameters to be used for BIOS calculations are: >cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) > >Warning: BIOS sector numbering starts with sector 1 >Information from DOS bootblock is: >The data for partition 0 is: >sysid 165,(FreeBSD/NetBSD/386BSD) > start 32, size 6281184 (3066 Meg), flag 80 > beg: cyl 0/ sector 1/ head 1; > end: cyl 1023/ sector 32/ head 63 >The data for partition 1 is: > >The data for partition 2 is: > >The data for partition 3 is: > ># ># fdisk sd1 >******* Working on device /dev/rsd1 ******* >parameters extracted from in-core disklabel are: >cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 >parameters to be used for BIOS calculations are: >cylinders=3067 heads=64 sectors/track=32 (2048 blks/cyl) > >Warning: BIOS sector numbering starts with sector 1 >Information from DOS bootblock is: >The data for partition 0 is: >sysid 165,(FreeBSD/NetBSD/386BSD) > start 32, size 6281184 (3066 Meg), flag 80 > beg: cyl 0/ sector 1/ head 1; > end: cyl 1023/ sector 32/ head 63 >The data for partition 1 is: > >The data for partition 2 is: > >The data for partition 3 is: > ># > ># dmesg >Copyright (c) 1992-1996 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > >FreeBSD 3.0-CURRENT #0: Sun Dec 8 16:23:36 MET 1996 > kuku@bach.physik.rwth-aachen.de:/usr/src/sys/compile/DUKE >Calibrating clock(s) relative to mc146818A clock ... i586 clock: 100248720 Hz, i8254 clock: 1193437 Hz >CPU: AMD Unknown (100.23-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x511 >real memory = 33554432 (32768K bytes) >avail memory = 30928896 (30204K bytes) >Probing for devices on PCI bus 0: >chip0 rev 2 on pci0: 0 >chip1 rev 1 on pci0:7:0 >chip2 rev 0 on pci0:7:1 >ncr0 rev 17 int a irq 11 on pci0:8 >ncr0 waiting for scsi devices to settle >(ncr0:0:0): "QUANTUM FIREBALL_TM3200S 300N" type 0 fixed SCSI 2 >sd0(ncr0:0:0): Direct-Access >sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. >3067MB (6281856 512 byte sectors) >ncr1 rev 17 int a irq 10 on pci0:11 >ncr1 waiting for scsi devices to settle >(ncr1:0:0): "QUANTUM FIREBALL_TM3200S 300N" type 0 fixed SCSI 2 >sd1(ncr1:0:0): Direct-Access >sd1(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. >3067MB (6281856 512 byte sectors) >Probing for devices on the ISA bus: >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: MDA/hercules <16 virtual consoles, flags=0x0> >ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 8192 on isa >ed0: address 00:00:c0:bd:8a:16, type WD8003E (8 bit) >sio0 at 0x3f8-0x3ff irq 4 on isa >sio0: type 16550A >sio1 at 0x2f8-0x2ff irq 3 on isa >sio1: type 16550A >lpt0 at 0x3bc-0x3c3 irq 7 on isa >lpt0: Interrupt-driven port >lp0: TCP/IP capable interface >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >fdc0: NEC 765 >fd0: 1.44MB 3.5in >wdc0 at 0x1f0-0x1f7 irq 14 on isa >wd0: 124MB (254592 sectors), 936 cyls, 16 heads, 17 S/T, 512 B/S >npx0 on motherboard >npx0: INT 16 interface >ccd0-3: Concatenated disk drivers ># ># ls -l /dev/*ccd* >brw-r----- 1 root wheel 21, 0 Dec 9 01:02 /dev/ccd0a >brw-r----- 1 root wheel 21, 1 Dec 9 01:02 /dev/ccd0b >brw-r----- 1 root wheel 21, 2 Dec 9 01:02 /dev/ccd0c >brw-r----- 1 root wheel 21, 3 Dec 9 01:02 /dev/ccd0d >brw-r----- 1 root wheel 21, 4 Dec 9 01:02 /dev/ccd0e >brw-r----- 1 root wheel 21, 5 Dec 9 01:02 /dev/ccd0f >brw-r----- 1 root wheel 21, 6 Dec 9 01:02 /dev/ccd0g >brw-r----- 1 root wheel 21, 7 Dec 9 01:02 /dev/ccd0h >crw------- 1 root wheel 74, 0x20000000 Dec 11 04:47 /dev/rccd0.ctl >crw-r----- 1 root wheel 74, 0 Dec 9 01:02 /dev/rccd0a >crw-r----- 1 root wheel 74, 1 Dec 9 01:02 /dev/rccd0b >crw-r----- 1 root wheel 74, 2 Dec 9 01:02 /dev/rccd0c >crw-r----- 1 root wheel 74, 3 Dec 9 01:02 /dev/rccd0d >crw-r----- 1 root wheel 74, 4 Dec 9 01:02 /dev/rccd0e >crw-r----- 1 root wheel 74, 5 Dec 9 01:02 /dev/rccd0f >crw-r----- 1 root wheel 74, 6 Dec 9 01:02 /dev/rccd0g >crw-r----- 1 root wheel 74, 7 Dec 9 01:02 /dev/rccd0h ># > > >Is there something special to partitioning? > > >--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Wed Dec 11 08:52:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA21658 for hackers-outgoing; Wed, 11 Dec 1996 08:52:48 -0800 (PST) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA21652 for ; Wed, 11 Dec 1996 08:52:46 -0800 (PST) Received: from PacBell.TelcoSucks.org (PacBell.TelcoSucks.org [207.90.181.5]) by DNS.Lamb.net (8.8.3/8.8.2) with SMTP id IAA01455; Wed, 11 Dec 1996 08:52:20 -0800 (PST) Message-Id: <3.0.32.19961211085303.006ea834@Gatekeeper-3.Lamb.net> X-Sender: ulf@Gatekeeper-3.Lamb.net X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Wed, 11 Dec 1996 08:53:05 -0800 To: "Eric J. Schwertfeger" , Rohit Dube From: Ulf Zimmermann Subject: Re: Sendmail question for Gurus Cc: freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 08:03 AM 12/11/96 -0800, Eric J. Schwertfeger wrote: > > >On Wed, 11 Dec 1996, Rohit Dube wrote: > >> I wanted sendmail on the machine to deliver mail for both >> the domain names. What is the cleanest/easiest way to achieve >> this? > >If the userlist is the same for both domains (ie webmaster@domain1.com is >the same as webaster@domain2.com), then all you need do is add >the new domain to /etc/sendmail.cw. If you need to be able to seperate >out the two, then check out http://cybernut.com/guides/virtual.html >(http://pandora.bfd.com/guides/virtual.html if that doesn't work). It has >a cookbook solution to virtualizing sendmail far enough to let the same >name at two different domains route to two different mailboxes, without >needing a sendmail recompile (at least under 2.1.5 and later). Or just look at the function (m4 macro) virtusertable of sendmail 8.7.x and newer. I used hacked rules before, but I recently swichted to the virtusertable and it works better then before. Ulf. ----------------------------------------------------------- Alameda Networks, Inc. | Ulf Zimmermann (ulf@Alameda.net) 1525 Pacific Avenue | Phone: (510)769-2936 Alameda, CA 94501 | Fax : (510)521-5073 From owner-freebsd-hackers Wed Dec 11 09:52:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA25009 for hackers-outgoing; Wed, 11 Dec 1996 09:52:08 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA25004 for ; Wed, 11 Dec 1996 09:52:05 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id SAA10575; Wed, 11 Dec 1996 18:53:26 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id TAA22444; Wed, 11 Dec 1996 19:05:38 +0100 (MET) From: Christoph Kukulies Message-Id: <199612111805.TAA22444@gilberto.physik.rwth-aachen.de> Subject: Re: ccd - partitioning In-Reply-To: <199612111643.KAA02338@friley216.res.iastate.edu> from Chris Csanady at "Dec 11, 96 10:43:54 am" To: ccsanady@friley216.res.iastate.edu (Chris Csanady) Date: Wed, 11 Dec 1996 19:05:37 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >I still have no luck getting ccd working here with 2 SCSI disks and > >two controllers . > > I think that the problem is that the fstype in the disklabel is unused. > Try changing both e's to 4.2BSD, and see what that does. Also, I noticed > in disklabel.h there is a disk type "CCD". I'm not sure if changing the > type to this value is significant or not though. Bingo! You just won a bottle of (please check) [ ] bottle of Altbier (1 l) [ ] bottle of French White Wine (Sancerre) > > e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) > ^^^^^^ > >8 partitions: > ># size offset fstype [fsize bsize bps/cpg] > > c: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) > > e: 6281184 0 unused 0 0 # (Cyl. 0 - 3066*) > ^^^^^^ > ># ccdconfig -C > >ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format > >^^^^^^^^^^^^^^^^^ This remains the key problem ^^^^^^^^^^^^^^^^^ The error message is really very enlightening . Now: # ccdconfig -Cv ccd0: 2 components (sd0e, sd1e), 12562336 blocks interleaved at 16 blocks # # > >npx0: INT 16 interface > >ccd0-3: Concatenated disk drivers > >Is there something special to partitioning? > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Wed Dec 11 10:09:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA26353 for hackers-outgoing; Wed, 11 Dec 1996 10:09:58 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA26346 for ; Wed, 11 Dec 1996 10:09:56 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id LAA18098; Wed, 11 Dec 1996 11:09:45 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id LAA29977; Wed, 11 Dec 1996 11:03:56 -0700 (MST) Date: Wed, 11 Dec 1996 11:03:55 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: Ollivier Robert cc: "FreeBSD Hackers' list" Subject: Re: Fwd: CVSup with SSH In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Why not modify your cvs-supfile.cvsup to use localhost instead of freefall? If it stores any state data locally on a per-hostname basis it could get confused if you setup the ssh forwarding to different hosts at different times, but should work. On Wed, 11 Dec 1996, Ollivier Robert wrote: > According to Marc van Kempen: > > Did you try the plug-gw from the fwtk from TIS? You can use this > > to forward a port/ip-no from your internal network to a port/ip-no > > I can't use but SSH should be able to do the same thing as plug-gw (except > it can forward multiple port whereas plug-gw can't). The problem is that > CVSup tries to connect to freefall "directly" because I can't seem to force > CVSup to use the port I decided. > > What I want is a way to tell CVSup : use these two ports on localhost where > the ports have been magically redirected to ports on freefall by SSH. > -- > Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr > From owner-freebsd-hackers Wed Dec 11 10:34:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27691 for hackers-outgoing; Wed, 11 Dec 1996 10:34:43 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27683 for ; Wed, 11 Dec 1996 10:34:40 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA13287; Wed, 11 Dec 1996 11:34:16 -0700 (MST) Date: Wed, 11 Dec 1996 11:34:16 -0700 (MST) Message-Id: <199612111834.LAA13287@rocky.mt.sri.com> From: Nate Williams To: Darren Davis Cc: hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Darren Davis writes: [ Hit the dang return key Darren. It's there for a purpose. :) ] > I went out to Marimba (http://www.marimba.com) and got their > unsupported version of Castanet tuner for FreeBSD. It also has > version 1.0.2 of the JDK. I was able to get the javac they ported to > work, but get the following problems when I try to run the java > emulator (I also get this same problem when I try to run the tuner). > I have tried this with both stable and current. Has anybody got this > stuff to work? I'll bet you're running the JDK on a display which isn't 8/24 bit, right? It's broken as shipped from SUN. Either switch X to 8 bit or 24 bit. Nate From owner-freebsd-hackers Wed Dec 11 10:45:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA28292 for hackers-outgoing; Wed, 11 Dec 1996 10:45:57 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA28287 for ; Wed, 11 Dec 1996 10:45:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA13353; Wed, 11 Dec 1996 11:45:15 -0700 (MST) Date: Wed, 11 Dec 1996 11:45:15 -0700 (MST) Message-Id: <199612111845.LAA13353@rocky.mt.sri.com> From: Nate Williams To: batie@agora.rdrop.com (Alan Batie) Cc: hackers@freefall.freebsd.org, pst@shockwave.com Subject: Re: PC CARD stuff In-Reply-To: References: <199612101408.GAA01396@freefall.freebsd.org> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm thinking of going out and getting one of the 3COM 3c589 cards > > and a Megahertz 3811 cellular modem, but the combo is /not/ cheap. > > I got the 3com 3c589 to use in a Toshiba 115cs as a cheap portable net > monitor. Lo, it won't go into promiscuous mode, so it's not a very useful > net monitor. Are you running 2.1.6.1 on it? I fixed a bug sometime around the 2.1.5 time that supposedly fixed promiscious mode in the zp driver. > For modem, I'm using a Motorola Montana ("named after the state with no > speed limits") Hey, that's not true. :) Our speed limit is 'Safe and Prudent', which in reality kicks in about 80 mph. Nate From owner-freebsd-hackers Wed Dec 11 11:06:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29391 for hackers-outgoing; Wed, 11 Dec 1996 11:06:29 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA29365 for ; Wed, 11 Dec 1996 11:06:16 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Wed, 11 Dec 96 20:06 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-hackers@freebsd.org id ; Wed, 11 Dec 96 20:06 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA17058; Wed, 11 Dec 96 19:57:41 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9612111857.AA17058@wavehh.hanse.de> Subject: FDW: pthreads based on kernel managed threads for FreeBSD 2.1 almost ready To: freebsd-hackers@freebsd.org Date: Wed, 11 Dec 1996 19:57:40 +0100 (MET) Cc: doug@qnx.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ I forwarded this message to the freebsd-hackers mailing list. ] This guy asks for help in finishing a kernel-thread thread solution. Would be intersting to see at least the performance penality over a userlevel package or a mixed model like the DEC work discussed here some days ago. I think you can get many useful locking items from the linuxthreads package, which is a pthread implementation on top of Linux' clone() call (somewhat equivalent to rfork()). Get it from alpha.gnu.prep.ai.mit.edu. It is GPLed, of course. Martin >From: doug@qnx.com (Doug Santry) >Newsgroups: comp.unix.bsd.freebsd.misc >Subject: pthreads based on kernel managed threads for FreeBSD 2.1 almost ready >Date: 10 Dec 1996 10:24:14 -0500 >Organization: QNX Software Systems >Message-ID: <58jvau$9tt@qnx.com> Hi y'all. I am currently working on a pthreads interface to my kernel managed threads for FreeBSD 2.1, the first release won't be complete, I plan to support : pthread_create, pthread_join, pthread_kill, pthread_sigmask, pthread_exit pthread_self and pthread_detached. In addition to the above there will also be pthread_mutex_init and the lock, unlock trylock and destroy functions. The code is all written but still buggy so I am hanging onto it a bit longer, but when I send it out, you can see it isn't complete by any means. I need your help! Is anybody out there interested in writing the condvar stuff and some other bits? I simply haven't got the time do it all in a useful timeframe... DJS From owner-freebsd-hackers Wed Dec 11 11:09:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29701 for hackers-outgoing; Wed, 11 Dec 1996 11:09:49 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA29696 for ; Wed, 11 Dec 1996 11:09:47 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06756; Wed, 11 Dec 1996 11:48:14 -0700 From: Terry Lambert Message-Id: <199612111848.LAA06756@phaeton.artisoft.com> Subject: Re: driver problems To: amir@comtrol.com (Amir Farah) Date: Wed, 11 Dec 1996 11:48:14 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: <199612111526.JAA23157@rocket.comtrol.com> from "Amir Farah" at Dec 11, 96 09:26:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > problem: > > I have a serial port driver which works fine with modems. I can make PPP > connections and all is well. The problem is "cu". The first time I run cu on > a callout port it runs fine. When I quit it drops DTR and exits normally. > Next time I start cu on the same port it just hangs until I either turn off > the modem and turn it back on or remove the port cable from the modem for a > second. Everything then works fine. It starts taking at commands and ~. to > quit. I can enter cu again and it will work. Just that each time I quit I > have to turn off the modem. What remains hanging when the driver closes the > port to cause this problem?? On on-to-off DTR, the modem is supposed to be programmed to reset as if powered off-then-on. If your modem does not reset this way, you can have all sorts of problems, ranging from the modem leaving the phone line active when the software isn't using it (phone_bill++), to the sort of problem you are describing. > general question: > > How can you set tty speed for 64K bits/sec or 56K bits/sec for data transfer > over ISDN?? You can't; on a normal IBM serial port, you program the UART by programming a divider value. Each of the speed values are manifest bit values for B9600, B19200, etc.. To use non-standard speeds, assuming you are using a non-standard serial card, and not an IBM serial port where you can only twiddle the divider, you have to steal from the allowable bit values. For instance, you could change B110 to mean "set this non-IBM serial port to 64K". In reality, for serial devices with external clocks, you don't *need* to set serial port speed. For internal modems or UART-CSU/DSU pairs, you should be able to match the UART-to-other-chip speed without needing the user to explicitly program the UART (yeah, right, that'll work...). If your driver supports this, and is an integrated device, you could pretty much ignore the user specified baud rate, and "just work". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Dec 11 11:13:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA00244 for hackers-outgoing; Wed, 11 Dec 1996 11:13:46 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA00238 for ; Wed, 11 Dec 1996 11:13:44 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06772; Wed, 11 Dec 1996 11:51:04 -0700 From: Terry Lambert Message-Id: <199612111851.LAA06772@phaeton.artisoft.com> Subject: Re: Discovering network interfaces To: ormonde@trem.cnt.org.br (Rodrigo Ormonde) Date: Wed, 11 Dec 1996 11:51:03 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <9612111740.AA13674@trem.cnt.org.br> from "Rodrigo Ormonde" at Dec 11, 96 02:40:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have to write a program to show the user the names of the currently > configured network interfaces. (something like netstat -in) > The problem is that I have no idea how this could be done inside a C program > (I don't want to execute a external program like netstat to do this. It'd be > nice if I could do it inside my C program). > > Does anybody know a function/system call which can be used to list the > network interfaces ? Look at the source code that netstat -in uses. It is located in: /usr/src/usr.bin/netstat Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Dec 11 11:30:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA01640 for hackers-outgoing; Wed, 11 Dec 1996 11:30:02 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA01607 for ; Wed, 11 Dec 1996 11:29:56 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id LAA29107 for ; Wed, 11 Dec 1996 11:29:55 -0800 (PST) Date: Wed, 11 Dec 1996 11:29:55 -0800 (PST) From: Jaye Mathisen Reply-To: Jaye Mathisen To: hackers@freebsd.org Subject: CVSUP dying Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk trying to sup -current. Edit src/release/sysinstall/nfs.c Add delta 1.12 96.12.11.09.35.04 jkh Edit src/release/sysinstall/package.c Add delta 1.50 96.12.11.09.35.04 jkh @" Invalid list file: Invalid integer "~p U|! (Lots of binary characters after that jkh, somehitng about /usr/sup/src-lib/checkouts.cvs:. Invalid list file: Invalid Integer. From owner-freebsd-hackers Wed Dec 11 12:23:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06539 for hackers-outgoing; Wed, 11 Dec 1996 12:23:50 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA06532 for ; Wed, 11 Dec 1996 12:23:47 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA15500 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Wed, 11 Dec 1996 21:22:38 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id TAA00689; Wed, 11 Dec 1996 19:51:11 +0100 (MET) From: Wilko Bulte Message-Id: <199612111851.TAA00689@yedi.iaf.nl> Subject: Re: Discovering network interfaces To: ormonde@trem.cnt.org.br (Rodrigo Ormonde) Date: Wed, 11 Dec 1996 19:51:11 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <9612111740.AA13674@trem.cnt.org.br> from "Rodrigo Ormonde" at Dec 11, 96 02:40:27 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Rodrigo Ormonde wrote... > Helo. > > I have to write a program to show the user the names of the currently > configured network interfaces. (something like netstat -in) > The problem is that I have no idea how this could be done inside a C program I don't know, but wouldn't a short peek in the netstat source code tell you how they do it? Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Dec 11 12:25:28 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06641 for hackers-outgoing; Wed, 11 Dec 1996 12:25:28 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA06633 for ; Wed, 11 Dec 1996 12:25:22 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id MAA27141; Wed, 11 Dec 1996 12:16:45 -0800 (PST) Message-ID: <32AF1685.41C67EA6@whistle.com> Date: Wed, 11 Dec 1996 12:16:05 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Rodrigo Ormonde CC: hackers@FreeBSD.ORG Subject: Re: Discovering network interfaces References: <9612111740.AA13674@trem.cnt.org.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Rodrigo Ormonde wrote: > > Helo. > > I have to write a program to show the user the names of the currently > configured network interfaces. (something like netstat -in) > The problem is that I have no idea how this could be done inside a C program > (I don't want to execute a external program like netstat to do this. It'd be > nice if I could do it inside my C program). > > Does anybody know a function/system call which can be used to list the > network interfaces ? > > Any help will be apreciated. > > Please send answers to me, I'm not on the list. A Here's a little program that dumps out interfaces and their addresses (some of which you don't normally see) alter to your heart's content.. :) -cut here- #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include void showbytes(unsigned char *cptr,int len) { int i,j; for (j = 0 ;len > 0 ;j++) { for ( i = 0; i < 16; i++) { printf("0x%x ",*cptr++); if (--len == 0) break; } printf("\n"); } } void print_sa (struct sockaddr *sap) { char buf[128]; printf("len=%d,",sap->sa_len); switch(sap->sa_family) { case AF_LINK: printf(" family=LINK\n"); { char *cptr; struct sockaddr_dl *sdl = (struct sockaddr_dl *)sap; cptr = sdl->sdl_data; printf("index=%u, type=%u ", sdl->sdl_index, sdl->sdl_type); printf("nlen=%u, alen=%u, slen=%u\n", sdl->sdl_nlen, sdl->sdl_alen, sdl->sdl_slen); if(sdl->sdl_nlen) { bcopy(cptr,buf,sdl->sdl_nlen); buf[sdl->sdl_nlen] = 0; printf(" name = %s\n",buf); cptr += sdl->sdl_nlen; } if(sdl->sdl_alen) { printf(" address = "); showbytes(cptr,sdl->sdl_alen); cptr += sdl->sdl_alen; } if(sdl->sdl_slen) { printf(" selector = "); showbytes(cptr,sdl->sdl_slen); cptr += sdl->sdl_slen; } } break; case AF_INET: printf(" family=INET\n"); printf("[%s]", inet_ntoa(((struct sockaddr_in *)sap)->sin_addr)); printf(".%hu\n",((struct sockaddr_in *)sap)->sin_port); break; default: printf(" family=%d\n",sap->sa_family); showbytes(sap->sa_data,sap->sa_len-2); } } /* * Get the configuration from the kernel. Only called if there's no * configuration. */ void getifconf( void ) { struct ifconf ifc; struct ifreq ifrs[ 64 ], *ifr, *nextifr; struct interface *iface, *niface; int s; struct sockaddr *sa_p; int ifrsize = 0; bzero(&ifc,sizeof(struct ifconf)); bzero(ifrs,sizeof(struct ifreq) * 64); if (( s = socket( AF_INET, SOCK_DGRAM, 0 )) < 0 ) { perror( "socket" ); exit( 1 ); } ifc.ifc_len = sizeof( ifrs ); ifc.ifc_buf = (caddr_t)ifrs; if ( ioctl( s, SIOCGIFCONF, &ifc ) < 0 ) { perror( "getifconf" ); exit( 1 ); } for ( ifr = ifc.ifc_req; ifc.ifc_len >= sizeof( struct ifreq ); ifr = nextifr, ifc.ifc_len -= ifrsize) { /* * in BSD4.4, this returns an entry for every address * Associated with the if. including physical.. they * include a sockaddr which is VARIABLE LENGTH! * * Calculate the length of this entry. */ sa_p = &(ifr->ifr_addr); print_sa(&(ifr->ifr_addr)); /* print_sa(&(ifr->ifr_dstaddr)); print_sa(&(ifr->ifr_broadaddr)); */ ifrsize = IFNAMSIZ + sa_p->sa_len; nextifr = (struct ifreq *)((caddr_t)ifr + ifrsize); /* * Now get it's flags */ if ( ioctl( s, SIOCGIFFLAGS, ifr ) < 0 ) { perror( ifr->ifr_name ); exit( 1 ); } printf("FLAGS = 0x%x\n",(unsigned short)ifr->ifr_flags); printf("\n"); } if ( ifc.ifc_len != 0 ) { fprintf( stderr, "Funky gifconf return.\n" ); exit( 1 ); } (void)close( s ); return; } main() { getifconf(); exit(0); } /* EOF */ From owner-freebsd-hackers Wed Dec 11 13:45:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA11705 for hackers-outgoing; Wed, 11 Dec 1996 13:45:25 -0800 (PST) Received: from simba.tc.gc.ca (aladdin.tc.gc.ca [198.103.96.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA11695; Wed, 11 Dec 1996 13:45:18 -0800 (PST) Received: from smtp.tc.gc.ca (smtp.tc.gc.ca [142.210.48.99]) by simba with ESMTP (DuhMail/3.0) id QAA08535; Wed, 11 Dec 1996 16:44:32 -0500 Received: from Microsoft Mail (PU Serial #1464) by SMTP.tc.gc.ca (PostalUnion/SMTP(tm) v2.1.8d for Windows NT(tm)) id AA-1996Dec11.163245.1464.485827; Wed, 11 Dec 1996 16:35:35 -0500 From: LUMARK@tc.gc.ca (Lu, Mark) To: freebsd-hackers@freebsd.org ('SMTP: freebsd-hackers@freebsd.org') Cc: freebsd-hardware@freebsd.org ('SMTP: freebsd-hardware@freebsd.org'), ianw@ee.usyd.edu.au ('SMTP: ianw@ee.usyd.edu.au') Message-ID: <1996Dec11.163245.1464.485827@SMTP.tc.gc.ca> X-Mailer: Microsoft Mail via PostalUnion/SMTP for Windows NT Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Wed, 11 Dec 1996 16:35:35 -0500 Subject: Re: How can i run Eicon X.25 card with F Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Really. I think you must look at > FreeBSD-current/src/share/doc/iso/wisc/eicon.nr >I hope, that is true, what is written in this document and >driver for EICON really exist. But it's really difficult to use >it without support in kernel ;) Does anyone know if the source code for these drivers are available somewhere? 'cause i have some of these cards, but with only dos drivers. From owner-freebsd-hackers Wed Dec 11 13:48:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA11887 for hackers-outgoing; Wed, 11 Dec 1996 13:48:33 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA11878 for ; Wed, 11 Dec 1996 13:48:30 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id NAA14404 for ; Wed, 11 Dec 1996 13:48:23 -0800 (PST) Date: Wed, 11 Dec 1996 13:48:23 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: iostat counters for ccd? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It would be nice if iostat would run against a ccd device. Also, how about getting rid of the decimal point stuff in iostat to make room for more disks? From owner-freebsd-hackers Wed Dec 11 14:01:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12533 for hackers-outgoing; Wed, 11 Dec 1996 14:01:32 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12527 for ; Wed, 11 Dec 1996 14:01:29 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id RAA03134; Wed, 11 Dec 1996 17:01:20 -0500 (EST) Date: Wed, 11 Dec 1996 17:01:20 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Nate Williams cc: Darren Davis , hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: <199612111834.LAA13287@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone confirm if Jeffrey Hsu's JDK 1.0.2 port works on 2.2-ALPHA (or later, but not -current)? I believe I followed the instructions exactly, but javac immediately gives: SIGSEGV 11* segmentation violation sig 11, code 12 or 0xc, sc 0xefbfd3b8, addr 0x1c Full thread dump: at which point it hangs. -john From owner-freebsd-hackers Wed Dec 11 15:12:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17062 for hackers-outgoing; Wed, 11 Dec 1996 15:12:24 -0800 (PST) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA17056 for ; Wed, 11 Dec 1996 15:12:21 -0800 (PST) Received: from localhost (mark@localhost) by vinyl.quickweb.com (8.7.5/8.6.12) with SMTP id SAA25076; Wed, 11 Dec 1996 18:11:24 -0500 (EST) Date: Wed, 11 Dec 1996 18:11:24 -0500 (EST) From: Mark Mayo To: John Fieber cc: Nate Williams , Darren Davis , hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, John Fieber wrote: > Can anyone confirm if Jeffrey Hsu's JDK 1.0.2 port works on > 2.2-ALPHA (or later, but not -current)? > > I believe I followed the instructions exactly, but javac > immediately gives: > > SIGSEGV 11* segmentation violation > sig 11, code 12 or 0xc, sc 0xefbfd3b8, addr 0x1c > > Full thread dump: > > at which point it hangs. It works for me -- are you using his latest jdk102.11-26.tar.gz ?? I'm not sure about the compiler, but the interpreter (java) only runs in 8bpp and 24bpp display mode... For some reason, I can't get the appletviewer to run (it ran on the older jdk, but not on the new one..). I've tested it pretty hard, and it seems quite good. Older bugs with serversockets are now cleaned up, and the interpreter even runs the Marimba products! Neato! -mark > > -john > > > From owner-freebsd-hackers Wed Dec 11 15:26:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17922 for hackers-outgoing; Wed, 11 Dec 1996 15:26:13 -0800 (PST) Received: from eve.speakeasy.org (cgray@eve.speakeasy.org [199.238.226.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA17913 for ; Wed, 11 Dec 1996 15:26:10 -0800 (PST) Received: from localhost (cgray@localhost) by eve.speakeasy.org (8.8.3/8.7.3) with SMTP id PAA04041; Wed, 11 Dec 1996 15:25:29 -0800 (PST) Date: Wed, 11 Dec 1996 15:25:29 -0800 (PST) From: Cyrus Gray To: hackers@freebsd.org Subject: Atlas SCSI 3 Drive GEO Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a 4.3 Gig atlas Wide SCSI 3 drive (Model M343xx) plugged into an Adaptec 2940UW When setting up FreeBSD I get a message that it can't get the drive Geometry. No biggy I've had this sort of thing happen before. So I went to Quantums Homepage and got the drive geo plugged it in and it still gives me the same error. Has anyone else gotten one of these to work? If so what drive GEO did you use? Thanks Cyrus Gray From owner-freebsd-hackers Wed Dec 11 15:41:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA18774 for hackers-outgoing; Wed, 11 Dec 1996 15:41:01 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA18767 for ; Wed, 11 Dec 1996 15:40:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA14658; Wed, 11 Dec 1996 16:40:47 -0700 (MST) Date: Wed, 11 Dec 1996 16:40:47 -0700 (MST) Message-Id: <199612112340.QAA14658@rocky.mt.sri.com> From: Nate Williams To: John Fieber Cc: Nate Williams , Darren Davis , hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: References: <199612111834.LAA13287@rocky.mt.sri.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can anyone confirm if Jeffrey Hsu's JDK 1.0.2 port works on > 2.2-ALPHA (or later, but not -current)? It works fine on a pre-ALPHA system and a 2.1.6.1 system, as well as a 2.2 system from last week and a -current system. Nate From owner-freebsd-hackers Wed Dec 11 15:43:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA18888 for hackers-outgoing; Wed, 11 Dec 1996 15:43:00 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA18875 for ; Wed, 11 Dec 1996 15:42:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA14686; Wed, 11 Dec 1996 16:42:41 -0700 (MST) Date: Wed, 11 Dec 1996 16:42:41 -0700 (MST) Message-Id: <199612112342.QAA14686@rocky.mt.sri.com> From: Nate Williams To: Mark Mayo Cc: hackers@freebsd.org Subject: JDK and appletviewer (was Re: Marimba for FreeBSD...) In-Reply-To: References: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Can anyone confirm if Jeffrey Hsu's JDK 1.0.2 port works on > > 2.2-ALPHA (or later, but not -current)? > > It works for me -- are you using his latest jdk102.11-26.tar.gz ?? I'm not > sure about the compiler, but the interpreter (java) only runs in 8bpp and > 24bpp display mode... Yep, Jeffrey even knows about the bug(s), but mentioned he didn't have time to fix them. > For some reason, I can't get the appletviewer to run Hmm, it works fine for me, but I had to delete some of the older stuff I had lying around. Nate From owner-freebsd-hackers Wed Dec 11 15:55:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19949 for hackers-outgoing; Wed, 11 Dec 1996 15:55:09 -0800 (PST) Received: from narcissus.ml.org (brosenga.st.pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA19919 for ; Wed, 11 Dec 1996 15:54:59 -0800 (PST) Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id PAA01742; Wed, 11 Dec 1996 15:54:52 -0800 (PST) Date: Wed, 11 Dec 1996 15:54:52 -0800 (PST) From: Snob Art Genre To: Cyrus Gray cc: hackers@freebsd.org Subject: Re: Atlas SCSI 3 Drive GEO In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Cyrus Gray wrote: > I have a 4.3 Gig atlas Wide SCSI 3 drive (Model M343xx) > plugged into an Adaptec 2940UW > > When setting up FreeBSD I get a message that it can't > get the drive Geometry. No biggy I've had this sort of > thing happen before. So I went to Quantums Homepage > and got the drive geo plugged it in and it still gives me > the same error. Has anyone else gotten one of these to work? > If so what drive GEO did you use? > > > Thanks > Cyrus Gray > > Sometimes it helps if you create a small DOS partition at the beginning of your hard drive. Ben The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-hackers Wed Dec 11 15:56:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA20123 for hackers-outgoing; Wed, 11 Dec 1996 15:56:03 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA20097 for ; Wed, 11 Dec 1996 15:55:59 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Wed, 11 Dec 1996 16:54:06 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 11 Dec 1996 16:53:41 -0700 From: Darren Davis To: jfieber@indiana.edu, mark@quickweb.com Cc: hackers@freebsd.org, nate@mt.sri.com Subject: Re: Marimba for FreeBSD... -Reply Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a good success in running the Marimba stuff with the castanet tuner. The only problem I had was running X in 16bpp mode. I switched to 32bpp and it works great. The appletviewer works fine with my simple java applets. Darren From owner-freebsd-hackers Wed Dec 11 16:06:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA21654 for hackers-outgoing; Wed, 11 Dec 1996 16:06:33 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA21643 for ; Wed, 11 Dec 1996 16:06:28 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id QAA01862 for ; Wed, 11 Dec 1996 16:06:27 -0800 (PST) Date: Wed, 11 Dec 1996 16:06:27 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: Bug in netstat -r Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 2.2-current (from August or so). Or at least I consider it a bug. If you have a DNS entry that matches a /etc/networks entry, the DNS IN-ADDR lookup takes preference over the /etc/networks entry even when showing the route to a network as opposed to a host. Seems to me that when showing a G entry, it should always show either IP address or the /etc/networks entry. Or am I missing something? For example: net1801/27 med-pm9 UGSc 0 2942376 ep1 => net1801 med-pm9 UGc 0 3555 ep1 med-0002.dip med-pm10 UGH 0 0 ep1 => med-0002.dip/27 med-pm10 UGSc 0 406135 ep1 med-0002.dip should be net1802 defined in /etc/networks. net1801 works, because I have no inverse lookup for my .0 entry. From owner-freebsd-hackers Wed Dec 11 16:23:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA22913 for hackers-outgoing; Wed, 11 Dec 1996 16:23:47 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA22897 for ; Wed, 11 Dec 1996 16:23:41 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id TAA03815; Wed, 11 Dec 1996 19:20:12 -0500 (EST) Date: Wed, 11 Dec 1996 19:20:12 -0500 (EST) From: John Fieber Reply-To: John Fieber To: Nate Williams cc: Darren Davis , hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: <199612112340.QAA14658@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Nate Williams wrote: > It works fine on a pre-ALPHA system and a 2.1.6.1 system, as well as a > 2.2 system from last week and a -current system. Okay, good. Three responses so far confirming that it does work on systems like mine, but apparently not *exactly* like mine. So, where lies the crutial difference? Would a ktrace dump help anyone figure this out? It really doesn't get very far at all before crashing. It loads some libraries (m, Xt, Xext, X11, and c), tries to read /etc/malloc.conf (which doesn't exist), does a getrlimit, setrlimit, sigprocmask, sigaction, sigprocmask, break, break and crashes displaying: SIGSEGV 11* segmentation violation sig 11, code 12 or 0xc, sc 0xefbfd3a4, addr 0x1c Full thread dump: Is there anything in the kernel config that could affect it one way or another? -john From owner-freebsd-hackers Wed Dec 11 16:46:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA24343 for hackers-outgoing; Wed, 11 Dec 1996 16:46:27 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA24336 for ; Wed, 11 Dec 1996 16:46:23 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id RAA06026 for hackers@freebsd.org; Wed, 11 Dec 1996 17:46:20 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id RAA02294 for ; Wed, 11 Dec 1996 17:45:49 -0700 (MST) Date: Wed, 11 Dec 1996 17:45:49 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hackers@freebsd.org Subject: TCP FIN/ACK storm oddity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We ran into a situation with a FreeBSD-stable box and an Ascend MAX 4000 router that was somewhat odd. The MAX has a pretty little full screen display that is constantly updated with status information. I telnetted to the MAX from the freebsd box, and then suspended the telnet session and forgot about it, leaving it stopped in the background on the FreeBSD box. A few hours later, I remembered it and brought it back to the foreground. It started displaying a whole bunch of updates very quickly then, as expected, died because it had been suspended too long. After it died, I observed a flood of packets such as the following on the ethernet: 16:31:46.852314 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack 490176104 win 2048 16:31:46.852489 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] 16:31:46.853961 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack 490176104 win 2048 16:31:46.855045 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] 16:31:46.855161 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack 490176104 win 2048 16:31:46.855364 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] 16:31:46.856240 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack 490176104 win 2048 16:31:46.856503 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] futurity is the MAX, darkly is the FreeBSD box. A tcpdump -w stored a dozen megs of this in a couple of minutes. It looks like darkly is trying to close the connection to futurity, so it is sending a FIN. It then gets an ACK back from futurity, as it should. However, why does darkly send another FIN? Shouldn't it then shutup and let things close? Should futurity be ignoring any more FINs it gets after the first one? The other possibility is that the connection is already closed on darkly, and futurity is the one trying to send an ACK. However I don't see why darkly would send a FIN in response to an ACK for a connection it no longer knew anything about; it should send a RST from my reading of things. Unfortunately I don't know exactly what state the connection was in on the FreeBSD box while this was happening. After a few minutes of this, I put a packet filter in on the FreeBSD box to stop the packets and the storm died. Any ideas? From owner-freebsd-hackers Wed Dec 11 20:40:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA12863 for hackers-outgoing; Wed, 11 Dec 1996 20:40:43 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA12851; Wed, 11 Dec 1996 20:40:38 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612120440.UAA12851@freefall.freebsd.org> Subject: Re: Marimba for FreeBSD... To: jfieber@indiana.edu Date: Wed, 11 Dec 1996 20:40:38 -0800 (PST) Cc: nate@mt.sri.com, DARREND@novell.com, hackers@freebsd.org In-Reply-To: from "John Fieber" at Dec 11, 96 07:20:12 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber wrote: > > On Wed, 11 Dec 1996, Nate Williams wrote: > > > It works fine on a pre-ALPHA system and a 2.1.6.1 system, as well as a > > 2.2 system from last week and a -current system. > > Okay, good. Three responses so far confirming that it does work > on systems like mine, but apparently not *exactly* like mine. > So, where lies the crutial difference? > > Would a ktrace dump help anyone figure this out? It really > doesn't get very far at all before crashing. It loads some > libraries (m, Xt, Xext, X11, and c), tries to read > /etc/malloc.conf (which doesn't exist), does a getrlimit, > setrlimit, sigprocmask, sigaction, sigprocmask, break, break and > crashes displaying: > > SIGSEGV 11* segmentation violation > sig 11, code 12 or 0xc, sc 0xefbfd3a4, addr 0x1c John, Marimba seems to be very picky about where java is installed. I had installed jdk102.11-26.tar.gz to /usr/local/share/java. marimba would not run, could not find the Thread class. I edited the tuner shell script (added the location of the Thread class to the end of the CLASSPATH variable). then it started dumping a trace and seg faulting, just like you experienced. I moved java to /usr/local/java and NOW it works. initial start up seems cranky. had to rm the files in ~/.marimba a couple times to get the tuner to perform its initial installation configuration stuff and then update itself. initial config is (to the best of my memory) entering your name and email address specifing a http proxy (if there is one) specifing a *marimba* proxy (if there is one) downloading the newest version (1.2Mb [sic]) processing the update (some changes were made) > when all is finished the "tuner" window appears--empty just two shades of gray, darker across the top (ala menu bar) and lighter in the remainder of the window. rm'ed the files in ~/.marimba again, and restarted the tuner entered all the info again and now i have a populated tuner window that works. so,,,,i guess you just have to keep pushing on it and it does work in the end ;) i still have some bogons however....it wants a different version of one of the X libraries ...so.6.1.in place of ...so.6.0 my libmarimba.so has bad magic bad magic number in "/home/jmb/tmp/marimba/tuner/lib/libmarimba.so" (/home/jmb/tmp/marimba/tuner/lib/libmarimba.so) java.lang.UnsatisfiedLinkError: no marimba in shared library path at java.lang.Runtime.loadLibrary(Runtime.java) at java.lang.System.loadLibrary(System.java) at marimba.desktop.FileSystem.(FileSystem.java:254) .... jmb From owner-freebsd-hackers Wed Dec 11 20:56:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14770 for hackers-outgoing; Wed, 11 Dec 1996 20:56:45 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA14764 for ; Wed, 11 Dec 1996 20:56:42 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id XAA05102; Wed, 11 Dec 1996 23:56:41 -0500 (EST) Date: Wed, 11 Dec 1996 23:56:40 -0500 (EST) From: John Fieber To: "Jonathan M. Bresler" cc: hackers@freebsd.org Subject: Re: Marimba for FreeBSD... In-Reply-To: <199612120440.UAA12851@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Jonathan M. Bresler wrote: > Marimba seems to be very picky about where java is installed. > > I had installed jdk102.11-26.tar.gz to /usr/local/share/java. > marimba would not run, could not find the Thread class. For kicks I moved jdk to /usr/local/share/java (was /usr/local/java) to no avail. Ktrace shows that it is basically crashing upon engine start, before takeoff, *long* before it would even consider looking for a class. -john From owner-freebsd-hackers Wed Dec 11 21:15:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA16639 for hackers-outgoing; Wed, 11 Dec 1996 21:15:37 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA16633 for ; Wed, 11 Dec 1996 21:15:32 -0800 (PST) Received: by agora.rdrop.com (Smail3.1.29.1 #17) id m0vY3UT-0008vHC; Wed, 11 Dec 96 21:15 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: PC CARD stuff To: nate@mt.sri.com (Nate Williams) Date: Wed, 11 Dec 1996 21:15:25 -0800 (PST) Cc: hackers@freefall.freebsd.org, pst@shockwave.com In-Reply-To: <199612111845.LAA13353@rocky.mt.sri.com> from "Nate Williams" at Dec 11, 96 11:45:15 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Are you running 2.1.6.1 on it? I don't think so, but I'll upgrade and give it a try. > Hey, that's not true. :) > Our speed limit is 'Safe and Prudent', which in reality kicks in about > 80 mph. Just quoting Motorola :-) I did enjoy driving "safely and prudently" there a few months ago... -- Alan Batie ______ batie@agora.rdrop.com \ / Assimilate this! +1 503 452-0960 \ / --Worf, First Contact DE 3C 29 17 C0 49 7A 27 \/ 40 A5 3C 37 4A DA 52 B9 It is my policy to avoid purchase of any products from companies which use unrequested email advertisements or telephone solicitation. From owner-freebsd-hackers Wed Dec 11 21:32:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA18528 for hackers-outgoing; Wed, 11 Dec 1996 21:32:09 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA18479 for ; Wed, 11 Dec 1996 21:32:01 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id GAA20816; Thu, 12 Dec 1996 06:31:50 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA15036; Thu, 12 Dec 1996 06:31:25 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id CAA17825; Thu, 12 Dec 1996 02:01:40 +0100 (CET) Message-ID: Date: Thu, 12 Dec 1996 02:01:40 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-hackers@freebsd.org (FreeBSD Hackers' list) Cc: Ollivier.Robert@eurocontrol.fr (Ollivier Robert) Subject: Re: Fwd: CVSup with SSH References: X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 In-Reply-To: ; from Marc Slemko on Dec 11, 1996 11:03:55 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Marc Slemko: > Why not modify your cvs-supfile.cvsup to use localhost instead of > freefall? If it stores any state data locally on a per-hostname basis it I did. CVSup still wants to connect to freefall directly for its second connection... My goal is: SSH link 22 5998 -----\___________________________________/----> 5998 5999 -----/ \----> 5999 localhost freefall 5998-5999 is the default mentionned in cvsup.1 but it still tries to connect to freefall. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-hackers Wed Dec 11 21:46:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA19610 for hackers-outgoing; Wed, 11 Dec 1996 21:46:22 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA19600 for ; Wed, 11 Dec 1996 21:46:16 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id VAA14560; Wed, 11 Dec 1996 21:46:10 -0800 (PST) Message-Id: <199612120546.VAA14560@austin.polstra.com> To: mrcpu@cdsnet.net Subject: Re: CVSUP dying Newsgroups: polstra.freebsd.hackers In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Wed, 11 Dec 1996 21:46:10 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article Jaye Mathisen writes: > > trying to sup -current. > > Edit src/release/sysinstall/nfs.c > Add delta 1.12 96.12.11.09.35.04 jkh > Edit src/release/sysinstall/package.c > Add delta 1.50 96.12.11.09.35.04 jkh > @" > Invalid list > file: Invalid integer "~p U|! > > > (Lots of binary characters after that jkh, somehitng about > /usr/sup/src-lib/checkouts.cvs:. Invalid list file: Invalid Integer. It's best to send (or cc) questions like this to "cvsup-bugs@polstra.com". I can usually help, but I don't always keep up with the mailing lists. Anyway, to answer your question, your list file "/usr/sup/src-lib/checkouts.cvs:." is apparently spammed. You can check the file by looking at it with an editor. It's a plain text file and you'll be able to see that it's damaged, I have a feeling. Assuming the list file is damaged, you can just delete it and then re-run CVSup. (But see below.) It will create a new one for you. It's much more efficient to have a list file, but it's not essential for correct operation. In the next CVSup release, I'll fix the error message so that it doesn't try to print out the invalid thing it got. The other question is, how did the file get damaged? I would be surprised if CVSup itself damaged it. It first writes the information to a temporary file, and only renames it after it's been completely and successfully written. Have you noticed any console messages about disk errors lately? If you find that the file in question contains a bad block, _don't_ remove it. Instead, rename it to something else, then fix your bad blocks, then delete the file after that. Otherwise, you'll just release the bad block back into the free list where it could cause further problems. (Been there, done that.) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Wed Dec 11 22:11:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA21497 for hackers-outgoing; Wed, 11 Dec 1996 22:11:21 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA21488 for ; Wed, 11 Dec 1996 22:11:17 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id WAA25631; Wed, 11 Dec 1996 22:11:10 -0800 (PST) To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-hackers@freebsd.org (FreeBSD Hackers' list), Ollivier.Robert@eurocontrol.fr (Ollivier Robert) Subject: Re: Fwd: CVSup with SSH In-reply-to: Your message of "Thu, 12 Dec 1996 02:01:40 +0100." Date: Wed, 11 Dec 1996 22:11:10 -0800 Message-ID: <25627.850371070@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I did. CVSup still wants to connect to freefall directly for its second > connection... Weird. And I assume that you're not mentioning freefall explicitly anywhere? You've got host=localhost in your supfile? (Right?? :-) Jordan > > My goal is: > SSH link 22 > 5998 -----\___________________________________/----> 5998 > 5999 -----/ \----> 5999 > > localhost freefall > > 5998-5999 is the default mentionned in cvsup.1 but it still tries to > connect to freefall. > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-hackers Wed Dec 11 22:22:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA22345 for hackers-outgoing; Wed, 11 Dec 1996 22:22:16 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22337 for ; Wed, 11 Dec 1996 22:22:14 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id WAA14772; Wed, 11 Dec 1996 22:19:43 -0800 (PST) Message-Id: <199612120619.WAA14772@austin.polstra.com> To: roberto@eurocontrol.fr Subject: Re: Fwd: CVSup with SSH Newsgroups: polstra.freebsd.hackers In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Wed, 11 Dec 1996 22:19:42 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier ROBERT writes: > [I sent this to -hubs which is probably not the right list] Cvsup-bugs@polstra.com (and optionally -hackers) would be best. > I'm behind a firewall and I can't use SOCKS. I'd like to use the port > forwarding features of SSH (the 22 port is open) with CVSup. Has anyone > tried the same setup ? > > I've tried > > ssh -L 5999:freefall.freebsd.org:5999 -L 5998:freefall.freebsd.org:5998 > freefall.freebsd.org > > and > > cvsup -L 1 -g -p 5999 -P - cvs-supfile.cvsup > > but it still tries to connect to freefall directly: I've been thinking this over. I don't think it can be made to work with the current release of CVSup. I have an idea about how to enhance CVSup so that it will be possible. I'll see if I can implement it soon. John From owner-freebsd-hackers Wed Dec 11 22:31:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA22969 for hackers-outgoing; Wed, 11 Dec 1996 22:31:38 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA22964 for ; Wed, 11 Dec 1996 22:31:33 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id XAA20591 for hackers@freebsd.org; Wed, 11 Dec 1996 23:31:32 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id XAA03818 for ; Wed, 11 Dec 1996 23:31:08 -0700 (MST) Date: Wed, 11 Dec 1996 23:31:08 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hackers@freebsd.org Subject: CVS branch update oddity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, so I do a cvs checkout -rRELENG_2_1_0 src Why can't I use a cvs update -dP src to keep it up to date? If I try, it will bring in newly created directories in other branches. If I use cvs update -dP -rRELENG_2_1_0 src it seems to work as expected but, in general, the -r flag to checkout is supposed to be sticky. The man page seems to imply that I should not need to specify the -r for the update. This is using cvs 1.6.3pl2, which is what is in -stable. It may well just be a bogon in the old version, but didn't notice a mention of the problem being fixed in the ChangeLog for the current version... From owner-freebsd-hackers Wed Dec 11 22:41:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA23554 for hackers-outgoing; Wed, 11 Dec 1996 22:41:48 -0800 (PST) Received: (from hsu@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA23548 for hackers; Wed, 11 Dec 1996 22:41:47 -0800 (PST) Date: Wed, 11 Dec 1996 22:41:47 -0800 (PST) From: Jeffrey Hsu Message-Id: <199612120641.WAA23548@freefall.freebsd.org> To: hackers Subject: Re: Marimba for FreeBSD... Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I modified the Marimba scripts to look in /usr/local/java for the FreeBSD JDK. If you've untar'ed the FreeBSD JDK in some other directory, just make a soft link to point to your directory. If you have CLASSPATH problems, look in the archive for my explanation of CLASSPATH resolution process. I sent it out to -hackers and -questions, but no longer have a copy. From owner-freebsd-hackers Wed Dec 11 23:16:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA25467 for hackers-outgoing; Wed, 11 Dec 1996 23:16:58 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA25462 for ; Wed, 11 Dec 1996 23:16:55 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id HAA07265; Thu, 12 Dec 1996 07:16:43 GMT Date: Thu, 12 Dec 1996 16:16:43 +0900 (JST) From: Michael Hancock To: Marc Slemko cc: hackers@freebsd.org Subject: Re: CVS branch update oddity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Marc Slemko wrote: > Ok, so I do a > cvs checkout -rRELENG_2_1_0 src > > Why can't I use a > cvs update -dP src > > to keep it up to date? If I try, it will bring in newly created > directories in other branches. If I use > cvs update -dP -rRELENG_2_1_0 src > > it seems to work as expected but, in general, the -r flag to checkout is > supposed to be sticky. The man page seems to imply that I should not need > to specify the -r for the update. I had a similar problem. My .cvsrc file had a update -A in it that caused it to ignore sticky tags. If you want to be sure put the following into your .cvsrc file: update -P -rRELENG_2_1_0 Regards, Mike From owner-freebsd-hackers Wed Dec 11 23:51:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA27078 for hackers-outgoing; Wed, 11 Dec 1996 23:51:07 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA27073 for ; Wed, 11 Dec 1996 23:51:04 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA03181 for ; Thu, 12 Dec 1996 08:52:42 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id JAA25514 for freebsd-hackers@freefall.cdrom.com; Thu, 12 Dec 1996 09:05:27 +0100 (MET) Date: Thu, 12 Dec 1996 09:05:27 +0100 (MET) From: Christoph Kukulies Message-Id: <199612120805.JAA25514@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: ccd - some measurements Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yesterday I finally got my ccd drive working. I have slow but cheap SCSI disks and I thought I'd invest in future and put in two ncr/pci controllers, with one drive attached to each (for the first). Then I ran a batch job #!/bin/sh for i in 8 10 12 14 16 18 20 22 24 26 28 30 32 40 48 56 64 72 80 96 do umount /a 2>&1 >/dev/null ccdconfig -U ccdconfig ccd0c $i none /dev/sd0e /dev/sd1e newfs /dev/rccd0c 2>&1 >/dev/null mount /dev/ccd0c /a cd /a bonnie 2>&1 >/root/$i.result cd / umount /a done which tested the ccd performance with different interleave factors using bonnie. The results are below. I didn't yet get higher than an interleave of 96. I didn't expect that the results did still grow beyonf and interleave of 32 anyway. So I tend to think that benchmarking the ccd with bonnie that way might be questionable. Also strange the high CPU percentage which I would expect with a PCI busmaster DMA driven controller/transfer. Quantum Atlas 2GB, PPRO-200/256, 32MB Bonnie result: -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU PPRO 100 5006 43.3 4959 11.3 2290 6.3 5022 43.7 4890 7.0 87.1 1.9 CCD Amd K5/PR-133, two ncr/pci controllers, 2 Quantum Tempest 3.2 GB (slow) I/L 8 100 2103 39.5 2118 10.9 828 7.0 2555 39.6 2324 13.6 58.9 4.3 12 100 2151 36.7 2160 10.4 968 8.0 3305 50.4 3067 17.0 59.1 4.3 10 100 2209 39.4 2231 11.4 934 7.9 2940 45.1 2682 15.2 61.3 4.6 18 100 2304 38.1 2290 10.8 1118 9.3 4182 64.4 3899 21.8 60.9 4.2 14 100 2415 41.2 2436 12.3 1020 8.7 3568 54.5 3293 18.1 60.5 4.3 20 100 2494 41.6 2525 12.0 1158 9.9 4523 68.6 4227 24.2 62.8 4.3 22 100 2559 42.0 2580 11.7 1153 9.6 4583 69.9 4527 24.8 64.3 4.4 16 100 2749 47.1 2790 13.2 1148 9.7 4150 62.8 3892 21.5 68.0 3.9 24 100 2760 45.8 2787 12.8 1197 10.4 4921 74.6 4900 26.9 66.0 4.2 26 100 2783 45.8 2814 13.3 1257 10.7 4962 74.9 4734 26.2 63.0 4.1 40 100 2853 45.0 2851 12.5 1416 11.5 5465 82.2 5256 28.9 67.3 4.2 28 100 2920 48.1 2941 13.7 1283 10.9 5224 79.2 4946 27.5 64.5 4.2 48 100 2934 46.5 2959 12.9 1657 13.5 5555 83.9 5340 29.8 67.8 4.0 30 100 3094 50.8 3133 14.2 1333 10.9 5370 81.2 5138 27.5 64.3 4.2 56 100 3210 51.7 3258 14.6 1737 14.2 5772 87.2 5643 31.2 68.4 4.2 32 100 3271 53.3 3322 14.8 1469 12.2 5241 78.7 5067 27.5 68.7 4.0 72 100 3552 56.6 3641 16.0 1963 15.9 5829 86.3 5651 29.8 67.7 4.1 80 100 3643 57.7 3679 16.1 2102 16.7 6113 90.5 5884 31.5 69.2 4.0 64 100 3657 57.8 3669 15.9 2153 17.7 6417 95.2 6430 34.5 69.2 4.1 96 100 4312 69.6 4404 19.7 2414 19.5 6359 93.6 6486 34.4 67.8 4.1 --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Thu Dec 12 00:53:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA00572 for hackers-outgoing; Thu, 12 Dec 1996 00:53:14 -0800 (PST) Received: from Guard.Polynet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA00566 for ; Thu, 12 Dec 1996 00:52:48 -0800 (PST) Received: (from smap@localhost) by Guard.Polynet.Lviv.UA (8.7.5/8.6.12) id KAA11856 for ; Thu, 12 Dec 1996 10:52:24 +0200 (EET) Received: from netsurfer.lp.lviv.ua(192.168.0.3) by Guard.Polynet.Lviv.UA via smap (V2.0beta) id xma011851; Thu, 12 Dec 96 10:52:23 +0200 Received: (from pam@localhost) by NetSurfer.lp.lviv.ua (8.7.5/8.6.12) id KAA08655 for hackers@freefall.freebsd.org; Thu, 12 Dec 1996 10:51:20 +0200 (EET) From: Adrian Pavlykevych Message-Id: <199612120851.KAA08655@NetSurfer.lp.lviv.ua> Subject: [Q] Does XFree86 run on SIS 6205 based card To: hackers@freefall.freebsd.org Date: Thu, 12 Dec 1996 10:51:19 +0000 (EET) In-Reply-To: <199612120717.XAA25476@freefall.freebsd.org> from "owner-hackers-digest@freefall.freebsd.org" at Dec 11, 96 11:17:00 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi everybody, Has anybody luck running X on machine equipped with SIS 6205 Share memory VGA controller. It supports up to 2MB memory and up to 1024x768 16bpp It is rather strange beast - uses usual system memory as video, but good performer. (at least it beats S3 Virge easily). It is somehow :-) compatible with TSENG W32. I tried XF_SVGA and XF_W32 servers but had no luck in setting monitor timings (no sync on screen - sometimes I've got couple of interleaving screens or similar output) Can somebody give an advice? TIA, Adrian Pavlykevych From owner-freebsd-hackers Thu Dec 12 04:12:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA08932 for hackers-outgoing; Thu, 12 Dec 1996 04:12:01 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA08911 for ; Thu, 12 Dec 1996 04:11:51 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA01522; Thu, 12 Dec 1996 12:35:43 +0100 From: Luigi Rizzo Message-Id: <199612121135.MAA01522@labinfo.iet.unipi.it> Subject: Weird bug in /etc/group -related library functions To: hackers@freebsd.org Date: Thu, 12 Dec 1996 12:35:43 +0100 (MET) Cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, yesterday we have experienced a weird bug related to an invalid /etc/group. I'll submit a PR as soon as I have more detailed info, but the thing was as follows: 1) by mistake an invalid line was inserted in /etc/group. But we did not know... 2) our system (basically running 2.1R) started giving "Memory error" and killing processes on Signal 11 This happened on reboot as well, and on both statically and dynamically linked programs (but we realized this late...) 3) suspecting some hw problem in the system, we started the usual, painful sequence of swapping memory, cache, motherboard, and all possible hardware on the system. Finally, replacing the disk with another one with a fresh install of FreeBSD we found that the hw was working. 4) suspecting some corrupt libraries we replaced them and all the faulting programs, but without result. It took a while to figure out where the problem was: a corrupt line in /etc/group. Any idea on what routine can be at fault ? Among the programs giving Memory fault - signal 11 there were quotacheck, sendmail, and possibly login (it was not possible to log into the system). It sounds like a nasty bug in some library code related to the parsing of /etc/group Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Thu Dec 12 05:46:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA12740 for hackers-outgoing; Thu, 12 Dec 1996 05:46:39 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA12735 for ; Thu, 12 Dec 1996 05:46:35 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id OAA20938; Thu, 12 Dec 1996 14:44:36 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id OAA03415; Thu, 12 Dec 1996 14:44:52 +0100 (MET) Message-Id: <3.0.32.19961212144449.00912810@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 12 Dec 1996 14:44:51 +0100 To: Luigi Rizzo From: Eivind Eklund Subject: Re: Weird bug in /etc/group -related library functions Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:35 PM 12/12/96 +0100, Luigi Rizzo wrote: >Hi, > >yesterday we have experienced a weird bug related to an invalid >/etc/group. I'll submit a PR as soon as I have more detailed info, but >the thing was as follows: >1) by mistake an invalid line was inserted in /etc/group. But we > did not know... [description of extremely unstable system deleted] We had the same problem once - however, that wasn't with a garbage line, it was with a line containing user-id's not registered at that machine. (Both the group and the passwd file was copied from another server, and then a lot of accounts were deleted) I didn't report it back then, as the problem occurred in a snapshot, and the box was a bit unstable anyway (bad motherboard). But the problem was defineatly there. (This was a snapshot of current a while before 2.1.5 was released, for anybody wanting more specifics) -- Eivind Eklund gopher://nic.follonett.no:79/0eivind Work: eivind@dimaga.com http://www.dimaga.com/ Home: perhaps@yes.no http://maybes.yes.no/perhaps/ All of the above is a product of either your or my imagination, and not official. From owner-freebsd-hackers Thu Dec 12 05:52:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA13089 for hackers-outgoing; Thu, 12 Dec 1996 05:52:38 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA13076; Thu, 12 Dec 1996 05:52:36 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612121352.FAA13076@freefall.freebsd.org> Subject: Re: Marimba for FreeBSD... To: jfieber@indiana.edu (John Fieber) Date: Thu, 12 Dec 1996 05:52:35 -0800 (PST) Cc: hackers@freebsd.org In-Reply-To: from "John Fieber" at Dec 11, 96 11:56:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber wrote: > > On Wed, 11 Dec 1996, Jonathan M. Bresler wrote: > > > Marimba seems to be very picky about where java is installed. > > > > I had installed jdk102.11-26.tar.gz to /usr/local/share/java. > > marimba would not run, could not find the Thread class. > > For kicks I moved jdk to /usr/local/share/java (was > /usr/local/java) to no avail. Ktrace shows that it is basically > crashing upon engine start, before takeoff, *long* before > it would even consider looking for a class. it should be in /usr/local/java sorry, i should have stated that (sigh) can you compile and run other java apps? there are a variety available at gamelan and ora jmb From owner-freebsd-hackers Thu Dec 12 07:30:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA16939 for hackers-outgoing; Thu, 12 Dec 1996 07:30:57 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA16933 for ; Thu, 12 Dec 1996 07:30:51 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id QAA10231 for ; Thu, 12 Dec 1996 16:30:18 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vYD5J-0001zWC; Thu, 12 Dec 96 16:30 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA154004578; Thu, 12 Dec 1996 16:29:38 +0100 From: "Hr.Ladavac" Message-Id: <199612121529.AA154004578@ws2301.gud.siemens.co.at> Subject: Re: ccd - some measurements To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Thu, 12 Dec 1996 16:29:38 +0100 (MEZ) Cc: freebsd-hackers@freefall.freebsd.org In-Reply-To: <199612120805.JAA25514@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Dec 12, 96 09:05:27 am X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk E-mail message from Christoph Kukulies contained: > > > > Quantum Atlas 2GB, PPRO-200/256, 32MB > > Bonnie result: > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > PPRO 100 5006 43.3 4959 11.3 2290 6.3 5022 43.7 4890 7.0 87.1 1.9 ^^^^ ^^^^ These percentages are bad. Should be higher. It means that the machine is IO limited even in the per char test which does getchar() and should be CPU limited instead. This thing needs a faster disk or ccd *badly* > > > > CCD Amd K5/PR-133, two ncr/pci controllers, 2 Quantum Tempest 3.2 GB (slow) > > I/L > 8 100 2103 39.5 2118 10.9 828 7.0 2555 39.6 2324 13.6 58.9 4.3 > 12 100 2151 36.7 2160 10.4 968 8.0 3305 50.4 3067 17.0 59.1 4.3 > 10 100 2209 39.4 2231 11.4 934 7.9 2940 45.1 2682 15.2 61.3 4.6 > 18 100 2304 38.1 2290 10.8 1118 9.3 4182 64.4 3899 21.8 60.9 4.2 > 14 100 2415 41.2 2436 12.3 1020 8.7 3568 54.5 3293 18.1 60.5 4.3 > 20 100 2494 41.6 2525 12.0 1158 9.9 4523 68.6 4227 24.2 62.8 4.3 > 22 100 2559 42.0 2580 11.7 1153 9.6 4583 69.9 4527 24.8 64.3 4.4 > 16 100 2749 47.1 2790 13.2 1148 9.7 4150 62.8 3892 21.5 68.0 3.9 > 24 100 2760 45.8 2787 12.8 1197 10.4 4921 74.6 4900 26.9 66.0 4.2 > 26 100 2783 45.8 2814 13.3 1257 10.7 4962 74.9 4734 26.2 63.0 4.1 > 40 100 2853 45.0 2851 12.5 1416 11.5 5465 82.2 5256 28.9 67.3 4.2 > 28 100 2920 48.1 2941 13.7 1283 10.9 5224 79.2 4946 27.5 64.5 4.2 > 48 100 2934 46.5 2959 12.9 1657 13.5 5555 83.9 5340 29.8 67.8 4.0 > 30 100 3094 50.8 3133 14.2 1333 10.9 5370 81.2 5138 27.5 64.3 4.2 > 56 100 3210 51.7 3258 14.6 1737 14.2 5772 87.2 5643 31.2 68.4 4.2 > 32 100 3271 53.3 3322 14.8 1469 12.2 5241 78.7 5067 27.5 68.7 4.0 > 72 100 3552 56.6 3641 16.0 1963 15.9 5829 86.3 5651 29.8 67.7 4.1 > 80 100 3643 57.7 3679 16.1 2102 16.7 6113 90.5 5884 31.5 69.2 4.0 > 64 100 3657 57.8 3669 15.9 2153 17.7 6417 95.2 6430 34.5 69.2 4.1 > 96 100 4312 69.6 4404 19.7 2414 19.5 6359 93.6 6486 34.4 67.8 4.1 ^^^^ ^^^^ Getting better. Okay, it's a slower CPU, but it's still IO limited in getchar(). You can get some more out of the box. /Marino > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > From owner-freebsd-hackers Thu Dec 12 08:58:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA22740 for hackers-outgoing; Thu, 12 Dec 1996 08:58:59 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA22735; Thu, 12 Dec 1996 08:58:55 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id IAA17824 ; Thu, 12 Dec 1996 08:58:44 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id IAA17705; Thu, 12 Dec 1996 08:57:16 -0800 (PST) Message-Id: <199612121657.IAA17705@austin.polstra.com> To: roberto@eurocontrol.fr Subject: Re: Fwd: CVSup with SSH Newsgroups: polstra.freebsd.hackers In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org, marcs@znep.com, jkh@freebsd.org Date: Thu, 12 Dec 1996 08:57:16 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk About running CVSup through a firewall by using SSH port forwarding, I wrote: > I've been thinking this over. I don't think it can be made to work > with the current release of CVSup. Good news, I was wrong! It seems to be possible after all. Here is the recipe: * Invoke ssh with: -L 5999:localhost:5999 -R 6666:localhost:6666 ^^^^...........^^^^ (any free port) Note that it's "-L" in the first one and "-R" in the second one. * Specify "host=localhost" in your cvsupfile. * Invoke cvsup with "-P 6666". I tried a quick test of it between two machines here, and it seemed to work OK. I checked both sides of the link with netstat, and the connections were all set up right through the ssh channel. I did a small update which worked and completed successfully. It definitely needs more thorough testing, though. To work with CVSup, a proxy has to be very good about handling some strange communication patterns. For example, it is normal and common that at least one of the 4 unidirectional channels is completely full and blocked by flow control. Yet the other 3 unidirectional channels have to continue to flow unimpeded. If the proxy falls short in that regard, deadlock results. Please let me know how it works out in practice. Here's how the connections are set up under this method: * Client connects to port 5999 on its own host, and that gets forwarded to port 5999 of the server host. Because of the forwarding, both client and server think they're connected to "localhost". * Client sets up a second socket, binds it to "localhost:6666", and listens. * Over the first channel, client instructs server to do a connect to "localhost:6666". * Server does the connect. Because it's "localhost", it connects to its own host rather than the client's host. Sshd is already there, listening for the connection. It forwards the connect to port 6666 on the client host. The key to it working is that localhost has the same address everywhere, but it references different hosts depending on where you are. Thanks to Marc Slemko for the idea! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Thu Dec 12 09:27:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA23876 for hackers-outgoing; Thu, 12 Dec 1996 09:27:16 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA23866 for ; Thu, 12 Dec 1996 09:27:09 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA23073; Thu, 12 Dec 1996 12:22:59 -0500 From: Bill Paul Message-Id: <199612121722.MAA23073@skynet.ctr.columbia.edu> Subject: Re: Weird bug in /etc/group -related library functions To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 12 Dec 1996 12:22:57 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199612121135.MAA01522@labinfo.iet.unipi.it> from "Luigi Rizzo" at Dec 12, 96 12:35:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Luigi Rizzo had to walk into mine and say: > Hi, > > yesterday we have experienced a weird bug related to an invalid > /etc/group. I'll submit a PR as soon as I have more detailed info, but > the thing was as follows: > > 1) by mistake an invalid line was inserted in /etc/group. But we > did not know... > > 2) our system (basically running 2.1R) started giving > "Memory error" and killing processes on Signal 11 > This happened on reboot as well, and on both statically and > dynamically linked programs (but we realized this late...) > > 3) suspecting some hw problem in the system, we started the usual, > painful sequence of swapping memory, cache, motherboard, and all > possible hardware on the system. Finally, replacing the disk with > another one with a fresh install of FreeBSD we found that the hw was > working. > > 4) suspecting some corrupt libraries we replaced them and all the > faulting programs, but without result. > > It took a while to figure out where the problem was: a corrupt line in > /etc/group. Any idea on what routine can be at fault ? Among the > programs giving Memory fault - signal 11 there were quotacheck, > sendmail, and possibly login (it was not possible to log into the > system). It sounds like a nasty bug in some library code related to the > parsing of /etc/group The getgrent(3) module in libc parses /etc/group. But, if this was in 2.1.0-RELEASE, the odds are it's already been fixed (I stomped a couple such bugs after 2.1 came out). If you're going to submit a PR, try to confirm that the bug is still present in 2.1.6.1 or 2.2 (or -current), and be sure to supply a sample /etc/groups line that trips tbe bug. Please don't forget this part: I hate it when people get all up in arms about a showstopper bug and then don't bother showing a decent test case that reproduces it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Thu Dec 12 09:46:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA24885 for hackers-outgoing; Thu, 12 Dec 1996 09:46:09 -0800 (PST) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA24866 for ; Thu, 12 Dec 1996 09:46:05 -0800 (PST) From: Gregory_D_Moncreaff@ccmail.ed.ray.com Received: (mailer@localhost) by gatekeeper.ray.com (8.7.5/8.7.3) id MAA02505; Thu, 12 Dec 1996 12:45:48 -0500 Received: from zeus.ed.ray.com by gatekeeper.ray.com; Thu Dec 12 12:44:24 1996 Received: from ccmail.ed.ray.com by ZEUS.ED.RAY.COM (PMDF V4.2-10 #4335) id <01ICX8P4KM1C00470Y@ZEUS.ED.RAY.COM>; Thu, 12 Dec 1996 12:45:36 EST Date: Thu, 12 Dec 1996 12:28 -0500 (EST) Subject: Re[2]: FreeBSD 2.1: panic: vm_page_free: invalid wire count To: mbarkah@hemi.com Cc: hackers@freebsd.org Message-id: <01ICX8P5WKHY00470Y@ZEUS.ED.RAY.COM> MIME-version: 1.0 Content-transfer-encoding: 7BIT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We got someone to run norton diagnostics on it. It had walking one's RAM test fail. We tried swapping the RAM and it still failed. We swapped out the motherboard and everything was happy. ______________________________ Reply Separator _________________________________ Subject: Re: FreeBSD 2.1: panic: vm_page_free: invalid wire count Author: mbarkah@hemi.com at PMDF Date: 12/7/96 8:40 PM > One of my FreeBSD 2.1 machines died Friday. It got caught > in a panic - reboot loop with the following message: > > panic: vm_page_free: invalid wire count Probably either bad RAM or bad cache. Try swapping your RAM and disabling cache. Regards, -Ade Barkah ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 12 10:20:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA26530 for hackers-outgoing; Thu, 12 Dec 1996 10:20:13 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA26523 for ; Thu, 12 Dec 1996 10:20:10 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id TAA14012 for ; Thu, 12 Dec 1996 19:19:48 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vYFjL-0001zaC; Thu, 12 Dec 96 19:19 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA221754747; Thu, 12 Dec 1996 19:19:07 +0100 From: "Hr.Ladavac" Message-Id: <199612121819.AA221754747@ws2301.gud.siemens.co.at> Subject: 2.1.5-R kernel root on sd0 fails To: hackers@freebsd.org Date: Thu, 12 Dec 1996 19:19:07 +0100 (MEZ) X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I know that 2.1.5 is last year's snow, but: I had a happy installation with one SCSI disk and then had to add a wd0--don't ask why. Subsequently I went to generate a new kernel in order to be able to boot from sd0 without manual keyboard intervention every time. I added kernel root on sd0 swap on sd0 to the config file, re-ran config and had a panic: cannot set sd1 root device. Whatever I tried (I did not delve into config source, though) I could not persuade the kernel to set root to sd0. I did manage it afterwards by hardcoding makedev(4,0) in autoconfig.c and swapgeneric.c as the rootdev, but this is not exactly the solution I sought for. What was I doing wrong? How is config supposed to alter the files in order to enforce "root on ..."? Is it, perhaps, a bug? /Marino From owner-freebsd-hackers Thu Dec 12 10:36:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27081 for hackers-outgoing; Thu, 12 Dec 1996 10:36:42 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27076 for ; Thu, 12 Dec 1996 10:36:37 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id TAA23610 for hackers@freebsd.org; Thu, 12 Dec 1996 19:35:17 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id TAA05198 for ; Thu, 12 Dec 1996 19:32:19 +0100 (MET) Message-Id: <3.0.32.19961212193214.00a34100@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 12 Dec 1996 19:32:16 +0100 To: hackers@freebsd.org From: Eivind Eklund Subject: 2.1.6 on Compaq Prosignia 500 (2.1.5 worked) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to get a 2.1.6 kernel up and running on a Compaq Prosignia 500. To get 2.1.5 running, there were three changes I had to do: (1) Replace i386/isa/pcibus.c with the version from -current, due to PCI V2 handshaking. This seems to work by default in 2.1.6. (2) Move the lnc0 adapter to be detected like this (in config) >device lnc0 at isa? port 0x7000 net irq 3 drq 0 vector lncintr (3) Add >options "MAXMEM=65536" # 64 MB memory due to Compaq (and Dell) using an extremely irritating aspect of the EISA standard, and saying that they have 16MB in RTC-memory. With this in place, it boots fine under 2.1.5. However, under 2.1.6 it detect the ncr0-device in the Prosignia, print >ncr0: restart (scsi reset) and get a kernel trap (supervisor read from address 0x7 at 0xF0176378) On the 2.1.5, it contnues with the next line >ncr0 waiting for scsi-devices to settle I've tried swapping some of the files back to their 2.1.5 counterparts, but this hasn't helped. I've also tried running with the same pcibus.c as I did under 2.1.5 (from -current late August). If this could be of interest, I'm running GCC 2.7.2.1, which I've compiled myself. I haven't yet tried with a GENERIC kernel, as that won't work on this box anyway (I'll loose my network, and as the box is running as a server...) Anybody got any clues? If not, I'll try to track the bug down further, but I don't want to put down the work if somebody know just what's wrong. -- Eivind Eklund gopher://nic.follonett.no:79/0eivind Work: eivind@dimaga.com http://www.dimaga.com/ Home: perhaps@yes.no http://maybes.yes.no/perhaps/ All of the above is a product of either your or my imagination, and not official. From owner-freebsd-hackers Thu Dec 12 11:01:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA28282 for hackers-outgoing; Thu, 12 Dec 1996 11:01:29 -0800 (PST) Received: from phoenix.aristar.com (slip125.winc.com [204.178.182.125]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA28274 for ; Thu, 12 Dec 1996 11:01:20 -0800 (PST) Received: (from mgessner@localhost) by phoenix.aristar.com (8.6.12/8.6.12) id OAA00477 for hackers@freebsd.org; Thu, 12 Dec 1996 14:03:15 -0500 Message-Id: <199612121903.OAA00477@phoenix.aristar.com> Subject: talk and talkd To: hackers@freebsd.org (FreeBSD Hackers) Date: Thu, 12 Dec 1996 14:03:14 -0500 (EST) From: Matthew Gessner Organization: Aristar Software Development, Inc. Reply-To: mgessner@aristar.com X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, all, Why won't talk(1) work out of the box? I have a 2.1.0 machine, and talk mgessner doesn't work even on the same machine. /etc/inetd.conf says to use ntalkd, if that helps. TIA Matt From owner-freebsd-hackers Thu Dec 12 14:06:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA10389 for hackers-outgoing; Thu, 12 Dec 1996 14:06:20 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA10370 for ; Thu, 12 Dec 1996 14:06:16 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA01123 (5.67b/IDA-1.5 for hackers@freefall.freebsd.org); Thu, 12 Dec 1996 23:05:46 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id WAA00724; Thu, 12 Dec 1996 22:18:04 +0100 (MET) From: Wilko Bulte Message-Id: <199612122118.WAA00724@yedi.iaf.nl> Subject: Re: PC CARD stuff To: batie@agora.rdrop.com (Alan Batie) Date: Thu, 12 Dec 1996 22:18:04 +0100 (MET) Cc: nate@mt.sri.com, hackers@freefall.freebsd.org, pst@shockwave.com In-Reply-To: from "Alan Batie" at Dec 11, 96 09:15:25 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Alan Batie wrote... > > Are you running 2.1.6.1 on it? > > I don't think so, but I'll upgrade and give it a try. > > > Hey, that's not true. :) > > Our speed limit is 'Safe and Prudent', which in reality kicks in about > > 80 mph. > > Just quoting Motorola :-) I did enjoy driving "safely and prudently" > there a few months ago... Come over to Germany. They have no speedlimit at all (and act like it..) :-) Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 12 14:06:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA10472 for hackers-outgoing; Thu, 12 Dec 1996 14:06:41 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA10463 for ; Thu, 12 Dec 1996 14:06:38 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA01137 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Thu, 12 Dec 1996 23:06:20 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id XAA01358 for FreeBSD-hackers@freebsd.org; Thu, 12 Dec 1996 23:00:30 +0100 (MET) From: Wilko Bulte Message-Id: <199612122200.XAA01358@yedi.iaf.nl> Subject: looking for freeware SNMP monitoring tools To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Thu, 12 Dec 1996 23:00:30 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there, Maybe slightly off topic but: Is there any freeware SNMP monitoring tool available, preferably usable under FreeBSD? I want to check out SNMP monitoring on some Cabletron MMAC chassis I've obtained for a local hobby club. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Thu Dec 12 14:24:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12122 for hackers-outgoing; Thu, 12 Dec 1996 14:24:58 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12117 for ; Thu, 12 Dec 1996 14:24:52 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id OAA01655; Thu, 12 Dec 1996 14:24:47 -0800 (PST) Message-Id: <199612122224.OAA01655@austin.polstra.com> To: roberto@eurocontrol.fr Cc: hackers@freebsd.org Subject: Re: Fwd: CVSup with SSH In-reply-to: <199612121657.IAA17705@austin.polstra.com> References: <199612121657.IAA17705@austin.polstra.com> Date: Thu, 12 Dec 1996 14:24:38 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Following up once more on using the TCP forwarding of ssh to CVSup through a firewall: > * Invoke ssh with: > > -L 5999:localhost:5999 -R 6666:localhost:6666 > ^^^^...........^^^^ (any free port) > > Note that it's "-L" in the first one and "-R" in the second one. > > * Specify "host=localhost" in your cvsupfile. > > * Invoke cvsup with "-P 6666". I tried a large update (src + ports from several days ago) using this method, and it worked great! I am still astounded. Finally there's a proxy that does what it is supposed to do, and does it right. This should be _really_ useful to those poor souls who haven't been able to get the SOCKS stuff working. I'm going to document it in the manual page and/or the FAQ. (What FAQ?! you ask. I'm workin' on it. ;-) Thanks for this great suggestion! John PS - For best results, disable CVSup's compression (add "-Z" to the command line). Since ssh already compresses, doing it again in CVSup is just a waste of CPU time. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Thu Dec 12 14:35:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA13565 for hackers-outgoing; Thu, 12 Dec 1996 14:35:13 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA13518 for ; Thu, 12 Dec 1996 14:35:08 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id QAA18418; Thu, 12 Dec 1996 16:34:11 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma018409; Thu Dec 12 16:33:55 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id QAA06449; Thu, 12 Dec 1996 16:34:11 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id QAA02971; Thu, 12 Dec 1996 16:34:27 -0600 (CST) Message-Id: <199612122234.QAA02971@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: John Polstra Cc: hackers@freebsd.org Subject: Re: Fwd: CVSup with SSH In-reply-to: Your message of "Thu, 12 Dec 1996 14:24:38 PST." <199612122224.OAA01658@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Dec 1996 16:34:26 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Polstra writes: > >Following up once more on using the TCP forwarding of ssh to CVSup >through a firewall: > > >I tried a large update (src + ports from several days ago) using this >method, and it worked great! I am still astounded. Finally there's a >proxy that does what it is supposed to do, and does it right. Yeay! I just tried the cvs tree, and it looks ok. > >This should be _really_ useful to those poor souls who haven't been >able to get the SOCKS stuff working. I'm going to document it in the ;-) That's me! I whipped up a new fbsd-update script. I had to use expect, unless someone can help me out a bit with ssh from a script: ------------------cut--here----------------------- #!/usr/local/bin/expect set lport 6666 set cvsupfile $env(HOME)/lib/cvs-supfile.cvsup set d [exec date +%v] set cvsup $env(HOME)/var/log/cvsup-$d set cvs_co $env(HOME)/var/log/cvs_co-$d set ssh [spawn ssh -C -v -L 5999:localhost:5999 -R $lport:localhost:$lport freefall] expect "(tty..@freefall)\$ " exec cvsup -Z -g -L 2 -P $lport $cvsupfile >& $cvsup send -- "exit\r" ------------------end--of--script----------------- of course you'll have to edit the freefall prompt. Is there anyway to get this to work without actually logging in? > >John > >- -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > Thanks Tons! eric -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Dec 12 14:51:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14797 for hackers-outgoing; Thu, 12 Dec 1996 14:51:38 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA14785 for ; Thu, 12 Dec 1996 14:51:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA00873; Thu, 12 Dec 1996 23:51:19 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA13637; Thu, 12 Dec 1996 23:51:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA13029; Thu, 12 Dec 1996 23:32:48 +0100 (MET) From: J Wunsch Message-Id: <199612122232.XAA13029@uriah.heep.sax.de> Subject: Re: 2.1.5-R kernel root on sd0 fails To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 12 Dec 1996 23:32:48 +0100 (MET) Cc: lada@ws2301.gud.siemens.co.at (Hr.Ladavac) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612121819.AA221754747@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at "Dec 12, 96 07:19:07 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Hr.Ladavac wrote: > I added > > kernel root on sd0 swap on sd0 This should not be needed, unless you boot with the -r option. > to the config file, re-ran config and had a panic: cannot set sd1 > root device. Ah, wait a minute... you had the IDE drive still enabled in the BIOS? Then it's obvious: you gotta boot with 1:sd(0,a)/kernel Disabling the IDE drive in the BIOS is also an option (you could still use it from BSD anyway). > I did manage it afterwards by hardcoding makedev(4,0) in autoconfig.c > and swapgeneric.c as the rootdev, but this is not exactly the solution ^^^^^^^^^^^^^ > I sought for. swapgeneric.c is only used if you configure your kernel as config kernel swap generic -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Dec 12 14:51:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14836 for hackers-outgoing; Thu, 12 Dec 1996 14:51:51 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA14822 for ; Thu, 12 Dec 1996 14:51:45 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id OAA01790; Thu, 12 Dec 1996 14:51:42 -0800 (PST) Message-Id: <199612122251.OAA01790@austin.polstra.com> To: "Eric L. Hernes" cc: hackers@freebsd.org, roberto@eurocontrol.fr Subject: Re: Fwd: CVSup with SSH In-reply-to: Your message of "Thu, 12 Dec 1996 16:34:26 CST." <199612122234.QAA02971@jake.lodgenet.com> References: <199612122234.QAA02971@jake.lodgenet.com> Date: Thu, 12 Dec 1996 14:51:42 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yeay! I just tried the cvs tree, and it looks ok. > > >This should be _really_ useful to those poor souls who haven't been > >able to get the SOCKS stuff working. I'm going to document it in the > ;-) That's me! All _right_! You've been one of my toughest cases. ;-) I'm glad there's finally a solution for you. > I whipped up a new fbsd-update script. I had to use expect, unless > someone can help me out a bit with ssh from a script: > ------------------cut--here----------------------- > #!/usr/local/bin/expect > > set lport 6666 One caution: Don't everybody start using 6666, or this thing will never work. It has to be a port that's free on both your local machine and on the server host. If everybody starts using 6666, they'll be colliding before long. Pick some creative individual number. Better yet, make the script choose one semi-randomly. > Is there anyway to get this to work without actually logging in? I was wondering the same thing. Could some ssh expert answer that, please? The only idea I could think of was something like this: ssh -L 5999:localhost:5999 -R $lport:localhost:$lport freefall sleep 3600 and then kill the ssh process with a signal when the update completes. I haven't tried it, though. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Thu Dec 12 15:05:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15826 for hackers-outgoing; Thu, 12 Dec 1996 15:05:26 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA15821 for ; Thu, 12 Dec 1996 15:05:21 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id RAA19925; Thu, 12 Dec 1996 17:04:31 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma019903; Thu Dec 12 17:04:18 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id RAA07094; Thu, 12 Dec 1996 17:04:34 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id RAA07956; Thu, 12 Dec 1996 17:04:50 -0600 (CST) Message-Id: <199612122304.RAA07956@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: John Polstra cc: "Eric L. Hernes" , hackers@freebsd.org, roberto@eurocontrol.fr Subject: Re: Fwd: CVSup with SSH In-reply-to: Your message of "Thu, 12 Dec 1996 14:51:42 PST." <199612122251.OAA01790@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Dec 1996 17:04:49 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Polstra writes: >> set lport 6666 > >One caution: Don't everybody start using 6666, or this thing will never >work. It has to be a port that's free on both your local machine and on >the server host. If everybody starts using 6666, they'll be colliding >before long. Pick some creative individual number. Better yet, make >the script choose one semi-randomly. I thought about that and didn't post the script with my real port in it ;-) > >I was wondering the same thing. Could some ssh expert answer that, >please? > >The only idea I could think of was something like this: > > ssh -L 5999:localhost:5999 -R $lport:localhost:$lport freefall sleep 3600 Yea I thought about that too, but the network between here and freefall is *so* unprediciable that the sleep could end up timing out before the update finished. I guess I could crank the sleep up to something like a couple days... That's why my update script graduated from /bin/sh to expect. > >John >-- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth thanks again. eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Dec 12 15:07:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15961 for hackers-outgoing; Thu, 12 Dec 1996 15:07:20 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA15919 for ; Thu, 12 Dec 1996 15:06:46 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id AAA18362 for ; Fri, 13 Dec 1996 00:06:15 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vYKCa-0001zcC; Fri, 13 Dec 96 00:06 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA208211935; Fri, 13 Dec 1996 00:05:35 +0100 From: "Hr.Ladavac" Message-Id: <199612122305.AA208211935@ws2301.gud.siemens.co.at> Subject: Re: 2.1.5-R kernel root on sd0 fails To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 13 Dec 1996 00:05:35 +0100 (MEZ) Cc: freebsd-hackers@freebsd.org, lada@ws2301.gud.siemens.co.at In-Reply-To: <199612122232.XAA13029@uriah.heep.sax.de> from "J Wunsch" at Dec 12, 96 11:32:48 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk E-mail message from J Wunsch contained: > As Hr.Ladavac wrote: > > > I added > > > > kernel root on sd0 swap on sd0 > > This should not be needed, unless you boot with the -r option. Well, it didn't work anyway. > > > to the config file, re-ran config and had a panic: cannot set sd1 > > root device. > > Ah, wait a minute... you had the IDE drive still enabled in the BIOS? > Then it's obvious: you gotta boot with > > 1:sd(0,a)/kernel Sure, I know that. But it requires manual intervention on *every* boot. > > Disabling the IDE drive in the BIOS is also an option (you could still > use it from BSD anyway). Not on this box (or the owner of the disk would hang me by the balls). She wants to have access to her files and does not like the idea of fiddling with the BIOS configuration. > > > I did manage it afterwards by hardcoding makedev(4,0) in autoconfig.c > > and swapgeneric.c as the rootdev, but this is not exactly the solution > ^^^^^^^^^^^^^ > > I sought for. > > swapgeneric.c is only used if you configure your kernel as > > config kernel swap generic Honestly speaking, I didn't really look into the link list; I just changed it as that was the only place I could find where rootdev and dumpdev are defined. I guess it needs to be linked in. OTOH, your statement implies that the kernel root device configuration option is actually broken. I'll take a look in the config sources, then. /Marino > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-hackers Thu Dec 12 15:09:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA16104 for hackers-outgoing; Thu, 12 Dec 1996 15:09:19 -0800 (PST) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA16099 for ; Thu, 12 Dec 1996 15:09:12 -0800 (PST) Received: from sol1.gud.siemens.co.at (root@[10.1.143.100]) by zwei.siemens.at (8.7.5/8.7.3) with SMTP id AAA18380 for ; Fri, 13 Dec 1996 00:08:44 +0100 (MET) Received: from ws2301.gud.siemens.co.at by sol1.gud.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0vYKEy-0001zcC; Fri, 13 Dec 96 00:08 MET Received: by ws2301.gud.siemens.co.at (1.37.109.16/1.37) id AA214742083; Fri, 13 Dec 1996 00:08:03 +0100 From: "Hr.Ladavac" Message-Id: <199612122308.AA214742083@ws2301.gud.siemens.co.at> Subject: Re: PC CARD stuff To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Fri, 13 Dec 1996 00:08:03 +0100 (MEZ) Cc: batie@agora.rdrop.com, nate@mt.sri.com, hackers@freefall.freebsd.org, pst@shockwave.com In-Reply-To: <199612122118.WAA00724@yedi.iaf.nl> from "Wilko Bulte" at Dec 12, 96 10:18:04 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk E-mail message from Wilko Bulte contained: > As Alan Batie wrote... > > > Are you running 2.1.6.1 on it? > > > > I don't think so, but I'll upgrade and give it a try. > > > > > Hey, that's not true. :) > > > Our speed limit is 'Safe and Prudent', which in reality kicks in about > > > 80 mph. > > > > Just quoting Motorola :-) I did enjoy driving "safely and prudently" > > there a few months ago... > > Come over to Germany. They have no speedlimit at all (and act like it..) Eh, the good old times ... in the last months some silly round tables with 130 written on them have been sprouting all over the place. /Marino > > :-) > > Wilko > _ ____________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands > |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda > -------------------------------------------------------------------------- > From owner-freebsd-hackers Thu Dec 12 15:29:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17485 for hackers-outgoing; Thu, 12 Dec 1996 15:29:09 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA17331 for ; Thu, 12 Dec 1996 15:27:38 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA22354 (5.67b/IDA-1.5 for ); Fri, 13 Dec 1996 00:23:53 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id QAA02452; Thu, 12 Dec 1996 16:23:16 +0100 (CET) Message-Id: Date: Thu, 12 Dec 1996 16:21:56 +0100 From: se@freebsd.org (Stefan Esser) To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: ccd - some measurements References: <199612120805.JAA25514@gilberto.physik.rwth-aachen.de> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: <199612120805.JAA25514@gilberto.physik.rwth-aachen.de>; from Christoph Kukulies on Dec 12, 1996 09:05:27 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 12, kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) wrote: > > Yesterday I finally got my ccd drive working. I have slow but cheap > SCSI disks and I thought I'd invest in future and put in two > ncr/pci controllers, with one drive attached to each (for the first). Did you try with both drives connected to one controller, too ? > Then I ran a batch job [ ... ] > which tested the ccd performance with different interleave factors using > bonnie. The results are below. > > I didn't yet get higher than an interleave of 96. I didn't expect that > the results did still grow beyonf and interleave of 32 anyway. So > I tend to think that benchmarking the ccd with bonnie that way might > be questionable. Why ??? > Also strange the high CPU percentage which I would expect with a PCI > busmaster DMA driven controller/transfer. Yes, it seems that the CCD configuration needs a lot more CPU cycles than the single drive. But in order to test for the cycles actually spent in the driver, you have to directly access the raw disk device. And you will most probably find a load in the low percent range, even for very small block sizes. On my ASUS SP3G with an 133MHz AMD 486 CPU (AMD 5x86): # time dd if=/dev/rsd0 of=/dev/null bs=1k count=10000 10240000 bytes transferred in 6.515382 secs (1571665 bytes/sec) 6.59 real 0.09 user 1.79 sys # time dd if=/dev/rsd0 of=/dev/null bs=10k count=1000 10240000 bytes transferred in 2.618192 secs (3911096 bytes/sec) 2.66 real 0.02 user 0.19 sys # time dd if=/dev/rsd0 of=/dev/null bs=32k count=1000 32768000 bytes transferred in 4.923350 secs (6655631 bytes/sec) 4.94 real 0.03 user 0.22 sys This (and further measurements I made) indicate a driver overhead of 177us (incl. kernel call an estimated 25us system call overhead) plus 6.5us per 4KB page transfered. This does not account for the reduced CPU performance (due to reduced memory bandwidth and higher latency, while a DMA transfer is active). For comaprison: The numbers for /dev/zero are 24us + 96us/Page. All these overheads are computed per transfer, of course, and do account for reading the input file and writing to /dev/null, since that is what "dd" does ... (BTW: The user time per transfer comes out a factor of 4 lower when reading from /dev/zero, than from /dev/rsd0. It appears to be some 3.5us per read from /dev/zero, but 12us per read from /dev/rsd0. The user time values are much less reproducable in the latter case, but vary between 7us and 20us. But they are significantly higher than the /dev/zero numbers, anyway ...) > Quantum Atlas 2GB, PPRO-200/256, 32MB > > Bonnie result: > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > PPRO 100 5006 43.3 4959 11.3 2290 6.3 5022 43.7 4890 7.0 87.1 1.9 These numbers are significantly lower than the typical throughput of the Atlas on the outer tracks, so I assume you either used a partition that started far inside, or the file system was mostly full ... > CCD Amd K5/PR-133, two ncr/pci controllers, 2 Quantum Tempest 3.2 GB (slow) > > I/L > 8 100 2103 39.5 2118 10.9 828 7.0 2555 39.6 2324 13.6 58.9 4.3 > 32 100 3271 53.3 3322 14.8 1469 12.2 5241 78.7 5067 27.5 68.7 4.0 > 64 100 3657 57.8 3669 15.9 2153 17.7 6417 95.2 6430 34.5 69.2 4.1 > 96 100 4312 69.6 4404 19.7 2414 19.5 6359 93.6 6486 34.4 67.8 4.1 Hmmm, what is the unit of I/L in this case ? Since the drives spindles are not synchronized and the QM TM has a very small cache, the results might vary quite a lot, depending on the relative angular position of the platters. The AMD 5K86 CPU load per MB/s is about twice that of the PPro/Atlas, and that does not look that wrong to me :) The compute intensive tasks are the buffer management and file system overhead, which is independent of the controller and disk drives used. But since these operations are being performed simultanously to the file data transfers (at least for the read ahead, and also if tags are used), it pays back to have the CPU do them, while the controller does the data transfer on its own (ie. as a bus-master). Although the average load of a PIO controller over the day is not high, it happens to consume cycles exactly when the system is running under a peak load anyway. That's why I still prefer bus-master DMA, no matter how fast the CPU gets ... (And in fact, the relative impact of PIO I/O on the CPU is higher if the CPU is faster. It has to wait for the slow peripheral, and just can't switch back to executing user code, even if the drive can't deliver data fast enough to keep the CPU busy. But it is hard to measure that effect, since the PIO cycles will be accounted to some unrelated program ...) Regards, STefan From owner-freebsd-hackers Thu Dec 12 15:51:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19234 for hackers-outgoing; Thu, 12 Dec 1996 15:51:38 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA19202 for ; Thu, 12 Dec 1996 15:51:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA02322; Fri, 13 Dec 1996 00:51:18 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14633; Fri, 13 Dec 1996 00:51:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA13735; Fri, 13 Dec 1996 00:33:30 +0100 (MET) From: J Wunsch Message-Id: <199612122333.AAA13735@uriah.heep.sax.de> Subject: Re: 2.1.5-R kernel root on sd0 fails To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 00:33:30 +0100 (MET) Cc: lada@ws2301.gud.siemens.co.at (Hr.Ladavac) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612122305.AA208211935@ws2301.gud.siemens.co.at> from "Hr.Ladavac" at "Dec 13, 96 00:05:35 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Hr.Ladavac wrote: > > > kernel root on sd0 swap on sd0 > > > > This should not be needed, unless you boot with the -r option. > > Well, it didn't work anyway. It did work as intended. It didn't work as you expected though. Booting with -r should have got you where you wanted it, but is of course... > > 1:sd(0,a)/kernel > > Sure, I know that. But it requires manual intervention on *every* boot. ...in the same boat with this solution. ``nextboot'' is the projected solution to your problem, but Julian Elischer apparently failed to document how to set it up, and to advocate for its use. You might give it a try, perhaps you can figure out how it works? (Don't ask me though, i don't have disks where i could spare sector 2 for the nextboot information.) > > Disabling the IDE drive in the BIOS is also an option (you could still > > use it from BSD anyway). > > Not on this box (or the owner of the disk would hang me by the balls). > She wants to have access to her files and does not like the idea of > fiddling with the BIOS configuration. ``access to her files'' -- You can _access_ them fine from within FreeBSD, even with the IDE drive disabled. That's probably not what you meant, but it's what you wrote. :) > OTOH, your statement implies that the kernel root device configuration > option is actually broken. I'll take a look in the config sources, then. No, it ain't broken. The root device is _intended_ to be automatically changed to the device where the system has been booted from. (Ever wondered about the ``changing root device to XXX'' message?) Digging into the config sources would only waste your time, since this is a kernel issue, not a matter of config. The bootstrap is indeed the key to your problem. (It passes the struct bootinfo down to the kernel, and this will in turn be the information source for the kernel to learn about its boot device.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Dec 12 15:51:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19299 for hackers-outgoing; Thu, 12 Dec 1996 15:51:52 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA19277 for ; Thu, 12 Dec 1996 15:51:48 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA25773 (5.67b/IDA-1.5 for ); Fri, 13 Dec 1996 00:51:39 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id AAA00797; Fri, 13 Dec 1996 00:51:35 +0100 (CET) Message-Id: Date: Fri, 13 Dec 1996 00:51:35 +0100 From: se@freebsd.org (Stefan Esser) To: lada@ws2301.gud.siemens.co.at (Hr.Ladavac) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies), freebsd-hackers@freefall.freebsd.org Subject: Re: ccd - some measurements References: <199612120805.JAA25514@gilberto.physik.rwth-aachen.de> <199612121529.AA154004578@ws2301.gud.siemens.co.at> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: <199612121529.AA154004578@ws2301.gud.siemens.co.at>; from Hr.Ladavac on Dec 12, 1996 16:29:38 +0100 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 12, lada@ws2301.gud.siemens.co.at (Hr.Ladavac) wrote: > E-mail message from Christoph Kukulies contained: > > Quantum Atlas 2GB, PPRO-200/256, 32MB > > > > Bonnie result: > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > PPRO 100 5006 43.3 4959 11.3 2290 6.3 5022 43.7 4890 7.0 87.1 1.9 > ^^^^ ^^^^ > These percentages are bad. Should be higher. It > means that the machine is IO limited even in the > per char test which does getchar() and should be > CPU limited instead. This thing needs a faster > disk or ccd *badly* No, it seems the test was run on a file system that restricted the data rate to just about 5MB/s. Both the per char and the block I/O results are within a 1% window around 4950KB/s ... There are not so many faster disks than the Atlas (well, the IBM DHCS, the Quantum Atlas II, and the latest Seagate drives seem to go from 10MB/s to 7MB/s sustained, outer to inner tracks). But what is bad about having half the CPU available to do some real work :) If you are doing compilations, then the system has half a PPro-200 for the compiler, while reading the sources at 5MB/s. That's the way it is supposed to be (IMHO) ... > > CCD Amd K5/PR-133, two ncr/pci controllers, 2 Quantum Tempest 3.2 GB (slow) > > > > I/L > > 8 100 2103 39.5 2118 10.9 828 7.0 2555 39.6 2324 13.6 58.9 4.3 > > 96 100 4312 69.6 4404 19.7 2414 19.5 6359 93.6 6486 34.4 67.8 4.1 > ^^^^ ^^^^ > Getting better. Okay, it's a slower CPU, but it's > still IO limited in getchar(). You can get some more > out of the box. Same here: The CPU is usually limiting the per char results, but with CPUs getting faster and faster we just have to get used to have systems, that have cycles left, when all I/O channels are busy. Reading is much faster than writing, here, and I'd try to get the write spead up. But the drives used have very small caches, which don't hold even a single track of data. It is possible that with tags disabled and write caching on (ie. early write success status delivery) the writes will become as fast as reads ... It would be really interesting to compare bonnie throughput with and without tags for this CCD file system ... Gruss, STefan From owner-freebsd-hackers Thu Dec 12 15:52:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19382 for hackers-outgoing; Thu, 12 Dec 1996 15:52:04 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA19270 for ; Thu, 12 Dec 1996 15:51:47 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA02302; Fri, 13 Dec 1996 00:50:41 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA14587; Fri, 13 Dec 1996 00:50:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id AAA13632; Fri, 13 Dec 1996 00:20:54 +0100 (MET) From: J Wunsch Message-Id: <199612122320.AAA13632@uriah.heep.sax.de> Subject: Re: talk and talkd To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 00:20:54 +0100 (MET) Cc: mgessner@aristar.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612121903.OAA00477@phoenix.aristar.com> from Matthew Gessner at "Dec 12, 96 02:03:14 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Matthew Gessner wrote: > Why won't talk(1) work out of the box? I think you need to provide more data. talk is fairly fragile, but nevertheless works (apparently) for most of us out of the box. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Dec 12 15:59:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21094 for hackers-outgoing; Thu, 12 Dec 1996 15:59:10 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA21079; Thu, 12 Dec 1996 15:59:05 -0800 (PST) Received: from ginger.eng.umd.edu (ginger.eng.umd.edu [129.2.103.20]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id SAA23248; Thu, 12 Dec 1996 18:59:02 -0500 (EST) Received: from localhost (chuckr@localhost) by ginger.eng.umd.edu (8.8.3/8.7.3) with SMTP id SAA07601; Thu, 12 Dec 1996 18:59:01 -0500 (EST) X-Authentication-Warning: ginger.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 12 Dec 1996 18:59:01 -0500 (EST) From: Chuck Robey X-Sender: chuckr@ginger.eng.umd.edu To: FreeBSD-Hackers cc: FreeBSD Ports Subject: lint Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does anyone know the parentage of /usr/bin/lint? I'd thought that it originally grew out of lclint, but when I looked at the sources, lclint didn't seem to be listed (it looks like an import from NetBSD). I was wondering, in the light of our new lclint port, I wanted to make sure it _was_ different. Thanks ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Dec 12 16:42:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA26814 for hackers-outgoing; Thu, 12 Dec 1996 16:42:37 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA26737; Thu, 12 Dec 1996 16:41:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA03414; Fri, 13 Dec 1996 01:41:21 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA16137; Fri, 13 Dec 1996 01:41:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id BAA14253; Fri, 13 Dec 1996 01:30:51 +0100 (MET) From: J Wunsch Message-Id: <199612130030.BAA14253@uriah.heep.sax.de> Subject: Re: lint To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 13 Dec 1996 01:30:50 +0100 (MET) Cc: FreeBSD-Hackers@FreeBSD.ORG, FreeBSD-Ports@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Chuck Robey at "Dec 12, 96 06:59:01 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > Does anyone know the parentage of /usr/bin/lint? I'd thought that it > originally grew out of lclint, but when I looked at the sources, lclint > didn't seem to be listed (it looks like an import from NetBSD). It has been written from scratch by Jochen Pohl for the NetBSD project. I'm not sure whether Jochen still maintains it for NetBSD, now that he went out to become a co-founder of his own company. The only reason why it's still not yet enabled in our source tree is since our libc is simply not lintable. :-( Last time i've been checking (around the time i've imported Jochen's lint), there was a type clash between `struct pmap', which describes a connection to the portmapper if used in an RPC context, but is used for some page map stuff in the /usr/include/sys/ header files. Since libc #include's both meanings, lint doesn't pass through. It requires somebody to pick all this lint stuff as his pet project, and cleans up the remaining bogons in the tree. It's quite a little more work than just a weekend to spend though. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Dec 12 16:52:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA27691 for hackers-outgoing; Thu, 12 Dec 1996 16:52:40 -0800 (PST) Received: from tulpi.interconnect.com.au (root@tulpi.interconnect.com.au [192.189.54.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA27681 for ; Thu, 12 Dec 1996 16:52:32 -0800 (PST) Received: from solsbury-hill.home (acc5-ppp37.mel.interconnect.com.au [210.8.0.165]) by tulpi.interconnect.com.au with ESMTP id LAA20264 (8.7.6/IDA-1.6 for ); Fri, 13 Dec 1996 11:52:25 +1100 (EST) Received: from localhost (suttonj@localhost) by solsbury-hill.home (8.7.5/8.7.3) with SMTP id LAA00272 for ; Fri, 13 Dec 1996 11:30:28 +1100 (EST) Date: Fri, 13 Dec 1996 11:30:21 +1100 (EST) From: Joel Sutton X-Sender: suttonj@solsbury-hill.home Reply-To: Joel Sutton To: FreeBSD Hackers Subject: My Banksia Internal Modem - sio driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm sure this is a common subject so I'll try to keep it brief. I'm running 2.1.5 with 4 serial ports - 1 internal modem. Up until today I have been having all sorts of problems getting the sio driver to recognise my internal modem on a regular basis. Sometimes it would recognise it (after numerous reboots) and sometimes not. So I did some searching of the mail archives and realised that I should use the 0x80 flag to see what was happening (should have read the sio man page...). I suddenly found that it was failing consistently on the 6th probe: /kernel: sio1: probe test 6 failed Thinking I had nothing to loose I then changed the source for sio so that the sixth probe always returned a successful result. So far I haven't had any problems more internal modem problems or problems with my other 3 serial ports. Device drivers are definitely way above my level of programming skill so what I'm wondering is - Is it likely that I may create any other problems by doing this? Could adding extra DELAY statements achieve a similar result more cleanly?? Thanks for your patience, Joel... From owner-freebsd-hackers Thu Dec 12 18:22:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA03477 for hackers-outgoing; Thu, 12 Dec 1996 18:22:49 -0800 (PST) Received: from fps.biblos.unal.edu.co ([168.176.37.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA03245 for ; Thu, 12 Dec 1996 18:19:20 -0800 (PST) Received: from unalmodem.usc.unal.edu.co by fps.biblos.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA23130; Thu, 12 Dec 1996 21:23:55 -0500 Message-Id: <32B0E6A6.319D@fps.biblos.unal.edu.co> Date: Thu, 12 Dec 1996 21:16:22 -0800 From: "Pedro Giffuni S." Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: hackers@freeBSD.org Subject: Plug'n Play Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, I don´t know if everyone has this, but I dropped the PnP specification in ftp.freefall.org/pub/incoming/PnP.ps.gz I got it with some "confidential" information from Microsoft, but it is freely distributable. The bad news is that windows 3.1 postscript drivers don´t generate page numbers (if someone really needs it I can try with W95 or OS2, but the first page says how to get that stuff). Pedro. From owner-freebsd-hackers Thu Dec 12 18:34:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA04246 for hackers-outgoing; Thu, 12 Dec 1996 18:34:17 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA04241 for ; Thu, 12 Dec 1996 18:34:14 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vYNRh-0006ro-00; Thu, 12 Dec 1996 19:33:53 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: talk and talkd Cc: freebsd-hackers@freebsd.org (FreeBSD hackers), mgessner@aristar.com In-reply-to: Your message of "Fri, 13 Dec 1996 00:20:54 +0100." <199612122320.AAA13632@uriah.heep.sax.de> References: <199612122320.AAA13632@uriah.heep.sax.de> Date: Thu, 12 Dec 1996 19:33:52 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199612122320.AAA13632@uriah.heep.sax.de> J Wunsch writes: : As Matthew Gessner wrote: : : > Why won't talk(1) work out of the box? : : I think you need to provide more data. talk is fairly fragile, but : nevertheless works (apparently) for most of us out of the box. There are also multiple talk protocols that are used by talk. And the one that Sun uses is not compatible with anybody :-( Warner From owner-freebsd-hackers Thu Dec 12 18:44:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA05373 for hackers-outgoing; Thu, 12 Dec 1996 18:44:48 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA05365 for ; Thu, 12 Dec 1996 18:44:38 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id CAA12318 for ; Fri, 13 Dec 1996 02:44:25 GMT Date: Fri, 13 Dec 1996 11:44:25 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers Subject: Implementing atomic DCAS on Intel for NBS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It doesn't look like the P5 has DCAS which is important for NBS because it wants to atomically manipulate a structure and update it's version number. Here's some pseudo code: int DCAS( int *p1, int *p2, int old1, int old2 int new1, int new2) { if ((*p1 == old1) && (*p2 == old2)) { *p1 = new1; *p2 = new2; return TRUE; } else { return FALSE; } } Is there an an assembler guru out there who can tell us how many instructions would be necessary to implement this for a P5? Here's a link for an R4000 version: http://www-dsg.stanford.edu/papers/non-blocking-osdi/node11.html Regards, Mike Hancock From owner-freebsd-hackers Thu Dec 12 18:58:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA06428 for hackers-outgoing; Thu, 12 Dec 1996 18:58:55 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA06420 for ; Thu, 12 Dec 1996 18:58:51 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA09713; Fri, 13 Dec 1996 13:28:45 +1030 (CST) From: Michael Smith Message-Id: <199612130258.NAA09713@genesis.atrad.adelaide.edu.au> Subject: Re: Novell offers free NDS, just a thought... In-Reply-To: from Darren Davis at "Nov 12, 96 04:06:19 pm" To: DARREND@novell.com (Darren Davis) Date: Fri, 13 Dec 1996 13:28:42 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Darren Davis stands accused of saying: ... > Novell is committed to integrating NDS into all major server > platforms. The company has taken the first step by allowing the NDS > source code to be licensed by industry-leading operating system > providers, royalty-free. The company will also distribute a single server Has anyone followed through on this? The source is obviously not freely available to the public, but I think that the FreeBSD Project counts as an 'industry-leading vendor' in one way or another. 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Dec 12 19:53:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11321 for hackers-outgoing; Thu, 12 Dec 1996 19:53:44 -0800 (PST) Received: from cathouse.vu.com (root@cathouse.vu.com [204.209.156.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA11316; Thu, 12 Dec 1996 19:53:41 -0800 (PST) Received: (from mike@localhost) by cathouse.vu.com (8.8.4/8.8.2) id UAA02506; Thu, 12 Dec 1996 20:55:16 -0700 (MST) Date: Thu, 12 Dec 1996 20:55:16 -0700 (MST) From: Mike Nemeth Message-Id: <199612130355.UAA02506@cathouse.vu.com> To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: want your input for a *BSD-device-driver-writing FAQ Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk as it appears that i'm not going to get any help from the *bsd "experts" in the local geographic area, i would like to solicit information on the writing of device drivers under *BSD for incorporation into a FAQ. if you have experience in writing/debugging device drivers under *BSD, particularly NetBSD 1.1, please forward any information you have found to be of use to driverfaq@cathouse.vu.com thank you! From owner-freebsd-hackers Thu Dec 12 21:47:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA20414 for hackers-outgoing; Thu, 12 Dec 1996 21:47:27 -0800 (PST) Received: from hub.org (root@hub.org [207.107.138.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA20408 for ; Thu, 12 Dec 1996 21:47:24 -0800 (PST) Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id AAA18275; Fri, 13 Dec 1996 00:47:11 -0500 (EST) Date: Fri, 13 Dec 1996 00:47:09 -0500 (EST) From: "Marc G. Fournier" To: "Eric L. Hernes" cc: hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: <199612101935.NAA16873@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 10 Dec 1996, Eric L. Hernes wrote: > "Marc G. Fournier" writes: > > > > Okay...maybe I'm missing something as far as mmap() is concerned, > >but what I want to be able to do is allocated X bytes of memory to be > >shared amongst several processes. After the memory is allocated, I will > >*then* want to fill the memory (ie. with data read from a socket). > > > > From reading the mmap() man page (any good reference/textbooks that > >I might want to pick up?), mmap() allocates and fills the memory space at > >the same time, based on a previously opened, already existing, file (fd). > > > > Yup, > * The Design and Implemenatation of the 4.4BSD Operating System > ~page 139 > * UNIX Internals The New Frontiers > ~page 440 > > One way, is to open a (previously agreed upon) named file that > will be used to share data, ftruncate() it to the size you want, > then mmap() it. Other processes can open and mmap() this same file > to get at the data. Okay...I'm convinced that mmap() is the way to go (alot of it has to do with the fact that I'm still unable to get past 29 shm buffers *sigh*) but the more that I think on it, and re-read what has been said on the subject, the better mmap() seems...so... I picked up "Advanced Programming in the Unix Environment" by Stevens, which has several sections/examples of using mmap(), along with alot of stuff that I probably never even knew about *grin* My new "light reading", I guess... The one question that I can't seem to find addressed though is opening the named file. Now, since I'm closing the file after MMAP'ng it, does it matter how I open it? I incorrectly used the terms 'child/parent' when I first asked...the reason I'm going named file is because its a client/server environment...sorry if that changes everything, but from what I've read, I don't think it does... Now, if I understand it correctly, what I'm goin to want to do is: parent: open named file (O_RDONLY, O_RDWR, or it doesn't matter?) ftruncate named file mmap it using something similar to: mmap(0, , PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); close named file child: open named file (again, does the mode matter?) mmap it using something similar to: mmap(0, , PROT_READ, MAP_SHARED, fd, 0); close named file Is that the gist of it? Then I can "read/write" the mmap'd area just like I would a similarly malloc()'d area, correct? Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-hackers Thu Dec 12 21:56:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA21251 for hackers-outgoing; Thu, 12 Dec 1996 21:56:48 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA21246 for ; Thu, 12 Dec 1996 21:56:45 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id WAA21997 for hackers@FreeBSD.org; Thu, 12 Dec 1996 22:56:40 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id WAA11152 for ; Thu, 12 Dec 1996 22:56:19 -0700 (MST) Date: Thu, 12 Dec 1996 22:56:18 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca Reply-To: Marc Slemko To: hackers@FreeBSD.org Subject: Re: TCP FIN/ACK storm oddity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Ok, a bit more data. It seems after 50 minutes or so the state on the FreeBSD box goes from ESTABLISHED to CLOSE_WAIT. Then I make telnet active again, and it exits. The flood of packets starts, and the connection goes into the LAST_ACK stage. I have put a filter in on the FreeBSD box which (obviously) stops the flood. If I remove the filter too quickly (a couple of minutes) the first traffic I get: 03:49:01.543147 futurity.worldgate.com.telnet > darkly.worldgate.com.1701: F 541 865:541865(0) ack 1325056048 win 2048 03:49:01.543355 darkly.worldgate.com.1701 > futurity.worldgate.com.telnet: F 1:1 (0) ack 1 win 17153 (DF) [tos 0x10] 03:49:01.544357 futurity.worldgate.com.telnet > darkly.worldgate.com.1701: . ack 1 win 2048 03:49:01.544561 darkly.worldgate.com.1701 > futurity.worldgate.com.telnet: F 1:1 (0) ack 1 win 17153 (DF) [tos 0x10] 03:49:01.545629 futurity.worldgate.com.telnet > darkly.worldgate.com.1701: . ack 1 win 2048 So darkly gets a FIN, replies with a FIN, then keeps getting acks back in response to the FINs so it keeps sending FINs. Something is certainly wrong here. My first reaction is that once darkly gets the ack to its FIN, it should stop. However, I don't have the books at home to look it up. Julian Elischer made the good suggestion of disabling the T/TCP extensions, so I tried it with them (net.inet.tcp.rfc1644=0) disabled and, for the fun of it, the RFC1323 stuff disabled too. No difference; it still happened. It also happens if I connect from a BSD/OS 2.0 box to the Ascend; haven't tried a more diverse platform yet. I haven't been able to make the same thing happen with a simple test between two FreeBSD boxes (ie. one sending data constantly, suspend telnet, see if it messes up) but that doesn't mean it can't. OTOH, I would not be the least suprised if it were a bug in Ascend's silly software; they have enough of them, they'd never notice another one. On Wed, 11 Dec 1996, Marc Slemko wrote: > We ran into a situation with a FreeBSD-stable box and an Ascend MAX > 4000 router that was somewhat odd. The MAX has a pretty little full > screen display that is constantly updated with status information. I > telnetted to the MAX from the freebsd box, and then suspended the > telnet session and forgot about it, leaving it stopped in the > background on the FreeBSD box. A few hours later, I remembered it and > brought it back to the foreground. It started displaying a whole > bunch of updates very quickly then, as expected, died because it had > been suspended too long. > > After it died, I observed a flood of packets such as the following on > the ethernet: > > 16:31:46.852314 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack > 490176104 win 2048 > 16:31:46.852489 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 > 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] > 16:31:46.853961 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack > 490176104 win 2048 > 16:31:46.855045 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 > 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] > 16:31:46.855161 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack > 490176104 win 2048 > 16:31:46.855364 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 > 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] > 16:31:46.856240 futurity.worldgate.com.telnet > darkly.worldgate.com.1194: . ack > 490176104 win 2048 > 16:31:46.856503 darkly.worldgate.com.1194 > futurity.worldgate.com.telnet: F 490 > 176104:490176104(0) ack 595604 win 17153 (DF) [tos 0x10] > > futurity is the MAX, darkly is the FreeBSD box. A tcpdump -w stored a > dozen megs of this in a couple of minutes. > > It looks like darkly is trying to close the connection to futurity, so > it is sending a FIN. It then gets an ACK back from futurity, as it > should. However, why does darkly send another FIN? Shouldn't it then > shutup and let things close? Should futurity be ignoring any more > FINs it gets after the first one? > > The other possibility is that the connection is already closed on > darkly, and futurity is the one trying to send an ACK. However I don't > see why darkly would send a FIN in response to an ACK for a connection > it no longer knew anything about; it should send a RST from my reading > of things. > > Unfortunately I don't know exactly what state the connection was in on > the FreeBSD box while this was happening. After a few minutes of > this, I put a packet filter in on the FreeBSD box to stop the packets > and the storm died. > > Any ideas? > > From owner-freebsd-hackers Thu Dec 12 22:29:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA23568 for hackers-outgoing; Thu, 12 Dec 1996 22:29:13 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA23558; Thu, 12 Dec 1996 22:29:09 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.6/8.7.3) with SMTP id BAA08762; Fri, 13 Dec 1996 01:29:03 -0500 (EST) Date: Fri, 13 Dec 1996 01:29:03 -0500 (EST) From: John Fieber To: Mike Nemeth cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: want your input for a *BSD-device-driver-writing FAQ In-Reply-To: <199612130355.UAA02506@cathouse.vu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 12 Dec 1996, Mike Nemeth wrote: > local geographic area, i would like to solicit information on the writing of > device drivers under *BSD for incorporation into a FAQ. if you have experience If you have not already, be sure to look at http://www.freebsd.org/tutorials/ddwg/ddwg.html. That might be a good place to start. Information on writing a device driver is certainly more substantial than the FAQ was intended for. -john From owner-freebsd-hackers Thu Dec 12 22:52:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA25065 for hackers-outgoing; Thu, 12 Dec 1996 22:52:52 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA25060 for ; Thu, 12 Dec 1996 22:52:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.7.6/8.6.12) with SMTP id BAA17932; Fri, 13 Dec 1996 01:53:31 -0500 (EST) Message-Id: <199612130653.BAA17932@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Hancock Cc: FreeBSD Hackers Subject: Re: Implementing atomic DCAS on Intel for NBS In-reply-to: Your message of "Fri, 13 Dec 1996 11:44:25 +0900." Date: Fri, 13 Dec 1996 01:53:31 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It doesn't look like the P5 has DCAS which is important for NBS because it > wants to atomically manipulate a structure and update it's version > number. P5/P6 have CMPXCHG. cmpxchg src, dst is defined to be if (accumulator==dst) { zeroflag = 1; dst = src; } else { zeroflag = 0; accumulator = dst; } When src is a register & dst is a memory addr, this instruction is the same as compare-and-swap (CAS). The processor implements using locked bus cycles so this is guaranteed to be atomic. Here is some crude, untested C+asm goop for a cas() function: /* * \begin{critical section} * if (*addr == old) { *addr = new; return 1; } else return 0; * \end{critical section} */ int cas(int* addr, register int old, register int new) { int r = 0; asm volatile("movl %0,%%eax": "=r"(old)); asm volatile("cmpxchg %0,%1": "=r"(new): "r"(addr)); asm volatile("je L1"); r = 1; asm("L1:"); return r; } Undoubtely this can be optmized and turned into an inline function if we can get rid of that L1 label. Anyway, you can implement DCAS in terms of CAS. Doing so for an MP kernel is easy because all the kernel threads can use the same global shared variable to guard the DCAS code. volatile int global_dcas_lock = 0; ... dcas(int *addr1, int* addr2, int old1, int old2, int new1, int new2) { int r; while (cas(&global_dcas_lock, 0, p->p_pid) == 0) continue; r = *addr1 == old1 && *addr2 == old2; if (r) { *addr1 == new1; *addr2 == new2; } global_dcas_lock = 0; return r; } Note that effectively we have reduced the number of locks to 1 and this lock is held for a very short duration. This is why the priority inversion problem does not even arise. If you want a user level DCAS, you can do something similar. But the user process can get preempted in the middle. So at the very least you have to provide enough info to the kernel so that it can roll you back out of a partial dcas(). If you don't want to use such a global variable, it gets quite a bit hairy. Proof left as an exercise. Structures like singly linked list, trees and so forth can be updated with just DCAS using the version numer idea. But updating a doubly linked list will require CAS3 (deletion will require updating version number, which may be stored in a list head, this->prev->next, this->next->prev). In general you may need vcas(), to atomically update N words. The above implementation easily extends to vcas(). Comments about NBS: In general, when the number of words read exceeds the number of written words (for shared data structures), NBS will be more efficient than lockIng. Deadlock simply can not happen because atmost there is just one shared lock. So in an MP kernel instead of a few (or one!) very coarse grained lock)s( to guard shared data structures you can use NBS and increase concurrency. You still have to identify shared data structures and figure out the boundaries of your transactions but intuitively this seems easier than increasing kernel concurrency by replacing a few coarse grain locks with many fine grained locks. Unfortunately I don't have time to test this theory :-( -- bakul From owner-freebsd-hackers Thu Dec 12 23:29:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA27596 for hackers-outgoing; Thu, 12 Dec 1996 23:29:15 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA27587 for ; Thu, 12 Dec 1996 23:29:09 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id SAA24286; Fri, 13 Dec 1996 18:22:41 +1100 Date: Fri, 13 Dec 1996 18:22:41 +1100 From: Bruce Evans Message-Id: <199612130722.SAA24286@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: 2.1.5-R kernel root on sd0 fails Cc: lada@ws2301.gud.siemens.co.at Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > 1:sd(0,a)/kernel >> >> Sure, I know that. But it requires manual intervention on *every* boot. > >...in the same boat with this solution. > >``nextboot'' is the projected solution to your problem, but Julian >Elischer apparently failed to document how to set it up, and to >advocate for its use. You might give it a try, perhaps you can figure >out how it works? (Don't ask me though, i don't have disks where i >could spare sector 2 for the nextboot information.) It has a man page and should be easy to set up by compiling biosboot with the option for it. However, I project nuking it. I'm allergic to magic spare sectors. They are worse than magic builtin sectors (like the label sector which is sometimes in the middle of the bootstrap). >> OTOH, your statement implies that the kernel root device configuration >> option is actually broken. I'll take a look in the config sources, then. > >No, it ain't broken. The root device is _intended_ to be >automatically changed to the device where the system has been booted >from... It would be nice if the entries in /etc/fstab for the boot device were automatically changed. I keep a backup root file system on a removable (zip) drive and the drive number is often wrong when I need it. Bruce From owner-freebsd-hackers Thu Dec 12 23:53:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA29580 for hackers-outgoing; Thu, 12 Dec 1996 23:53:15 -0800 (PST) Received: from blacklodge.c2.net (root@blacklodge.c2.net [140.174.185.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA29560; Thu, 12 Dec 1996 23:53:09 -0800 (PST) Received: from clotho.c2.org (clotho.c2.org [140.174.185.10]) by blacklodge.c2.net (8.7.6/8.7.3) with ESMTP id XAA12484; Thu, 12 Dec 1996 23:54:49 -0800 (PST) From: sameer Received: (from sameer@localhost) by clotho.c2.org (8.7.6/8.7.3) id XAA11862; Thu, 12 Dec 1996 23:53:25 -0800 (PST) Message-Id: <199612130753.XAA11862@clotho.c2.org> Subject: getdtablesize, OPEN_MAX, and sysctl To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Date: Thu, 12 Dec 1996 23:53:25 -0800 (PST) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk So I have a machine (2.1-STABLE) with OPEN_MAX set to 256. When I do sysctl -a kern.maxfiles is 2088. Is there a relationship between OPEN_MAX and something that shows up in sysctl? I have this program, where if I do a getdtablesize (or sysconf(SC_OPEN_MAX)) it returns 256 at program startup, but returns *258* on a getdtablesize() call further on in execution. (Right before a select(), which then subsequently fails with EINVAL) Anyone know how the getdtablesize() result could have changed by two? I have another machine (2.1-STABLE) with OPEN_MAX of 1024. sysctl kern.maxfiles is 2088. getdtablesize() returns 1024 on program startup and 1026 right before that select call. I have yet another machine (2.1.5-RELEASE) with a default OPEN_MAX. kern.maxfiles is 4136. When I run this same program, it works. getdtablesize() returns 64 on startup and 66 right before the select. I have yet another machine (2.1.0-RELEASE) with an OPEN_MAX of 128 and kern.maxfiles is 360. getdtablesize() at main is 128 at right before the select it is 130. On the last two machines, the select runs fine On the first two, the select (the result of the getdtablesize() is going to the first arg of the select() call) returns EINVAL. Could someone point me in the direction of a clue? thanks. -- Sameer Parekh Voice: 510-986-8770 President FAX: 510-986-8777 C2Net http://www.c2.net/ sameer@c2.net From owner-freebsd-hackers Fri Dec 13 00:27:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA01704 for hackers-outgoing; Fri, 13 Dec 1996 00:27:39 -0800 (PST) Received: from blacklodge.c2.net (root@blacklodge.c2.net [140.174.185.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA01678; Fri, 13 Dec 1996 00:27:30 -0800 (PST) Received: from atropos.c2.org (atropos.c2.org [140.174.185.14]) by blacklodge.c2.net (8.7.6/8.7.3) with ESMTP id AAA18689; Fri, 13 Dec 1996 00:29:11 -0800 (PST) From: sameer Received: (from sameer@localhost) by atropos.c2.org (8.7.6/8.7.3) id AAA20468; Fri, 13 Dec 1996 00:27:06 -0800 (PST) Message-Id: <199612130827.AAA20468@atropos.c2.org> Subject: Re: getdtablesize, OPEN_MAX, and sysctl To: sameer@blacklodge.c2.org (sameer) Date: Fri, 13 Dec 1996 00:27:06 -0800 (PST) Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org In-Reply-To: from "sameer" at Dec 12, 96 11:53:25 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk More information -- on the 2.1-STABLE machine with OPEN_MAX of 256 we tested it by subtracting two from the getdtablesize() result before passing it to select() -- it now works. > So I have a machine (2.1-STABLE) with OPEN_MAX set to 256. > When I do sysctl -a kern.maxfiles is 2088. Is there a relationship > between OPEN_MAX and something that shows up in sysctl? > I have this program, where if I do a getdtablesize (or > sysconf(SC_OPEN_MAX)) it returns 256 at program startup, but returns > *258* on a getdtablesize() call further on in execution. (Right before > a select(), which then subsequently fails with EINVAL) Anyone know how > the getdtablesize() result could have changed by two? > > I have another machine (2.1-STABLE) with OPEN_MAX of > 1024. sysctl kern.maxfiles is 2088. getdtablesize() returns 1024 on > program startup and 1026 right before that select call. > > I have yet another machine (2.1.5-RELEASE) with a default > OPEN_MAX. kern.maxfiles is 4136. When I run this same program, it > works. getdtablesize() returns 64 on startup and 66 right before the > select. > > I have yet another machine (2.1.0-RELEASE) with an OPEN_MAX of > 128 and kern.maxfiles is 360. getdtablesize() at main is 128 at right > before the select it is 130. > > On the last two machines, the select runs fine On the first > two, the select (the result of the getdtablesize() is going to the > first arg of the select() call) returns EINVAL. > > Could someone point me in the direction of a clue? thanks. -- Sameer Parekh Voice: 510-986-8770 President FAX: 510-986-8777 C2Net http://www.c2.net/ sameer@c2.net From owner-freebsd-hackers Fri Dec 13 00:51:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA02962 for hackers-outgoing; Fri, 13 Dec 1996 00:51:16 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA02957 for ; Fri, 13 Dec 1996 00:51:13 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id AAA13378 for ; Fri, 13 Dec 1996 00:51:12 -0800 (PST) Date: Fri, 13 Dec 1996 00:51:12 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: More ports breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Trying to build xperfmon on a 2.2-RELEASE (That's what it says. Hah!) box, supped 12/12/96 ===> Patching for xperfmon++-1.33 ===> Applying FreeBSD patches for xperfmon++-1.33 ===> Configuring for xperfmon++-1.33 mv -f Makefile Makefile.bak imake -DUseInstalled -I/usr/X11R6/lib/X11/config make Makefiles make includes make depend makedepend -- -I. -I./lib/Xt -I. -I./X11 -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -- TimeChart.c StripChart.c misc.c .c xperfmon.c makedepend: warning: TimeChart.c: 57: # error You have to use at least a FreeBSD 2.X system makedepend: warning: StripChart.c: 65: # error You have to use at least a FreeBSD 2.X system makedepend: warning: misc.c: 33: # error You have to use at least a FreeBSD 2.X system makedepend: warning: cannot open ".c" makedepend: warning: xperfmon.c: 68: # error You have to use at least a FreeBSD 2.X system From owner-freebsd-hackers Fri Dec 13 00:58:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA03265 for hackers-outgoing; Fri, 13 Dec 1996 00:58:43 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA03242; Fri, 13 Dec 1996 00:58:35 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id TAA26648; Fri, 13 Dec 1996 19:54:23 +1100 Date: Fri, 13 Dec 1996 19:54:23 +1100 From: Bruce Evans Message-Id: <199612130854.TAA26648@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, sameer@c2.net Subject: Re: getdtablesize, OPEN_MAX, and sysctl Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So I have a machine (2.1-STABLE) with OPEN_MAX set to 256. >When I do sysctl -a kern.maxfiles is 2088. Is there a relationship >between OPEN_MAX and something that shows up in sysctl? No. OPEN_MAX is broken and should never be used. It is currently used in /usr/src only to configure the number of descriptors for the for the init process. This value is inherited by child processes. To determine the current limit, use sysconf(_SC_OPEN_MAX) in "portable" programs or getdtablesize() in BSD programs or sysctl() in BSD4.4 programs. getdtablesize() is the easiest to use and the least buggy. The limit is supposed to be invariant across the lifetime of a process, but isn't. Long-lived processes may have to worry about the limit being reduced by the sysadmin (`sysctl -w kern.maxfilesperproc=fewer'). The bugs have to do with this possibility. The actual limit is min(resource limit, maxfilesperproc). getdtablesize() returns this but the alternative syscalls return the resource limit. Also, setrlimit silently reduces the resource limit to min(requested resource limit, maxfilesperproc). > I have this program, where if I do a getdtablesize (or >sysconf(SC_OPEN_MAX)) it returns 256 at program startup, but returns >*258* on a getdtablesize() call further on in execution. (Right before >a select(), which then subsequently fails with EINVAL) Anyone know how >the getdtablesize() result could have changed by two? Something must have increased it using setrlimit(). > On the last two machines, the select runs fine On the first >two, the select (the result of the getdtablesize() is going to the >first arg of the select() call) returns EINVAL. select() only supports a fixed maximum number of descriptors in -stable. The default is FD_SETSIZE = 256. 2.2 and -current support any reasonable number provided the application is compiled with FD_SETSIZE defined as a larger number. Bruce From owner-freebsd-hackers Fri Dec 13 01:29:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA04844 for hackers-outgoing; Fri, 13 Dec 1996 01:29:03 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA04838 for ; Fri, 13 Dec 1996 01:28:59 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA27331; Fri, 13 Dec 1996 20:22:40 +1100 Date: Fri, 13 Dec 1996 20:22:40 +1100 From: Bruce Evans Message-Id: <199612130922.UAA27331@godzilla.zeta.org.au> To: hackers@freebsd.org, suttonj@interconnect.com.au Subject: Re: My Banksia Internal Modem - sio driver Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >(after numerous reboots) and sometimes not. So I did some searching of the >mail archives and realised that I should use the 0x80 flag to see what was >happening (should have read the sio man page...). I suddenly found that it >was failing consistently on the 6th probe: > >/kernel: sio1: probe test 6 failed > >Thinking I had nothing to loose I then changed the source for sio so that >the sixth probe always returned a successful result. So far I haven't had >any problems more internal modem problems or problems with my other 3 >serial ports. Device drivers are definitely way above my level of >programming skill so what I'm wondering is - Is it likely that I may >create any other problems by doing this? It depends. Failure 6 without failure 5 says that the interrupt went away before it really went away :-). The interrupt handler uses the "real" interrupt bit to decide whether it should loop looking for more things to do. Looping once or twice only adds 5-10% to the serial overhead. >Could adding extra DELAY >statements achieve a similar result more cleanly?? There's already a huge delay of 1000 usec that covers test 6. You might learn how long the interrupt takes to really go away. I guess it doesn't go away. Looping in the interrupt handler for one or two multiples of 1000 usec would increase serial overhead by a large factor. Bruce From owner-freebsd-hackers Fri Dec 13 01:45:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA05802 for hackers-outgoing; Fri, 13 Dec 1996 01:45:50 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA05797 for ; Fri, 13 Dec 1996 01:45:47 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id BAA25437; Fri, 13 Dec 1996 01:42:32 -0800 (PST) Date: Fri, 13 Dec 1996 01:41:51 -0800 (PST) From: Julian Elischer To: Bruce Evans cc: hackers@freebsd.org Subject: Re: Nextboot(8) In-Reply-To: <199612130722.SAA24286@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Dec 1996, Bruce Evans wrote: > > It has a man page and should be easy to set up by compiling biosboot > with the option for it. However, I project nuking it. I'm allergic to > magic spare sectors. They are worse than magic builtin sectors (like > the label sector which is sometimes in the middle of the bootstrap). > Well I think that is something you are welcome to do as soon as you can replace the functionality.. (better suggestions gladly accepted). 1/ nextboot refuses to write the block if it is within a slice, so it should not be possible to clobber important info, and it's not compulsory to use it. 2/ I need the bootblocks to MODIFY whatever is there so I can detect failing boots and do something different next time. 3/ I do NOT trust the bootblocks to fetch that information from the disklabel and write back a modified disklabel block. So block 2 if it's available and has the right magic numbers seems as safe as I can get.. I have plans on nuking your diskslice code too.. as soon as I can replace it with something that works as well.. ;) (i.e. don't hold your breath :) we're all forced to do hacks to get around teh PC architecture.. I have the nextboot code running on all the interjets. that will be several thousand machines in a matter of a few months.. so it should be pretty tested soon :) julian From owner-freebsd-hackers Fri Dec 13 02:38:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA07859 for hackers-outgoing; Fri, 13 Dec 1996 02:38:06 -0800 (PST) Received: from nts.novoch.ru (nts-gw.rnd.su [194.220.3.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA07837 for ; Fri, 13 Dec 1996 02:37:53 -0800 (PST) Received: by nts.novoch.ru id NAA24160; (8.6.11/vak/1.9) Fri, 13 Dec 1996 13:36:04 +0300 To: freebsd-hackers@freebsd.org Message-ID: Organization: Information Centre of Novocherkassk Telephone Station From: "Sergei Ulianov" Date: Fri, 13 Dec 96 13:36:04 +0300 X-Mailer: BML [UNIX Beauty Mail v.1.39] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk help --- Sergei Ulianov | WAN Engineer, Information Centre +7(86352)43692 | of Novocherkassk Telephone Station us@nts.rnd.su | +7(86352)48292 ----------------------------------------------------- From owner-freebsd-hackers Fri Dec 13 02:54:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA08488 for hackers-outgoing; Fri, 13 Dec 1996 02:54:29 -0800 (PST) Received: from hda.hda.com (ip24-max1-fitch.ziplink.net [199.232.245.24]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA08482 for ; Fri, 13 Dec 1996 02:54:25 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id FAA12751; Fri, 13 Dec 1996 05:51:45 -0500 From: Peter Dufault Message-Id: <199612131051.FAA12751@hda.hda.com> Subject: Re: Implementing atomic DCAS on Intel for NBS In-Reply-To: <199612130653.BAA17932@chai.plexuscom.com> from Bakul Shah at "Dec 13, 96 01:53:31 am" To: bakul@plexuscom.com (Bakul Shah) Date: Fri, 13 Dec 1996 05:51:44 -0500 (EST) Cc: michaelh@cet.co.jp, Hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Comments about NBS: > > In general, when the number of words read exceeds the number of > written words (for shared data structures), NBS will be more > efficient than lockIng. Deadlock simply can not happen because > atmost there is just one shared lock. That one shared lock will get pretty busy, while with standard locking the lock activity can "page" to a point in an MP hierarchy where they are actually used. I'll have to look up the references to see how this locality issue is discussed. Language support with some kind of commit operation on data structures seems attractive - by this I mean only declaring those parts of a data structure that must be lockable lockable, and automatically getting write accesses nCAS'd where the system would update all fields at once from a temporary (together with the serial number update - go easy on this - I haven't thought about it much yet). -- Peter Dufault (dufault@hda.com) Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Fri Dec 13 02:58:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA08626 for hackers-outgoing; Fri, 13 Dec 1996 02:58:09 -0800 (PST) Received: from mail.netvision.net.il (mail.NetVision.net.il [194.90.1.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA08621 for ; Fri, 13 Dec 1996 02:58:06 -0800 (PST) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mail.netvision.net.il (8.7.5/8.7.3) with SMTP id MAA09502 for ; Fri, 13 Dec 1996 12:57:58 +0200 (IST) Message-ID: X-Mailer: XFMail 0.5-beta [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 13 Dec 1996 12:54:42 +0200 (IST) X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: hackers@FreeBSD.ORG Subject: mmap() with offset Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! For some reason mmap(...) call with offset other then 0 fails with invalid argument error. The code looks like: msg->msg_body = (char *)mmap(NULL, (size_t)mlen, PROT_READ, 0,mfd, (off_t)mofft)) == (char *)-1); You can reproduce it by running cmp with skip arguments (cmp file1 file2 10 10). Any ideas? Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena PGP public key is available by fingering gena@netvision.net.il This message was sent at 13-Dec-96 12:54:42 by XF-Mail From owner-freebsd-hackers Fri Dec 13 04:20:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA12850 for hackers-outgoing; Fri, 13 Dec 1996 04:20:11 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA12842 for ; Fri, 13 Dec 1996 04:20:06 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03470; Fri, 13 Dec 1996 13:19:03 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21304; Fri, 13 Dec 1996 10:48:22 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17346; Fri, 13 Dec 1996 10:15:42 +0100 (MET) From: J Wunsch Message-Id: <199612130915.KAA17346@uriah.heep.sax.de> Subject: Re: talk and talkd To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 10:15:42 +0100 (MET) Cc: mgessner@aristar.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Warner Losh at "Dec 12, 96 07:33:52 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Warner Losh wrote: > : I think you need to provide more data. talk is fairly fragile, but > : nevertheless works (apparently) for most of us out of the box. > > There are also multiple talk protocols that are used by talk. And the > one that Sun uses is not compatible with anybody :-( ytalk is supposed to speak the Sun protocol as well (including the required byte order changes Sun was so proud to forget). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Dec 13 04:20:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA12893 for hackers-outgoing; Fri, 13 Dec 1996 04:20:26 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA12802 for ; Fri, 13 Dec 1996 04:19:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03409; Fri, 13 Dec 1996 13:18:45 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21373; Fri, 13 Dec 1996 10:52:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17368; Fri, 13 Dec 1996 10:18:31 +0100 (MET) From: J Wunsch Message-Id: <199612130918.KAA17368@uriah.heep.sax.de> Subject: Re: Novell offers free NDS, just a thought... To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 10:18:30 +0100 (MET) Cc: DARREND@novell.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130258.NAA09713@genesis.atrad.adelaide.edu.au> from Michael Smith at "Dec 13, 96 01:28:42 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > Has anyone followed through on this? The source is obviously not > freely available to the public, but I think that the FreeBSD Project > counts as an 'industry-leading vendor' in one way or another. 8) But as long as the code cannot be redistributed freely, we cannot include their stuff into the base system. Of course, somebody could write and maintain third-party software, that can be made available as a port. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Dec 13 04:20:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA12911 for hackers-outgoing; Fri, 13 Dec 1996 04:20:29 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA12889 for ; Fri, 13 Dec 1996 04:20:25 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03396 for ; Fri, 13 Dec 1996 13:18:43 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA21451 for freebsd-hackers@freebsd.org; Fri, 13 Dec 1996 11:03:36 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17585 for freebsd-hackers@freebsd.org; Fri, 13 Dec 1996 10:29:23 +0100 (MET) From: J Wunsch Message-Id: <199612130929.KAA17585@uriah.heep.sax.de> Subject: Re: 2.1.5-R kernel root on sd0 fails To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 10:29:23 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612130722.SAA24286@godzilla.zeta.org.au> from Bruce Evans at "Dec 13, 96 06:22:41 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >No, it ain't broken. The root device is _intended_ to be > >automatically changed to the device where the system has been booted > >from... > > It would be nice if the entries in /etc/fstab for the boot device were > automatically changed. I keep a backup root file system on a removable > (zip) drive and the drive number is often wrong when I need it. This is a chicken-and-egg problem, isn't it? The root file system must be mounted first (and _that_'s the operation that fails), in order to change the fstab. Changing the fstab could perhaps be made by some clever trickery in /etc/rc, but it's certainly not easy to cover all cases. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Dec 13 04:26:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13282 for hackers-outgoing; Fri, 13 Dec 1996 04:26:30 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA13258 for ; Fri, 13 Dec 1996 04:26:17 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA03492; Fri, 13 Dec 1996 13:19:07 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21142; Fri, 13 Dec 1996 10:40:44 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA17301; Fri, 13 Dec 1996 10:11:05 +0100 (MET) From: J Wunsch Message-Id: <199612130911.KAA17301@uriah.heep.sax.de> Subject: Re: My Banksia Internal Modem - sio driver To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 10:11:05 +0100 (MET) Cc: suttonj@interconnect.com.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Joel Sutton at "Dec 13, 96 11:30:21 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Joel Sutton wrote: > /kernel: sio1: probe test 6 failed Test 6 checks that the interrupt request disappeared after clearing the interrupt condition. You're suffering from a typical slowness as many emulated UARTs in internal modems experience. Bumping the DELAY right before test 6 is probably your best solution. (I thought there was an entry for internal modems in the FAQ, but couldn't find it. Bruce?) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Dec 13 04:32:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13588 for hackers-outgoing; Fri, 13 Dec 1996 04:32:41 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA13583 for ; Fri, 13 Dec 1996 04:32:38 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA32237; Fri, 13 Dec 1996 23:31:06 +1100 Date: Fri, 13 Dec 1996 23:31:06 +1100 From: Bruce Evans Message-Id: <199612131231.XAA32237@godzilla.zeta.org.au> To: gena@NetVision.net.il, hackers@FreeBSD.ORG Subject: Re: mmap() with offset Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >For some reason mmap(...) call with offset other then 0 fails with invalid >argument error. > >The code looks like: > msg->msg_body = (char *)mmap(NULL, (size_t)mlen, PROT_READ, 0,mfd, > (off_t)mofft)) == (char *)-1); > >You can reproduce it by running cmp with skip arguments (cmp file1 file2 10 10). >Any ideas? mmap() currently requires the offset to be a multiple of PAGE_SIZE (4096). This is a bug according to the man page. Similar restrictions on other mmap args were removed in February 1996. The args get rounded up or down to a multiple of PAGE_SIZE as appropriate. Bruce From owner-freebsd-hackers Fri Dec 13 04:40:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA13990 for hackers-outgoing; Fri, 13 Dec 1996 04:40:31 -0800 (PST) Received: from mail.netvision.net.il (mail.NetVision.net.il [194.90.1.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA13985 for ; Fri, 13 Dec 1996 04:40:26 -0800 (PST) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mail.netvision.net.il (8.7.5/8.7.3) with SMTP id OAA00755; Fri, 13 Dec 1996 14:40:00 +0200 (IST) Message-ID: X-Mailer: XFMail 0.5-beta [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199612131231.XAA32237@godzilla.zeta.org.au> Date: Fri, 13 Dec 1996 14:38:16 +0200 (IST) X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: Bruce Evans Subject: Re: mmap() with offset Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! On 13-Dec-96 Bruce Evans wrote: >mmap() currently requires the offset to be a multiple of PAGE_SIZE (4096). >This is a bug according to the man page. Similar restrictions on other >mmap args were removed in February 1996. The args get rounded up or down >to a multiple of PAGE_SIZE as appropriate. Thanks , i just figured this out by myself, when looking at vm_mmap.c . Also i'm not sure that this can be defined as "bug", since the same restriction exists on Solaris, and even documented in the man page. >Bruce Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena PGP public key is available by fingering gena@netvision.net.il This message was sent at 13-Dec-96 14:38:16 by XF-Mail From owner-freebsd-hackers Fri Dec 13 04:53:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA14775 for hackers-outgoing; Fri, 13 Dec 1996 04:53:04 -0800 (PST) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA14769 for ; Fri, 13 Dec 1996 04:52:58 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.4/8.8.2) id NAA04767 for freebsd-hackers@freebsd.org; Fri, 13 Dec 1996 13:52:53 +0100 (MET) From: Guido van Rooij Message-Id: <199612131252.NAA04767@gvr.win.tue.nl> Subject: notebook: which one To: freebsd-hackers@freebsd.org Date: Fri, 13 Dec 1996 13:52:53 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am looking for a notebook that is well supported under FreeBSD. It should have 16 mb and a decent screen and have either a 0.5 or 1.0 gigabyte fixed disk. I am particularly interested in which brand is the best to choose. -Guido From owner-freebsd-hackers Fri Dec 13 05:48:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA18290 for hackers-outgoing; Fri, 13 Dec 1996 05:48:16 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA18285 for ; Fri, 13 Dec 1996 05:48:12 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id AAA01802; Sat, 14 Dec 1996 00:43:59 +1100 Date: Sat, 14 Dec 1996 00:43:59 +1100 From: Bruce Evans Message-Id: <199612131343.AAA01802@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, j@uriah.heep.sax.de Subject: Re: 2.1.5-R kernel root on sd0 fails Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> It would be nice if the entries in /etc/fstab for the boot device were >> automatically changed. I keep a backup root file system on a removable >> (zip) drive and the drive number is often wrong when I need it. > >This is a chicken-and-egg problem, isn't it? The root file system >must be mounted first (and _that_'s the operation that fails), in >order to change the fstab. vfs_mountroot() normally succeeds in mounting it ro (because the bootstrap has passed the correct device number), but remounting it rw usual fails (becuase the device number in fstab is different). It's stupid to even look in fstab for the root file system. Other file systems are more interesting. The device names for the the ones on the same disk as the root file system (as specified in fstab) normally need to be changed in the same way as for the root file system. Bruce From owner-freebsd-hackers Fri Dec 13 05:58:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA18800 for hackers-outgoing; Fri, 13 Dec 1996 05:58:20 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA18790 for ; Fri, 13 Dec 1996 05:58:11 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id AAA02142; Sat, 14 Dec 1996 00:55:58 +1100 Date: Sat, 14 Dec 1996 00:55:58 +1100 From: Bruce Evans Message-Id: <199612131355.AAA02142@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, j@uriah.heep.sax.de Subject: Re: My Banksia Internal Modem - sio driver Cc: suttonj@interconnect.com.au Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Test 6 checks that the interrupt request disappeared after clearing >the interrupt condition. You're suffering from a typical slowness as >many emulated UARTs in internal modems experience. Bumping the DELAY >right before test 6 is probably your best solution. Tests 5 and 6 both check for that, after delaying for about 1000 times longer than real hardware would need. An emulator should take at most 10-100 times longer. Test 5 is more likely to faily than test 6. Bruce From owner-freebsd-hackers Fri Dec 13 06:05:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA19119 for hackers-outgoing; Fri, 13 Dec 1996 06:05:01 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA19107 for ; Fri, 13 Dec 1996 06:04:56 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA15311; Fri, 13 Dec 1996 08:04:06 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma015308; Fri Dec 13 08:03:53 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA13634; Fri, 13 Dec 1996 08:04:10 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id IAA08338; Fri, 13 Dec 1996 08:04:24 -0600 (CST) Message-Id: <199612131404.IAA08338@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "Marc G. Fournier" cc: "Eric L. Hernes" , hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Fri, 13 Dec 1996 00:47:09 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Dec 1996 08:04:23 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" writes: > > The one question that I can't seem to find addressed though is >opening the named file. > > Now, since I'm closing the file after MMAP'ng it, does it matter >how I open it? I incorrectly used the terms 'child/parent' when I first >asked...the reason I'm going named file is because its a client/server >environment...sorry if that changes everything, but from what I've >read, I don't think it does... > Are these true parent/children, or server/client. It doesn't change *everything*, mostly it just throws out some of the shortcuts, like inheriting file descriptors and/or mmap'd regions. > Now, if I understand it correctly, what I'm goin to want to do is: > >parent: > > open named file (O_RDONLY, O_RDWR, or it doesn't matter?) I think there's a correspondence between the file mode and the PROT_*, specifically, if you open a file O_RDONLY, then mmap with PROT_WRITE, the mmap will fail with EACCES. > ftruncate named file > mmap it using something similar to: > mmap(0, , PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); > close named file > >child: > > open named file (again, does the mode matter?) > mmap it using something similar to: > mmap(0, , PROT_READ, MAP_SHARED, fd, 0); > close named file > > Is that the gist of it? Then I can "read/write" the mmap'd area >just like I would a similarly malloc()'d area, correct? > Yes, that looks ok. To update the image on disk, you'll need to use msync(). I'm not sure if there's ever a predictable implicit msync(). Certainly when memory is scarce, but that's not predicable. Possibly when munmap'ing, or at process exit. > >Marc G. Fournier scrappy@hub.org >Systems Administrator @ hub.org scrappy@freebsd.org > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Dec 13 06:12:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA19438 for hackers-outgoing; Fri, 13 Dec 1996 06:12:59 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA19423 for ; Fri, 13 Dec 1996 06:12:37 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id BAA05221 Sat, 14 Dec 1996 01:11:23 +1100 (EST) From: michael butler Message-Id: <199612131411.BAA05221@asstdc.scgt.oz.au> Subject: Re: notebook: which one In-Reply-To: <199612131252.NAA04767@gvr.win.tue.nl> from Guido van Rooij at "Dec 13, 96 01:52:53 pm" To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Sat, 14 Dec 1996 01:11:23 +1100 (EST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Guido van Rooij writes: > I am looking for a notebook that is well supported under FreeBSD. It > should have 16 mb and a decent screen and have either a 0.5 or 1.0 > gigabyte fixed disk. I am particularly interested in which brand is the > best to choose. I'm writing this from my ThinkPad 560 running -current. Works really well even without a L2 cache .. and at less than 2kg it's no great problem to cart around. Nearly 3hrs battery life (Lithium) in normal, text-mode, non disk-intensive use. Only one sticking point .. X on the DSTN model is (still) not working at better than 640x480 where others have managed to get it to fly at 800x600 on the TFT (active) models. I've used a 3C589b (with a small tweak to the ep driver) and a D-Link DE-650 (no tweaking required) with it. In contrast, I had all sorts of bother trying to get an AST J-10 to run at all with -current back in June .. I gave it back after a week of arguing with the PCIC stuff over some non-standard port problem (it didn't appear to use 0x3e0 :-(), michael From owner-freebsd-hackers Fri Dec 13 06:50:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA22836 for hackers-outgoing; Fri, 13 Dec 1996 06:50:56 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA22831 for ; Fri, 13 Dec 1996 06:50:53 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA21388; Fri, 13 Dec 1996 08:50:02 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma021369; Fri Dec 13 08:49:34 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA14567; Fri, 13 Dec 1996 08:49:50 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id IAA17282; Fri, 13 Dec 1996 08:50:03 -0600 (CST) Message-Id: <199612131450.IAA17282@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Wilko Bulte cc: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list) Subject: Re: looking for freeware SNMP monitoring tools In-reply-to: Your message of "Thu, 12 Dec 1996 23:00:30 +0100." <199612122200.XAA01358@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Dec 1996 08:50:02 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wilko Bulte writes: >Hi there, > >Maybe slightly off topic but: > >Is there any freeware SNMP monitoring tool available, preferably >usable under FreeBSD? I want to check out SNMP monitoring on some >Cabletron MMAC chassis I've obtained for a local hobby club. ports/net/scotty will do SNMP browsing. tkined is the program. It also provides a tcl interface to write your own scripted tools. > >Wilko >_ ____________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands > |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda >-------------------------------------------------------------------------- > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Dec 13 07:52:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA25654 for hackers-outgoing; Fri, 13 Dec 1996 07:52:21 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA25642; Fri, 13 Dec 1996 07:52:16 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id IAA27816; Fri, 13 Dec 1996 08:52:15 -0700 (MST) From: Ade Barkah Message-Id: <199612131552.IAA27816@hemi.com> Subject: Wrong ssh checksum(!) in 2.1.5/6 ports To: hackers@freebsd.org Date: Fri, 13 Dec 1996 08:52:14 -0700 (MST) Cc: torstenb@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, The ssh-1.2.14 md5 checksum in the ports-2.1.5 ssh package (as downloaded from ftp.cdrom.com) does not match the actual dis- tribution. Obviously this affects 2.1.6.1 as well. The md5 expected by the port: MD5 (ssh-1.2.14.tar.gz) = 4c23661228a7946f9fb7aa40d6c7dad4 Actual md5 from the downloaded distfile: MD5 (ssh-1.2.14.tar.gz) = c95349f27d32ad270dda4b87051f2a5f Wrong signatures in such "secure" packages always make me nervous. =-) -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Fri Dec 13 08:39:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA27853 for hackers-outgoing; Fri, 13 Dec 1996 08:39:40 -0800 (PST) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA27847 for ; Fri, 13 Dec 1996 08:39:33 -0800 (PST) Received: from localhost (brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) with SMTP id JAA05945; Fri, 13 Dec 1996 09:37:12 -0700 (MST) Date: Fri, 13 Dec 1996 09:37:11 -0700 (MST) From: Brandon Gillespie To: Darren Davis cc: mtaylor@cybernet.com, hackers@freebsd.org Subject: RE: Help! Turning off DTR on a serial device -Reply In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 11 Dec 1996, Darren Davis wrote: > Well, actually, I was the Developer Support Engineer for UnixWare at > Univel/Novell. I suspect that you will find that there are some > differences. In looking at man termio(7), you want to look at > TIOCM_DTR. Thanks :) From owner-freebsd-hackers Fri Dec 13 09:30:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00684 for hackers-outgoing; Fri, 13 Dec 1996 09:30:02 -0800 (PST) Received: from hub.org (root@hub.org [207.107.138.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA00650 for ; Fri, 13 Dec 1996 09:29:59 -0800 (PST) Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id MAA22881; Fri, 13 Dec 1996 12:29:38 -0500 (EST) Date: Fri, 13 Dec 1996 12:29:38 -0500 (EST) From: "Marc G. Fournier" To: "Eric L. Hernes" cc: hackers@FreeBSD.ORG Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: <199612131404.IAA08338@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Dec 1996, Eric L. Hernes wrote: > Are these true parent/children, or server/client. It doesn't change > *everything*, mostly it just throws out some of the shortcuts, like > inheriting file descriptors and/or mmap'd regions. > true client/server...basically, the "server" is a stand alone process that talks, via sockets, to another machine, and needs to store the information in memory, vs disk for the client(s) to access... > I think there's a correspondence between the file mode and the PROT_*, > specifically, if you open a file O_RDONLY, then mmap with PROT_WRITE, > the mmap will fail with EACCES. > Okay, makes sense...will keep that one in mind... > Yes, that looks ok. To update the image on disk, you'll need to > use msync(). I'm not sure if there's ever a predictable implicit > msync(). Certainly when memory is scarce, but that's not predicable. > Possibly when munmap'ing, or at process exit. > S'alright, the only reason I'm using a named file in the first place is for easy of connecting clients to the MMAPd region...the data will never need to be written to disk, as its out of date seconds after its created. Now, I think I have enough to actually write the shared memory aspect of things...at least now it makes a helluva lot more sense then it did :) Thanks to all... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@freebsd.org From owner-freebsd-hackers Fri Dec 13 09:54:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA02820 for hackers-outgoing; Fri, 13 Dec 1996 09:54:57 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA02808 for ; Fri, 13 Dec 1996 09:54:51 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vYbjj-0007k5-00; Fri, 13 Dec 1996 10:49:27 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: talk and talkd Cc: freebsd-hackers@freebsd.org (FreeBSD hackers), mgessner@aristar.com In-reply-to: Your message of "Fri, 13 Dec 1996 10:15:42 +0100." <199612130915.KAA17346@uriah.heep.sax.de> References: <199612130915.KAA17346@uriah.heep.sax.de> Date: Fri, 13 Dec 1996 10:49:27 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199612130915.KAA17346@uriah.heep.sax.de> J Wunsch writes: : ytalk is supposed to speak the Sun protocol as well (including the : required byte order changes Sun was so proud to forget). True enough, but that's not FreeBSD's talk :-). All this started back in BSD 4.2 on the vax when they designed a protocol that worked great if you were talking to other vaxen. Then Sun ported talk to their machine, and the size of the message changed, but it was still in host byte order. There are hacks in Sun's talkd to swap bytes when talking to a VAX, but I don't think that they really work (could be wrong). Then in BSD 4.3 they came up with an architecture neutral protocol that was always in network byte order, had good, compiler friendly byte alignment in its structures. Sun never picked up these changes :-(. Warner From owner-freebsd-hackers Fri Dec 13 11:03:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA06527 for hackers-outgoing; Fri, 13 Dec 1996 11:03:31 -0800 (PST) Received: from antonios.Stanford.EDU (antonios.Stanford.EDU [171.64.96.57]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA06520 for ; Fri, 13 Dec 1996 11:03:26 -0800 (PST) Received: from localhost (yergeau@localhost) by antonios.Stanford.EDU (8.8.4/8.7.1) with ESMTP id LAA05307; Fri, 13 Dec 1996 11:03:20 -0800 (PST) Message-Id: <199612131903.LAA05307@antonios.Stanford.EDU> To: "Hr.Ladavac" cc: hackers@freebsd.org Subject: Re: 2.1.5-R kernel root on sd0 fails In-reply-to: Your message of "Thu, 12 Dec 1996 19:19:07 +0100." <199612121819.AA221754747@ws2301.gud.siemens.co.at> Date: Fri, 13 Dec 1996 11:03:19 -0800 From: Dan Yergeau Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Hr.Ladavac" writes: >Hi all, > >I know that 2.1.5 is last year's snow, but: > >I had a happy installation with one SCSI disk and then had to add >a wd0--don't ask why. > >Subsequently I went to generate a new kernel in order to be able to >boot from sd0 without manual keyboard intervention every time. There doesn't appear to be a way to convince the biosboot to pass the "correct" information to the kernel (after all, both are bios drives). Just putting "root on sd0" in the kernel config does not appear to work (the kernel still tries what it got from biosboot, sd1), but the following worked for me. Put "root on sd1" and wire the SCSI drive to be sd1 (e.g. "disk sd1 at scbus0 target 0"). You may also need to wire scbus0 to a particular controller (e.g. "controller scbus0 at ahc0"). See the LINT kernel config if you need more information on how to wire disk and controller targets. Before you boot with the new kernel, make sure that you've updated /etc/fstab and created the needed slice devices for sd1s?[a-h] in /dev (if they don't already exist). AND, have a fixit floppy handy! Dan From owner-freebsd-hackers Fri Dec 13 11:43:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA08650 for hackers-outgoing; Fri, 13 Dec 1996 11:43:00 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA08645 for ; Fri, 13 Dec 1996 11:42:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15610; Fri, 13 Dec 1996 12:19:53 -0700 From: Terry Lambert Message-Id: <199612131919.MAA15610@phaeton.artisoft.com> Subject: Re: Multiple Buffer allocation of Shared Memory To: scrappy@hub.org (Marc G. Fournier) Date: Fri, 13 Dec 1996 12:19:52 -0700 (MST) Cc: erich@lodgenet.com, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Dec 13, 96 00:47:09 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > parent: > > open named file (O_RDONLY, O_RDWR, or it doesn't matter?) > ftruncate named file > mmap it using something similar to: > mmap(0, , PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); > close named file > > child: > > open named file (again, does the mode matter?) > mmap it using something similar to: > mmap(0, , PROT_READ, MAP_SHARED, fd, 0); > close named file I believe the mode does not matter. Specifically, the mode is on the fd, not on the vp. All fd's point to the same vp. One posible change in the future, however, is honoring the read/write restrictions on the fd when the fd is mmap'ed. This may be done so that fd's inherited from suid/sgid modes and opened read-only *remain* read-only independent of what you specify to mmap. I'm not sure if fd's inherited this way can currently be mapped or not... it's an interesting special case. Either way, I'd suggest opening O_RDWR if you plan to later map the file PROT_READ|PROT_WRITE. > Is that the gist of it? Then I can "read/write" the mmap'd area > just like I would a similarly malloc()'d area, correct? Yes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Dec 13 11:48:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA08809 for hackers-outgoing; Fri, 13 Dec 1996 11:48:22 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA08804 for ; Fri, 13 Dec 1996 11:48:17 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id NAA08263; Fri, 13 Dec 1996 13:47:15 -0600 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma008248; Fri Dec 13 13:46:56 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id NAA21128; Fri, 13 Dec 1996 13:47:14 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.3/8.6.12) with ESMTP id NAA02070; Fri, 13 Dec 1996 13:47:41 -0600 (CST) Message-Id: <199612131947.NAA02070@jake.lodgenet.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Terry Lambert cc: scrappy@hub.org (Marc G. Fournier), erich@lodgenet.com, hackers@freebsd.org Subject: Re: Multiple Buffer allocation of Shared Memory In-reply-to: Your message of "Fri, 13 Dec 1996 12:19:52 MST." <199612131919.MAA15610@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Dec 1996 13:47:41 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > >I believe the mode does not matter. Specifically, the mode is on the >fd, not on the vp. All fd's point to the same vp. > >From mmap(2): ERRORS Mmap() will fail if: [EACCES] The flag PROT_READ was specified as part of the prot param- eter and fd was not open for reading. The flags PROT_WRITE, MAP_SHARED and MAP_WRITE were specified as part of the flags and prot parameters and fd was not open for writing. although the actual implementation is sometimes different from the man page. Again enough speculation... time for t.c ;-) > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Fri Dec 13 11:53:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA09050 for hackers-outgoing; Fri, 13 Dec 1996 11:53:12 -0800 (PST) Received: from chai.plexuscom.com (chai.plexuscom.com [207.87.46.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA09045 for ; Fri, 13 Dec 1996 11:53:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chai.plexuscom.com (8.7.6/8.6.12) with SMTP id OAA19205; Fri, 13 Dec 1996 14:51:48 -0500 (EST) Message-Id: <199612131951.OAA19205@chai.plexuscom.com> X-Authentication-Warning: chai.plexuscom.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Peter Dufault Cc: michaelh@cet.co.jp, Hackers@freebsd.org Subject: Re: Implementing atomic DCAS on Intel for NBS In-reply-to: Your message of "Fri, 13 Dec 1996 05:51:44 EST." <199612131051.FAA12751@hda.hda.com> Date: Fri, 13 Dec 1996 14:51:48 -0500 From: Bakul Shah Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > That one shared lock will get pretty busy, while with standard > locking the lock activity can "page" to a point in an MP hierarchy > where they are actually used. I'll have to look up the references > to see how this locality issue is discussed. True. There is an implementation that avoids a shared lock but it is messy (not inefficient, just messy). Follow a link on http://www.cs.unc.edu/~anderson/papers.html) to `A framework for implementing objects and scheduling tasks in lock-free reak-time systems' by Anderson & Ramamoorthy. Given that DCAS is used in a specific way (the first value changed is always the version number), a simpler solution may be possible. > Language support with some kind of commit operation on data structures > seems attractive - by this I mean only declaring those parts of a > data structure that must be lockable lockable, and automatically > getting write accesses nCAS'd where the system would update all > fields at once from a temporary (together with the serial number > update - go easy on this - I haven't thought about it much yet). You seem to be looking for `atomic transactions' so that all the changes occur or none. All writes bracketed by begin transaction ... end transaction are written to a `log' and these changes are commited (or aborted) at the end. Obviously, commits are done by using nCAS. Within the transaction each thread/process wants to see their own changes as if they are already commited but not any other thread's -- if the compiler does the bookkeeping of whether you should get the value of foo->bar from &foo->bar or the temp place, the code logic remains uncluttered with such low level details. On the other hand I wouldn't hold my breath on any compiler providing support for this. You may wish to read `Nested Transactions' by J. Elliot B. Moss (MIT press, 1985). But we are getting away from any FreeBSD relevance! -- bakul From owner-freebsd-hackers Fri Dec 13 12:05:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA09598 for hackers-outgoing; Fri, 13 Dec 1996 12:05:57 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA09554 for ; Fri, 13 Dec 1996 12:05:06 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA15651; Fri, 13 Dec 1996 12:42:01 -0700 From: Terry Lambert Message-Id: <199612131942.MAA15651@phaeton.artisoft.com> Subject: Re: 2.1.5-R kernel root on sd0 fails To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 13 Dec 1996 12:42:01 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199612130929.KAA17585@uriah.heep.sax.de> from "J Wunsch" at Dec 13, 96 10:29:23 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >No, it ain't broken. The root device is _intended_ to be > > >automatically changed to the device where the system has been booted > > >from... > > > > It would be nice if the entries in /etc/fstab for the boot device were > > automatically changed. I keep a backup root file system on a removable > > (zip) drive and the drive number is often wrong when I need it. > > This is a chicken-and-egg problem, isn't it? The root file system > must be mounted first (and _that_'s the operation that fails), in > order to change the fstab. > > Changing the fstab could perhaps be made by some clever trickery in > /etc/rc, but it's certainly not easy to cover all cases. The fstab could be changed to a "mapping description" file instead of a "mount these FS's" file. This would require assigning a resource ID to each device (we could call such an ID a "label" 8-) 8-)). The probe code would find the devices and call back into the FS code with "device arrived" events. The same events could be used for removable media (like JAZ, Zip, and Syquest drives, CDROMs, floppy disks, and PCMCIA "Flash" cards). This requires having an "arrived device structure" (we could call it "struct mount" 8-) 8-)). This would require changing the mount list structure such that "the root device" is a logical, rather than a structural abstraction. This means on process fork, the chroot fd would need to be set to the parent chroot fd in the proc structure; for init, the value would be preinitialized to the "root" FS. The namei() code would have to be changed to make the root/chroot code distinction "go away". This would simplify the namei() code. In order to create a mount structure for a device, you would need to process the device arrival. You would do this by asking each FS if they "wanted" the FS (ie: call each FS specific mount() from the FS vfsops structure, and when it returns 'true', quit calling). So what do we end up with? Automatic mounts of all devices into "volume" decriptors -- "struct mount". *THEN* when the system comes up, it maps the mount by volume ID into vnode covering (incidental to this, the "exports" and "mount point covered" processing moves into common code, and doesn't have to be reimplemented for each FS type -- the kernel size goes down at the same time the reliability of the process goes up). *THEN* your "chicken and egg" problem simply "goes away". A side effect of this is that we win immediate support for transient resources using the POSIX name space escape "\\volume_label\..." relative root using symbolic links... voila', support for nomadic computing for transient network connectivity with software packages as sharable resources. Luckily, I submitted the code to do all this in June of 1995. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Dec 13 12:32:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA11017 for hackers-outgoing; Fri, 13 Dec 1996 12:32:51 -0800 (PST) Received: from hda.hda.com (ip90-max1-fitch.ziplink.net [199.232.245.90]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA10973 for ; Fri, 13 Dec 1996 12:32:32 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id PAA13437; Fri, 13 Dec 1996 15:28:25 -0500 From: Peter Dufault Message-Id: <199612132028.PAA13437@hda.hda.com> Subject: Re: Multiple Buffer allocation of Shared Memory In-Reply-To: <199612131919.MAA15610@phaeton.artisoft.com> from Terry Lambert at "Dec 13, 96 12:19:52 pm" To: terry@lambert.org (Terry Lambert) Date: Fri, 13 Dec 1996 15:28:24 -0500 (EST) Cc: scrappy@hub.org, erich@lodgenet.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Either way, I'd suggest opening O_RDWR if you plan to later map the file > PROT_READ|PROT_WRITE. Even if we don't now require it: P1003.1b says you must have opened the file with write permission in the general PROT_WRITE case (other than MAP_PRIVATE), and you must open in with read permission in all cases. -- Peter Dufault (dufault@hda.com) Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hackers Fri Dec 13 14:03:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20523 for hackers-outgoing; Fri, 13 Dec 1996 14:03:53 -0800 (PST) Received: from blacklodge.c2.net (root@blacklodge.c2.net [140.174.185.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA20495; Fri, 13 Dec 1996 14:03:43 -0800 (PST) Received: (from sameer@localhost) by blacklodge.c2.net (8.7.6/8.7.3) id OAA00366; Fri, 13 Dec 1996 14:05:02 -0800 (PST) From: sameer Message-Id: <199612132205.OAA00366@blacklodge.c2.net> Subject: Re: getdtablesize, OPEN_MAX, and sysctl To: bde@zeta.org.au (Bruce Evans) Date: Fri, 13 Dec 1996 14:05:02 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, sameer@c2.net In-Reply-To: <199612130854.TAA26648@godzilla.zeta.org.au> from Bruce Evans at "Dec 13, 96 07:54:23 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > So I have a machine (2.1-STABLE) with OPEN_MAX set to 256. > >When I do sysctl -a kern.maxfiles is 2088. Is there a relationship > >between OPEN_MAX and something that shows up in sysctl? > > No. OPEN_MAX is broken and should never be used. It is currently > used in /usr/src only to configure the number of descriptors for the > for the init process. This value is inherited by child processes. By OPEN_MAX I am referring to the options OPEN_MAX=XX in the kernel config file. I thought that OPEN_MAX was the thing to use for setting max # of fds in your kernel. If that isn't it, what should I use? > > On the last two machines, the select runs fine On the first > >two, the select (the result of the getdtablesize() is going to the > >first arg of the select() call) returns EINVAL. > > select() only supports a fixed maximum number of descriptors in > -stable. The default is FD_SETSIZE = 256. 2.2 and -current support > any reasonable number provided the application is compiled with > FD_SETSIZE defined as a larger number. > I'm pretty sure this is the problem. Are you saying that on 2.1-stable you can't do a select on more than 256 fds, and on 2.2 and -current you can do a select on more than 256 fds but you need to make sure you #define FD_SETSIZE first? -- Sameer Parekh Voice: 510-986-8770 President FAX: 510-986-8777 C2Net http://www.c2.net/ sameer@c2.net From owner-freebsd-hackers Fri Dec 13 14:07:32 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20826 for hackers-outgoing; Fri, 13 Dec 1996 14:07:32 -0800 (PST) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA20802 for ; Fri, 13 Dec 1996 14:07:29 -0800 (PST) Received: from papillon.lemis.de by suntan.tandem.com (8.6.12/suntan5.961027) id OAA27994; Fri, 13 Dec 1996 14:07:28 -0800 From: Greg Lehey Received: (grog@localhost) by papillon.lemis.de (8.8.4/8.6.12) id TAA00340; Thu, 12 Dec 1996 19:38:42 -0500 (EST) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612130038.TAA00340@papillon.lemis.de> Subject: Re: Intelligent source IP's in multinet singlephysicalnet connections? In-Reply-To: <199612100321.WAA25837@crh.cl.msu.edu> from Charles Henrich at "Dec 9, 96 10:21:08 pm" To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Thu, 12 Dec 1996 19:38:41 -0500 (EST) Cc: hackers@freebsd.org (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Henrich writes: > I posted this some months ago, but the suggested "I just fixed it" apparently > didnt. > > On a FreeBSD box with multiple IP addresses, shouldnt FreeBSD pick the source > IP of a packet of the net that the destination IP address is for (if possible?) > > That is, in my case I have an IP address on a standard network class C address, > as well as an alias in the non-routed 10.x.x.x range. I have a default route > for both networks: > > e.g. > > 10 link#1 UCSc 11 0 > CLASSC link#1 UC 0 0 > > When I send any packets to the 10. addresses, I want my source IP to be my > aliased 10. Address. In all other cases I want it to be my normal address. > > This is because I have a bunch of devices hanging on the 10. network that I > want to talk to, and who can only communicate to other devices on the 10. > network. The kicker is this works under Win95 if I define multiple networks > for myself.. I'm not sure that I understand what you're saying here, but what I think you're saying is: when sending a local packet (i.e. a packet that originates on my machine), the source IP address should be the source IP address of the interface on which the packet leaves the machine. For example, assume you have two interfaces: ep0 192.168.0.1 (default) ep1 10.0.0.1 (for net 10) All locally generated packets which leave on ep0 will have the source address 192.168.0.1, and those which leave on ep1 will have the source address 10.0.0.1. Of course, if the packets are being routed, their source address remains unchanged. Does this answer your question? Is it what you want? Greg From owner-freebsd-hackers Fri Dec 13 14:08:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20965 for hackers-outgoing; Fri, 13 Dec 1996 14:08:02 -0800 (PST) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA20938 for ; Fri, 13 Dec 1996 14:07:59 -0800 (PST) Received: from papillon.lemis.de by suntan.tandem.com (8.6.12/suntan5.961027) id OAA27997; Fri, 13 Dec 1996 14:07:29 -0800 From: Greg Lehey Received: (grog@localhost) by papillon.lemis.de (8.8.4/8.6.12) id TAA00305; Thu, 12 Dec 1996 19:15:36 -0500 (EST) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Message-Id: <199612130015.TAA00305@papillon.lemis.de> Subject: Re: FreeBSD on Laptop In-Reply-To: <199612091400.JAA18180@lakes.water.net> from Thomas David Rivers at "Dec 9, 96 09:00:27 am" To: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Date: Thu, 12 Dec 1996 19:15:35 -0500 (EST) Cc: hackers@freebsd.org (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thomas David Rivers writes: >> >> I want to buy a laptop that will work well with FreeBSD. I'm thinking >> specifically of the ACER Light Note series. Do you have any information >> on FreeBSD compatability with ACER and other laptops? > > As it so happens, I run FreeBSD 2.1.5 on an Acer Note (Not the "light" > version) laptop.. Pentium 75, 8meg ram, 810meg hard disk, dual-scan display, > PS/2 mouse, serial port... > > It runs just fine there - recognizes the sound card and everything. In > fact, its one of my easier machines to handle. I do have a problem > using the mouse-pad on very humid days; so I always carry a PS/2 mouse > along with me. > > The only "real" problem I've encountered is the PCMCIA port - I haven't > successfully gotten my no-name NE2000 card recognized yet. I wouldn't expect > that to be a problem of the Acer though; but more likely the PCMCIA support > in FreeBSD 2.1.5 (it's "beta" quality there.) I replied to the original question before, but now I have an update (this is coming from the laptop, BTW, currently at Cincinnati airport). You may have followed my trials and tribulations getting the Ethernet up and running. One of the things I tried was a card which I believe was NE2000 compatible, but the skimpy documentation didn't bother to give that information, and since I couldn't get it to work, I sent it back. I *did* get the 3Com 3C589C to work, but it was difficult. After comparing notes with 3Com and the -mobile people, I am tending to the impression that there is something non-standard about the PCMCIA adapter. The support person at 3Com said that they had problems with non-Intel PCMCIA chipsets. Bottom line: you can get the 3C589C to work only if you don't generate in PCMCIA support. The GENERIC kernel on the CD-ROM should work fine. I'm running 3.0-CURRENT, but I didn't need to do anything special to get the board to work beyond setting the links: if you're connecting to RG58, do 'ifconfig zp0 link1'. UTP must be link0, but I haven't tried that yet. Greg From owner-freebsd-hackers Fri Dec 13 14:51:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA23457 for hackers-outgoing; Fri, 13 Dec 1996 14:51:30 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA23449 for ; Fri, 13 Dec 1996 14:51:28 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.6/8.7.3) id RAA05759; Fri, 13 Dec 1996 17:51:23 -0500 (EST) From: Charles Henrich Message-Id: <199612132251.RAA05759@crh.cl.msu.edu> Subject: Re: Intelligent source IP's in multinet singlephysicalnet connections? To: grog@lemis.de (Greg Lehey) Date: Fri, 13 Dec 1996 17:51:23 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199612130038.TAA00340@papillon.lemis.de> from Greg Lehey at "Dec 12, 96 07:38:41 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm not sure that I understand what you're saying here, but what I > think you're saying is: when sending a local packet (i.e. a packet > that originates on my machine), the source IP address should be the > source IP address of the interface on which the packet leaves the > machine. For example, assume you have two interfaces: > > ep0 192.168.0.1 (default) > ep1 10.0.0.1 (for net 10) > > All locally generated packets which leave on ep0 will have the source > address 192.168.0.1, and those which leave on ep1 will have the source > address 10.0.0.1. Of course, if the packets are being routed, their > source address remains unchanged. > > Does this answer your question? Is it what you want? No. Only a single interface ed0, with multiple IP's aliased to it, otherwise yes. I would assume that what you said should already be happening due to the multiple interfaces? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Dec 13 14:53:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA23622 for hackers-outgoing; Fri, 13 Dec 1996 14:53:46 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA23617 for ; Fri, 13 Dec 1996 14:53:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA29157; Fri, 13 Dec 1996 23:53:01 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA05037; Fri, 13 Dec 1996 23:53:00 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA19757; Fri, 13 Dec 1996 23:48:25 +0100 (MET) From: J Wunsch Message-Id: <199612132248.XAA19757@uriah.heep.sax.de> Subject: Re: Nextboot(8) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 13 Dec 1996 23:48:25 +0100 (MET) Cc: julian@whistle.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Julian Elischer at "Dec 13, 96 01:41:51 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > 1/ nextboot refuses to write the block if it is within a slice, so > it should not be possible to clobber important info, ... Unless other (e.g. DOS) programs think in the same way netboot thinks, and happily clobber information in the spare sectors after the MBR if they find them being outside of slices. :-) You should perhaps better try to _allocate_ a slice of its own for nextboot (start=1, length=1)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Dec 13 21:13:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA07832 for hackers-outgoing; Fri, 13 Dec 1996 21:13:10 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA07825 for ; Fri, 13 Dec 1996 21:13:06 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA26856; Sat, 14 Dec 1996 16:07:41 +1100 Date: Sat, 14 Dec 1996 16:07:41 +1100 From: Bruce Evans Message-Id: <199612140507.QAA26856@godzilla.zeta.org.au> To: lada@ws2301.gud.siemens.co.at, yergeau@gloworm.Stanford.EDU Subject: Re: 2.1.5-R kernel root on sd0 fails Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I had a happy installation with one SCSI disk and then had to add >>a wd0--don't ask why. >> >>Subsequently I went to generate a new kernel in order to be able to >>boot from sd0 without manual keyboard intervention every time. > >There doesn't appear to be a way to convince the biosboot to pass >the "correct" information to the kernel (after all, both are bios >drives). Just putting "root on sd0" in the kernel config does not >appear to work (the kernel still tries what it got from biosboot, >sd1), but the following worked for me. Three ways: 1. manual keyboard intervention every time. Type something like 1:sd(0,a)kernel 2. configure the boot blocks with the BOOT_HD_BIAS option. Something like CFLAGS += -DBOOT_HD_BIAS=1. 3. configure the boot boot blocks with the NAMEBLOCK option and put the string in (1) in the nameblock using nextboot(8). I haven't tried this. >Put "root on sd1" and wire the SCSI drive to be sd1 (e.g. "disk sd1 >at scbus0 target 0"). You may also need to wire scbus0 to a >particular controller (e.g. "controller scbus0 at ahc0"). See the >LINT kernel config if you need more information on how to wire disk >and controller targets. This might be necessary if there are more drives and the BIOS drive order is different than the FreeBSD drive order. Bruce From owner-freebsd-hackers Fri Dec 13 21:31:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA08882 for hackers-outgoing; Fri, 13 Dec 1996 21:31:58 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA08871 for ; Fri, 13 Dec 1996 21:31:54 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id GAA26581 for ; Sat, 14 Dec 1996 06:31:43 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA16374 for hackers@freebsd.org; Sat, 14 Dec 1996 06:31:23 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id BAA24345; Sat, 14 Dec 1996 01:34:47 +0100 (CET) Message-ID: Date: Sat, 14 Dec 1996 01:34:47 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: Wrong ssh checksum(!) in 2.1.5/6 ports References: <199612131552.IAA27816@hemi.com> X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 In-Reply-To: <199612131552.IAA27816@hemi.com>; from Ade Barkah on Dec 13, 1996 08:52:14 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Ade Barkah: > Wrong signatures in such "secure" packages always make me > nervous. =-) You should not use any version other than 1.2.17. The port is outdated but we can't do anything about it. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-hackers Fri Dec 13 21:47:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA09748 for hackers-outgoing; Fri, 13 Dec 1996 21:47:27 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA09728; Fri, 13 Dec 1996 21:47:21 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA27898; Sat, 14 Dec 1996 16:44:05 +1100 Date: Sat, 14 Dec 1996 16:44:05 +1100 From: Bruce Evans Message-Id: <199612140544.QAA27898@godzilla.zeta.org.au> To: bde@zeta.org.au, sameer@c2.net Subject: Re: getdtablesize, OPEN_MAX, and sysctl Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > By OPEN_MAX I am referring to the > >options OPEN_MAX=XX > > in the kernel config file. I thought that OPEN_MAX was the >thing to use for setting max # of fds in your kernel. If that isn't >it, what should I use? This option sets the soft resource limit for the maximum number of open files for the init process. The limit is inherited by all processes but may be changed. Processes should change it using setrlimit() if they or their children need a larger limit. >> select() only supports a fixed maximum number of descriptors in >> -stable. The default is FD_SETSIZE = 256. 2.2 and -current support >> any reasonable number provided the application is compiled with >> FD_SETSIZE defined as a larger number. >> > > I'm pretty sure this is the problem. Are you saying that on >2.1-stable you can't do a select on more than 256 fds, and on 2.2 and >-current you can do a select on more than 256 fds but you need to make >sure you #define FD_SETSIZE first? In 2.1-stable, you can't do a select on more than FD_SETSIZE fd's, where FD_SETSIZE is whatever it is when the kernel is compiled (default 256). In later versions, there is no limit in the kernel; if you want more than the default FD_SETSIZE number of fds, you just have to define FD_SETSIZE consistently before including any headers (since any header might include ). Bruce From owner-freebsd-hackers Sat Dec 14 01:29:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA18259 for hackers-outgoing; Sat, 14 Dec 1996 01:29:08 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA18254 for ; Sat, 14 Dec 1996 01:29:01 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA15058; Sat, 14 Dec 1996 19:58:44 +1030 (CST) From: Michael Smith Message-Id: <199612140928.TAA15058@genesis.atrad.adelaide.edu.au> Subject: Re: Novell offers free NDS, just a thought... In-Reply-To: <199612130918.KAA17368@uriah.heep.sax.de> from J Wunsch at "Dec 13, 96 10:18:30 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 14 Dec 1996 19:58:43 +1030 (CST) Cc: freebsd-hackers@freebsd.org, DARREND@novell.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > As Michael Smith wrote: > > > Has anyone followed through on this? The source is obviously not > > freely available to the public, but I think that the FreeBSD Project > > counts as an 'industry-leading vendor' in one way or another. 8) > > But as long as the code cannot be redistributed freely, we cannot > include their stuff into the base system. Of course, somebody could > write and maintain third-party software, that can be made available as > a port. Depends on the degree of sophistry we're willing to undertake. You could argue that anyone with the FreeBSD source code is effectively a developer 8) The "right" way is of course to approach Novell and see if they'd be willing to play things our way. Darren D.? > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Dec 14 01:30:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA18406 for hackers-outgoing; Sat, 14 Dec 1996 01:30:39 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA18390 for ; Sat, 14 Dec 1996 01:30:36 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id BAA21656 for ; Sat, 14 Dec 1996 01:30:51 -0800 (PST) Received: (qmail 17540 invoked from network); 14 Dec 1996 09:00:36 -0000 Received: from unknown (HELO profane.iq.org) (203.4.184.215) by suburbia.net with SMTP; 14 Dec 1996 09:00:36 -0000 Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id MAA04639; Sat, 14 Dec 1996 12:35:26 +1100 (EST) From: Julian Assange Message-Id: <199612140135.MAA04639@profane.iq.org> Subject: vulnerability in new pw suite To: security@freebsd.org Date: Sat, 14 Dec 1996 12:35:25 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The FreeBSD account administration pw suite is able to produce "random" passwords for new accounts. Due to the simplicity of the password generation algorithm involved, the passwords are easily predictable amid a particular range of possibilities. This range may be very narrow, depending on what sort of information is available to the attacker. The pid and the current time in seconds are ored (NOT xored) together and used as the seed. Because of this, the probability of a lower bit in the seed of being on is 3/4. The msb's of the seed change very slowly and predictably over time and in effect contain no entropy. If the attacker has access to the file system then the time the account was created on can by guessed very accurately by examining the creation date of the new account's directory, or the creation date of the new account's mail spool file. With the time part of the seed known it is then possible to generate an a mask to eliminate 50% of the remaining possible pid values. The pid can be further approximated retrospectively by correlation between time stamps and pid values from a wide number of file system sources such as the pid of the sendmail task used to deliver the new-user mail, to names of /tmp and queue files. An active attack (looking for the "pw" process or other signs of account creation) will of course locate the pid very closely, if not exactly. The attached patch addresses the problem. -Julian A. (proff@suburbia.net) --- /usr/src/usr.sbin/pw/pw_user.c.orig Thu Dec 12 02:10:47 1996 +++ /usr/src/usr.sbin/pw/pw_user.c Sat Dec 14 11:37:50 1996 @@ -33,6 +33,10 @@ #include #include #include +#include +#include +#include +#include #include "pw.h" #include "bitmap.h" #include "pwupd.h" @@ -738,19 +742,61 @@ return strcpy(buf, crypt(password, salt)); } +u_char * +pw_genmd5rand (u_char *d) /* cryptographically secure rng */ +{ + MD5_CTX md5_ctx; + struct timeval tv, tvo; + struct rusage ru; + int n=0; + int t; + MD5Init (&md5_ctx); + t=getpid(); + MD5Update (&md5_ctx, (u_char*)&t, sizeof t); + t=getppid(); + MD5Update (&md5_ctx, (u_char*)&t, sizeof t); + gettimeofday (&tvo, NULL); + do { + getrusage (RUSAGE_SELF, &ru); + MD5Update (&md5_ctx, (u_char*)&ru, sizeof ru); + gettimeofday (&tv, NULL); + MD5Update (&md5_ctx, (u_char*)&tv, sizeof tv); + } while (n++<20 || tv.tv_usec-tvo.tv_usec<100*1000); + MD5Final (d, &md5_ctx); + return d; +} + +static u_char * +pw_getrand(u_char *buf, int len) +{ + int fd; + fd = open("/dev/urandom", O_RDONLY); + if (!fd || read(fd, buf, len)!=len) { + int n; + for (n=0;ndefault_password) { case -1: /* Random password */ srandom((unsigned) (time(NULL) | getpid())); l = (random() % 8 + 8); /* 8 - 16 chars */ + pw_getrand(rndbuf, l); for (i = 0; i < l; i++) - pwbuf[i] = chars[random() % sizeof(chars)]; + pwbuf[i] = chars[rndbuf[i] % sizeof(chars)]; pwbuf[i] = '\0'; /* From owner-freebsd-hackers Sat Dec 14 01:30:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA18419 for hackers-outgoing; Sat, 14 Dec 1996 01:30:40 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA18400 for ; Sat, 14 Dec 1996 01:30:38 -0800 (PST) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id BAA21660 for ; Sat, 14 Dec 1996 01:31:05 -0800 (PST) Received: (qmail 17575 invoked from network); 14 Dec 1996 09:09:09 -0000 Received: from unknown (HELO profane.iq.org) (203.4.184.215) by suburbia.net with SMTP; 14 Dec 1996 09:09:09 -0000 Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id MAA04647; Sat, 14 Dec 1996 12:43:58 +1100 (EST) Date: Sat, 14 Dec 1996 12:43:58 +1100 (EST) From: Julian Assange Message-Id: <199612140143.MAA04647@profane.iq.org> To: hackers@freebsd.org, security@freebsd.org Subject: pw account suite patch typo Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk + if (!fd || read(fd, buf, len)!=len) { should of course read + if (fd == -1 || read(fd, buf, len)!=len) { -Julian A. From owner-freebsd-hackers Sat Dec 14 02:36:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA21255 for hackers-outgoing; Sat, 14 Dec 1996 02:36:31 -0800 (PST) Received: from cyclone.degnet.baynet.de (root@cyclone.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA21249 for ; Sat, 14 Dec 1996 02:36:23 -0800 (PST) Received: from nada (ppp5 [194.95.214.135]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id MAA00586; Sat, 14 Dec 1996 12:36:26 +0100 Message-Id: <3.0.32.19961214112917.00697814@cyclone.degnet.baynet.de> X-Sender: moos@cyclone.degnet.baynet.de (Unverified) X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 14 Dec 1996 11:29:28 -0100 To: Charles Henrich From: Darius Moos Subject: Re: Intelligent source IP's in multinet singlephysicalnet connections? Cc: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi Charles, what you are trying to do definately works !!! I'll show it to you now. 1. Two FreeBSD-boxes. FreeBSD-2.1.5 <--------- ethernet (ed0) -----------------> FreeBSD-1.1.5.1 192.168.250.5 netmask 0xfffffff8 | 192.168.250.1 netmask 0xfffffff8 192.168.250.2 alias netmask 0xffffffff | 10.0.0.2 alias netmask 0xffffff00 10.0.0.1 alias netmask 0xffffff00 | 2. At bootup the 10.0.0.x alias adr.es are NOT assigned. I'll do it in the session. 3. Now please read the session carefully and right to the end. What are the IP-adr.es and domain-names (parts of the tcpdump-output are with domain-names, so the following is for clarifying): neuron:~> nslookup neuron Server: neuron.bsd.uni-passau.de Address: 192.168.250.5 Name: neuron.bsd.uni-passau.de Address: 192.168.250.5 neuron:~> nslookup vampire Server: neuron.bsd.uni-passau.de Address: 192.168.250.5 Name: vampire.bsd.uni-passau.de Address: 192.168.250.1 Now the routing-tabel for 192.168.250.5 after bootup: neuron:/usr/home/moos# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 10 31 lo0 192.168.250/29 link#1 UC 0 0 192.168.250.1 0:0:44:3:be:2b UHLW 10 337 ed0 1067 192.168.250.2 0:0:44:5:e2:50 UHLW 0 0 lo0 => 192.168.250.2/32 link#1 UC 0 0 192.168.250.5 0:0:44:5:e2:50 UHLW 1 44 lo0 224.0.0.9 127.0.0.1 UH 0 0 lo0 Routing-table for 192.168.250.1 after bootup: vampire:~> netstat -rn Routing tables Destination Gateway Flags Refs Use IfaceMTU Rtt Netmasks: (root node) (0) 0000 ffff fff8 (root node) Route Tree for Protocol Family inet: (root node) => default 192.168.250.5 UG 1 126 ed0 - - 127.0.0.1 127.0.0.1 UH 1 0 lo0 - - 192.168.250 192.168.250.1 U 9 247 ed0 - - 192.168.250.1 127.0.0.1 UGH 6 123 lo0 - - 192.168.250.2 192.168.250.5 UGH 0 0 ed0 - - (root node) Now the IP-aliasing: neuron:/usr/home/moos# ifconfig ed0 inet 10.0.0.1 netmask 0xffffff00 alias vampire:/mount/neuron/usr/home/moos# ifconfig ed0 inet 10.0.0.2 netmask 0xffffff00 alias Verifying that the alias worked for 192.168.250.5 (alias 10.0.0.1): neuron:/usr/home/moos# ping 10.0.0.2 PING 10.0.0.2 (10.0.0.2): 56 data bytes 64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=1.737 ms 64 bytes from 10.0.0.2: icmp_seq=1 ttl=255 time=0.893 ms ^C --- 10.0.0.2 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.893/1.315/1.737 ms neuron:/usr/home/moos# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 10/24 link#1 UC 0 0 10 192.168.250.1 UGc 0 0 ed0 10.0.0.2 0:0:44:3:be:2b UHLW 0 2 ed0 1181 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 10 31 lo0 192.168.250/29 link#1 UC 0 0 192.168.250.1 0:0:44:3:be:2b UHLW 11 653 ed0 813 192.168.250.2 0:0:44:5:e2:50 UHLW 0 0 lo0 => 192.168.250.2/32 link#1 UC 0 0 192.168.250.5 0:0:44:5:e2:50 UHLW 2 69 lo0 224.0.0.9 127.0.0.1 UH 0 0 lo0 Verifying that the alias worked for 192.168.250.1 (alias 10.0.0.2): vampire:/mount/neuron/usr/home/moos# netstat -rn Routing tables Destination Gateway Flags Refs Use IfaceMTU Rtt Netmasks: (root node) (0) 0000 ffff ff00 (0) 0000 ffff fff8 (root node) Route Tree for Protocol Family inet: (root node) => default 192.168.250.5 UG 1 270 ed0 - - 10 10.0.0.2 U 1 4 ed0 - - 127.0.0.1 127.0.0.1 UH 1 0 lo0 - - 192.168.250 192.168.250.1 U 9 729 ed0 - - 192.168.250.1 127.0.0.1 UGH 2 153 lo0 - - 192.168.250.2 192.168.250.5 UGH 0 0 ed0 - - (root node) Now making a telnet-session: neuron:~> telnet 10.0.0.2 Trying 10.0.0.2... Connected to 10.0.0.2. Escape character is '^]'. FreeBSD (vampire.bsd.uni-passau.de) (ttyp1) login: The tcpdump-output for this telnet-connection: 10:43:43.191331 arp who-has 10.0.0.1 tell 10.0.0.1 10:43:43.205452 10.0.0.1.router > 10.0.0.255.router: rip-req 24 [ttl 1] 10:43:43.205842 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:43:56.650242 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:44:54.748619 arp who-has 10.0.0.2 tell 10.0.0.1 10:44:54.749218 arp reply 10.0.0.2 is-at 0:0:44:3:be:2b 10:44:54.749367 10.0.0.1 > 10.0.0.2: icmp: echo request 10:44:54.749984 10.0.0.2 > 10.0.0.1: icmp: echo reply 10:44:55.750215 10.0.0.1 > 10.0.0.2: icmp: echo request 10:44:55.750820 10.0.0.2 > 10.0.0.1: icmp: echo reply 10:44:56.650277 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:45:26.650248 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:45:56.650693 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:46:15.036308 10.0.0.1.1037 > 10.0.0.2.telnet: . ack 1 win 17520 (DF) [tos 0x10] 10:46:15.038426 10.0.0.1.1037 > 10.0.0.2.telnet: P 1:28(27) ack 1 win 17520 (DF) [tos 0x10] 10:46:15.039001 10.0.0.2.telnet > 10.0.0.1.1037: . ack 28 win 16033 ... 10:46:26.650263 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:46:56.650249 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:47:26.650263 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] ... 10:47:30.234997 10.0.0.2.telnet > 10.0.0.1.1037: P 1:13(12) ack 28 win 16033 [tos 0x10] 10:47:30.235495 10.0.0.1.1037 > 10.0.0.2.telnet: P 28:31(3) ack 13 win 17520 (DF) [tos 0x10] 10:47:30.236256 10.0.0.2.telnet > 10.0.0.1.1037: P 13:31(18) ack 31 win 16057 [tos 0x10] 10:47:30.237059 10.0.0.1.1037 > 10.0.0.2.telnet: P 31:40(9) ack 31 win 17520 (DF) [tos 0x10] 10:47:30.237670 10.0.0.2.telnet > 10.0.0.1.1037: P 31:49(18) ack 40 win 16051 [tos 0x10] 10:47:30.242244 10.0.0.1.1037 > 10.0.0.2.telnet: P 40:100(60) ack 49 win 17520 (DF) [tos 0x10] 10:47:30.242957 10.0.0.2.telnet > 10.0.0.1.1037: . ack 100 win 16000 [tos 0x10] 10:47:30.256849 10.0.0.2.telnet > 10.0.0.1.1037: P 49:52(3) ack 100 win 16060 [tos 0x10] 10:47:30.257153 10.0.0.1.1037 > 10.0.0.2.telnet: P 100:103(3) ack 52 win 17520 (DF) [tos 0x10] 10:47:30.257813 10.0.0.2.telnet > 10.0.0.1.1037: . ack 103 win 16057 [tos 0x10] 10:47:30.262996 10.0.0.2.telnet > 10.0.0.1.1037: P 52:107(55) ack 103 win 16060 [tos 0x10] 10:47:30.263411 10.0.0.1.1037 > 10.0.0.2.telnet: P 103:106(3) ack 107 win 17520 (DF) [tos 0x10] 10:47:30.264039 10.0.0.2.telnet > 10.0.0.1.1037: . ack 106 win 16057 [tos 0x10] 10:47:30.270898 10.0.0.2.telnet > 10.0.0.1.1037: P 107:113(6) ack 106 win 16060 [tos 0x10] 10:47:30.430115 10.0.0.1.1037 > 10.0.0.2.telnet: . ack 113 win 17520 (DF) [tos 0x10] 10:47:30.431090 10.0.0.2.telnet > 10.0.0.1.1037: P 113:126(13) ack 106 win 16060 [tos 0x10] 10:47:30.630119 10.0.0.1.1037 > 10.0.0.2.telnet: . ack 126 win 17520 (DF) [tos 0x10] ... 10:47:49.445254 10.0.0.1.1037 > 10.0.0.2.telnet: P 106:107(1) ack 126 win 17520 (DF) [tos 0x10] 10:47:49.445836 10.0.0.2.telnet > 10.0.0.1.1037: . ack 107 win 16059 [tos 0x10] 10:47:49.453783 10.0.0.2.telnet > 10.0.0.1.1037: F 126:126(0) ack 107 win 16059 [tos 0x10] 10:47:49.453950 10.0.0.1.1037 > 10.0.0.2.telnet: . ack 127 win 17520 (DF) [tos 0x10] 10:47:49.454322 10.0.0.1.1037 > 10.0.0.2.telnet: F 107:107(0) ack 127 win 17520 (DF) [tos 0x10] 10:47:49.454873 10.0.0.2.telnet > 10.0.0.1.1037: . ack 108 win 16058 [tos 0x10] ... 10:47:56.650267 10.0.0.1.router > 10.0.0.255.router: rip-resp 1: 192.168.250.2(1) [ttl 1] Now a telnet-session with the 192.168.250.x-block: neuron:~> telnet 192.168.250.1 Trying 192.168.250.1... Connected to 192.168.250.1. Escape character is '^]'. FreeBSD (vampire.bsd.uni-passau.de) (ttyp1) login: Connection closed by foreign host. neuron:~> And the tcpdump-output for it: 10:51:10.002743 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: S 94016001:94016001(0) win 16384 neuron.bsd.uni-passau.de.1038: S 100864001:100864001(0) ack 94016002 win 16060 10:51:10.004080 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: . ack 1 win 17520 (DF) [tos 0x10] 10:51:10.005492 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 1:28(27) ack 1 win 17520 (DF) [tos 0x10] 10:51:10.006108 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: . ack 28 win 16033 10:51:10.082834 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: P 1:13(12) ack 28 win 16033 [tos 0x10] 10:51:10.083262 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 28:31(3) ack 13 win 17520 (DF) [tos 0x10] 10:51:10.084065 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: P 13:31(18) ack 31 win 16057 [tos 0x10] 10:51:10.084740 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 31:40(9) ack 31 win 17520 (DF) [tos 0x10] 10:51:10.085370 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: P 31:49(18) ack 40 win 16051 [tos 0x10] 10:51:10.089673 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 40:100(60) ack 49 win 17520 (DF) [tos 0x10] 10:51:10.090371 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: . ack 100 win 16000 [tos 0x10] 10:51:10.103909 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: P 49:52(3) ack 100 win 16060 [tos 0x10] 10:51:10.104214 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 100:103(3) ack 52 win 17520 (DF) [tos 0x10] 10:51:10.104886 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: . ack 103 win 16057 [tos 0x10] 10:51:10.110191 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: P 52:107(55) ack 103 win 16060 [tos 0x10] 10:51:10.110607 neuron.bsd.uni-passau.de.1038 > vampire.bsd.uni-passau.de.telnet: P 103:106(3) ack 107 win 17520 (DF) [tos 0x10] 10:51:10.111250 vampire.bsd.uni-passau.de.telnet > neuron.bsd.uni-passau.de.1038: . ack 106 win 16057 [tos 0x10] Conclusion: ----------- Depending on the dest-net-adr the src-adr is set accordingly. Was it that what you wanted to do? Maybe i misunderstood something in your problem-description. Darius Moos. At 05:33 10.12.96 -0500, you wrote: >> Some months ago i tried this with FreeBSD-2.1.5 and it worked. I've >> checked it with bpf. When you have defined an alias-adr on your >> network-card, and you are sending packets to the network the alias-adr. >> lives in, the src-ip-adr is set to this alias-adr. > >I think you just got lucky, as it doesnt do this on any system of mine 2.1.x or >2.2.x, and one of the developers had told me some time ago they patched it in >2.2. > >-Crh > > Charles Henrich Michigan State University henrich@msu.edu > > http://pilot.msu.edu/~henrich > > From owner-freebsd-hackers Sat Dec 14 03:34:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA22818 for hackers-outgoing; Sat, 14 Dec 1996 03:34:05 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA22772; Sat, 14 Dec 1996 03:34:00 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA02828; Sat, 14 Dec 1996 12:33:24 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA02700; Sat, 14 Dec 1996 12:33:23 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id MAA25312; Sat, 14 Dec 1996 12:30:53 +0100 (MET) From: J Wunsch Message-Id: <199612141130.MAA25312@uriah.heep.sax.de> Subject: Re: pw account suite patch typo To: proff@iq.org (Julian Assange) Date: Sat, 14 Dec 1996 12:30:53 +0100 (MET) Cc: hackers@freebsd.org, security@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612140143.MAA04647@profane.iq.org> from Julian Assange at "Dec 14, 96 12:43:58 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Julian Assange wrote: > + if (!fd || read(fd, buf, len)!=len) { > > should of course read > + if (fd == -1 || read(fd, buf, len)!=len) { Which file? Which file revision? I can't seem to find your quote in the entire suite anyway. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Dec 14 03:35:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA22991 for hackers-outgoing; Sat, 14 Dec 1996 03:35:10 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA22969; Sat, 14 Dec 1996 03:35:01 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA02833; Sat, 14 Dec 1996 12:34:42 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA02701; Sat, 14 Dec 1996 12:33:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id MAA25325; Sat, 14 Dec 1996 12:31:37 +0100 (MET) From: J Wunsch Message-Id: <199612141131.MAA25325@uriah.heep.sax.de> Subject: Re: vulnerability in new pw suite To: proff@iq.org (Julian Assange) Date: Sat, 14 Dec 1996 12:31:37 +0100 (MET) Cc: security@freebsd.org, hackers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612140135.MAA04639@profane.iq.org> from Julian Assange at "Dec 14, 96 12:35:25 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Julian Assange wrote: > The FreeBSD account administration pw suite is able to produce > "random" passwords for new accounts. Due to the simplicity of the > password generation algorithm involved, the passwords are easily > predictable amid a particular range of possibilities. This range > may be very narrow, depending on what sort of information is > available to the attacker. Is there any particular reason why you didn't submit this to the author in the first place? (Forwarded to David now.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Dec 14 04:59:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA26073 for hackers-outgoing; Sat, 14 Dec 1996 04:59:33 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA26063 for ; Sat, 14 Dec 1996 04:59:31 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id FAA24302 for ; Sat, 14 Dec 1996 05:00:05 -0800 (PST) Received: (qmail 989 invoked by uid 110); 14 Dec 1996 12:59:16 -0000 Message-ID: <19961214125916.988.qmail@suburbia.net> Subject: Re: vulnerability in new pw suite In-Reply-To: <199612141131.MAA25325@uriah.heep.sax.de> from J Wunsch at "Dec 14, 96 12:31:37 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 14 Dec 1996 23:59:16 +1100 (EST) Cc: proff@iq.org, security@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > may be very narrow, depending on what sort of information is > > available to the attacker. > > Is there any particular reason why you didn't submit this to the > author in the first place? (Forwarded to David now.) The pw code only made it into current a week ago. I doubt anyone is using it yet. From owner-freebsd-hackers Sat Dec 14 05:43:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA28336 for hackers-outgoing; Sat, 14 Dec 1996 05:43:10 -0800 (PST) Received: from irz401.inf.tu-dresden.de (irz401.inf.tu-dresden.de [141.76.1.12]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id FAA28331 for ; Sat, 14 Dec 1996 05:43:05 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz401.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA05170; Sat, 14 Dec 1996 14:39:16 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA04028; Sat, 14 Dec 1996 14:37:59 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id OAA26445; Sat, 14 Dec 1996 14:29:27 +0100 (MET) From: J Wunsch Message-Id: <199612141329.OAA26445@uriah.heep.sax.de> Subject: Re: vulnerability in new pw suite To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Sat, 14 Dec 1996 14:29:27 +0100 (MET) Cc: proff@iq.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19961214125916.988.qmail@suburbia.net> from "proff@suburbia.net" at "Dec 14, 96 11:59:16 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As proff@suburbia.net wrote: > > Is there any particular reason why you didn't submit this to the > > author in the first place? (Forwarded to David now.) > > The pw code only made it into current a week ago. I doubt anyone > is using it yet. Your doubts are wrong. It's as well in 2.2, and sysinstall is using it. (This has been the main reason to force its merge into 2.2.) Anyway, it's always best to approach the authors first for code that is being actively maintained. They are the first to include new submissions, rather than anybody else. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Dec 14 06:13:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA00417 for hackers-outgoing; Sat, 14 Dec 1996 06:13:08 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA00410 for ; Sat, 14 Dec 1996 06:13:05 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBE996.4A7BE3A0@kaori.communique.net>; Sat, 14 Dec 1996 08:10:38 -0600 Message-ID: From: Raul Zighelboim To: "'lada@ws2301.gud.siemens.co.at'" , "'yergeau@gloworm.Stanford.EDU'" , "'Bruce Evans'" Cc: "'hackers@freebsd.org'" Subject: RE: 2.1.5-R kernel root on sd0 fails Date: Sat, 14 Dec 1996 08:10:37 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is what I set on my kernel to able to boot from sd when wd: config kernel root on sd1 controller scbus0 at aic0 device sd1 at scbus0 target 0 unit 0 hope this helps. >---------- >From: Bruce Evans[SMTP:bde@zeta.org.au] >Sent: Friday, December 13, 1996 11:07 PM >To: lada@ws2301.gud.siemens.co.at; yergeau@gloworm.Stanford.EDU >Cc: hackers@freebsd.org >Subject: Re: 2.1.5-R kernel root on sd0 fails > >>>I had a happy installation with one SCSI disk and then had to add >>>a wd0--don't ask why. >>> >>>Subsequently I went to generate a new kernel in order to be able to >>>boot from sd0 without manual keyboard intervention every time. >> >>There doesn't appear to be a way to convince the biosboot to pass >>the "correct" information to the kernel (after all, both are bios >>drives). Just putting "root on sd0" in the kernel config does not >>appear to work (the kernel still tries what it got from biosboot, >>sd1), but the following worked for me. > >Three ways: >1. manual keyboard intervention every time. Type something like > 1:sd(0,a)kernel >2. configure the boot blocks with the BOOT_HD_BIAS option. Something > like CFLAGS += -DBOOT_HD_BIAS=1. >3. configure the boot boot blocks with the NAMEBLOCK option and put > the string in (1) in the nameblock using nextboot(8). I haven't > tried this. > >>Put "root on sd1" and wire the SCSI drive to be sd1 (e.g. "disk sd1 >>at scbus0 target 0"). You may also need to wire scbus0 to a >>particular controller (e.g. "controller scbus0 at ahc0"). See the >>LINT kernel config if you need more information on how to wire disk >>and controller targets. > >This might be necessary if there are more drives and the BIOS drive >order is different than the FreeBSD drive order. > >Bruce > From owner-freebsd-hackers Sat Dec 14 06:16:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA00647 for hackers-outgoing; Sat, 14 Dec 1996 06:16:02 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id GAA00632; Sat, 14 Dec 1996 06:15:58 -0800 (PST) Received: by sovcom.kiae.su id AA28924 (5.65.kiae-1 ); Sat, 14 Dec 1996 16:54:21 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 14 Dec 96 16:54:21 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with SMTP id QAA00442; Sat, 14 Dec 1996 16:51:09 +0300 (MSK) Date: Sat, 14 Dec 1996 16:51:08 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: Julian Assange Cc: security@freebsd.org, hackers@freebsd.org Subject: Re: vulnerability in new pw suite In-Reply-To: <199612140135.MAA04639@profane.iq.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, Julian Assange wrote: > The FreeBSD account administration pw suite is able to produce > "random" passwords for new accounts. Due to the simplicity of the > password generation algorithm involved, the passwords are easily > predictable amid a particular range of possibilities. This range > may be very narrow, depending on what sort of information is > available to the attacker. I agree on this subj. but I wonder about method you use, it is unnecessary complex, reading /dev/urandom will be enough without MD5 hashing. /dev/urandom not optional device, so if it isn't exists or not give enough bytes it must be detected as program failure and not covered by MD5 workaround. random() must be replaced with /dev/urandom reading, because password length will be easily predicted too. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-hackers Sat Dec 14 08:08:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA11101 for hackers-outgoing; Sat, 14 Dec 1996 08:08:44 -0800 (PST) Received: from sumter.awod.com (awod.com [198.81.225.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA11089 for ; Sat, 14 Dec 1996 08:08:41 -0800 (PST) Received: from tsunami..awod.com (chs0083.awod.com [198.81.225.192]) by sumter.awod.com (8.7.6/8.6.12) with SMTP id LAA02135; Sat, 14 Dec 1996 11:08:23 -0500 (EST) Message-Id: <3.0.32.19961214110824.00755e24@awod.com> X-Sender: klam@awod.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 14 Dec 1996 11:08:26 -0500 To: Guido van Rooij , freebsd-hackers@freebsd.org From: Ken Lam Subject: Re: notebook: which one Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:52 PM 12/13/96 +0100, Guido van Rooij wrote: >I am looking for a notebook that is well supported under FreeBSD. >It should have 16 mb and a decent screen and have either a 0.5 or 1.0 >gigabyte fixed disk. I am particularly interested in which brand is the best >to choose. I have always been a 7xx series Thinkpad owner, but last week. I ordered a Fujitsu Lifebook 520T and have been really happy with it. I wish it had a trackpoint like the TPs instead of the finger pad, but I use a PS/2 mouse for windoweze operation. It has a built in 28.8 modem which leaves both pc card slots free. I've got a 11.8 inch active screen which is GREAT, haven't setup X for 8x600 yet, I need to get the latest XF (since I installed 2.1.5). Has a 6x IDE CD and a 810MB HD (replacable, but not easily removable). External Floppy (which I believe is swappable with the internal CDROM). And of course it is a P5-120 with 256 ext cache (so it is fast). I have the 3c589c PC card for ether and it works nicely. Good solid case, nice design, good keyboard. Stereo speakers for the ESS sound. Much better $ deal than from Toshiba or IBM. I got a P120/16MB/810MB/11.8"TFT/3c589C for under $2900 US which beat all comparable models by several hundred at the least. FUJI makes much of the laptop components for other laptops and unlike the other guys, these are in-stock ready to ship (the TP760 and the Toshiba I was looking at were both about $1200 more and probably 2 weeks wait!). Q: Does anyone know of a high-perf SCSI pc-card? I'd like to hang one of my JAZZ drives off this and seems that the supported PC scsi cards are AIC driver supported (YUK!) -Ken --- Ken Lam lam@awod.com Integrated Technical Systems Systems, Networks, and Internet Solutions -- Defining Technology Today "'Plug and Play' was only applicable to the original ATARI(tm)" From owner-freebsd-hackers Sat Dec 14 10:23:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA24115 for hackers-outgoing; Sat, 14 Dec 1996 10:23:24 -0800 (PST) Received: from ginger.vnet.net (root@ginger.vnet.net [166.82.1.69]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA24106 for ; Sat, 14 Dec 1996 10:23:22 -0800 (PST) Received: from jimi.vnet.net (jimi.vnet.net [166.82.1.19]) by ginger.vnet.net (8.8.2/8.8.2) with ESMTP id NAA25945 for ; Sat, 14 Dec 1996 13:29:27 -0500 Received: from artist.vnet.net (artist.vnet.net [166.82.239.40]) by jimi.vnet.net (8.8.4/8.8.4) with SMTP id NAA15470 for ; Sun, 15 Dec 1996 13:22:58 -0500 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 14 Dec 1996 13:20:04 -0500 (EST) From: Edwin Burley To: hackers@FreeBSD.org Subject: can't find wish in ports Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk ---------------------------------- E-Mail: khan@vnet.net Date: 12/14/96 Time: 13:20:04 ---------------------------------- Can someone tell me what happen to wish in the ports dir....it was under www but it is not there now...just got the new delta's for CTM today...and it is no t there.... thanks From owner-freebsd-hackers Sat Dec 14 10:46:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27282 for hackers-outgoing; Sat, 14 Dec 1996 10:46:04 -0800 (PST) Received: from tippy2.vnet.net (tippy2.vnet.net [166.82.197.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27272 for ; Sat, 14 Dec 1996 10:46:01 -0800 (PST) Received: from localhost (cmadison@localhost) by tippy2.vnet.net (8.8.3/8.6.9) with SMTP id NAA07429; Sat, 14 Dec 1996 13:46:17 -0500 (EST) Date: Sat, 14 Dec 1996 13:46:16 -0500 (EST) From: Chris Madison To: Edwin Burley cc: hackers@FreeBSD.org Subject: Re: can't find wish in ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Can someone tell me what happen to wish in the ports dir....it was under www > but it is not there now...just got the new delta's for CTM today...and it is no > t > there.... Isn't wish part of Tcl????? From owner-freebsd-hackers Sat Dec 14 11:03:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29228 for hackers-outgoing; Sat, 14 Dec 1996 11:03:58 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA29220 for ; Sat, 14 Dec 1996 11:03:55 -0800 (PST) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id OAA12344; Sat, 14 Dec 1996 14:03:52 -0500 (EST) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.8.3/8.7.3) with SMTP id OAA11351; Sat, 14 Dec 1996 14:03:51 -0500 (EST) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 14 Dec 1996 14:03:50 -0500 (EST) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: Chris Madison cc: Edwin Burley , hackers@FreeBSD.ORG Subject: Re: can't find wish in ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, Chris Madison wrote: > > > Can someone tell me what happen to wish in the ports dir....it was under www > > but it is not there now...just got the new delta's for CTM today...and it is no > > t > > there.... > > Isn't wish part of Tcl????? You're thinking of tclsh, wish is part of tk. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Dec 14 11:06:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29465 for hackers-outgoing; Sat, 14 Dec 1996 11:06:31 -0800 (PST) Received: from tippy2.vnet.net (tippy2.vnet.net [166.82.197.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA29454 for ; Sat, 14 Dec 1996 11:06:27 -0800 (PST) Received: from localhost (cmadison@localhost) by tippy2.vnet.net (8.8.3/8.6.9) with SMTP id OAA07546; Sat, 14 Dec 1996 14:06:40 -0500 (EST) Date: Sat, 14 Dec 1996 14:06:40 -0500 (EST) From: Chris Madison To: Chuck Robey cc: Edwin Burley , hackers@FreeBSD.ORG Subject: Re: can't find wish in ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You're thinking of tclsh, wish is part of tk. Yep, you be right;-) Checked the man page and it is part of Tk. From owner-freebsd-hackers Sat Dec 14 11:07:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29642 for hackers-outgoing; Sat, 14 Dec 1996 11:07:59 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA29631 for ; Sat, 14 Dec 1996 11:07:55 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA28104 for ; Sat, 14 Dec 1996 20:07:45 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA27712 for hackers@FreeBSD.org; Sat, 14 Dec 1996 20:07:29 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id UAA27551; Sat, 14 Dec 1996 20:07:16 +0100 (CET) Message-ID: Date: Sat, 14 Dec 1996 20:07:15 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@FreeBSD.org Subject: Re: can't find wish in ports References: X-Mailer: Mutt 0.53 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2768 In-Reply-To: ; from Chris Madison on Dec 14, 1996 13:46:16 -0500 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Chris Madison: > Isn't wish part of Tcl????? Not exactly. Wish is the graphical shell from Tk. The shell from tcl is tclsh. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 From owner-freebsd-hackers Sat Dec 14 11:43:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA03321 for hackers-outgoing; Sat, 14 Dec 1996 11:43:42 -0800 (PST) Received: from ginger.vnet.net (root@ginger.vnet.net [166.82.1.69]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA03315 for ; Sat, 14 Dec 1996 11:43:39 -0800 (PST) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.8.2/8.8.2) with ESMTP id OAA27581; Sat, 14 Dec 1996 14:49:45 -0500 Received: from artist.vnet.net (artist.vnet.net [166.82.239.40]) by elvis.vnet.net (8.8.4/8.8.4) with SMTP id OAA01006; Sat, 14 Dec 1996 14:43:26 -0500 (EST) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 14 Dec 1996 14:41:55 -0500 (EST) From: Edwin Burley To: (Ollivier Robert) Subject: Re: can't find wish in ports Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 15-Dec-96 roberto@keltia.freenix.fr wrote: >>According to Chris Madison: >> Isn't wish part of Tcl????? > >Not exactly. Wish is the graphical shell from Tk. The shell from tcl is >tclsh. >-- >Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 - Have you they moved it...Robert From owner-freebsd-hackers Sat Dec 14 11:59:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04779 for hackers-outgoing; Sat, 14 Dec 1996 11:59:04 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04752 for ; Sat, 14 Dec 1996 11:58:56 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id LAA19998 for ; Sat, 14 Dec 1996 11:58:55 -0800 (PST) Message-Id: <199612141958.LAA19998@austin.polstra.com> To: freebsd-hackers@freebsd.org Subject: CVSup 14.0 is now available Date: Sat, 14 Dec 1996 11:58:54 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Announcing CVSup 14.0 --------------------- Release 14.0 of CVSup, the CVS-aware network distribution system, is now available. Where to Get CVSup ------------------ CVSup is free software. It is available from the following FTP sites: ftp://freefall.freebsd.org/pub/CVSup/ ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ (slow; avoid if possible) Full sources as well as FreeBSD binaries are available: cvsup-bin-14.0.tar.gz FreeBSD static binaries for the client cvsupd-bin-14.0.tar.gz FreeBSD static binaries for the server cvsup-14.0.tar.gz Sources ** MD5 signatures for these files are: MD5 (cvsup-bin-14.0.tar.gz) = 7a5cef5919d28979d6e33dcf7b2898c0 MD5 (cvsupd-bin-14.0.tar.gz) = 5c29e36e339582693f2bc2db23254449 MD5 (cvsup-14.0.tar.gz) = 331bb5c114bac2053eeaa46eaa8f19c3 An updated port will appear in the FreeBSD ports and packages collections soon: ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/net/cvsup/ ftp://ftp.freebsd.org/pub/FreeBSD/packages-current/net/cvsup-14.0.tgz The FreeBSD package now depends only on the "modula-3-lib" package, a subset of the Modula-3 installation consisting of only the shared libraries. Because of this, you can now install and use the "cvsup" package in a reasonable amount of disk space. The package is much smaller than the statically linked binary distribution, so updates to new versions of CVSup should be more convenient now. The package is the recommended distribution for binary-only users. The static binary distributions will probably be phased out soon. If you want SOCKS support, you must also install the "modula-3-socks" port or package: ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/lang/modula-3-socks/ ftp://ftp.freebsd.org/pub/FreeBSD/packages-current/lang/modula-3-socks-1.0.tgz SOCKS is supported only under FreeBSD, and only with dynamically linked executables. The static binary distributions do not support SOCKS. ** If you wish to build CVSup from the sources, be sure to read the discussion further on in this announcement. Should You Bother to Upgrade? ----------------------------- Yes, you should. This release has many enhancements over the previous release, not to mention a few non-negligible bug fixes and security precautions. People running servers are particularly urged to upgrade. Clients won't be able to take advantage of the enhancements unless their servers support them. Compatibility with Previous Releases ------------------------------------ There are a couple of very minor compatibility issues which could affect a few users upgrading from an earlier release. Clients: The default for the "base" directory has changed from "/usr" to "/usr/local/etc/cvsup". Practically everybody specifies the base explicitly in their supfiles, so this change will have no impact for most people. If you have been using the default value, you will need to add a line "*default base=/home" to your supfile, or specify "-b /home" on the cvsup command line. Servers: The "hostbase" is no longer taken from the client's supfile. It is now controlled on the server host. On the FreeBSD project, "hostbase=/home" was always used in the past. People operating servers will need to specify "-b /home" on the cvsupd command line to get the same effect. Alternatively, move your server configuration files from "/home" to the new default location, "/usr/local/etc/cvsup". (As before, most of the configuration files appear under a subdirectory named "sup".) What Has Changed Since the Previous Release? -------------------------------------------- CVSup now uses Tridgell & Mackerras' "rsync" algorithm for updating non-RCS files. It is enabled by default, though it can be turned off for individual collections by specifying the "norysnc" keyword. The supfile can now have special collections named "*default" to specify default parameters for subsequent collections. The "base" and "host" supfile settings can now be overridden on the client's command line. The client now supports multiple "refuse" files: a global one which applies to all collections; a per-collection one; and one that is specific to a release+tag within its collection. There is now a client option to specify a lock file, to prevent multiple cvsup processes from interfering with each other. It is useful when the client is run periodically from cron, to avoid trouble if a job runs unusually long because of network problems. The client now refuses to create the "base" or "prefix" directory for any collection. Instead, it emits a diagnostic if either directory doesn't exist. As a special case, if the "prefix" is a symbolic link pointing to a nonexistent file named "SKIP", the associated collection will be skipped without complaint. The default "base" for the client is now "/usr/local/etc/cvsup". Both the server's and client's "prefix" directories are now interpreted relative to their base directories, if they are not absolute pathnames. The client now silently refuses to set the setuid, setgid, and sticky bits in files that it creates or updates. The client now does a better job of cleaning up its temporary files when it is killed by a signal. The client now tries harder to look up the IP address of the server host. There is a new "keywordprefix" keyword for the server's "releases" file. It specifies a prefix that is used when constructing the pathnames generated by the Header and Source RCS keywords. This allows the actual repositories to be in different places on different machines, while still producing identical expansions of the RCS keywords. The server will now accept connections from certain "friends" listed in a configuration file, regardless of whether the maximum number of simultaneous connections has been exceeded. The server can now do its logging via syslog. The server log messages have been cleaned up quite a bit. The server now logs any repository problems that it notices, e.g., unparsable RCS files, non-RCS files in the Attic, and so forth. The server now ignores any "hostbase" specified in the client's supfile. A new server argument "-b base" specifies the base directory. The default is now "/usr/local/etc/cvsup". The server now validates all collection names to make sure they contain no slashes and are not equal to "." or "..". The server now checks for certain errors earlier, before becoming a daemon. All of the programs except the server now install into "/usr/local/bin". The server still installs into "/usr/local/sbin". Fixed a bug in the ordering of the "branches" list in the RCS file, which on very rare occasions caused a "fixup" to be required. Fixed a bug which could cause the client to hang trying to flush its network buffers after the user pressed the "stop" button in the GUI. Fixed a bug that caused the client to complain "file exists" when trying to create directories leading up to a new file, if the pathname contained a "." (current directory) component in it. This prevented "upgrade ." from being used in the server collection list files. Unfortunately, since it's a client-side bug, such lines still should not be used for a while, until older releases of the client have evaporated away. Fixed a bug which produced a misleading error message when a failure occurred in making the directories leading up to the temporary file that is used for the list file in the client. When bad tokens or protocol errors are encountered, the offending text is no longer included in the error message. Sometimes it contained voluminous amounts of garbage. Messages reporting errors in the client-side list files are accompanied by line numbers now. What Is CVSup? -------------- CVSup is a software package for distributing and updating collections of files across a network. CVSup is specifically tailored to distributing CVS repositories. By taking advantage of the special properties of the files contained in CVS repositories, CVSup is able to perform updates much faster than traditional systems. It is especially valuable for people with slow Internet connections. CVSup parses and understands the RCS files making up a CVS repository. When updates occur, CVSup extracts new deltas directly from the RCS files on the server and edits them into the client's RCS files. Likewise, CVSup notes the addition of new symbolic tags to the files on the server and sends only the new tags to the client. CVSup is able to merge new deltas and tags from the server with deltas and tags added locally on the client machine. This makes it possible for the client to check local modifications into his repository without their being obliterated by subsequent updates from the server. Note: Although this feature is fully implemented in CVSup, it will probably not be practical to use it until some small changes have been made to CVS. In addition to distributing the RCS files themselves, CVSup is able to distribute specific checked-out versions. The client can specify a symbolic tag, a date, or both and CVSup will extract the appropriate versions from the server's CVS repository. Checked-out versions do not need to be stored on the server since CVSup can extract any version directly from the CVS repository. If the client has an existing checked-out tree, CVSup will apply the appropriate edits to update the tree or transform it into the requested version. Only the differences between the existing version and the desired version are sent across the network. To update non-RCS files, CVSup uses the highly efficient rsync algorithm, developed by Andrew Tridgell and Paul Mackerras. CVSup uses lightweight processes (threads) to implement a streaming protocol across the network. This completely eliminates the delays associated with the lock-step, request-reply form of communication used by many existing protocols, such as sup and NNTP. Information is transferred at the full available speed of the network in both directions at once. Network latency and server response delays are rendered practically irrelevant. CVSup uses the "zlib" compression package to optionally compress all communications. This provides an additional 65-75% compression, on top of the diff-based compression already built into CVSup. For efficiency, all processing is built into the CVSup package itself. Neither the client nor the server executes any other programs. For further information about how CVSup works, see the "Blurb" document in the CVSup distribution. Using CVSup to Maintain FreeBSD Sources --------------------------------------- CVSup servers are currently running at the following FreeBSD mirror sites: USA: cvsup.freebsd.org cvsup2.freebsd.org The Netherlands: cvsup.nl.freebsd.org Using CVSup, you can easily receive or update any of the standard FreeBSD source releases, namely, "cvs", "current", and "stable". The manual page for cvsup(1) describes how to do that. If all goes well, additional servers will come on-line soon. Building CVSup from the Sources ------------------------------- CVSup is written in Modula-3, a modern, compiled, object-oriented language. Modula-3 integrates threads, exceptions, and garbage collection, providing an ideal vehicle for this sort of application. Without Modula-3, CVSup would almost certainly not exist today. If you wish to build CVSup from the sources, you will first need to install the free Modula-3 compiler and runtime libraries from DEC SRC. A port is available in the FreeBSD ports collection, in "lang/modula-3". The corresponding package is, of course, available in the packages collection. You will also need version 1.0.4 or later of the "zlib" library. In FreeBSD-2.1.6 and later releases, this library has been incorporated into the system sources, in "src/lib/libz". Prior to that, a FreeBSD port was available in "devel/libz" of the FreeBSD ports collection. For other sources of this library, see the "Install" file. Do not try to use versions earlier than 1.0.4. You will also need Poul-Henning Kamp's "libmd" library. It is a standard library on FreeBSD systems. Portability Issues ------------------ I intend for CVSup to be portable to most POSIX systems. The present release has only been tested under FreeBSD versions 2.1 and later. Primarily because of packaging problems, this release of CVSup probably won't build out-of-the-box on other systems. Among other things, it relies on Poul-Henning Kamp's "libmd" encapsulation of the MD5 subroutines. The library itself is quite portable, but its Makefiles are BSD-specific. There are probably some other FreeBSD-specific things in CVSup that have not been found yet. Anybody who succeeds in porting CVSup to other systems is encouraged to send his changes to . As long as the changes are reasonably palatable, they will be incorporated into future CVSup releases. CVSup uses several POSIX-specific functions which may make it more of an effort to port the package to non-POSIX systems such as Win32. These functions include mmap, fork, syslog, stat, and chmod, among others. Status of this Release ---------------------- CVSup has seen heavy use and has been quite stable for months. Like all software, though, it is not perfect. Please be prepared to find bugs -- without a doubt, there are some. Please report bugs to . -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Sat Dec 14 12:13:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06366 for hackers-outgoing; Sat, 14 Dec 1996 12:13:20 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA06356 for ; Sat, 14 Dec 1996 12:13:16 -0800 (PST) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id PAA10995; Sat, 14 Dec 1996 15:13:13 -0500 (EST) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.8.3/8.7.3) with SMTP id PAA11539; Sat, 14 Dec 1996 15:13:12 -0500 (EST) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 14 Dec 1996 15:13:12 -0500 (EST) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: Edwin Burley cc: roberto@keltia.freenix.fr, hackers@freebsd.org Subject: Re: can't find wish in ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, Edwin Burley wrote: > > On 15-Dec-96 roberto@keltia.freenix.fr wrote: > >>According to Chris Madison: > >> Isn't wish part of Tcl????? > > > >Not exactly. Wish is the graphical shell from Tk. The shell from tcl is > >tclsh. It's right where it always was, in with tk. /usr/ports/x11/tk41, for the latest one ported. > >-- > >Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr > > FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Tue Dec 3 23:52:58 CET 1996 > > - > Have you they moved it...Robert > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Dec 14 12:44:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA10570 for hackers-outgoing; Sat, 14 Dec 1996 12:44:43 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA10550 for ; Sat, 14 Dec 1996 12:44:39 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id MAA00303 for ; Sat, 14 Dec 1996 12:45:06 -0800 (PST) Received: (qmail 973 invoked by uid 110); 14 Dec 1996 20:44:16 -0000 Message-ID: <19961214204416.972.qmail@suburbia.net> Subject: Re: questions... In-Reply-To: from Steve Reid at "Dec 14, 96 12:18:21 pm" To: steve@edmweb.com (Steve Reid) Date: Sun, 15 Dec 1996 07:44:16 +1100 (EST) Cc: hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Only worry about files that are suid or sgid. Other binaries can't do > anything that the user can't do. Removing the execute bit from > non-suid/sgid binaries won't add any to security- a malicious user can > create any non-suid/sgid file him/her self. Even if you remove gcc, the > user could still FTP the files from ftp.cdrom.com. Removing FTP won't help > either- clever use of redirection can allow a user to transfer whatever > files they want over their own tty. /dev/wd0a on / (asynchronous, local, noatime) procfs on /proc (local, nodev, noexec, nosuid) mfs:24 on /tmp (asynchronous, local, noatime, nodev, noexec, nosuid) /dev/wd0s1f on /usr (asynchronous, local, noatime, nodev) /dev/wd0s1e on /var (asynchronous, local, noatime, nodev, noexec, nosuid) /dev/wd2s1e on /usr/local/var (asynchronous, local, nodev, noexec, nosuid) /dev/wd3s1e on /home (asynchronous, local, nodev, noexec, nosuid) /dev/sd0s1e on /data (asynchronous, local, nodev, noexec, nosuid) /data/ftp/pub on /usr/local/ftp/pub (local, nodev, noexec, nosuid) /dev/matcd0a on /usr/local/ftp/mnt/cd0 (local, nodev, noexec, nosuid, read-only) ../sbin-sec is root, mode 700 there are no writable directories on / or /usr Note that you will also need to modify ld.so to prevent dynamic binding using env variables. Unfortunately this isn't a total cure, because there are 1001 stack overflows in NON-suid programs. total 10676 -r-xr-xr-x 1 bin bin 57344 Dec 12 17:21 adjkerntz -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 badsect lrwxr-xr-x 1 bin bin 21 Dec 12 17:22 ccdconfig -> ../sbin-sec/ccdconfig -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 clri -r-xr-xr-x 1 bin bin 36864 Dec 12 17:21 comcontrol -r-xr-xr-x 1 bin bin 110592 Dec 12 17:21 disklabel lrwxr-xr-x 1 bin bin 17 Dec 12 17:22 dmesg -> ../sbin-sec/dmesg -r-xr-xr-x 1 bin bin 90112 Dec 12 17:21 dset lrwxr-xr-x 1 bin bin 16 Dec 12 17:22 dump -> ../sbin-sec/dump -r-xr-xr-x 1 bin bin 61440 Dec 12 17:21 dumpfs -r-xr-xr-x 1 bin bin 57344 Dec 12 17:21 dumplfs -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 dumpon -r-xr-xr-x 4 bin bin 167936 Dec 12 17:22 fastboot -r-xr-xr-x 4 bin bin 167936 Dec 12 17:22 fasthalt -r-xr-xr-x 1 bin bin 53248 Dec 12 17:21 fdisk -r-xr-xr-x 1 bin bin 180224 Dec 12 17:21 fsck -r-xr-xr-x 1 bin bin 270336 Dec 12 17:21 fsdb -r-xr-xr-x 1 bin bin 57344 Dec 12 17:21 ft -r-xr-xr-x 4 bin bin 167936 Dec 12 17:22 halt -r-xr-x--- 1 bin staff 131072 Dec 12 17:21 ifconfig -r-x------ 1 bin bin 184320 Nov 23 17:53 init -r-xr-xr-x 1 bin bin 122880 Dec 12 17:21 ipfw -r-xr-xr-x 1 bin bin 45056 Dec 12 17:21 ldconfig -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 md5 -r-xr-xr-x 1 bin bin 36864 Dec 12 17:21 mknod -r-xr-xr-x 1 bin bin 45056 Dec 12 17:21 modload -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 modunload -r-xr-xr-x 1 bin bin 69632 Dec 12 17:21 mount -r-xr-xr-x 1 bin bin 49152 Dec 12 17:21 mount_cd9660 -r-xr-xr-x 5 bin bin 49152 Dec 12 17:21 mount_devfs -r-xr-xr-x 1 bin bin 49152 Dec 12 17:21 mount_ext2fs -r-xr-xr-x 5 bin bin 49152 Dec 12 17:21 mount_fdesc -r-xr-xr-x 5 bin bin 49152 Dec 12 17:21 mount_kernfs -r-xr-xr-x 1 bin bin 49152 Dec 12 17:21 mount_lfs -r-xr-xr-x 2 bin bin 122880 Dec 12 17:21 mount_mfs lrwxr-xr-x 1 bin bin 23 Dec 12 17:22 mount_msdos -> ../sbin-sec/mount_msdos -r-xr-xr-x 1 bin bin 122880 Dec 12 17:21 mount_nfs -r-xr-xr-x 1 bin bin 53248 Dec 12 17:21 mount_null -r-xr-xr-x 1 bin bin 204800 Dec 12 17:21 mount_portal -r-xr-xr-x 5 bin bin 49152 Dec 12 17:21 mount_procfs -r-xr-xr-x 5 bin bin 49152 Dec 12 17:21 mount_std -r-xr-xr-x 1 bin bin 57344 Dec 12 17:21 mount_umap -r-xr-xr-x 1 bin bin 53248 Dec 12 17:21 mount_union -r-xr-xr-x 1 bin bin 200704 Dec 12 17:21 mountd -r-xr-xr-x 2 bin bin 122880 Dec 12 17:21 newfs -r-xr-xr-x 1 bin bin 98304 Dec 12 17:21 newlfs -r-xr-xr-x 1 bin bin 40960 Dec 12 17:21 nextboot -r-xr-xr-x 1 bin bin 69632 Dec 12 17:21 nfsd -r-xr-xr-x 1 bin bin 61440 Dec 12 17:21 nfsiod -r-xr-xr-x 1 bin bin 1907 Dec 12 17:21 nologin -r-sr-xr-x 1 root bin 122880 Dec 12 17:21 ping -r-xr-xr-x 1 bin bin 139264 Dec 12 17:21 quotacheck -r-xr-xr-x 1 root bin 118784 Dec 12 17:21 rdisc lrwxr-xr-x 1 bin bin 17 Dec 12 17:22 rdump -> ../sbin-sec/rdump -r-xr-xr-x 4 bin bin 167936 Dec 12 17:22 reboot lrwxr-xr-x 1 bin bin 19 Dec 12 17:22 restore -> ../sbin-sec/restore lrwxr-xr-x 1 bin bin 17 Dec 12 17:22 route -> ../sbin-sec/route -r-x------ 1 root bin 180224 Dec 12 17:22 routed lrwxr-xr-x 1 bin bin 20 Dec 12 17:22 rrestore -> ../sbin-sec/rrestore -r-x------ 1 root bin 122880 Dec 12 17:22 rtquery -r-xr-xr-x 1 bin bin 69632 Dec 12 17:22 savecore -r-xr-xr-x 1 bin bin 65536 Dec 12 17:22 scsi -r-xr-xr-x 1 bin bin 3306 Dec 12 17:22 scsiformat lrwxr-xr-x 1 bin bin 20 Dec 12 17:22 shutdown -> ../sbin-sec/shutdown -r-xr-xr-x 1 bin bin 61440 Dec 12 17:22 slattach lrwxr-xr-x 1 bin bin 21 Dec 12 17:22 sliplogin -> ../sbin-sec/sliplogin -r-xr-xr-x 1 bin bin 69632 Dec 12 17:22 startslip -r-xr-xr-x 1 bin bin 49152 Dec 12 17:22 swapon -r-xr-xr-x 1 bin bin 45056 Dec 12 17:22 tunefs -r-xr-xr-x 1 bin bin 122880 Dec 12 17:22 umount -Julian A. (proff@suburbia.net) From owner-freebsd-hackers Sat Dec 14 13:26:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA14453 for hackers-outgoing; Sat, 14 Dec 1996 13:26:42 -0800 (PST) Received: from rosemary.fsl.noaa.gov (rosemary.fsl.noaa.gov [137.75.8.41]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA14447 for ; Sat, 14 Dec 1996 13:26:39 -0800 (PST) Received: from sage.fsl.noaa.gov (sage.fsl.noaa.gov [137.75.253.42]) by rosemary.fsl.noaa.gov (8.7.5/8.6.12) with SMTP id OAA04186; Sat, 14 Dec 1996 14:25:49 -0700 (MST) Message-ID: <32B31B5C.167EB0E7@fsl.noaa.gov> Date: Sat, 14 Dec 1996 14:25:48 -0700 From: Sean Kelly Organization: NOAA Forecast Systems Laboratory X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Chuck Robey CC: Edwin Burley , roberto@keltia.freenix.fr, hackers@freebsd.org Subject: Re: can't find wish in ports References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey wrote: > It's right where it always was, in with tk. /usr/ports/x11/tk41, for the > latest one ported. But the latest version is tk4.2 and tcl7.6. Luckily, they both compile and install out-of-the-box on FreeBSD 2.1.5. Tk4.2 features a couple of nice file selection dialog boxes, too. -- Sean Kelly NOAA Forecast Systems Laboratory Boulder Colorado USA From owner-freebsd-hackers Sat Dec 14 13:27:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA14575 for hackers-outgoing; Sat, 14 Dec 1996 13:27:26 -0800 (PST) Received: from narcissus.ml.org (brosenga.st.pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA14569 for ; Sat, 14 Dec 1996 13:27:24 -0800 (PST) Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id NAA05614; Sat, 14 Dec 1996 13:27:13 -0800 (PST) Date: Sat, 14 Dec 1996 13:27:12 -0800 (PST) From: Snob Art Genre To: John Polstra cc: freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-Reply-To: <199612141958.LAA19998@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, John Polstra wrote: > Building CVSup from the Sources > ------------------------------- > You will also need version 1.0.4 or later of the "zlib" library. > In FreeBSD-2.1.6 and later releases, this library has been incorporated > into the system sources, in "src/lib/libz". Prior to that, a > FreeBSD port was available in "devel/libz" of the FreeBSD ports > collection. For other sources of this library, see the "Install" > file. Do not try to use versions earlier than 1.0.4. Where can version 1.0.4 or later for FreeBSD 2.1.5 be found? I've poked around on the FTP site and all I can find is version 1.0.2; that's also what lives in the ports/packages collections on the 2.1.5 CDs. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > Ben The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-hackers Sat Dec 14 13:30:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA14896 for hackers-outgoing; Sat, 14 Dec 1996 13:30:30 -0800 (PST) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA14864; Sat, 14 Dec 1996 13:30:21 -0800 (PST) Received: from localhost (jdowdal@localhost) by destiny.erols.com (8.8.4/8.6.12) with SMTP id QAA20784; Sat, 14 Dec 1996 16:28:37 -0500 (EST) Date: Sat, 14 Dec 1996 16:28:36 -0500 (EST) From: John Dowdal To: proff@suburbia.net cc: Steve Reid , hackers@freebsd.org, security@freebsd.org Subject: Re: questions... In-Reply-To: <19961214204416.972.qmail@suburbia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 15 Dec 1996 proff@suburbia.net wrote: > Unfortunately this isn't a total cure, because there are 1001 stack overflows > in NON-suid programs. So what. The programs will just core dump if they stack overflow, else just not work right. Since they are not SUID and not run as root [inetd, ...], they won't be able to get root if they blow up. John From owner-freebsd-hackers Sat Dec 14 13:32:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA15041 for hackers-outgoing; Sat, 14 Dec 1996 13:32:04 -0800 (PST) Received: from blacklodge.c2.net (root@blacklodge.c2.net [140.174.185.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA15035; Sat, 14 Dec 1996 13:32:01 -0800 (PST) Received: from clotho.c2.org (clotho.c2.org [140.174.185.10]) by blacklodge.c2.net (8.7.6/8.7.3) with ESMTP id NAA12111; Sat, 14 Dec 1996 13:33:31 -0800 (PST) From: sameer Received: (from sameer@localhost) by clotho.c2.org (8.7.6/8.7.3) id NAA11065; Sat, 14 Dec 1996 13:32:14 -0800 (PST) Message-Id: <199612142132.NAA11065@clotho.c2.org> Subject: Re: getdtablesize, OPEN_MAX, and sysctl To: bde@zeta.org.au (Bruce Evans) Date: Sat, 14 Dec 1996 13:32:14 -0800 (PST) Cc: bde@zeta.org.au, sameer@c2.net, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG In-Reply-To: <199612140544.QAA27898@godzilla.zeta.org.au> from "Bruce Evans" at Dec 14, 96 04:44:05 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This option sets the soft resource limit for the maximum number of open > files for the init process. The limit is inherited by all processes > but may be changed. Processes should change it using setrlimit() if > they or their children need a larger limit. I see. > > In 2.1-stable, you can't do a select on more than FD_SETSIZE fd's, where > FD_SETSIZE is whatever it is when the kernel is compiled (default 256). > In later versions, there is no limit in the kernel; if you want more > than the default FD_SETSIZE number of fds, you just have to define > FD_SETSIZE consistently before including any headers (since any header > might include ). That makes sense, thanks a lot. -- Sameer Parekh Voice: 510-986-8770 President FAX: 510-986-8777 C2Net http://www.c2.net/ sameer@c2.net From owner-freebsd-hackers Sat Dec 14 13:46:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA16346 for hackers-outgoing; Sat, 14 Dec 1996 13:46:03 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA16338; Sat, 14 Dec 1996 13:46:01 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA22244; Sat, 14 Dec 1996 14:23:11 -0700 From: Terry Lambert Message-Id: <199612142123.OAA22244@phaeton.artisoft.com> Subject: Re: vulnerability in new pw suite To: proff@iq.org (Julian Assange) Date: Sat, 14 Dec 1996 14:23:11 -0700 (MST) Cc: security@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199612140135.MAA04639@profane.iq.org> from "Julian Assange" at Dec 14, 96 12:35:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The FreeBSD account administration pw suite is able to produce > "random" passwords for new accounts. Due to the simplicity of the > password generation algorithm involved, the passwords are easily > predictable amid a particular range of possibilities. This range > may be very narrow, depending on what sort of information is > available to the attacker. [ ... vunerability description elided ... ] I've noticed a similar restriction on the search space is caused by enforcing password length and use of particular values (digits, control characters, and capitalization) Once we add in "non-pronouncible" and "not in dictionary" and so on, I think that eventually, in the interests of "security", users will be forced to choose from a list of 10 or so "sufficiently safe" passwords. Of course, once that happens, we'll just publish the list... any restriction on "allowed values" is an implicit restriction of the search space a cracker is required to search, and makes cracking just that much easier. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Dec 14 13:48:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA16760 for hackers-outgoing; Sat, 14 Dec 1996 13:48:49 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA16749 for ; Sat, 14 Dec 1996 13:48:46 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id NAA23179; Sat, 14 Dec 1996 13:48:30 -0800 (PST) Message-Id: <199612142148.NAA23179@austin.polstra.com> To: Snob Art Genre cc: freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-reply-to: Your message of "Sat, 14 Dec 1996 13:27:12 PST." References: Date: Sat, 14 Dec 1996 13:48:30 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Where can version 1.0.4 or later for FreeBSD 2.1.5 be found? I've poked > around on the FTP site and all I can find is version 1.0.2; that's also > what lives in the ports/packages collections on the 2.1.5 CDs. FTP to this directory: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/lib/ and fetch "Makefile.inc" and also the entire "libz" subdirectory. Then you should be able to chdir into "libz" and build and install the library with the usual "make" incantations. If it doesn't work for you, please let me know. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Sat Dec 14 14:02:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA18411 for hackers-outgoing; Sat, 14 Dec 1996 14:02:21 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18401 for ; Sat, 14 Dec 1996 14:02:18 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id OAA01324 for ; Sat, 14 Dec 1996 14:02:42 -0800 (PST) Received: (qmail 6372 invoked by uid 110); 14 Dec 1996 22:01:41 -0000 Message-ID: <19961214220141.6371.qmail@suburbia.net> Subject: Re: questions... In-Reply-To: from John Dowdal at "Dec 14, 96 04:28:36 pm" To: jdowdal@destiny.erols.com (John Dowdal) Date: Sun, 15 Dec 1996 09:01:41 +1100 (EST) Cc: steve@edmweb.com, hackers@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sun, 15 Dec 1996 proff@suburbia.net wrote: > > > Unfortunately this isn't a total cure, because there are 1001 stack overflows > > in NON-suid programs. > > So what. The programs will just core dump if they stack overflow, else > just not work right. Since they are not SUID and not run as root [inetd, > ...], they won't be able to get root if they blow up. > > John > > You miss the point. There are kernel level bugs, and bugs in suid programs often requires executable trigger code. The design goal behind the file system layout I presented is to prevent execution of any attacker designed code. This is not possible due to stack over-write conditions in NON suid programs. Decent mmu's, such is found on alpha cpu's have real PROT_EXEC memory protections, which is turned off for the stack segment. It is still possible to exploit stack over-flows as the pc is usurpable. Finding existing code to point it to that will achieve your ends however is very difficult. Which reminds me. Several mmu changes were introduced with the P6 including 2Mb pages and 36 bit addressing modes. Has anyone verified that real exec protections didn't also make their way in? I don't know much about P5/P6 hardware break-point/watch support, but I can't help wondering if it will take ranges, rather than just fixed locations and for exec instead of r/w. Can someone who knows more about the P5/6 enhancements than myself comment? Note that sunos4.1.x is not vulnerable to noexec subversion by LD_PRELOADing, as mmap's of PROT_EXEC fail on noexec file systems. I haven't examined FreeBSD's vm system in this regard, but clearly the sun behaviour is correct, as is refusing mprotect() changes to fd's on noexec vnodes. btw (dyson?) are union mounts working correctly yet? Seems like the ideal solution for ro file systems with site modifications. -Julian A. (proff@suburbia.net) From owner-freebsd-hackers Sat Dec 14 14:17:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20137 for hackers-outgoing; Sat, 14 Dec 1996 14:17:02 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA20130 for ; Sat, 14 Dec 1996 14:16:59 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA25681; Sat, 14 Dec 1996 15:16:53 -0700 (MST) Date: Sat, 14 Dec 1996 15:16:53 -0700 (MST) Message-Id: <199612142216.PAA25681@rocky.mt.sri.com> From: Nate Williams To: John Polstra Cc: freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-Reply-To: <199612141958.LAA19998@austin.polstra.com> References: <199612141958.LAA19998@austin.polstra.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Polstra writes: > Announcing CVSup 14.0 > --------------------- > Release 14.0 of CVSup, the CVS-aware network distribution system, is now > available. :) ... > What Has Changed Since the Previous Release? > -------------------------------------------- > The client now supports multiple "refuse" files: a global one > which applies to all collections; a per-collection one; and one > that is specific to a release+tag within its collection. OK, since I have no reason/interest to have the pc98 files, I decided I'd blow them away on my box and tell CVSup not to get them anymore. I created the file ~sup/src-sys/refuse.cvs with the following lines: */pc98 */pc98/* src/sys/pc98 src/sys/pc98/* But none of them work. How do I tell my client to not get the pc98 files? Nate From owner-freebsd-hackers Sat Dec 14 14:44:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA23838 for hackers-outgoing; Sat, 14 Dec 1996 14:44:35 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA23833 for ; Sat, 14 Dec 1996 14:44:32 -0800 (PST) Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id RAA16011; Sat, 14 Dec 1996 17:44:25 -0500 (EST) Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.3/8.7.3) with SMTP id RAA23442; Sat, 14 Dec 1996 17:44:24 -0500 (EST) X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 14 Dec 1996 17:43:34 -0500 (EST) From: Chuck Robey X-Sender: chuckr@uplink.eng.umd.edu To: Sean Kelly cc: Edwin Burley , roberto@keltia.freenix.fr, hackers@freebsd.org Subject: Re: can't find wish in ports In-Reply-To: <32B31B5C.167EB0E7@fsl.noaa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 14 Dec 1996, Sean Kelly wrote: > Chuck Robey wrote: > > > It's right where it always was, in with tk. /usr/ports/x11/tk41, for the > > latest one ported. > > But the latest version is tk4.2 and tcl7.6. Luckily, they both compile > and install out-of-the-box on FreeBSD 2.1.5. > > Tk4.2 features a couple of nice file selection dialog boxes, too. That's one of the first things I'm going to do (at least it's high on my list) when my last final finishes, on Thursday. > > -- > Sean Kelly > NOAA Forecast Systems Laboratory > Boulder Colorado USA > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Dec 14 14:55:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA24919 for hackers-outgoing; Sat, 14 Dec 1996 14:55:19 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA24906 for ; Sat, 14 Dec 1996 14:55:14 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id OAA23778; Sat, 14 Dec 1996 14:55:10 -0800 (PST) Message-Id: <199612142255.OAA23778@austin.polstra.com> To: Nate Williams cc: freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-reply-to: Your message of "Sat, 14 Dec 1996 15:16:53 MST." <199612142216.PAA25681@rocky.mt.sri.com> References: <199612141958.LAA19998@austin.polstra.com> <199612142216.PAA25681@rocky.mt.sri.com> Date: Sat, 14 Dec 1996 14:55:10 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The client now supports multiple "refuse" files: a global one > > which applies to all collections; a per-collection one; and one > > that is specific to a release+tag within its collection. > > OK, since I have no reason/interest to have the pc98 files, I decided > I'd blow them away on my box and tell CVSup not to get them anymore. > > I created the file ~sup/src-sys/refuse.cvs with the following lines: > */pc98 > */pc98/* > src/sys/pc98 > src/sys/pc98/* > > But none of them work. How do I tell my client to not get the pc98 > files? This ought to work. I tried it here with exactly the same setup, and it worked. Are you sure you're using version 14.0 of cvsup? Type "cvsup -v" to make sure. A couple of people have gotten bitten by my change of installation directory to "/usr/local/bin". They still had the old version in "/usr/local/sbin" and it was first in their PATH. If that's not it, let me know and we'll track this down. By the way, I think _any_ of the 4 lines in your refuse file should be sufficient. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Sat Dec 14 15:35:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA29176 for hackers-outgoing; Sat, 14 Dec 1996 15:35:58 -0800 (PST) Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA29169 for ; Sat, 14 Dec 1996 15:35:54 -0800 (PST) Received: from c493.tgb.toyota.co.uk (tgb-isd.demon.co.uk [194.222.88.26]) by deputy.pavilion.co.uk (8.7/8.7) with SMTP id XAA06148; Sat, 14 Dec 1996 23:34:38 GMT Date: Sat, 14 Dec 1996 23:34:38 GMT Message-Id: <199612142334.XAA06148@deputy.pavilion.co.uk> X-Sender: aledm@mailhost.pavilion.co.uk X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Guido van Rooij , freebsd-hackers@freebsd.org From: Aled Morris Subject: Re: notebook: which one Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 13:52 13/12/96 +0100, Guido van Rooij wrote: >I am looking for a notebook that is well supported under FreeBSD. >It should have 16 mb and a decent screen and have either a 0.5 or 1.0 >gigabyte fixed disk. I am particularly interested in which brand is the best >to choose. I have a Digitial HiNote Ultra (the "Ultra" bit is important!) which you can now get with Pentium processor (mine is 486) that I use for FreeBSD. I believe it is the development platform for the pccard stuff, so the support for PCMCIA should be good! The size and weight is remarkable, I strongly recommend them (much better than the Toshiba I'm temporarily lumbered with) Aled -- telephone +44 973 207987 O- From owner-freebsd-hackers Sat Dec 14 15:52:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA00905 for hackers-outgoing; Sat, 14 Dec 1996 15:52:44 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA00886 for ; Sat, 14 Dec 1996 15:52:39 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id PAA00848 for ; Sat, 14 Dec 1996 15:52:39 -0800 (PST) To: hackers@freebsd.org Subject: Important info for 4MB Mem/1.2MB floppy folk. Date: Sat, 14 Dec 1996 15:52:38 -0800 Message-ID: <843.850607558@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 2.2-RELEASE will not support installation of machines with < 4MB of memory or 1.2MB floppy drives - that is to say, only > 5MB memory & 1.44MB floppy drive systems are supported. In truth, 8MB of memory is the recommended minimum. Those who have such limitations on their configuration and can't upgrade, for whatever reason, are therefore urged to stay with 2.1.6-RELEASE, which has provisions for both types of installation and will probably be more than functional for as long as one might conceivably wish to continue operating such a system. We regret any inconvenience this may cause some of our users, but we have also been pressed for space on the installation media for some time now, and this was more or less inevitable. We've talked about killing the 4MB installation and 1.2MB floppies for over a year, and it's only through some of the most arcane trickery (you don't want to know) that we've managed to keep it all on a single floppy at all. Now that we've made the leap to 1.44MB/>6MB class machines, we've at least bought ourselves some room for future enhancements while still remaining on one floppy. Note that you can still build kernels which will run quite comfortably in a 4MB system, you just can't *install* with only 4MB in the machine. If you're trying to build a custom box with 4MB and a tiny configuration, for example, you might simply build its disk on a different machine set up specifically for that purpose. Jordan From owner-freebsd-hackers Sat Dec 14 16:21:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03613 for hackers-outgoing; Sat, 14 Dec 1996 16:21:38 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA03608 for ; Sat, 14 Dec 1996 16:21:35 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA01205; Sat, 14 Dec 1996 16:21:35 -0800 Date: Sat, 14 Dec 1996 16:21:35 -0800 (PST) From: "Brian N. Handy" To: freebsd-hackers@freebsd.org Subject: /compat location? Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Heya folks, Sooo...not too long ago I downloaded the latest greatest linux_lib distribution, and ... it's quite a bit bigger than it used to be. Now I knew this was going to happen, but that leads another question...My root partition (where /compat lives) isn't really big enough to sport linux_lib. Is there any compelling reason I have to have the /compat directory in my root partition, or can I make it a link to someplace with a mite more space? Thanks, Brian From owner-freebsd-hackers Sat Dec 14 16:27:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03840 for hackers-outgoing; Sat, 14 Dec 1996 16:27:53 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA03833 for ; Sat, 14 Dec 1996 16:27:50 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA22694; Sat, 14 Dec 1996 16:27:39 -0800 Date: Sat, 14 Dec 1996 16:27:39 -0800 (PST) From: "Brian N. Handy" To: John Polstra Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: CVSup 14.0 is now available In-Reply-To: <199612142255.OAA23778@austin.polstra.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Writes: >> I created the file ~sup/src-sys/refuse.cvs with the following lines: >> */pc98 >> */pc98/* >> src/sys/pc98 >> src/sys/pc98/* >> >> But none of them work. How do I tell my client to not get the pc98 >> files? John replies: >This ought to work. I tried it here with exactly the same setup, and it >worked. Are you sure you're using version 14.0 of cvsup? Type "cvsup -v" >to make sure. A couple of people have gotten bitten by my change of >installation directory to "/usr/local/bin". They still had the old >version in "/usr/local/sbin" and it was first in their PATH. I just tried it, same result as nate. I killed my pc98 stuff, did the above bit in the above file (actually just "*/pc98"), and ... I fetched the whole thing all over again. I verified I'm running cvsup-14.0. Here's the src-sys line from my supfile: src-sys release=cvs host=cvsup2.freebsd.org hostbase=/home base=/usr/2.2-CURRENT prefix=/usr/2.2-CURRENT delete old use-rel-suffix compress tag=RELENG_2_2 Awaiting orders, Brian From owner-freebsd-hackers Sat Dec 14 16:43:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA05779 for hackers-outgoing; Sat, 14 Dec 1996 16:43:19 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA05755 for ; Sat, 14 Dec 1996 16:43:16 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA26231; Sat, 14 Dec 1996 17:43:12 -0700 (MST) Date: Sat, 14 Dec 1996 17:43:12 -0700 (MST) Message-Id: <199612150043.RAA26231@rocky.mt.sri.com> From: Nate Williams To: "Brian N. Handy" Cc: John Polstra , Nate Williams , freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-Reply-To: References: <199612142255.OAA23778@austin.polstra.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> I created the file ~sup/src-sys/refuse.cvs with the following lines: > >> */pc98 > >> */pc98/* > >> src/sys/pc98 > >> src/sys/pc98/* > >> > >> But none of them work. How do I tell my client to not get the pc98 > >> files? > > John replies: > > >This ought to work. I tried it here with exactly the same setup, and it > >worked. Are you sure you're using version 14.0 of cvsup? Type "cvsup -v" > >to make sure. Duh, I wasn't running 14.0, but 13.5. I updated my binary (and centralized it) and it now works. > > A couple of people have gotten bitten by my change of installation > > directory to "/usr/local/bin". They still had the old version in > > "/usr/local/sbin" and it was first in their PATH. I had a version in $HOME/bin. > I just tried it, same result as nate. I killed my pc98 stuff, did the > above bit in the above file (actually just "*/pc98"), and ... I fetched > the whole thing all over again. Where did you add the refuse file, and what is it's name. Mine is ~sup/src-sys/refuse.cvs, and this seems to work fine. Nate > I verified I'm running cvsup-14.0. > > Here's the src-sys line from my supfile: > > src-sys release=cvs host=cvsup2.freebsd.org hostbase=/home > base=/usr/2.2-CURRENT prefix=/usr/2.2-CURRENT delete old use-rel-suffix > compress tag=RELENG_2_2 It may be possible that cvsup2 isn't yet running the new server. Nate From owner-freebsd-hackers Sat Dec 14 16:46:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA06581 for hackers-outgoing; Sat, 14 Dec 1996 16:46:02 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA06558 for ; Sat, 14 Dec 1996 16:45:58 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id QAA24162; Sat, 14 Dec 1996 16:45:52 -0800 (PST) Message-Id: <199612150045.QAA24162@austin.polstra.com> To: "Brian N. Handy" cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: CVSup 14.0 is now available In-reply-to: Your message of "Sat, 14 Dec 1996 16:27:39 PST." References: Date: Sat, 14 Dec 1996 16:45:52 -0800 From: John Polstra Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just tried it, same result as nate. I killed my pc98 stuff, did the > above bit in the above file (actually just "*/pc98"), and ... I fetched > the whole thing all over again. > > I verified I'm running cvsup-14.0. > > Here's the src-sys line from my supfile: > > src-sys release=cvs host=cvsup2.freebsd.org hostbase=/home > base=/usr/2.2-CURRENT prefix=/usr/2.2-CURRENT delete old use-rel-suffix > compress tag=RELENG_2_2 Hrmm. This is weird. Thanks for the detailed info. For this supfile line, your refuse file should be named: /usr/2.2-CURRENT/sup/src-sys/refuse.cvs:RELENG_2_2 Is it named correctly on your system? > Awaiting orders That's what I like to hear! :-) Please run it under ktrace. You can kill it as soon as it starts transferring files, to avoid using too much disk space for the ktrace.out file. Then run kdump into a pager. Search for "refuse" and you should find 3 closely-spaced NAMI lines where it's trying to open the 3 possible refuse files. Please let me know what file names appear in those lines. If it's not convenient for you to run ktrace (e.g., it's not configured into your kernel), then instead please rename your refuse file to this and tell me what happens: /usr/2.2-CURRENT/sup/src-sys/refuse Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Sat Dec 14 16:49:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA07250 for hackers-outgoing; Sat, 14 Dec 1996 16:49:07 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA07244 for ; Sat, 14 Dec 1996 16:49:03 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id QAA24206; Sat, 14 Dec 1996 16:48:58 -0800 (PST) Message-Id: <199612150048.QAA24206@austin.polstra.com> To: Nate Williams cc: "Brian N. Handy" , freebsd-hackers@freebsd.org Subject: Re: CVSup 14.0 is now available In-reply-to: Your message of "Sat, 14 Dec 1996 17:43:12 MST." <199612150043.RAA26231@rocky.mt.sri.com> References: <199612142255.OAA23778@austin.polstra.com> <199612150043.RAA26231@rocky.mt.sri.com> Date: Sat, 14 Dec 1996 16:48:57 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Duh, I wasn't running 14.0, but 13.5. I updated my binary (and > centralized it) and it now works. Yay! > > I just tried it, same result as nate. I killed my pc98 stuff, did the > > above bit in the above file (actually just "*/pc98"), and ... I fetched > > the whole thing all over again. > > Where did you add the refuse file, and what is it's name. Mine is > ~sup/src-sys/refuse.cvs, and this seems to work fine. Since Brian's using checkout mode, the name of the refuse file must have the tag in it too. So it should be "refuse.cvs:RELENG_2_2". That might be the problem. > It may be possible that cvsup2 isn't yet running the new server. It isn't yet, as a matter of fact. But this is strictly a client-side feature, so it still should work. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Sat Dec 14 16:49:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA07402 for hackers-outgoing; Sat, 14 Dec 1996 16:49:52 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA07386 for ; Sat, 14 Dec 1996 16:49:49 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sat, 14 Dec 1996 19:49:16 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA10401; Sat, 14 Dec 96 19:49:14 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA02194; Sat, 14 Dec 1996 19:48:17 -0500 Message-Id: Date: Sat, 14 Dec 1996 19:48:17 -0500 From: rhh@ct.picker.com (Randall Hopper) To: handy@sag.space.lockheed.com (Brian N. Handy) Cc: freebsd-hackers@freebsd.org Subject: Re: /compat location? References: X-Mailer: Mutt 0.54 Mime-Version: 1.0 In-Reply-To: ; from Brian N. Handy on Dec 14, 1996 16:21:35 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian N. Handy: |Sooo...not too long ago I downloaded the latest greatest linux_lib |distribution, and ... it's quite a bit bigger than it used to be. Now I |knew this was going to happen, but that leads another question...My root |partition (where /compat lives) isn't really big enough to sport |linux_lib. Is there any compelling reason I have to have the /compat |directory in my root partition, or can I make it a link to someplace with |a mite more space? No problem with that at all. I've had bunches of Linux bins running on my box and: stealth : ~ > ls -ld /compat lrwxr-xr-x 1 root wheel 13 Dec 14 09:41 /compat@ -> /share/compat Randall Hopper From owner-freebsd-hackers Sat Dec 14 18:25:23 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA13627 for hackers-outgoing; Sat, 14 Dec 1996 18:25:23 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA13621 for ; Sat, 14 Dec 1996 18:25:21 -0800 (PST) Received: from moth.us.dell.com (moth.us.dell.com [143.166.169.152]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id UAA11369; Sat, 14 Dec 1996 20:24:45 -0600 Message-Id: <3.0.1.32.19961214202436.0067ea7c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: Windows Eudora Light Version 3.0.1 beta 4 (32) Date: Sat, 14 Dec 1996 20:24:46 -0600 To: Eivind Eklund , hackers@freebsd.org From: Tony Overfield Subject: MAXMEM was: Re: 2.1.6 on Compaq Prosignia 500 (2.1.5 worked) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:32 PM 12/12/96 +0100, Eivind Eklund wrote: >>options "MAXMEM=65536" # 64 MB memory >due to Compaq (and Dell) using an extremely irritating aspect of the EISA >standard, and saying that they have 16MB in RTC-memory. I think you're irritated about the wrong thing. The RTC-memory cannot (in any standardized way) indicate more than ~65MB of system memory. This means that bypassing the BIOS and groping around in the RTC-memory is a dead-end solution. There are standardized BIOS calls to obtain the correct amount of memory, even when it exceeds 65 MB. I think the boot loader should make these BIOS calls and pass the correct information to the kernel. Tony - my personal opinion only From owner-freebsd-hackers Sat Dec 14 19:47:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA18326 for hackers-outgoing; Sat, 14 Dec 1996 19:47:22 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA18317 for ; Sat, 14 Dec 1996 19:47:18 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id EAA22560; Sun, 15 Dec 1996 04:45:18 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id EAA20536; Sun, 15 Dec 1996 04:46:48 +0100 (MET) Message-Id: <3.0.32.19961215044615.00925dd0@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 15 Dec 1996 04:46:16 +0100 To: Tony Overfield From: Eivind Eklund Subject: Re: MAXMEM was: Re: 2.1.6 on Compaq Prosignia 500 (2.1.5 worked) Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 08:24 PM 12/14/96 -0600, you wrote: >At 07:32 PM 12/12/96 +0100, Eivind Eklund wrote: >>>options "MAXMEM=65536" # 64 MB memory >>due to Compaq (and Dell) using an extremely irritating aspect of the EISA >>standard, and saying that they have 16MB in RTC-memory. > >I think you're irritated about the wrong thing. The RTC-memory >cannot (in any standardized way) indicate more than ~65MB of >system memory. This means that bypassing the BIOS and groping >around in the RTC-memory is a dead-end solution. > >There are standardized BIOS calls to obtain the correct amount of >memory, even when it exceeds 65 MB. I think the boot loader should >make these BIOS calls and pass the correct information to the kernel. The problem is that these BIOS calls are (to my knowledge; I'm no BIOS/PC hardware guru) only are guaranteed available on EISA computers, and only work from protected mode. To do this "properly" requires both a check to see if the computer has an EISA bus (which is in no way guaranteed - EISA seems to be dying), a switch to protected mode, and a fetch of the value. Few operating systems seems to do this "correctly". As examples, both Novell and SCO need this to be specified as an option. The reason I called it extremely irritating wasn't that I consider a BIOS call for getting amount of memory a bad idea - it was the fact that this is implemented as a protected mode call which only work if you've got EISA, instead of an extension that could be easily detected and called for any clone. I certainly agree that it would be nice for the boot code to detect this. I even looked at implementing it when the problem came up, but found it to be beyond what I wanted to learn about PC hardware. -- Eivind Eklund gopher://nic.follonett.no:79/0eivind Work: eivind@dimaga.com http://www.dimaga.com/ Home: perhaps@yes.no http://maybes.yes.no/perhaps/ All of the above is a product of either your or my imagination, and not official. From owner-freebsd-hackers Sat Dec 14 23:14:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA27843 for hackers-outgoing; Sat, 14 Dec 1996 23:14:56 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA27833; Sat, 14 Dec 1996 23:14:45 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id SAA05070; Sat, 14 Dec 1996 18:24:38 +1100 (EST) From: Julian Assange Message-Id: <199612140724.SAA05070@profane.iq.org> Subject: Re: vulnerability in new pw suite In-Reply-To: from "[______ ______, Andrey Chernov]" at "Dec 14, 96 04:51:08 pm" To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?=) Date: Sat, 14 Dec 1996 18:24:38 +1100 (EST) Cc: security@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Sat, 14 Dec 1996, Julian Assange wrote: > > > The FreeBSD account administration pw suite is able to produce > > "random" passwords for new accounts. Due to the simplicity of the > > password generation algorithm involved, the passwords are easily > > predictable amid a particular range of possibilities. This range > > may be very narrow, depending on what sort of information is > > available to the attacker. > > I agree on this subj. but I wonder about method you use, it > is unnecessary complex, reading /dev/urandom will be enough > without MD5 hashing. /dev/urandom not optional device, so > if it isn't exists or not give enough bytes it must be > detected as program failure and not covered by MD5 workaround. > -- > Andrey A. Chernov I thought it was optional, a check of this shows you are right. Still, it is possible that David is using pw(8) on more platforms than FreeBSD. As for the password length issue, known password length is only an issue with dictionary passwords, as length l-1 is always many times easier to check than length l, so any such checking algorithm always starts at the smallest length and works up. The worst case (security wise) senario only gains the attacker 1/n comparisons, such that n is the number of potential characters selectable for any given character position. i.e 1/n < 1/26 -Julian A. (proff@suburbia.net) From owner-freebsd-hackers Sat Dec 14 23:20:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA28280 for hackers-outgoing; Sat, 14 Dec 1996 23:20:33 -0800 (PST) Received: from rah.star-gate.com ([204.188.121.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA28274 for ; Sat, 14 Dec 1996 23:20:31 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.6/8.7.3) with ESMTP id XAA00409 for ; Sat, 14 Dec 1996 23:20:09 -0800 (PST) Message-Id: <199612150720.XAA00409@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: hackers@freebsd.org Subject: PCI 2.1 Byte Enables? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Dec 1996 23:20:08 -0800 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am writing a device driver for a PCI video capture board, Brooktree Bt848,as part of a dma risc instruction it requires : byte count and 4 bits for PCI byte enables. Can anyone guess what the PCI byte enables are for? Supposedley, the Bt848 is PCI 2.1 compliant. I have the databook for the Bt848 however it does not explain what the PCI byte enables field is for. I will probably contact again Brooktree next week if no one here knows what the field is for. Tnks, Amancio From owner-freebsd-hackers Sat Dec 14 23:53:34 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA01682 for hackers-outgoing; Sat, 14 Dec 1996 23:53:34 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA01673 for ; Sat, 14 Dec 1996 23:53:31 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA05573; Sat, 14 Dec 1996 23:53:28 -0800 Date: Sat, 14 Dec 1996 23:53:28 -0800 (PST) From: "Brian N. Handy" To: John Polstra Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: CVSup 14.0 is now available In-Reply-To: <199612150045.QAA24162@austin.polstra.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hey! >> src-sys release=cvs host=cvsup2.freebsd.org hostbase=/home >> base=/usr/2.2-CURRENT prefix=/usr/2.2-CURRENT delete old use-rel-suffix >> compress tag=RELENG_2_2 > >Hrmm. This is weird. Thanks for the detailed info. > >For this supfile line, your refuse file should be named: > > /usr/2.2-CURRENT/sup/src-sys/refuse.cvs:RELENG_2_2 > >Is it named correctly on your system? Oho! This was the problem, I didn't have the :RELENG_2_2 tacked onto the end of my file. (Which was sort of evident after the fact, I just followed Nate's example a bit too closely.) So...cool! Works great, lasts a long time. Thanks! Brian From owner-freebsd-hackers Sat Dec 14 23:58:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA01966 for hackers-outgoing; Sat, 14 Dec 1996 23:58:17 -0800 (PST) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA01961 for ; Sat, 14 Dec 1996 23:58:14 -0800 (PST) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id BAA11636; Sun, 15 Dec 1996 01:57:11 -0600 Message-Id: <3.0.1.32.19961215015705.0067a82c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: Windows Eudora Light Version 3.0.1 beta 4 (32) Date: Sun, 15 Dec 1996 01:57:11 -0500 To: Eivind Eklund From: Tony Overfield Subject: Re: MAXMEM was: Re: 2.1.6 on Compaq Prosignia 500 (2.1.5 worked) Cc: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 04:46 AM 12/15/96 +0100, Eivind Eklund wrote: >The reason I called it extremely irritating wasn't that I consider a BIOS >call for getting amount of memory a bad idea - it was the fact that this is >implemented as a protected mode call which only work if you've got EISA, >instead of an extension that could be easily detected and called for any >clone. > >Eivind Eklund gopher://nic.follonett.no:79/0eivind >Work: eivind@dimaga.com http://www.dimaga.com/ >Home: perhaps@yes.no http://maybes.yes.no/perhaps/ >All of the above is a product of either your or my imagination, and not >official. It's true that there are protected-mode EISA-specific calls to obtain the memory information. They can even be called from real-mode. However, there are, in fact, real-mode calls that are present on a great many systems, including most of the "any clone" type systems, which can provide the desired information. A few various queries using AltaVista turned up this link: http://www.uruk.org/grub/mem64mb.html which documents the calls. Perhaps not coincidentally, the link at: http://www.uruk.org/grub/ describes a fancy boot loader. - Tony