From owner-freebsd-hackers Sun Jul 26 00:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20199 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 00:08:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20194 for ; Sun, 26 Jul 1998 00:08:02 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id CAA07108 for ; Sun, 26 Jul 1998 02:07:04 -0500 (CDT) Message-Id: <199807260707.CAA07108@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: swapon, ccd: device not configure, eh what? To: hackers@FreeBSD.ORG Date: Sun, 26 Jul 1998 02:07:03 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi, I'm runing a -CURRENT w/CAM system, and trying to use a ccd as swap, i.e. ccdconfig -c ccd1 32 CCDF_SWAP /dev/da0s1b /dev/da1s1b swapon /dev/ccd1c but no joy. swapon spouts ``device not configured''. ccdconfig -g spits back out my ccd config as expected, and ``newfs ccd1c && mount /dev/ccd1c /mnt'' works just fine. Anyone have pointers? Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbrVljeRhT8JRySpAQHfgAQAhQluPQYvNnFJ/YcPvkpLDtu1pcBlcsmr FemWLPCvKvlfoiK26rKdJ4Y7swr9Rw2Fjudl8b2vN8ljvRNANQ5KCGua+7csw5rY Q5aw36ftlgoFl6MiJsY+2R1OcWjH9F5h/nmUJ3dN24YTly4TQhCQeAK4hpjjVwH2 /RbfDgsfpqM= =KfPd -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 01:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23604 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 01:10:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles129.castles.com [208.214.165.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23599 for ; Sun, 26 Jul 1998 01:10:01 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id BAA08760; Sun, 26 Jul 1998 01:09:09 -0700 (PDT) Message-Id: <199807260809.BAA08760@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: hackers@FreeBSD.ORG Subject: Re: swapon, ccd: device not configure, eh what? In-reply-to: Your message of "Sun, 26 Jul 1998 02:07:03 CDT." <199807260707.CAA07108@bone.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 01:09:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I'm runing a -CURRENT w/CAM system, and trying to use a > ccd as swap, i.e. > > ccdconfig -c ccd1 32 CCDF_SWAP /dev/da0s1b /dev/da1s1b > swapon /dev/ccd1c > > but no joy. swapon spouts ``device not configured''. > > ccdconfig -g spits back out my ccd config as expected, > and ``newfs ccd1c && mount /dev/ccd1c /mnt'' works just > fine. > > Anyone have pointers? Never attempt to swap on the "whole disk". And why on earth do you want to swap on a ccd? Just swap onto its components individually, and take advantage of the swap interleave. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 02:00:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27480 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 02:00:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iq.org (proff@polysynaptic.iq.org [203.4.184.222]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA27421 for ; Sun, 26 Jul 1998 01:59:56 -0700 (PDT) (envelope-from proff@iq.org) Received: (qmail 17002 invoked by uid 110); 26 Jul 1998 08:59:26 -0000 Date: 26 Jul 1998 08:59:26 -0000 Message-ID: <19980726085926.17001.qmail@iq.org> From: Julian Assange To: freebsd-hackers@FreeBSD.ORG Subject: realplayer5.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone had success in fudging linux realaudio5.0 to work under emmulation? (RealAudio stopped supporting FreeBSD as a platform after 3.0). Cheers, Julian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 02:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29573 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 02:29:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29560 for ; Sun, 26 Jul 1998 02:29:48 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA17189; Sun, 26 Jul 1998 02:28:36 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807260928.CAA17189@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Assange cc: freebsd-hackers@FreeBSD.ORG Subject: Re: realplayer5.0 In-reply-to: Your message of "26 Jul 1998 08:59:26 -0000." <19980726085926.17001.qmail@iq.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 02:28:36 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just bug them to release a FreeBSD native player . You see real audio's server where originally developed on FreeBSD and their Server Project Leader is an old FreeBSD multimedia hacker. Amancio > > Has anyone had success in fudging linux realaudio5.0 to work under > emmulation? (RealAudio stopped supporting FreeBSD as a platform after > 3.0). > > Cheers, > Julian. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 02:38:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00360 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 02:38:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00341; Sun, 26 Jul 1998 02:38:56 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA17306; Sun, 26 Jul 1998 11:38:26 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 11:38:25 +0200 (MET DST) Mime-Version: 1.0 To: Garrett Wollman Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysexits References: <199807260217.WAA05555@khavrinen.lcs.mit.edu> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 11:38:25 +0200 In-Reply-To: Garrett Wollman's message of "Sat, 25 Jul 1998 22:17:12 -0400 (EDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA00342 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman writes: > < > at least in some applications - a failed malloc(), calloc() or > > realloc(). I therefore suggest adding the constant EX_NOMEM, with the > > value 79, to /usr/include/sysexits.h, and bumping EX__MAX to 79 (as > Good idea. I would also add EX_NOGROUP (parallel to EX_NOUSER). > Don't forget to update the table of names in sendmail. Hmm... I didn't think of Sendmail. What will happen the next time we upgrade Sendmail (to 8.9.1)? Will somebody remember to merge that patch into the new version? Or will Sendmail suddenly no longer understand EX_NOMEM and EX_NOGROUP? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 03:00:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02329 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 03:00:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02301; Sun, 26 Jul 1998 03:00:43 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA18208; Sun, 26 Jul 1998 12:00:16 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 12:00:15 +0200 (MET DST) Mime-Version: 1.0 To: wayne@msen.com Cc: hackers@FreeBSD.ORG, freebsd-install@FreeBSD.ORG Subject: Re: Install problems with FreeBSD 2.2.7-RELEASE References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 12:00:14 +0200 In-Reply-To: wayne@msen.com's message of "Sat, 25 Jul 98 05:18:40 -0400" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA02303 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wayne@msen.com writes: > Trying to from-scratch via-ftp install 2.2.7 and seeing an odd > problem. Most of the way through the process an error occurs. The > screen says something like "if this is repeatable send mail". While > it's repeatable (takes about 40 minutes to get there so we only did it > 3 times), instead of pausing at this point, the machine reboots so fast > after printing this that the message is not easily read. You could try to use a serial console, or connect the failing box to another computer using a null-modem cable and use tip(1) as console. BTW, I can't find any code in sysinstall(8) or any of its friends that actually recommends sending mail about a bug (except for relnotes.hlp) > Since it is fairly late in the installation process, enough has been > installed to bring the machine up but SOMEthing is not right here. Bringing the machine up the rest of the way manually should be fairly simple if you are relatively experienced with Unix. The only gotcha once you've installed whatever distributions you want is copying the right timezone file to /etc/localtime (this should be documented somewhere...) Just locate the correct file in /usr/share/zoneinfo (probably /usr/share/zoneinfo/America/Detroit if 'whois msen.com'is to be trusted). If you forget to do this, the kernel (and everything started before you get a chance to set the TZ environment variable, such as, most annoyingly, cron) will run GMT. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 05:37:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20503 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 05:37:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20488 for ; Sun, 26 Jul 1998 05:37:34 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA30953 (5.67b/IDA-1.5); Sun, 26 Jul 1998 13:31:10 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id NAA23204; Sun, 26 Jul 1998 13:14:14 +0200 (CEST) From: Wilko Bulte Message-Id: <199807261114.NAA23204@yedi.iaf.nl> Subject: Re: Sendmail 8.9.1. antispam on 2.1.0R In-Reply-To: <19980726023140.A7527@keltia.freenix.fr> from Ollivier Robert at "Jul 26, 98 02:31:40 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 26 Jul 1998 13:14:14 +0200 (CEST) Cc: FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Ollivier Robert wrote... > According to Wilko Bulte: > > Strangely enough it does not seem to bother to check MAIL FROM: for a > > valid domain. According to www.sendmail.org it should. It does check > > for illegal relaying, this according to the docs. > > Did you kept the same sendmail.cf or did you rebuild a new one ? I rebuild it using the .mc I already had. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 05:37:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20551 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 05:37:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20540 for ; Sun, 26 Jul 1998 05:37:53 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA30977 (5.67b/IDA-1.5); Sun, 26 Jul 1998 13:31:14 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id NAA23301; Sun, 26 Jul 1998 13:20:02 +0200 (CEST) From: Wilko Bulte Message-Id: <199807261120.NAA23301@yedi.iaf.nl> Subject: Re: Sendmail 8.9.1. antispam on 2.1.0R In-Reply-To: from Mike at "Jul 25, 98 03:19:23 pm" To: mike@seidata.com (Mike) Date: Sun, 26 Jul 1998 13:20:02 +0200 (CEST) Cc: FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mike wrote... > On Sat, 25 Jul 1998, Wilko Bulte wrote: > > > I just installed sendmail 8.9.1 on a FreeBSD 2.1.0 box (remotely located > > so still not upgraded to something more recent). > > Curious: Did you encounter any error messages pertaining to your > sendmail.cf file when upgrading to 8.9.1? I was playing around with No, I rebuild the .cf from my existing .mc, of course using the 8.9.1 .cf build environment. > moving from 8.8.8 to 8.9.1 and whenever I'd restart sendmail or run > newaliases, I'd get complaints about having a 'Version 8 sendmail.cf'. > > Was this, perhaps, becuase I had a lot of anti-spam stuff in my existing > .cf file and much of this is 'built in' now? If you did not receive any > such errors, could I get a reference copy of your sendmail.cf file? Well, you would not be happy with it because it uses mailertables to dump things into UUCP queues etc. Very non typical config I guess. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 05:55:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21745 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 05:55:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA21740 for ; Sun, 26 Jul 1998 05:55:29 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA03080; Sun, 26 Jul 1998 13:01:39 +0200 From: Luigi Rizzo Message-Id: <199807261101.NAA03080@labinfo.iet.unipi.it> Subject: Re: realplayer5.0 To: proff@iq.org (Julian Assange) Date: Sun, 26 Jul 1998 13:01:39 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980726085926.17001.qmail@iq.org> from "Julian Assange" at Jul 26, 98 08:59:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone had success in fudging linux realaudio5.0 to work under > emmulation? (RealAudio stopped supporting FreeBSD as a platform after > 3.0). long ago i mentioned a patch to one pf the ioctl in the linux emulation to fool the player and make it believe it was a little bit ahead in the playback -- this was probably with a last year's version of the rvplayer5.0 (beta3 perhaps ?). Have things changed, and can someone summarize 1) the problem 2) an URL for the player that seems not to work ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 07:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26899 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 07:02:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26880 for ; Sun, 26 Jul 1998 07:02:17 -0700 (PDT) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id QAA02600; Sun, 26 Jul 1998 16:01:47 +0200 (CEST) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by campa.panke.de (8.8.8/8.8.8) id PAA02328; Sun, 26 Jul 1998 15:42:30 +0200 (MET DST) (envelope-from w) Message-ID: <19980726154226.A2270@panke.de> Date: Sun, 26 Jul 1998 15:42:26 +0200 From: Wolfram Schneider To: Markus Stumpf , freebsd-hackers@FreeBSD.ORG Subject: Re: swap/memory management problem References: <19980724035956.H11327@space.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980724035956.H11327@space.net>; from Markus Stumpf on Fri, Jul 24, 1998 at 03:59:56AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-24 03:59:56 +0200, Markus Stumpf wrote: > Watched this a loooong ;-) time and never seen pages swapped out but only in. > > The nasty thing with this is that squid is getting slower and slower and > even so the above numbers do no change its getting slower every day it > runs until I restart it. > > I assume this all is due to proactive swapping? > > Is there any chance to get rid of this behaviour? Would it help to reduce > the swap space to e.g. 30 MB? (the 27 GB disk is filled, so I don't think > squid will grow any further). Anything else I'm missing? There are several (undocumented) syctl variables which control swapping and paging. You can also disable swapping at all. $ sysctl -a | grep ^vm vm.loadavg: { 0.91 0.94 1.00 } vm.v_free_min: 161 vm.v_free_target: 607 vm.v_free_reserved: 124 vm.v_inactive_target: 1398 vm.v_cache_min: 810 vm.v_cache_max: 3242 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swapping_enabled: 1 Wolfram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 09:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06661 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 09:18:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06645 for ; Sun, 26 Jul 1998 09:18:15 -0700 (PDT) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id RAA00663; Sun, 26 Jul 1998 17:15:04 +0100 (BST) (envelope-from rjs) Date: Sun, 26 Jul 1998 17:15:04 +0100 (BST) From: Robert Swindells Message-Id: <199807261615.RAA00663@fdy2.demon.co.uk> To: mike@smith.net.au CC: hackers@FreeBSD.ORG In-reply-to: <199807252236.PAA06616@antipodes.cdrom.com> (message from Mike Smith on Sat, 25 Jul 1998 15:36:55 -0700) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Howdy; a straightforward question: FreeBSD Test Labs is looking for a >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST >chips. (Am79c97x etc.) http://www.amd.com/products/npd/overview/19433f.pdf I have got a few patches to the driver that allow it to recognize the later chips. I'll send it in when I have tidied it up a bit. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 09:19:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06744 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 09:19:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06739 for ; Sun, 26 Jul 1998 09:19:29 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id LAA08436; Sun, 26 Jul 1998 11:17:45 -0500 (CDT) Message-Id: <199807261617.LAA08436@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199807260809.BAA08760@antipodes.cdrom.com> References: <199807260809.BAA08760@antipodes.cdrom.com> Subject: Re: swapon, ccd: device not configure, eh what? To: Mike Smith cc: Jacques Vidrine , hackers@FreeBSD.ORG Date: Sun, 26 Jul 1998 11:17:45 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 26 July 1998 at 1:09, Mike Smith wrote: > Never attempt to swap on the "whole disk". Can I disklabel a ccd? I didn't think that I could, for some reason. > And why on earth do you want to swap on a ccd? Just swap onto its > components individually, and take advantage of the swap interleave. Oh, just for the hell of it. Because there is a CCDF_SWAP flag. To see if it worked as documented. etc. If it doesn't work, it needs to be fixed or ``undocumented''. Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbtWqTeRhT8JRySpAQF36QQAjd9yPPPYOZ+lGSc+1n6E2y3+T61Ek3nz Q8n8E9NNQ6wR8ApEuQgLJiDmqlEZCmRbV54ML6IgzN7zmf/maeyWZDawD3Oc0Yo4 qxAzKJGI9yhJ+WMk5QfI+tb/SmphMQdeDCRe4eGH/q9uw0VnqQSUIVTgP4CpdGeM wJrF6nWnTyQ= =kqEc -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 09:35:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07943 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 09:35:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.kacst.edu.sa (ns1.kacst.edu.sa [198.77.88.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07926 for ; Sun, 26 Jul 1998 09:35:48 -0700 (PDT) (envelope-from s961807@kfupm.edu.sa) Received: from ns1.kfupm.edu.sa ([198.77.102.26]) by relay.kacst.edu.sa (8.7.5/8.7.3) with ESMTP id TAA12208 for ; Sun, 26 Jul 1998 19:26:16 -0300 (GMT) Received: from dpc111.dpc.kfupm.edu.sa (dpc111.dpc.kfupm.edu.sa [196.15.32.11]) by ns1.kfupm.edu.sa (8.7.5/8.7.3) with ESMTP id TAA52340 for ; Sun, 26 Jul 1998 19:20:33 +0300 Received: from dpc107.dpc.kfupm.edu.sa (dpc107.dpc.kfupm.edu.sa [196.15.32.8]) by dpc111.dpc.kfupm.edu.sa (8.7.5/8.7.3) with ESMTP id TAA21748 for ; Sun, 26 Jul 1998 19:33:09 +0400 Received: from localhost (s961807@localhost) by dpc107.dpc.kfupm.edu.sa (8.7.5/8.7.3) with SMTP id TAA24267 for ; Sun, 26 Jul 1998 19:31:09 +0300 Date: Sun, 26 Jul 1998 19:31:09 +0300 (SAUST) From: "MidNight StR@nGeR~" X-Sender: s961807@dpc107.dpc.kfupm.edu.sa To: freebsd-hackers@FreeBSD.ORG Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10924 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:05:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10919 for ; Sun, 26 Jul 1998 10:05:38 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA10816; Sun, 26 Jul 1998 10:04:44 -0700 (PDT) Message-Id: <199807261704.KAA10816@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: hackers@FreeBSD.ORG Subject: Re: swapon, ccd: device not configure, eh what? In-reply-to: Your message of "Sun, 26 Jul 1998 11:17:45 CDT." <199807261617.LAA08436@bone.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 10:04:44 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----BEGIN PGP SIGNED MESSAGE----- > > On 26 July 1998 at 1:09, Mike Smith wrote: > > Never attempt to swap on the "whole disk". > > Can I disklabel a ccd? I didn't think that I could, for some > reason. Yup. This stuff gets better when SLICE comes into the picture, and you can disklable it, put an MBR inside each of the partitions, then disklabel the slices inside those, etc. 8) > > And why on earth do you want to swap on a ccd? Just swap onto its > > components individually, and take advantage of the swap interleave. > > Oh, just for the hell of it. Because there is a CCDF_SWAP flag. > To see if it worked as documented. etc. > > If it doesn't work, it needs to be fixed or ``undocumented''. It's not really documented (as far as I can see). The CCDF_SWAP flag is somewhat ambiguous though, yes. The real issue is that dev/ccd/ccd.c:ccdsize() returns -1 for partitions that do not have type == FS_SWAP, so you can't swap on something that's not marked as a swap partition, and that includes the 'c' partition in the case where there is no disklabel on the volume. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:12:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11807 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:12:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11802 for ; Sun, 26 Jul 1998 10:12:12 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA10890; Sun, 26 Jul 1998 10:11:15 -0700 (PDT) Message-Id: <199807261711.KAA10890@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Swindells cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Sun, 26 Jul 1998 17:15:04 BST." <199807261615.RAA00663@fdy2.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 10:11:14 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > >chips. (Am79c97x etc.) > > http://www.amd.com/products/npd/overview/19433f.pdf So nobody manufactures an adapter featuring the PC-Net FAST device? That's kinda depressing. 8( > I have got a few patches to the driver that allow it to recognize the > later chips. I'll send it in when I have tidied it up a bit. Recognising isn't so much the battle as working with them. But yes, please do. (File PR, naturally). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:14:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12161 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:14:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12150 for ; Sun, 26 Jul 1998 10:14:09 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 16233 invoked by uid 3759); 26 Jul 1998 17:14:53 -0000 Date: Sun, 26 Jul 1998 13:14:53 -0400 (EDT) From: "B. Richardson" To: Jacques Vidrine cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: swapon, ccd: device not configure, eh what? In-Reply-To: <199807261617.LAA08436@bone.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, Jacques Vidrine wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > On 26 July 1998 at 1:09, Mike Smith wrote: > > Never attempt to swap on the "whole disk". So if you had a system doing heavy I/O that kept *all* of its disk that had filesystems busy it would be a bad idea to dedicate a seperate disk to swap? > > Can I disklabel a ccd? I didn't think that I could, for some > reason. Well if you think about it, a ccd is a logical organization of slices of disks that are already disklabeled. > > > And why on earth do you want to swap on a ccd? Just swap onto its > > components individually, and take advantage of the swap interleave. > > Oh, just for the hell of it. Because there is a CCDF_SWAP flag. > To see if it worked as documented. etc. > If it doesn't work, it needs to be fixed or ``undocumented''. > > Jacques Vidrine > > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBNbtWqTeRhT8JRySpAQF36QQAjd9yPPPYOZ+lGSc+1n6E2y3+T61Ek3nz > Q8n8E9NNQ6wR8ApEuQgLJiDmqlEZCmRbV54ML6IgzN7zmf/maeyWZDawD3Oc0Yo4 > qxAzKJGI9yhJ+WMk5QfI+tb/SmphMQdeDCRe4eGH/q9uw0VnqQSUIVTgP4CpdGeM > wJrF6nWnTyQ= > =kqEc > -----END PGP SIGNATURE----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12620 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:17:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12615 for ; Sun, 26 Jul 1998 10:17:43 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id MAA08750; Sun, 26 Jul 1998 12:16:09 -0500 (CDT) Message-Id: <199807261716.MAA08750@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199807261704.KAA10816@antipodes.cdrom.com> References: <199807261704.KAA10816@antipodes.cdrom.com> Subject: Re: swapon, ccd: device not configure, eh what? To: Mike Smith cc: Jacques Vidrine , hackers@FreeBSD.ORG Date: Sun, 26 Jul 1998 12:16:09 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 26 July 1998 at 10:04, Mike Smith wrote: > The real issue is that dev/ccd/ccd.c:ccdsize() returns -1 for > partitions that do not have type == FS_SWAP, so you can't swap on > something that's not marked as a swap partition, and that includes the > 'c' partition in the case where there is no disklabel on the volume. I'll have to look closer, I suppose. I disklabel'd the ccd and made a b partition marked as swap, but I still get ``device not configured: ccd1b'' from swapon /dev/ccd1b. - -- Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbtkWTeRhT8JRySpAQFedwP+JS8MzWbDXzqccyy96fZ4IqCe6X1zw418 Zq0dHM4m4huA9KbUb6KjBCGTFdkGpkv49nvbL1xOiE73PdBocDHJ2EBpSA5F36Z9 uBtA4QjR8RotVmSljhHzAKGd7lCnwoqFlws7j7+dyY6h4g1E29VTn66wEI+QONSB WzVtjjBITXg= =ZD16 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:20:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13058 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:20:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bone.nectar.com (bone.nectar.com [204.27.67.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13051 for ; Sun, 26 Jul 1998 10:20:40 -0700 (PDT) (envelope-from nectar@bone.nectar.com) Received: from bone.nectar.com (localhost.nectar.com [127.0.0.1]) by bone.nectar.com (8.9.0/8.9.0) with ESMTP id MAA08888; Sun, 26 Jul 1998 12:18:53 -0500 (CDT) Message-Id: <199807261718.MAA08888@bone.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: References: Subject: Re: swapon, ccd: device not configure, eh what? To: "B. Richardson" cc: Mike Smith , hackers@FreeBSD.ORG Date: Sun, 26 Jul 1998 12:18:53 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 26 July 1998 at 13:14, "B. Richardson" wrote: > > On 26 July 1998 at 1:09, Mike Smith wrote: > > > Never attempt to swap on the "whole disk". > So if you had a system doing heavy I/O that kept *all* of its > disk that had filesystems busy it would be a bad idea to > dedicate a seperate disk to swap? I think he was referring to the ``c'' partition, which represents the ``whole disk''. - -- Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbtk/TeRhT8JRySpAQFOowP+I545G3fcWPrs3UO4jVyUFMVYMZkzAV00 3Btm+uy8ueSN1HC2JfybebDMMtxw5603oOgEGe+3x+62QwfAcMzN1laZTSVchb2b jnnff0CA6DooZSY0D4Cw1YNKmB3Ch8E93YCJR6dzskiVnTTmH3tGraUeIz6/6+oK 49U7B4pJ/1Q= =tThP -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13500 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:24:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13486 for ; Sun, 26 Jul 1998 10:24:51 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA10982; Sun, 26 Jul 1998 10:23:36 -0700 (PDT) Message-Id: <199807261723.KAA10982@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "B. Richardson" cc: Jacques Vidrine , Mike Smith , hackers@FreeBSD.ORG Subject: Re: swapon, ccd: device not configure, eh what? In-reply-to: Your message of "Sun, 26 Jul 1998 13:14:53 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 10:23:36 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On 26 July 1998 at 1:09, Mike Smith wrote: > > > Never attempt to swap on the "whole disk". > > So if you had a system doing heavy I/O that kept *all* of its > disk that had filesystems busy it would be a bad idea to > dedicate a seperate disk to swap? No. Note that "whole disk" was quoted, implying a different meaning, in this case the "whole disk partition". Doing anything with the 'c' partition is generally a Bad Idea. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 10:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13803 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 10:27:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13775 for ; Sun, 26 Jul 1998 10:26:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA11006; Sun, 26 Jul 1998 10:25:54 -0700 (PDT) Message-Id: <199807261725.KAA11006@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: swapon, ccd: device not configure, eh what? In-reply-to: Your message of "Sun, 26 Jul 1998 12:16:09 CDT." <199807261716.MAA08750@bone.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 10:25:53 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----BEGIN PGP SIGNED MESSAGE----- > > On 26 July 1998 at 10:04, Mike Smith wrote: > > The real issue is that dev/ccd/ccd.c:ccdsize() returns -1 for > > partitions that do not have type == FS_SWAP, so you can't swap on > > something that's not marked as a swap partition, and that includes the > > 'c' partition in the case where there is no disklabel on the volume. > > I'll have to look closer, I suppose. I disklabel'd the ccd and > made a b partition marked as swap, but I still get ``device not > configured: ccd1b'' from swapon /dev/ccd1b. Try instrumenting vm/vm_swap.c:swaponvp() and dev/ccd/ccd.c:ccdsize() just to see whether it's being refused there or elsewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 11:16:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18653 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 11:16:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18648 for ; Sun, 26 Jul 1998 11:16:05 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id LAA14570; Sun, 26 Jul 1998 11:15:21 -0700 (PDT) Message-ID: <19980726111521.B21764@Alameda.net> Date: Sun, 26 Jul 1998 11:15:21 -0700 From: Ulf Zimmermann To: Mike Smith , Robert Swindells Cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? Reply-To: ulf@Alameda.net References: <199807261615.RAA00663@fdy2.demon.co.uk> <199807261711.KAA10890@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807261711.KAA10890@antipodes.cdrom.com>; from Mike Smith on Sun, Jul 26, 1998 at 10:11:14AM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 10:11:14AM -0700, Mike Smith wrote: > > > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > > >chips. (Am79c97x etc.) > > > > http://www.amd.com/products/npd/overview/19433f.pdf > > So nobody manufactures an adapter featuring the PC-Net FAST device? > That's kinda depressing. 8( Hitachi used the AMD chip on their older notebooks. The newer Visionbook Pro has a 10/100 onboard, which I wouldn't be surprised to be an AMD again. > > > I have got a few patches to the driver that allow it to recognize the > > later chips. I'll send it in when I have tidied it up a bit. > > Recognising isn't so much the battle as working with them. But yes, > please do. (File PR, naturally). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 11:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19576 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 11:23:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19563 for ; Sun, 26 Jul 1998 11:23:52 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA11238; Sun, 26 Jul 1998 11:22:57 -0700 (PDT) Message-Id: <199807261822.LAA11238@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: ulf@Alameda.net cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Sun, 26 Jul 1998 11:15:21 PDT." <19980726111521.B21764@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 11:22:57 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jul 26, 1998 at 10:11:14AM -0700, Mike Smith wrote: > > > > > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > > > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > > > >chips. (Am79c97x etc.) > > > > > > http://www.amd.com/products/npd/overview/19433f.pdf > > > > So nobody manufactures an adapter featuring the PC-Net FAST device? > > That's kinda depressing. 8( > > Hitachi used the AMD chip on their older notebooks. The newer Visionbook Pro > has a 10/100 onboard, which I wouldn't be surprised to be an AMD again. Yes, it is. However there is a slight price differential between a PCI card and a new notebook, and the goal here is to use donors' funds as effectively as possible. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 12:01:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23980 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 12:01:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23974 for ; Sun, 26 Jul 1998 12:01:27 -0700 (PDT) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id TAA00871; Sun, 26 Jul 1998 19:58:10 +0100 (BST) (envelope-from rjs) Date: Sun, 26 Jul 1998 19:58:10 +0100 (BST) From: Robert Swindells Message-Id: <199807261858.TAA00871@fdy2.demon.co.uk> To: mike@smith.net.au CC: hackers@FreeBSD.ORG In-reply-to: <199807261711.KAA10890@antipodes.cdrom.com> (message from Mike Smith on Sun, 26 Jul 1998 10:11:14 -0700) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > > >chips. (Am79c97x etc.) > > >> http://www.amd.com/products/npd/overview/19433f.pdf >So nobody manufactures an adapter featuring the PC-Net FAST device? >That's kinda depressing. 8( I didn't check all the web sites to see if anyone was selling any newer cards than on that list. You are the one that wants to buy one :-) Try Allied Telesyn. They have a 100Mb/s card, but don't indicate whether it is an AMD board. Boca Research are another to try. We are using the PCnet-FAST at work, but it is built into a motherboard. > > I have got a few patches to the driver that allow it to recognize the > > later chips. I'll send it in when I have tidied it up a bit. >Recognising isn't so much the battle as working with them. But yes, >please do. (File PR, naturally). The driver in stable works fine with both the PCnet PCI-II and the PCnet-FAST reference boards from AMD. I have added support for the extra registers on these boards, but I did it more to allow me to debug some flakey hardware than to use the extra functionality. If I get time, I will add mediaopt support. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 13:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01861 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 13:18:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01856 for ; Sun, 26 Jul 1998 13:18:20 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id NAA20329; Sun, 26 Jul 1998 13:17:46 -0700 (PDT) Message-ID: <19980726131746.D21764@Alameda.net> Date: Sun, 26 Jul 1998 13:17:46 -0700 From: Ulf Zimmermann To: Robert Swindells , mike@smith.net.au Cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? Reply-To: ulf@Alameda.net References: <199807261711.KAA10890@antipodes.cdrom.com> <199807261858.TAA00871@fdy2.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807261858.TAA00871@fdy2.demon.co.uk>; from Robert Swindells on Sun, Jul 26, 1998 at 07:58:10PM +0100 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 07:58:10PM +0100, Robert Swindells wrote: > > > > > > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > > > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > > > >chips. (Am79c97x etc.) > > > > >> http://www.amd.com/products/npd/overview/19433f.pdf > > >So nobody manufactures an adapter featuring the PC-Net FAST device? > >That's kinda depressing. 8( > > I didn't check all the web sites to see if anyone was selling any newer > cards than on that list. You are the one that wants to buy one :-) > > Try Allied Telesyn. They have a 100Mb/s card, but don't indicate > whether it is an AMD board. Boca Research are another to try. Looking at the picture on their website, it seems to be an AMD. I tried to download the drivers to look for more informations, but they reject all anonymous logins. :-( Boca Research is a DEC 21x4x card as far I can see that from the drivers. I went through some of the other manufactors listed for the 10mbit cards, but everone seems to use something else, mostly DEC. > > We are using the PCnet-FAST at work, but it is built into a motherboard. > > > > I have got a few patches to the driver that allow it to recognize the > > > later chips. I'll send it in when I have tidied it up a bit. > > >Recognising isn't so much the battle as working with them. But yes, > >please do. (File PR, naturally). > > The driver in stable works fine with both the PCnet PCI-II and the > PCnet-FAST reference boards from AMD. > > I have added support for the extra registers on these boards, but I > did it more to allow me to debug some flakey hardware than to use the > extra functionality. If I get time, I will add mediaopt support. > > Robert Swindells > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 13:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02845 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 13:28:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2 (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA02831 for ; Sun, 26 Jul 1998 13:28:13 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2 (SMI-8.6/8.6.9) with SMTP id QAA24353 for ; Sun, 26 Jul 1998 16:27:43 -0400 Date: Sun, 26 Jul 1998 16:27:43 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: APTDpde question (pmap) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In pmap.c module, we set PTDPTDI entry of the page directory page to point to itself. So PTDpde and PTmap works well. However, I do not find a similar setting of APTDTDI (=1023) in pmap.c. My question is how APTDpde and the alternate address space it's supposed to relate to (APTmap) are used. (has something to do with pmap copy?) Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 13:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05383 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 13:54:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05378; Sun, 26 Jul 1998 13:54:28 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA15723; Sun, 26 Jul 1998 13:53:53 -0700 (MST) From: Terry Lambert Message-Id: <199807262053.NAA15723@usr01.primenet.com> Subject: Re: sysexits To: bde@zeta.org.au (Bruce Evans) Date: Sun, 26 Jul 1998 20:53:52 +0000 (GMT) Cc: current@FreeBSD.ORG, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG In-Reply-To: <199807260206.MAA29472@godzilla.zeta.org.au> from "Bruce Evans" at Jul 26, 98 12:06:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's wrong with errx(1, "[mcre]alloc failed")? The inherent unportability of such code to non-4.4-BSD derived systems, perhaps? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 13:56:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05643 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 13:56:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05595; Sun, 26 Jul 1998 13:55:59 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA15776; Sun, 26 Jul 1998 13:55:28 -0700 (MST) From: Terry Lambert Message-Id: <199807262055.NAA15776@usr01.primenet.com> Subject: Re: sysexits To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Sun, 26 Jul 1998 20:55:27 +0000 (GMT) Cc: wollman@khavrinen.lcs.mit.edu, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=" at Jul 26, 98 11:38:25 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm... I didn't think of Sendmail. What will happen the next time we > upgrade Sendmail (to 8.9.1)? Will somebody remember to merge that > patch into the new version? Or will Sendmail suddenly no longer > understand EX_NOMEM and EX_NOGROUP? It will "just work"... You *did* import sendmail on a vendor branch, right? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 14:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06397 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 14:01:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06384 for ; Sun, 26 Jul 1998 14:01:05 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA15891; Sun, 26 Jul 1998 14:00:20 -0700 (MST) From: Terry Lambert Message-Id: <199807262100.OAA15891@usr01.primenet.com> Subject: Re: AMD PCNet/FAST cards; suppliers? To: mike@smith.net.au (Mike Smith) Date: Sun, 26 Jul 1998 21:00:19 +0000 (GMT) Cc: rjs@fdy2.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: <199807261711.KAA10890@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 10:11:14 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Howdy; a straightforward question: FreeBSD Test Labs is looking for a > > >source for a PCI card or cards using the AMD PCNet and/or PCNet/FAST > > >chips. (Am79c97x etc.) > > > > http://www.amd.com/products/npd/overview/19433f.pdf > > So nobody manufactures an adapter featuring the PC-Net FAST device? > That's kinda depressing. 8( There is a Taiwanese clone board with a Cyrix "Media GX" that comes with an AMD PCNet chip on it. I believe Compaq builds a machine with an AMD PCNet/SCSI chip on it: both the networking chip and the SCSI interface. The SCSI interface is pretty primitive (ie: not very high powered). The PCNet part, as anoyone who has read the chip specs should know, is just a LANCE ethernet chip. The main problem for LANCE parts is recognizing them because they can live a lot of places and require a desctructive probe (you have to make them interrupt to detect them, unless the chip is on a board with a known ROM). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 14:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07702 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 14:09:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07694 for ; Sun, 26 Jul 1998 14:09:51 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA16210; Sun, 26 Jul 1998 14:09:22 -0700 (MST) From: Terry Lambert Message-Id: <199807262109.OAA16210@usr01.primenet.com> Subject: Re: Free BSD Port to new platform. (fwd) To: Matthew.Alton@anheuser-busch.com (Alton, Matthew) Date: Sun, 26 Jul 1998 21:09:21 +0000 (GMT) Cc: don@whtech.com, hackers@FreeBSD.ORG In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF90177661C@STLABCEXG011> from "Alton, Matthew" at Jul 24, 98 07:59:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With full access to the platform specs and the cooperation of design and > engineering people the project amounts to rewriting the hardware-dependent > portions of the code, resolving issues like endianness, alignment.... > and writing drivers for your new devices. It's a substantial project but > the process is quite well-defined. The NetBSD people have a small jump > here with the MIPS-specific work largely out of the way. The real issue > is willingness to do the work. Why not work with all comers? If this new > platform is even vaguely interesting it would be very difficult to keep > hackerfolk from supplying it with a real OS for free, anyway. :-) I'd bet > that you could get a different OS port done per each prototype box that > you were willing to supply. This sounds very interesting. Let's do it. Just a couple of points: 1) I know of someone who has done a lot of work with SPIM on FreeBSD, including working on loading NetBSD COFF/ELF binaries (this work is incomplete). 2) The NetBSD VM model for MIPS and Alpha are quite similar; this is not the "unifications vs. non-unification", but is more related to TLB techniques and page management. 3) FreeBSD is less tolerant of cross-building than NetBSD is; on the other hand, FreeBSD has more people to throw at the project, I believe. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 14:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08026 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 14:12:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08013 for ; Sun, 26 Jul 1998 14:12:02 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id WAA28386; Sun, 26 Jul 1998 22:12:41 +0100 (BST) Date: Sun, 26 Jul 1998 22:12:41 +0100 (BST) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: APTDpde question (pmap) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, zhihuizhang wrote: > > In pmap.c module, we set PTDPTDI entry of the page directory page to point > to itself. So PTDpde and PTmap works well. However, I do not find a > similar setting of APTDTDI (=1023) in pmap.c. My question is how APTDpde > and the alternate address space it's supposed to relate to (APTmap) are > used. (has something to do with pmap copy?) > > Any help is appreciated. I believe that APTD is used to access the ptes of a pmap which is not currently active. The function get_ptbase() sets this up if necessary. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 14:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10141 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 14:27:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10126 for ; Sun, 26 Jul 1998 14:27:06 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA11963; Sun, 26 Jul 1998 14:26:03 -0700 (PDT) Message-Id: <199807262126.OAA11963@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Swindells cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Sun, 26 Jul 1998 19:58:10 BST." <199807261858.TAA00871@fdy2.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 14:26:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Recognising isn't so much the battle as working with them. But yes, > >please do. (File PR, naturally). > > The driver in stable works fine with both the PCnet PCI-II and the > PCnet-FAST reference boards from AMD. That's very interesting. Reports and experience have suggested that some implementations don't work, but it's good to know that we do function correctly with the reference implementations. > I have added support for the extra registers on these boards, but I > did it more to allow me to debug some flakey hardware than to use the > extra functionality. If I get time, I will add mediaopt support. Thanks. Some support for the 32-bit I/O mode might improve efficiency too. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 15:32:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19748 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 15:32:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19711 for ; Sun, 26 Jul 1998 15:32:05 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA16544; Sun, 26 Jul 1998 15:29:15 -0700 (PDT) Message-Id: <199807262229.PAA16544@implode.root.com> To: zhihuizhang cc: hackers Subject: Re: APTDpde question (pmap) In-reply-to: Your message of "Sun, 26 Jul 1998 16:27:43 EDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 26 Jul 1998 15:29:15 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In pmap.c module, we set PTDPTDI entry of the page directory page to point >to itself. So PTDpde and PTmap works well. However, I do not find a >similar setting of APTDTDI (=1023) in pmap.c. My question is how APTDpde >and the alternate address space it's supposed to relate to (APTmap) are >used. (has something to do with pmap copy?) The alternate page table map is used when the kernel wants to access the page tables of a non-current process. The page directory of the target process is mapped at PTD offset 1023, which causes the target process's page tables to become accessable in the final 4MB of the current address space. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 15:35:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20234 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 15:35:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20218 for ; Sun, 26 Jul 1998 15:35:28 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA19067; Sun, 26 Jul 1998 15:34:46 -0700 (MST) From: Terry Lambert Message-Id: <199807262234.PAA19067@usr01.primenet.com> Subject: Re: AMD PCNet/FAST cards; suppliers? To: mike@smith.net.au (Mike Smith) Date: Sun, 26 Jul 1998 22:34:44 +0000 (GMT) Cc: rjs@fdy2.demon.co.uk, mike@smith.net.au, hackers@FreeBSD.ORG In-Reply-To: <199807262126.OAA11963@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 02:26:03 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Recognising isn't so much the battle as working with them. But yes, > > >please do. (File PR, naturally). > > > > The driver in stable works fine with both the PCnet PCI-II and the > > PCnet-FAST reference boards from AMD. > > That's very interesting. Reports and experience have suggested that > some implementations don't work, but it's good to know that we do > function correctly with the reference implementations. You should talk to Doug Ambrisko about this. Running 2 of these cards at 100 resulted in less than desirable throughput. I believe there were also problems with the hardware autodetection, unlike the 82558 part. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 17:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01330 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 17:10:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01252 for ; Sun, 26 Jul 1998 17:09:54 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA12761; Sun, 26 Jul 1998 17:08:47 -0700 (PDT) Message-Id: <199807270008.RAA12761@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), rjs@fdy2.demon.co.uk, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Sun, 26 Jul 1998 22:34:44 -0000." <199807262234.PAA19067@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 17:08:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You should talk to Doug Ambrisko about this. I would hope he'll drop into the discussion. > Running 2 of these cards at 100 resulted in less than desirable > throughput. This is unsurprising given the state of the driver at the moment. The goal here is to locate sample hardware so that we can address the driver issues. > I believe there were also problems with the hardware > autodetection, unlike the 82558 part. Detection of the PCI parts is, not surprisingly, trivial. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 17:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04147 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 17:25:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04103 for ; Sun, 26 Jul 1998 17:24:58 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA12870; Sun, 26 Jul 1998 17:23:17 -0700 (PDT) Message-Id: <199807270023.RAA12870@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Giao Nguyen cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Directory API port? In-reply-to: Your message of "Tue, 21 Jul 1998 18:24:56 EDT." <19980721182456.A13495@beelzebubba.sysabend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 17:23:16 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith said: > > > > > > 1) Is anyone actively working on such a port already? > > > > You will want to talk with Giao Nguyen who is > > carrying an LDAP torch at the moment. I believe he's still working on > > the Umich server port, which needs a million patches. He ought to be > > about ready with it though (*poke*). > > I think that was a hint. :) Very good. > Thank you for reminding me though. I haven't been working on the umich > port proper as much as digesting RFC's and notes from the FreeBSD community > and others. It's just not right to get into something without fully > understanding it (note: Send that last comment to a certain software > company). They will tell you it's better to get to market with a half-finished product, exterminate your competition and then rewrite from scratch. > I am now approaching patch collection status. If you've got patches since > the last port owner was active, please send them my way. *Active* work will > commence once I've got it all (or a good sized chunk). You have the list I gave you initially; I haven't seen anything beyond that AFAIK. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 18:35:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15196 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 18:35:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15172 for ; Sun, 26 Jul 1998 18:35:18 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA13259; Sun, 26 Jul 1998 18:33:48 -0700 (PDT) Message-Id: <199807270133.SAA13259@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: HAMADA Naoki cc: smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: NIC drivers In-reply-to: Your message of "Wed, 15 Jul 1998 15:47:29 +0900." <199807150647.PAA25283@stone.astec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 18:33:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > smoergrd@oslo.geco-prakla.slb.com writes: > >Believe me, it still sucks. Search the archives (both the mailing list > >archives and the PR database) for "no buffer space", and/or "ep0". > >Basically, the driver is fine for telnet and mail, but wedges under > >sustained load. I can get it to hang without ever going above 20 kBps > >(160 kbps). Gimme an Intel EtherExpress. > > I carefully looked through the source code to find a bug which results > mbuf leaks. Could you try this patch? Have you guys gone any further on this one? Is the patch OK, or broken? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 19:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19294 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 19:12:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19250 for ; Sun, 26 Jul 1998 19:12:35 -0700 (PDT) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id LAA10775; Mon, 27 Jul 1998 11:11:52 +0900 (JST) Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.26.2]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id LAA24520; Mon, 27 Jul 1998 11:11:52 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id LAA27031; Mon, 27 Jul 1998 11:11:50 +0900 (JST) Date: Mon, 27 Jul 1998 11:11:50 +0900 (JST) Message-Id: <199807270211.LAA27031@stone.astec.co.jp> From: HAMADA Naoki References: <199807270133.SAA13259@antipodes.cdrom.com> To: mike@smith.net.au CC: smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, hackers@FreeBSD.ORG In-reply-to: Mike Smith's message of "Sun, 26 Jul 1998 18:33:47 -0700" <199807270133.SAA13259@antipodes.cdrom.com> Subject: Re: NIC drivers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> smoergrd@oslo.geco-prakla.slb.com writes: >> >Believe me, it still sucks. Search the archives (both the mailing list >> >archives and the PR database) for "no buffer space", and/or "ep0". >> >Basically, the driver is fine for telnet and mail, but wedges under >> >sustained load. I can get it to hang without ever going above 20 kBps >> >(160 kbps). Gimme an Intel EtherExpress. >> >> I carefully looked through the source code to find a bug which results >> mbuf leaks. Could you try this patch? > >Have you guys gone any further on this one? Is the patch OK, or broken? Sorry guys, this patch is wrong. ERR_RX_INCOMPLETE (which should be renamed to `RX_INCOMPLETE') is an indication of not an error but an incoming packet, so you must not remove the incoming packet. NetBSD's ep driver seems to have some kluge for locking problems, but now I want to spend my time to support new 3C905B adapters... - nao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 19:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24638 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 19:59:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24633 for ; Sun, 26 Jul 1998 19:59:57 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA13670; Sun, 26 Jul 1998 19:57:59 -0700 (PDT) Message-Id: <199807270257.TAA13670@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: HAMADA Naoki cc: mike@smith.net.au, smoergrd@oslo.geco-prakla.slb.com, sbabkin@dcn.att.com, hackers@FreeBSD.ORG Subject: 3c905 driver status (was Re: NIC drivers) In-reply-to: Your message of "Mon, 27 Jul 1998 11:11:50 +0900." <199807270211.LAA27031@stone.astec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 19:57:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First, the issues inre: the old '509 driver; > >> smoergrd@oslo.geco-prakla.slb.com writes: > >> >Believe me, it still sucks. Search the archives (both the mailing list > >> >archives and the PR database) for "no buffer space", and/or "ep0". > >> >Basically, the driver is fine for telnet and mail, but wedges under > >> >sustained load. I can get it to hang without ever going above 20 kBps > >> >(160 kbps). Gimme an Intel EtherExpress. > >> > >> I carefully looked through the source code to find a bug which results > >> mbuf leaks. Could you try this patch? > > > >Have you guys gone any further on this one? Is the patch OK, or broken? > > Sorry guys, this patch is wrong. ERR_RX_INCOMPLETE (which should be > renamed to `RX_INCOMPLETE') is an indication of not an error but an > incoming packet, so you must not remove the incoming packet. OK. Any other ideas? Now, for the 905: > NetBSD's ep driver seems to have some kluge for locking problems, but > now I want to spend my time to support new 3C905B adapters... It would be good if we could have a quick headcount of people working on driver for these cards. I know that Bill Paul is just about ready to release, and there was at least one other individual that was reputedly "just about ready to go into testing" or similar. Can you folks pipe up and perhaps coordinate so that we end up with just one (preferred) driver? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 22:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09997 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 22:02:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09887 for ; Sun, 26 Jul 1998 22:01:59 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA00372; Mon, 27 Jul 1998 00:01:07 -0500 (EST) (envelope-from toor) Message-Id: <199807270501.AAA00372@dyson.iquest.net> Subject: Re: swap/memory management problem In-Reply-To: <19980726154226.A2270@panke.de> from Wolfram Schneider at "Jul 26, 98 03:42:26 pm" To: w@panke.de.freebsd.org (Wolfram Schneider) Date: Mon, 27 Jul 1998 00:01:07 -0500 (EST) Cc: maex-freebsd-hackers@Space.Net, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wolfram Schneider said: > On 1998-07-24 03:59:56 +0200, Markus Stumpf wrote: > > Watched this a loooong ;-) time and never seen pages swapped out but only in. > > > > The nasty thing with this is that squid is getting slower and slower and > > even so the above numbers do no change its getting slower every day it > > runs until I restart it. > > > > I assume this all is due to proactive swapping? > > > > Is there any chance to get rid of this behaviour? Would it help to reduce > > the swap space to e.g. 30 MB? (the 27 GB disk is filled, so I don't think > > squid will grow any further). Anything else I'm missing? > > There are several (undocumented) syctl variables which > control swapping and paging. You can also disable swapping at all. > > $ sysctl -a | grep ^vm > > vm.loadavg: { 0.91 0.94 1.00 } > vm.v_free_min: 161 > vm.v_free_target: 607 > vm.v_free_reserved: 124 > vm.v_inactive_target: 1398 > vm.v_cache_min: 810 > vm.v_cache_max: 3242 > vm.v_pageout_free_min: 34 > vm.pageout_algorithm: 0 > vm.swapping_enabled: 1 > Firstly, how big is squid? Is it bigger than physical memory? How much bigger than physical memory is it? You are probably not swapping but paging. If you are right on the edge is space, try halving vm.v_inactive_target and vm.v_free_target. Do not modify v_free_min, or even more critically, vm.v_free_reserved, unless you increase them slightly. Try also increasing/decreasing vm.v_cache_min -- that is a relatively insensitive control, but does change the disk caching behavior. If your system seems to "seize" due to paging (not "syncing"), you might try doubling the following: vm.v_pageout_free_min, vm.v_free_reserved and vm.v_free_min Also, decreasing vm.v_inactive_target to 75% of it's value might decrease paging (but will decrease the quality of the stats towards an LRU algorithm.) The pageout algorithm can be changed grossly by changing vm.pageout_algorithm=1, which converts the statstical paging algorithm to a more simplistic LRU approximation (this is useful if your locality of reference is flat and doesn't have a usable statistical skew.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 22:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14042 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 22:40:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14036 for ; Sun, 26 Jul 1998 22:40:16 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA14548; Sun, 26 Jul 1998 22:39:05 -0700 (PDT) Message-Id: <199807270539.WAA14548@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: karl@mcs.net (Karl Denninger), hackers@FreeBSD.ORG Subject: Re: Odd problem we're seeing here In-reply-to: Your message of "Sat, 14 Mar 1998 08:58:25 GMT." <199803140858.BAA17978@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 22:39:05 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm seeing an interesting problem here. > > No you're not. You are seeng a problem I already knew about, > and provided a patch for, but the patch was not checked in by > anyone (no, not the NFS locking patch; that should be checked > in, too, though). Was this issue ever resolved to your satisfaction? > The problem is in the lease code, and has been exaggerated by > recent changes that cause the paging path to be invoked for > writes, as well. Leases are the same thing as opportunistic > locks, and... "Opportunity only locks once". 8-) 8-). > > > > Assuming two writers to an NFS file from the SAME machine. > > > > Writer #1 has opened the file O_RDWR and intends to do a set of random > > operations on it. > > > > Writer #2 has opened the file O_WRONLY|O_APPEND and intends only to add > > to the end of the file. > > > > Writer #1 gets an flock on the file, and does things to the file. He > > might even do an ftruncate at some point to roll back the contents. > > > > Writer #2, in the meantime, attempts to get an flock on the file and > > (correctly) blocks, waiting for Writer #1 to finish. > > > > Writer #1 gets done, and releases his lock. > > > > Writer #2 *SOMETIMES DOES NOT WRITE TO THE CORRECT (END OF FILE) PLACE*. > > > > This is difficult to reproduce, but it can be done. It appears that the > > O_APPEND isn't causing the implied lseek(....., 0, SEEK_END) to be done > > before each write in this situation. > > This behaviour is a result of a race condition. > > When you open a file, you are saying > > "Give me the index into my open file table of the struct > file * whose f_data points to the struct vnode for the > file I am opening, and whose f_offset is set to the end > of the file *at the time the write is issued*" > > Now what does O_APPEND mean? > > "When you can vn_open on the nameidata pointer, when you > call the VOP_OPEN, pass the FAPPEND bit in the fmode > argument, where all the FS's will (incorrectly) compare > it to IO_APPEND, which will work because FAPPEND is > defined as IO_APPEND in fcntl.h" > > When nfs_write() is called (in /sys/nfs/nfs_bio.c), if the ioflag > contains IO_APPEND, then a VOP_GETATTR is issued on the vp, and > the uio->uio_offset is set to the value of n_size, which came > from the cache. > > The cache value is set from va_size from a proxied VOP_GETATTR > to the remote system, but *ONLY* if the lease has expired on its > own, or has explicitly been expired. > > What you are seeing is the result of n_attrstamp not being updated > when it should be. > > In fact, you are seeing a race between the flock( fd, LOCK_UN), and > the atime/mtime updates as a result of the operations by write #1. > > > And if you trace down this race window, you will see that what is > happening is that your write call is not calling VOP_LEASE. > > You can get the patch for the files: > > /sys/kern/kern_ktrace.c > /sys/kern/link_aout.c > /src/sys/kern/tty_tty.c > /sys/kern/vfs_vnops.c > > From: > > http://www.freebsd.org/~terry/DIFF.LEASE > > Note: I am not terribly happy about this code. I believe VOP_LEASE > should be called with the vp locked, but I don't do this in two > vn_rdwr cases because of the indeterminate vp lock state. Of course, > the existing code blows this all to hell (SMP problems with NFS, > anyone?). > > The only way to really fix this reasonable would be to get rid of > vn_rdwr, and replace it with vn_read or vn_write, as appropriate > to the situation. Luckily this is really only a problem for the > ktrace and other unlikely code (it used to be a problem for the > image activator, too, until John fixed it after I complained about > it). > > Pretty clearly vn_rdwr was a hack to avoid locking and unlocking > the vp over every call (cough, cough, lazy thinking, cough, cough). > > > > I'm trying to nail this one down. The latest patches to the NFS code appear > > to make this happen more often than it did before, but it did occasionally > > happen even before the patches. > > Writes to mapped NFS pages need to trigger the lease revocation code > as well. This basically means that there needs to be a VOP_LEASE > call for each and every VOP_PUTPAGES in to NFS. > > This should probably go in the vnode pager code before VOP_PUTPAGES > is called. Before the recent changes, paging *to* an NFS FS was a > hopeless case. Now, it can cause problems (though probably not this > one; I don't believe a putpages can be used to extend a file). The > generic routine should be used in case we ever want to export an > opportunity locking mechanism with full coherency to user space > programs. Like SAMBA. But only if we want O_APPEND to work for > SMB and NFS clients accessing the same file (and what idiot would > want a consistently functional system? Where's the adventure? 8-)). > > > > This NEVER happens on locally mounted files, but occasionally happens > > on NFS mounted files. > > Yes, well, it's a real coding error in the VFS client code; what do > you expect? ;-). > > Like I said, though, doing the patches won't fix all the races with > putpages (consider a record being written, and making the decision of > whether or not to read before write, and a record in an adjacent page > was just touched), and it won't work well under SMP unless vn_rdwr > dies (but then the existing code can't work well under SMP, since most > of the other vn_rdwr references have the same bug). > > > Regards, > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 23:06:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16217 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 23:06:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16198; Sun, 26 Jul 1998 23:06:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA14756; Sun, 26 Jul 1998 23:04:54 -0700 (PDT) Message-Id: <199807270604.XAA14756@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: winter@jurai.net (Matthew N. Dodd), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: temporary FreeBSD token-ring list. In-reply-to: Your message of "Thu, 16 Apr 1998 06:25:16 -0000." <199804160625.XAA13265@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 23:04:53 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > freebsd-tokenring@jurai.net is up and running as a temporary mailing list > > for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC > > support to FreeBSD > > > > As there are a number of non-token ring issues that we will have to solve > > before working on any token-ring specific issues, I invite everyone who > > has an interest in making the network subsystem a bit less ethernet > > centric in the places that it is, and those who have interest in > > supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all > > of these. > > As a point of interest, MITRE announced a working NetBEUI for > FreeBSD a number of moths ago on the SAMBA list. > > To do this, they must have implemented the 802.3 LLC. > > Someone should follow up with MITRE. Did they? This would be extremely useful. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 26 23:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18561 for freebsd-hackers-outgoing; Sun, 26 Jul 1998 23:34:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18542; Sun, 26 Jul 1998 23:34:22 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id IAA27175; Mon, 27 Jul 1998 08:33:50 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 27 Jul 1998 08:33:49 +0200 (MET DST) Mime-Version: 1.0 To: Terry Lambert Cc: wollman@khavrinen.lcs.mit.edu, hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysexits References: <199807262055.NAA15776@usr01.primenet.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Jul 1998 08:33:48 +0200 In-Reply-To: Terry Lambert's message of "Sun, 26 Jul 1998 20:55:27 +0000 (GMT)" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA18543 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > You *did* import sendmail on a vendor branch, right? Who, me? Never touched the thing. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 01:26:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29307 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 01:26:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29292 for ; Mon, 27 Jul 1998 01:26:50 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA22812; Mon, 27 Jul 1998 01:26:16 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd022793; Mon Jul 27 01:26:14 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA22455; Mon, 27 Jul 1998 01:26:10 -0700 (MST) From: Terry Lambert Message-Id: <199807270826.BAA22455@usr08.primenet.com> Subject: Re: AMD PCNet/FAST cards; suppliers? To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 08:26:10 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, rjs@fdy2.demon.co.uk, hackers@FreeBSD.ORG In-Reply-To: <199807270008.RAA12761@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 05:08:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You should talk to Doug Ambrisko about this. > > I would hope he'll drop into the discussion. Unfortunately, he has a life. 8-). > > I believe there were also problems with the hardware > > autodetection, unlike the 82558 part. > > Detection of the PCI parts is, not surprisingly, trivial. Autodetection of the 100 vs. 10 rate, not autodetection of the device. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 02:56:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13535 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 02:56:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from eve.speakeasy.org (root@eve.speakeasy.org [199.238.226.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13473 for ; Mon, 27 Jul 1998 02:55:47 -0700 (PDT) (envelope-from aron@speakeasy.net) Received: from term2-035.speakeasy.net (term2-035.speakeasy.net [204.202.112.35]) by eve.speakeasy.org (8.9.0/8.9.0) with SMTP id CAA13720; Mon, 27 Jul 1998 02:55:44 -0700 (PDT) Date: Mon, 27 Jul 1998 02:55:36 -0700 (PDT) From: Aron Roberts X-Sender: aron@localhost.my.domain Reply-To: atr@pobox.com To: Julian Assange cc: freebsd-hackers@FreeBSD.ORG Subject: Re: realplayer5.0 In-Reply-To: <19980726085926.17001.qmail@iq.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last I checked realplayer5.0 worked with no problems on my -current box at work.. the settings in the player were somewhat of a bitch... but that had nothing to do with the linux emulation aron roberts atr@pobox.com On 26 Jul 1998, Julian Assange wrote: > > Has anyone had success in fudging linux realaudio5.0 to work under > emmulation? (RealAudio stopped supporting FreeBSD as a platform after > 3.0). > > Cheers, > Julian. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 03:04:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15621 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 03:04:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14878 for ; Mon, 27 Jul 1998 03:01:45 -0700 (PDT) (envelope-from stb@freebsd.org) Received: from d254.promo.de (d254.Promo.DE [194.45.188.254]) by mail.promo.de (8.8.8/8.8.8) with SMTP id LAA05543; Mon, 27 Jul 1998 11:56:03 +0200 (CEST) Date: Mon, 27 Jul 1998 11:58:14 +0200 From: Stefan Bethke To: Luigi Rizzo cc: Julian Assange , freebsd-hackers@FreeBSD.ORG Subject: Re: realplayer5.0 Message-ID: <352577.3110529494@d254.promo.de> In-Reply-To: <199807261101.NAA03080@labinfo.iet.unipi.it> Originator-Info: login-token=Mulberry:017GVf&ABYAygAEAPcAFgDxAJA- X-Mailer: Mulberry Demo (MacOS) [1.4.0a7, s/n Evaluation] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Son, 26. Jul 1998 13:01 Uhr +0200 Luigi Rizzo wrote: >> Has anyone had success in fudging linux realaudio5.0 to work under >> emmulation? (RealAudio stopped supporting FreeBSD as a platform after >> 3.0). > > long ago i mentioned a patch to one pf the ioctl in the linux emulation > to fool the player and make it believe it was a little bit ahead in the > playback -- this was probably with a last year's version of the > rvplayer5.0 (beta3 perhaps ?). > > Have things changed, and can someone summarize 1) the problem 2) an URL > for the player that seems not to work ? Works like a charm for me (only tried audio). If it doesn't seem to be able to find it's decoder modules, set LD_LIBRARY_PATH=/usr/local/rvplayer5.0 (actually installed under /compat/linux/...) Stefan -- Hamburg | Voice: +49-177-3504009 Germany | e-mail: stb@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 03:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16996 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 03:10:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14000 for ; Mon, 27 Jul 1998 02:58:03 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id MAA11616; Mon, 27 Jul 1998 12:57:17 +0300 (EEST) (envelope-from ru) Message-ID: <19980727125717.A11528@ucb.crimea.ua> Date: Mon, 27 Jul 1998 12:57:17 +0300 From: Ruslan Ermilov To: hackers@FreeBSD.ORG Subject: Could anyone from committers please take a look on PR/6832 (patch for PING)? Mail-Followup-To: hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Please take a look on PR/6832. Is this trivial patch useless? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 04:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25891 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 04:02:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from styx.aic.net (Styx.AIC.NET [195.250.64.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25846; Mon, 27 Jul 1998 04:02:27 -0700 (PDT) (envelope-from ran@styx.aic.net) Received: (from ran@localhost) by styx.aic.net (8.9.0/8.9.0) id QAA18661; Mon, 27 Jul 1998 16:00:27 +0500 ( AMT ) Message-Id: <199807271100.QAA18661@styx.aic.net> Subject: Re: Driver for Arlan-655 In-Reply-To: <199807250021.RAA01186@dingo.cdrom.com> from Mike Smith at "Jul 24, 98 05:21:02 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 16:00:27 +0500 ( AMT ) Cc: ran@ran.am, jflowers@ezo.net, mike@smith.net.au, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, is@gcom.ru From: ran@ran.am Reply-To: ran@ran.am X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This is 8-bit ISA card. Can operate in two mode: > > point-to-point - between two 655 ( sorry, I will use old terminology ), > > and when one or more 655 card connected to access point - other Aironet's > > product - little box with antenna and ethernet connector ( old name > > arlan-640, new - BR2000 ). > > So you can't use more than two cards in a network without an access > point? > Yes. > > And last, I don't know about price :( > > OK. One more; I thought I read just recently that Aironet had just > recently changed the software interface to these cards and that > subsequent attempts to get documentation from them were being refused. > Can we get a confirm/deny on that? > No, I can't confirm it today, but I will try to get this documentation. In case it be success, I will forward to you if you want, of course :) > One other thing; could you submit a PR with the URL for the patches & > stuff, so that we don't lose track of your submission? Thanks! > Done. Category/number is kern/7410 > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > -- Ran d'Adi ran@ran.am ran@styx.aic.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 05:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03891 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 05:01:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from manchester.genrad.com (x159.genrad.co.uk [195.99.3.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03886 for ; Mon, 27 Jul 1998 05:01:10 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Mon, 27 Jul 1998 05:01:10 -0700 (PDT) Message-Id: <199807271201.FAA03886@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id PPD97TN2; Mon, 27 Jul 1998 13:00:01 +0100 From: Robert Swindells To: mike@smith.net.au Cc: hackers@FreeBSD.ORG, faber@isi.edu Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I may have spoken too soon about the driver in stable being OK. There was a change committed on July 20 which looks like it will break probing of the PCnet-II chip. There was a line added to if_lnc.h: > #define HITACHI_Am79C970 0x2621 This is the id of the Am79C970A. This went along with some changes to if_lnc.c that would attach it as an ISA device. I'll have a better look at it tonight. I'll test the driver at 100Mb/s too. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 06:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14174 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 06:17:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13866; Mon, 27 Jul 1998 06:15:00 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id QAA17696; Mon, 27 Jul 1998 16:13:11 +0300 (EEST) (envelope-from ru) Message-ID: <19980727161311.A17629@ucb.crimea.ua> Date: Mon, 27 Jul 1998 16:13:11 +0300 From: Ruslan Ermilov To: hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: I/O error on connection from hub.FreeBSD.ORG, anyone else? Mail-Followup-To: hackers@freebsd.org, postmaster@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Since middle of July my log files are full of messages like these: Jul 27 00:16:17 relay sendmail[6631]: AAA06631: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG Jul 27 00:24:13 relay sendmail[6647]: AAA06647: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG What is going on? The only server I see in such messages is hub.freebsd.org. Are some timeout values were set too small recently on hub.FreeBSD.ORG? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 07:58:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29891 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 07:58:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29876 for ; Mon, 27 Jul 1998 07:58:36 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id JAA00835; Mon, 27 Jul 1998 09:58:07 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id JAA24425; Mon, 27 Jul 1998 09:58:07 -0500 (CDT) Message-ID: <19980727095806.05337@mcs.net> Date: Mon, 27 Jul 1998 09:58:06 -0500 From: Karl Denninger To: Mike Smith Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Odd problem we're seeing here References: <199803140858.BAA17978@usr08.primenet.com> <199807270539.WAA14548@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807270539.WAA14548@antipodes.cdrom.com>; from Mike Smith on Sun, Jul 26, 1998 at 10:39:05PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 10:39:05PM -0700, Mike Smith wrote: > > > I'm seeing an interesting problem here. > > > > No you're not. You are seeng a problem I already knew about, > > and provided a patch for, but the patch was not checked in by > > anyone (no, not the NFS locking patch; that should be checked > > in, too, though). > > Was this issue ever resolved to your satisfaction? Not really. I turned off NVSV3 on the affected machines; that "fixed" it, but its a hack, not a real fix. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > The problem is in the lease code, and has been exaggerated by > > recent changes that cause the paging path to be invoked for > > writes, as well. Leases are the same thing as opportunistic > > locks, and... "Opportunity only locks once". 8-) 8-). > > > > > > > Assuming two writers to an NFS file from the SAME machine. > > > > > > Writer #1 has opened the file O_RDWR and intends to do a set of random > > > operations on it. > > > > > > Writer #2 has opened the file O_WRONLY|O_APPEND and intends only to add > > > to the end of the file. > > > > > > Writer #1 gets an flock on the file, and does things to the file. He > > > might even do an ftruncate at some point to roll back the contents. > > > > > > Writer #2, in the meantime, attempts to get an flock on the file and > > > (correctly) blocks, waiting for Writer #1 to finish. > > > > > > Writer #1 gets done, and releases his lock. > > > > > > Writer #2 *SOMETIMES DOES NOT WRITE TO THE CORRECT (END OF FILE) PLACE*. > > > > > > This is difficult to reproduce, but it can be done. It appears that the > > > O_APPEND isn't causing the implied lseek(....., 0, SEEK_END) to be done > > > before each write in this situation. > > > > This behaviour is a result of a race condition. > > > > When you open a file, you are saying > > > > "Give me the index into my open file table of the struct > > file * whose f_data points to the struct vnode for the > > file I am opening, and whose f_offset is set to the end > > of the file *at the time the write is issued*" > > > > Now what does O_APPEND mean? > > > > "When you can vn_open on the nameidata pointer, when you > > call the VOP_OPEN, pass the FAPPEND bit in the fmode > > argument, where all the FS's will (incorrectly) compare > > it to IO_APPEND, which will work because FAPPEND is > > defined as IO_APPEND in fcntl.h" > > > > When nfs_write() is called (in /sys/nfs/nfs_bio.c), if the ioflag > > contains IO_APPEND, then a VOP_GETATTR is issued on the vp, and > > the uio->uio_offset is set to the value of n_size, which came > > from the cache. > > > > The cache value is set from va_size from a proxied VOP_GETATTR > > to the remote system, but *ONLY* if the lease has expired on its > > own, or has explicitly been expired. > > > > What you are seeing is the result of n_attrstamp not being updated > > when it should be. > > > > In fact, you are seeing a race between the flock( fd, LOCK_UN), and > > the atime/mtime updates as a result of the operations by write #1. > > > > > > And if you trace down this race window, you will see that what is > > happening is that your write call is not calling VOP_LEASE. > > > > You can get the patch for the files: > > > > /sys/kern/kern_ktrace.c > > /sys/kern/link_aout.c > > /src/sys/kern/tty_tty.c > > /sys/kern/vfs_vnops.c > > > > From: > > > > http://www.freebsd.org/~terry/DIFF.LEASE > > > > Note: I am not terribly happy about this code. I believe VOP_LEASE > > should be called with the vp locked, but I don't do this in two > > vn_rdwr cases because of the indeterminate vp lock state. Of course, > > the existing code blows this all to hell (SMP problems with NFS, > > anyone?). > > > > The only way to really fix this reasonable would be to get rid of > > vn_rdwr, and replace it with vn_read or vn_write, as appropriate > > to the situation. Luckily this is really only a problem for the > > ktrace and other unlikely code (it used to be a problem for the > > image activator, too, until John fixed it after I complained about > > it). > > > > Pretty clearly vn_rdwr was a hack to avoid locking and unlocking > > the vp over every call (cough, cough, lazy thinking, cough, cough). > > > > > > > I'm trying to nail this one down. The latest patches to the NFS code appear > > > to make this happen more often than it did before, but it did occasionally > > > happen even before the patches. > > > > Writes to mapped NFS pages need to trigger the lease revocation code > > as well. This basically means that there needs to be a VOP_LEASE > > call for each and every VOP_PUTPAGES in to NFS. > > > > This should probably go in the vnode pager code before VOP_PUTPAGES > > is called. Before the recent changes, paging *to* an NFS FS was a > > hopeless case. Now, it can cause problems (though probably not this > > one; I don't believe a putpages can be used to extend a file). The > > generic routine should be used in case we ever want to export an > > opportunity locking mechanism with full coherency to user space > > programs. Like SAMBA. But only if we want O_APPEND to work for > > SMB and NFS clients accessing the same file (and what idiot would > > want a consistently functional system? Where's the adventure? 8-)). > > > > > > > This NEVER happens on locally mounted files, but occasionally happens > > > on NFS mounted files. > > > > Yes, well, it's a real coding error in the VFS client code; what do > > you expect? ;-). > > > > Like I said, though, doing the patches won't fix all the races with > > putpages (consider a record being written, and making the decision of > > whether or not to read before write, and a record in an adjacent page > > was just touched), and it won't work well under SMP unless vn_rdwr > > dies (but then the existing code can't work well under SMP, since most > > of the other vn_rdwr references have the same bug). > > > > > > Regards, > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 08:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08051 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 08:46:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07978 for ; Mon, 27 Jul 1998 08:45:59 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA09150 for ; Mon, 27 Jul 1998 08:44:52 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id LAA02790; Mon, 27 Jul 1998 11:44:03 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id MAA16199; Mon, 27 Jul 1998 12:18:46 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id LAA13790; Mon, 27 Jul 1998 11:48:11 -0400 (EDT) Date: Mon, 27 Jul 1998 11:48:11 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807271548.LAA13790@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com, sas@schell.de Subject: Freeing Free Block [was: Re: FreeBSD or LINUX??? - Which one should I choose?] In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sascha Schumann wrote: > > On 25 Jul 1998, Peter Mutsaers wrote: > > > >> On Fri, 24 Jul 1998 22:22:40 +0200 (MET DST), Sascha Schumann > > >> said: > [..] > > > > Maybe, but from my experience, FreeBSD (even -current) is more stable > > than Linux. > > I'm running FreeBSD-stable (2.2.7) now for four days and it crashed three > times on me. The first time, I copied a 2MB file to a clean ext2fs > partition - the system hang (I could still switch between terminals), > but the partition was mixed up - lots of errors while running e2fsck. The > second time happened while hammering the FreeBSD machine with lots of web > request. The system froze (=totally dead) after ~2M requests. The third > time was again disk related, "Freeing free block" and system reboot within > 15 seconds while installing a new kernel image. Sascha - I'd like to hear more about the last crash you got "Freeing free block". Can you describe the circumstances, and with luck; provide a reproduction? - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 09:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16324 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 09:33:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ultra3 (ultra3.cc.binghamton.edu [128.226.4.23]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA16314 for ; Mon, 27 Jul 1998 09:33:51 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by ultra3 (SMI-8.6/8.6.9) with SMTP id MAA00424; Mon, 27 Jul 1998 12:33:13 -0400 Date: Mon, 27 Jul 1998 12:33:11 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@ultra3 To: David Greenman cc: hackers Subject: Re: APTDpde question (pmap) In-Reply-To: <199807262229.PAA16544@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, David Greenman wrote: > >In pmap.c module, we set PTDPTDI entry of the page directory page to point > >to itself. So PTDpde and PTmap works well. However, I do not find a > >similar setting of APTDTDI (=1023) in pmap.c. My question is how APTDpde > >and the alternate address space it's supposed to relate to (APTmap) are > >used. (has something to do with pmap copy?) > > The alternate page table map is used when the kernel wants to access the > page tables of a non-current process. The page directory of the target > process is mapped at PTD offset 1023, which causes the target process's page > tables to become accessable in the final 4MB of the current address space. > (Please note that PTDPTDI = 959) I read the get_ptbase() again. The way it judges whether we are current address space is by comparing pmap->pm_pdir[PTDPTDI] & PG_FRAME and (((unsigned) PTDpde) & PG_FRAME). The value of pmap->pm_pdir[PTDPTDI] & PG_FRAME is the physical address of the page directory page of the pmap (set up by pmap_pinit()). But I am confused with the meaning of (((unsigned)PTDpde) & PG_FRAME). I thought the value of PTDpde (and similar things happen for APTDpde) is fixed as 959|959|959 (I divide the linear address into three parts, separating them by "|"). But the address, not the value, of the PTDpde should be 959|959|959 to make things work, because I believe that the way to determine that we are the current address space is to make sure that we are using the same page directory page. So I go to locore.s where PTDpde is defined. locore.s uses the .set directive. I guess the .set directive is not equal to assignment statement in C programming language. I looked the info file and find the following: "The value of a symbol is (usually) 32 bits. For a symbol which labels a location in the text, data, bss or absolute sections the value is the number of addresses from the start of that section to the label. Naturally for text, data and bss sections the value of a symbol changes as `ld' changes section base addresses during linking. Absolute symbols' values do not change during linking: that is why they are called absolute." So for assembly, the *value* of the absolute symbol PTDpde (actually _PTDpde) is 959|959|959. But for C, PTDpde has the address (not the value) of 959|959|959. Am I right? Please clarify this for me. Thanks for your help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 10:20:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24061 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 10:20:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24048 for ; Mon, 27 Jul 1998 10:20:29 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for hackers@FreeBSD.ORG id 0z0qwG-0007Xx-00; Mon, 27 Jul 1998 12:19:56 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: inetd enhancements To: hackers@FreeBSD.ORG Date: Mon, 27 Jul 1998 12:19:56 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi, I'd like to add some functionality to inetd. The two features needed are: * binding selected services to a particular interface * chroot'ing before exec'ing the service I've implemented these features as a port that modifies the stock inetd source: http://www.freebsd.org/~nectar/ports/ninetd.shar http://www.freebsd.org/~nectar/ports/ninetd.tar.gz (the modified inetd gets installed in /usr/local/sbin, and gets its config from /usr/local/etc/inetd.conf, so it shouldn't be too intrusive) I also came across a patch that implements the binding in a different manner: see PR bin/2387. I'd like comments. Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNby2vDeRhT8JRySpAQEzYQQAyWBRkv1lhYxrnT3GUeVSTh1CcUesQdXT nDvIIjO5AlQHXQodH241WZBED3v2fcnjmf5hc5msg3E4H5yx059T7TexG9pHeIXT EiUQe/ZqG6LP2Cs4rN3kGmPIsp1442byE3MmeaNO80VSmhv0olx6r5KV0YR4qVqo FyPgUDxwWcM= =S1bV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 10:38:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27473 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 10:38:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27468 for ; Mon, 27 Jul 1998 10:38:43 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id GAA16559; Mon, 27 Jul 1998 06:20:34 -0700 (PDT) Message-Id: <199807271320.GAA16559@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Swindells cc: mike@smith.net.au, hackers@FreeBSD.ORG, faber@isi.edu Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Mon, 27 Jul 1998 05:01:10 PDT." <199807271201.FAA03886@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 06:20:34 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I may have spoken too soon about the driver in stable being OK. > > There was a change committed on July 20 which looks like it will break > probing of the PCnet-II chip. > > There was a line added to if_lnc.h: > > > #define HITACHI_Am79C970 0x2621 > > This is the id of the Am79C970A. > > This went along with some changes to if_lnc.c that would attach it as > an ISA device. > > I'll have a better look at it tonight. I'll test the driver at 100Mb/s > too. OK. If you have any better ideas about fixing the problem that Ted fudged around, by all means put them forth. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 10:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27845 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 10:40:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27757 for ; Mon, 27 Jul 1998 10:40:10 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id GAA16516; Mon, 27 Jul 1998 06:10:59 -0700 (PDT) Message-Id: <199807271310.GAA16516@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Mon, 27 Jul 1998 08:26:10 -0000." <199807270826.BAA22455@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 06:10:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > You should talk to Doug Ambrisko about this. > > > > I would hope he'll drop into the discussion. > > Unfortunately, he has a life. 8-). Our loss, I guess. > > > I believe there were also problems with the hardware > > > autodetection, unlike the 82558 part. > > > > Detection of the PCI parts is, not surprisingly, trivial. > > Autodetection of the 100 vs. 10 rate, not autodetection of the device. That's "autonegotiation", and it's supposed to happen in hardware. This tends to contradict the claim that the AMD reference hardware works as-is... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 10:47:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29233 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 10:47:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29210 for ; Mon, 27 Jul 1998 10:47:39 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id KAA25470 for freebsd-hackers@freebsd.org; Mon, 27 Jul 1998 10:45:50 -0700 (PDT) (envelope-from dhw) Date: Mon, 27 Jul 1998 10:45:50 -0700 (PDT) From: David Wolfskill Message-Id: <199807271745.KAA25470@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-Reply-To: <35BC9088.D189FAEF@csl.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Original exchange from -questions; I think what I'm going on about is rather more -hackerish, so that's where this is. dhw] >Date: Mon, 27 Jul 1998 15:36:56 +0100 >From: Adam Nealis >> Could someone tell me how you can check the amount of RAM both available >> and in use at a given time on FreeBSD 2.2.6 ? >Try >dmesg | more >soon after a reboot. Should tell you how much RAM was found on the way up. Well, re-booting a production server that's been up for several months just to find out how much real memory the kernel saw may not be a viable option. :-} Granted, someone else suggested "top", which is fine for this particular resource.... However, as a follow-on to a discussion I was having with someone else (where I was doing a bunch of whining about the challenges I was having in "automatically" being able to determine the configuration of a given FreeBSD box), the random idea came up that *IF* the kernel could stash away the results of its probing in some way that might be amenable to access by suitably-privileged processes at times arbitrarily distant from re-boot (i.e, scannning logs & output of dmesg won't do the job), this *might* be sufficiently useful to warrant some effort. I suppose that one way to do a hack that could be adequate for a trial run would be to have /etc/rc run a script that would run "dmesg" & parse it, then stuff the results of this parsing into a file that could be read by a process running under effective GID "operator". The objective would be to record enough information that given the (properly-interpreted) content of the file in question, it would be possible to specify the components to re-construct the machine in question. In turn, the reason for this is for "disaster recovery preparedness". Does this seem as if it might possibly be of use to anyone else? Thanks, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04327 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:13:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04275; Mon, 27 Jul 1998 11:13:01 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from ivy.ezo.net (c3po.skylan.net [206.150.211.243]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id OAA16936; Mon, 27 Jul 1998 14:10:41 -0400 (EDT) Message-ID: <011501bdb98a$232e3c60$f3d396ce@ivy.ezo.net> From: "Jim Flowers" To: "Mike Smith" Cc: , Subject: Re: Driver for Arlan-655 Date: Mon, 27 Jul 1998 14:12:37 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Didn't get to the office until today. You can find US supplier and pricing at http://www.nortech.com/aironet/airprice.htm 655 card is $895 US. Don't know anything about Nortech except they are located in Yakima, WA. and seem to specialize in wireless. Jim Flowers -----Original Message----- From: Mike Smith To: ran@ran.am Cc: Mike Smith ; freebsd-hackers@FreeBSD.ORG ; freebsd-questions@FreeBSD.ORG ; is@gcom.ru Date: Thursday, July 23, 1998 7:01 PM Subject: Re: Driver for Arlan-655 >> > > >> > > Hi there, >> > > >> > > Attached to this letter you'll find source code of a driver for Aeronet >> > > radio modem arlan-655. The driver was developed by Iwan Sharow >> > > , I modified this driver to add multiple modems support, as >> > > well as have added a configuration program and its support in the driver >> > > through ioctl. >> > >> > Hmm. Aironet don't actually mention this product on their webpages. >> > Is it current, or obsolete? >> > >> >> Look here: >> http://www.aironet.com/products/2200fam/2200fam.html >> AFAIK, IC2200 is new name for arlan-655. > >Ok, that helps quite a lot. 8) > >How expensive are these cards? Anyone know of a supplier in the USA? > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07621 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:27:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07578 for ; Mon, 27 Jul 1998 11:27:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00633; Mon, 27 Jul 1998 11:25:51 -0700 (PDT) Message-Id: <199807271825.LAA00633@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-reply-to: Your message of "Mon, 27 Jul 1998 10:45:50 PDT." <199807271745.KAA25470@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 11:25:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. Something like /var/run/dmesg.boot, perhaps? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:28:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07742 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:28:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07653 for ; Mon, 27 Jul 1998 11:27:51 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id LAA16857; Mon, 27 Jul 1998 11:26:17 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id LAA04294; Mon, 27 Jul 1998 11:25:33 -0700 (PDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.68.38]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id OAA26967; Mon, 27 Jul 1998 14:26:15 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.8/8.8.8) with ESMTP id OAA18112; Mon, 27 Jul 1998 14:26:07 -0400 (EDT) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199807271826.OAA18112@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG cc: witr@rwwa.com, bwithrow@BayNetworks.COM Subject: Multi-function PC cards? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 14:26:07 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone tell me the state of play, architecturally and developmentally, of multi-function PC card software for FreeBSD (2.x and 3.x)? (Like for combo modem/ethernet cards.) Has anything been done? Has anything been designed? -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:44:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11929 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:44:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11821 for ; Mon, 27 Jul 1998 11:43:59 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id LAA25740; Mon, 27 Jul 1998 11:42:01 -0700 (PDT) (envelope-from dhw) Date: Mon, 27 Jul 1998 11:42:01 -0700 (PDT) From: David Wolfskill Message-Id: <199807271842.LAA25740@pau-amma.whistle.com> To: dhw@whistle.com, mike@smith.net.au Subject: Re: Checking RAM Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199807271825.LAA00633@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 27 Jul 1998 11:25:51 -0700 >From: Mike Smith >> However, as a follow-on to a discussion I was having with someone else >> (where I was doing a bunch of whining about the challenges I was having >> in "automatically" being able to determine the configuration of a given >> FreeBSD box), the random idea came up that *IF* the kernel could stash >> away the results of its probing in some way that might be amenable to >> access by suitably-privileged processes at times arbitrarily distant >> from re-boot (i.e, scannning logs & output of dmesg won't do the job), >> this *might* be sufficiently useful to warrant some effort. >Something like /var/run/dmesg.boot, perhaps? Yes, that's an excellent start -- thanks! However, unless I'm even less clueful than usual, that needs some augmentation if someone should be reasonably expected to take that file & be able to reconstruct the machine on which the file was created (assuming, say, "dump" backup images for all filesystems). For example, information about disk partitioning would seem to be necessary, as well as interpreting the "dmesg" output so someone could determine what cards go in what slots (assuming it makes a difference?). Please recall that the intended purpose is to be able to reconstruct the environment, assuming that (for whatever reason(s)) access to the original machines is not available (either for poking & prodding or logging in). Of course, I'm certainly open to comments like "this isn't really feasible" -- but it seems to me that it's just part of normal disaster recovery preparedness... and I'd think that folks have addressed the issue in some form previously.... Thanks again, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12420 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:47:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12324 for ; Mon, 27 Jul 1998 11:46:35 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id LAA17349; Mon, 27 Jul 1998 11:45:19 -0700 (PDT) Message-Id: <199807271845.LAA17349@tnt.isi.edu> To: Mike Smith Cc: Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Mon, 27 Jul 1998 06:20:34 PDT." <199807271320.GAA16559@antipodes.cdrom.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 11:45:19 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Mike Smith wrote: >> I'll have a better look at it tonight. I'll test the driver at 100Mb/s >> too. > >OK. If you have any better ideas about fixing the problem that Ted >fudged around, by all means put them forth. Indeed. I'd appreciate the chance to test them on my Hitachi as well. Hopefully we can get something stable that works for everyone. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbzKvYb4eisfQ5rpAQFEPwP+ONhKxSicnNDukV0YEpqhIqDjK+GroYKC p80iuOOTRfGu6nFRQg6xq4sm1VlE+0bTBDvoa+VADPDRUJ0ylyiXIGj3QlhzdUce uLY5b5NZFsPLHtkeWPbAVfin8gTB7/8Trf6MLmCtMHKTe4AjQnAKgRSQRmG/g0c5 hW9A/HqCfzs= =akg3 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 11:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14940 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 11:59:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14746 for ; Mon, 27 Jul 1998 11:58:40 -0700 (PDT) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA22592; Mon, 27 Jul 1998 11:46:41 -0700 (PDT) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdk22585; Mon Jul 27 18:46:34 1998 Received: (from ambrisko@localhost) by whistle.com (8.8.8/8.8.7) id SAA04478; Mon, 27 Jul 1998 18:35:01 GMT (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199807271835.SAA04478@whistle.com> Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: <199807270826.BAA22455@usr08.primenet.com> from Terry Lambert at "Jul 27, 98 08:26:10 am" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 27 Jul 1998 18:34:59 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, rjs@fdy2.demon.co.uk, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: | > > You should talk to Doug Ambrisko about this. | > | > I would hope he'll drop into the discussion. | | Unfortunately, he has a life. 8-). Atleast on weekends. | > > I believe there were also problems with the hardware | > > autodetection, unlike the 82558 part. | > | > Detection of the PCI parts is, not surprisingly, trivial. | | Autodetection of the 100 vs. 10 rate, not autodetection of the device. One of the issues is that at the time you couldn't set the card in 10 or 100 mode since the driver support wasn't there. Connecting multiple autosense cards via a cross cable sometimes causes both to bounce between 10 and 100 when trying to auto-detect. Using a hub got rid of this problem. Routing was a big issue. At 100BaseT speeds and one AMD card things were okay. I forget the numbers but "acceptable" not as good as DEC or Intel. The problem came as soon as you tried routing through two cards. performance would fall through the floor <.03Mbit/s. I also tried them with SCO Openserver (Personal edition). Routing was again terrible with SCO non-routing was okay. FYI SCO was <1/2 the routing performance of FreeBSD with good Intel cards. FreeBSD with our version of natd routing faster then SCO. Since AMD wasn't willing to put any effort into trying to reproduce the SCO case we dropped that idea (they blamed FreeBSD and SCO even though they supplied the SCO driver). I'm not sure if we still have the eval cards. BTW testing either card separately was okay, only when routing between cards or running both cards at the same time was there a problem. This problem was similar to the ISA AMD cards that bus master. One card is fine, start routing and things blow up due to bus master issues. This also means an AMD ISA card with a Adaptec 1542 is a bad idea (which I had at home). Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 12:02:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15660 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 12:02:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15492 for ; Mon, 27 Jul 1998 12:01:37 -0700 (PDT) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn149.dial.xs4all.nl [194.109.148.149]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id VAA16155 for ; Mon, 27 Jul 1998 21:01:02 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.8.8/8.8.8) id VAA02587; Mon, 27 Jul 1998 21:01:29 +0200 (MET DST) (envelope-from plm) To: freebsd-hackers@FreeBSD.ORG Subject: Re: realplayer5.0 References: <8767gje03e.fsf@totally-fudged-out-message-id> From: Peter Mutsaers Date: 27 Jul 1998 18:32:08 +0200 In-Reply-To: Aron Roberts's message of "Mon, 27 Jul 1998 02:55:36 -0700 (PDT)" Message-ID: <8790lfi7av.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.27/Emacs 20.2 Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> On Mon, 27 Jul 1998 02:55:36 -0700 (PDT), Aron Roberts said: AR> Last I checked realplayer5.0 worked with no problems on my AR> -current box at work.. the settings in the player were AR> somewhat of a bitch... but that had nothing to do with the AR> linux emulation It works on my -current, but after a while it locks up always. I do think there are some incompatabilities in the sound driver w.r.t. Linux emulation. -- /\_/\ ( o.o ) Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know ) ^ ( plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 12:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16059 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 12:03:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15911 for ; Mon, 27 Jul 1998 12:03:15 -0700 (PDT) (envelope-from nash@Venus.mcs.net) Received: from Venus.mcs.net (nash@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA19193; Mon, 27 Jul 1998 14:02:42 -0500 (CDT) Received: (from nash@localhost) by Venus.mcs.net (8.8.7/8.8.2) id OAA09753; Mon, 27 Jul 1998 14:02:41 -0500 (CDT) Message-ID: <19980727140238.12123@mcs.net> Date: Mon, 27 Jul 1998 14:02:38 -0500 From: Alex Nash To: David Wolfskill Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM References: <35BC9088.D189FAEF@csl.com> <199807271745.KAA25470@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807271745.KAA25470@pau-amma.whistle.com>; from David Wolfskill on Mon, Jul 27, 1998 at 10:45:50AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 10:45:50AM -0700, David Wolfskill wrote: > I suppose that one way to do a hack that could be adequate for a trial > run would be to have /etc/rc run a script that would run "dmesg" & parse > it, then stuff the results of this parsing into a file that could be > read by a process running under effective GID "operator". > > The objective would be to record enough information that given the > (properly-interpreted) content of the file in question, it would be > possible to specify the components to re-construct the machine in > question. Will /var/run/dmesg.boot do? :) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 12:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17415 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 12:09:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17280 for ; Mon, 27 Jul 1998 12:08:51 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id PAA18623; Mon, 27 Jul 1998 15:09:08 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 27 Jul 1998 15:09:08 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-Reply-To: <199807271745.KAA25470@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /var/run/dmesg.boot (this is on -current dunno about -stable) -Alfred On Mon, 27 Jul 1998, David Wolfskill wrote: > [Original exchange from -questions; I think what I'm going on about is > rather more -hackerish, so that's where this is. dhw] > > >Date: Mon, 27 Jul 1998 15:36:56 +0100 > >From: Adam Nealis > > >> Could someone tell me how you can check the amount of RAM both available > >> and in use at a given time on FreeBSD 2.2.6 ? > > >Try > > >dmesg | more > > >soon after a reboot. Should tell you how much RAM was found on the way up. > > Well, re-booting a production server that's been up for several months > just to find out how much real memory the kernel saw may not be a viable > option. :-} Granted, someone else suggested "top", which is fine for > this particular resource.... > > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. > > I suppose that one way to do a hack that could be adequate for a trial > run would be to have /etc/rc run a script that would run "dmesg" & parse > it, then stuff the results of this parsing into a file that could be > read by a process running under effective GID "operator". > > The objective would be to record enough information that given the > (properly-interpreted) content of the file in question, it would be > possible to specify the components to re-construct the machine in > question. > > In turn, the reason for this is for "disaster recovery preparedness". > > Does this seem as if it might possibly be of use to anyone else? > > Thanks, > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 13:04:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26373 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:04:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26327 for ; Mon, 27 Jul 1998 13:04:18 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id NAA07147; Mon, 27 Jul 1998 13:03:11 -0700 (PDT) Date: Mon, 27 Jul 1998 13:03:11 -0700 (PDT) From: Ian Kallen To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-Reply-To: <199807271745.KAA25470@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While it might indeed be useful to fetch the last reboot's dmesg output (stuff it into /var/log/dmesg.reboot or something), you can get the physical ram from "sysctl hw.physmem" -Ian On Mon, 27 Jul 1998, David Wolfskill wrote: :>> Could someone tell me how you can check the amount of RAM both available :>> and in use at a given time on FreeBSD 2.2.6 ? :>Try :>dmesg | more :>soon after a reboot. Should tell you how much RAM was found on the way up. : :Well, re-booting a production server that's been up for several months :just to find out how much real memory the kernel saw may not be a viable :option. :-} Granted, someone else suggested "top", which is fine for :this particular resource.... : :However, as a follow-on to a discussion I was having with someone else :(where I was doing a bunch of whining about the challenges I was having :in "automatically" being able to determine the configuration of a given :FreeBSD box), the random idea came up that *IF* the kernel could stash :away the results of its probing in some way that might be amenable to :access by suitably-privileged processes at times arbitrarily distant :from re-boot (i.e, scannning logs & output of dmesg won't do the job), :this *might* be sufficiently useful to warrant some effort. : :I suppose that one way to do a hack that could be adequate for a trial :run would be to have /etc/rc run a script that would run "dmesg" & parse :it, then stuff the results of this parsing into a file that could be :read by a process running under effective GID "operator". : :The objective would be to record enough information that given the :(properly-interpreted) content of the file in question, it would be :possible to specify the components to re-construct the machine in :question. : :In turn, the reason for this is for "disaster recovery preparedness". : :Does this seem as if it might possibly be of use to anyone else? -- We do not colonize. We conquer. We rule. There is no other way for us. -- Rojan, "By Any Other Name", stardate 4657.5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 13:10:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27823 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:10:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27759 for ; Mon, 27 Jul 1998 13:10:23 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA10805; Mon, 27 Jul 1998 22:09:35 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 27 Jul 1998 22:09:35 +0200 (MET DST) Mime-Version: 1.0 To: David Wolfskill Cc: mike@smith.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM References: <199807271842.LAA25740@pau-amma.whistle.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Jul 1998 22:09:34 +0200 In-Reply-To: David Wolfskill's message of "Mon, 27 Jul 1998 11:42:01 -0700 (PDT)" Message-ID: Lines: 68 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA27780 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Wolfskill writes: > >Date: Mon, 27 Jul 1998 11:25:51 -0700 > >From: Mike Smith > > >> However, as a follow-on to a discussion I was having with someone else > >> (where I was doing a bunch of whining about the challenges I was having > >> in "automatically" being able to determine the configuration of a given > >> FreeBSD box), the random idea came up that *IF* the kernel could stash > >> away the results of its probing in some way that might be amenable to > >> access by suitably-privileged processes at times arbitrarily distant > >> from re-boot (i.e, scannning logs & output of dmesg won't do the job), > >> this *might* be sufficiently useful to warrant some effort. > > >Something like /var/run/dmesg.boot, perhaps? > > Yes, that's an excellent start -- thanks! > > However, unless I'm even less clueful than usual, that needs some > augmentation if someone should be reasonably expected to take that file > & be able to reconstruct the machine on which the file was created > (assuming, say, "dump" backup images for all filesystems). > > For example, information about disk partitioning would seem to be > necessary, as well as interpreting the "dmesg" output so someone could > determine what cards go in what slots (assuming it makes a difference?). If you're running a DEVFS/SLICE system, disk slices and partitions will be probed in a manner similar to "real" devices and output from this process will appear in dmesg.boot: sd0: probing for MBR.. rejected.. Slice includes MBR sd0: probing for disklabel. . part a, start=0, size=131072 part b, start=131072, size=1048576 part d, start=3932160, size=4958600 part e, start=1179648, size=131072 part f, start=1310720, size=524288 part g, start=1835008, size=1048576 part h, start=2883584, size=1048576 sd1: probing for MBR.. rejected.. Slice includes MBR sd1: probing for disklabel. . part e, start=0, size=524288 part f, start=524288, size=1572864 part g, start=2097152, size=10560565 sd2: probing for MBR.. part 1, start=63, size=2104452 sd2s1: attaching disklabel.. part e, start=0, size=524288 part f, start=524288, size=1580164 In the non-SLICE case, I don't see any other solution than 'cat /etc/fstab' and a few judicious disklabel(8) runs. As to "what cards go in what slots", it's only relevant for PCI cards. You'll notice PCI devices have "on pcix.xx.x" at the end of the probe line: de0: rev 0x22 int a irq 15 on pci0.9.0 vga0: rev 0x70 int a irq 9 on pci0.10.0 ahc0: rev 0x00 int a irq 12 on pci0.11.0 ahc1: rev 0x00 int a irq 11 on pci0.12.0 The first number ('0'in 'pci0') is the bus number; the second is the slot number. In my case, the ordering of the cards is highly relevant, since the order in which the SCSI adapters are probed determines the order in which the disks are attached. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 13:11:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28053 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:11:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27997; Mon, 27 Jul 1998 13:11:25 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig1.att.att.com by cagw1.att.com (AT&T/UPAS) for freebsd.org!freebsd-questions freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Mon Jul 27 16:02 EDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id QAA17638; Mon, 27 Jul 1998 16:10:43 -0400 (EDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Mon, 27 Jul 1998 16:10:20 -0400 Message-ID: To: mike@smith.net.au, ran@ran.am Cc: jflowers@ezo.net, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, is@gcom.ru Subject: RE: Driver for Arlan-655 Date: Mon, 27 Jul 1998 16:10:18 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > > > > >How expensive are these cards? Anyone know of a supplier in the > USA? > > > > > > > > Ok, now I understood, Mike :) > > Thanks. 8) > > > This is 8-bit ISA card. Can operate in two mode: > > point-to-point - between two 655 ( sorry, I will use old terminology > ), > > and when one or more 655 card connected to access point - other > Aironet's > > product - little box with antenna and ethernet connector ( old name > > arlan-640, new - BR2000 ). > > So you can't use more than two cards in a network without an access > point? > May be I'm confusing something, but I think we had Aironet RadioEthernet bridges at my previous work. Or was that AirLAN ? Their speed was 2Mbit/s and they were able to work both point-to-point with directed antenna or broadcast with some different (all-directed) model of antenna which we did not have because we needed them as point-to point connection and directed antenna gave longer range. Most of the time they worked quite good. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 13:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03238 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:38:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03231 for ; Mon, 27 Jul 1998 13:38:48 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-126.camalott.com [208.229.74.126]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA31406; Mon, 27 Jul 1998 15:39:17 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA17808; Mon, 27 Jul 1998 15:38:04 -0500 (CDT) (envelope-from joelh) Date: Mon, 27 Jul 1998 15:38:04 -0500 (CDT) Message-Id: <199807272038.PAA17808@detlev.UUCP> To: dhw@whistle.com CC: freebsd-hackers@FreeBSD.ORG In-reply-to: <199807271745.KAA25470@pau-amma.whistle.com> (message from David Wolfskill on Mon, 27 Jul 1998 10:45:50 -0700 (PDT)) Subject: Re: Checking RAM From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807271745.KAA25470@pau-amma.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Could someone tell me how you can check the amount of RAM both available >>> and in use at a given time on FreeBSD 2.2.6 ? > >> Try >> dmesg | more >> soon after a reboot. Should tell you how much RAM was found on the way up. > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. I suppose you could add to your own /etc/local: dmesg | egrep '(real|avail) memory = ' > /var/log/mem More generally, you may prefer dmesg > /var/log/dmesg.boot instead. I can't see how this is useful, myself. In a situation where I don't know the configuration of each machine by heart, I use a binder to store configuration info. Helpful in the event of a machine failure. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 13:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04456 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 13:44:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04414; Mon, 27 Jul 1998 13:44:34 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id WAA19035; Mon, 27 Jul 1998 22:43:45 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id VAA00922; Sat, 25 Jul 1998 21:58:31 +0200 (CEST) X-Face: " Date: Sat, 25 Jul 1998 21:58:30 +0200 From: Stefan Esser To: HAMADA Naoki , gram@cdsec.com Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: Building a kernel with PCI devices Mail-Followup-To: HAMADA Naoki , gram@cdsec.com, hackers@FreeBSD.ORG References: <199807211322.PAA03583@cdsec.com> <199807220535.OAA12647@stone.astec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807220535.OAA12647@stone.astec.co.jp>; from HAMADA Naoki on Wed, Jul 22, 1998 at 02:35:45PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-22 14:35 +0900, HAMADA Naoki wrote: > gram writes: > >I was just wondering: if one is creating a config file for a kernel > >that should support multiple 3Com 3C59x NICs, should one have multiple > >vx entries in the config? I have built a kernel with: > > > > device vx0 > > device vx1 > > device vx2 > > > >The resulting kernel does support multiple cards, but I thought that > >it may be possible to use just a single vx entry and still be able to > >support multiple cards. The same question applies to the tx, fxp and > >de drivers. Does anyone know? > > For some historical reasons, the vx driver needs explicit declaration > in the config file to use multiple NICs. This can be fixed quite > easily, I suppose. Shold I? Yes, please go ahead. I made the necessary changes to the NE2000 and Lance drivers long ago, and I had assumed that all other PCI devices already dynamically allocated per device structs as required. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:09:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09266 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:09:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from santorini.odyssey.cs.cmu.edu (hmpierce@SANTORINI.ODYSSEY.CS.CMU.EDU [128.2.185.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09255 for ; Mon, 27 Jul 1998 14:08:56 -0700 (PDT) (envelope-from hmpierce@santorini.odyssey.cs.cmu.edu) Received: from localhost (hmpierce@localhost) by santorini.odyssey.cs.cmu.edu (8.8.7/8.8.7) with SMTP id RAA01697 for ; Mon, 27 Jul 1998 17:08:27 -0400 Date: Mon, 27 Jul 1998 17:08:27 -0400 (EDT) From: "Henry M. Pierce" To: hackers@FreeBSD.ORG Subject: FreeBSD for the Sparc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I am interested in helping with the development effort with the sparc port of FreeBSD with an SS1+ that was recently given to me. I am initially interested in beta testing. However, I have only just joined the mailing list so I am not clear what the status of the sparc port is nor where to get what is available. regards, henry m. pierce ---------------------------------------------- Henry M. Pierce Research Programmer Department of Computer Science Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA email: hmpierce@cs.cmu.edu, hmp@infomagic.com --- Quote for the Millennium: "It seems the most important metric of useful software is not its feature set, but its bug set." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11057 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:17:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11036 for ; Mon, 27 Jul 1998 14:17:31 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA16334 for ; Mon, 27 Jul 1998 23:16:51 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 27 Jul 1998 23:16:51 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG Subject: One for the Bruce filter... Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Jul 1998 23:16:50 +0200 Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA11041 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A thread on BUGTRAQ pointed me to this one. In readv() in /sys/kern/sys_generic.h, there is the following piece of code: auio.uio_resid = 0; for (i = 0; i < uap->iovcnt; i++) { auio.uio_resid += iov->iov_len; if (auio.uio_resid < 0) { error = EINVAL; goto done; } iov++; } However, iov->iov_vlen is a size_t, so it doesn't make sense to check auio.uio_resid for a negative value (unless that's your idea of detecting arithmetic overflow). Since auio.uio_resid is apparently being used as a byte count ("resid" is a wonderfully descriptive name, isn't it?), it should probably be a size_t, not an int. Anyway, the net result is that readv() returns EINVAL when it shouldn't, namely when the sum of the sizes of your data chunks exceeds 2^31 - 1. BTW, struct iovec and struct uio are in /usr/include/sys/uio.h. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:33:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14343 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:33:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14280 for ; Mon, 27 Jul 1998 14:33:08 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA12505; Mon, 27 Jul 1998 14:32:35 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdd10903; Mon Jul 27 14:32:13 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA23572; Mon, 27 Jul 1998 12:08:09 -0700 (MST) From: Terry Lambert Message-Id: <199807271908.MAA23572@usr02.primenet.com> Subject: Re: inetd enhancements To: n@nectar.com (Jacques Vidrine) Date: Mon, 27 Jul 1998 19:08:09 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jacques Vidrine" at Jul 27, 98 12:19:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd like to add some functionality to inetd. The two features > needed are: I like the idea; I'd like more information on the implementation (a 50,000 foot view)... > * binding selected services to a particular interface Do you so this by adding an "interface list" field? > * chroot'ing before exec'ing the service Do you run as other-than-root before you do this? Root can escape a chroot jail because of the way the chroot root vnode is (in my opinion) incorrectly set to NULL instead of the real root for the non-chroot case (fixing this would incidently simplify the namei code). The "ftpd" case is especially vulnerable... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:34:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14564 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:34:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14457 for ; Mon, 27 Jul 1998 14:34:10 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA09798; Mon, 27 Jul 1998 17:33:31 -0400 (EDT) Date: Mon, 27 Jul 1998 17:33:30 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-Reply-To: <199807271745.KAA25470@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, David Wolfskill wrote: > However, as a follow-on to a discussion I was having with someone else > (where I was doing a bunch of whining about the challenges I was having > in "automatically" being able to determine the configuration of a given > FreeBSD box), the random idea came up that *IF* the kernel could stash > away the results of its probing in some way that might be amenable to > access by suitably-privileged processes at times arbitrarily distant > from re-boot (i.e, scannning logs & output of dmesg won't do the job), > this *might* be sufficiently useful to warrant some effort. /var/run/dmesg.boot Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15352 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:38:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from the.oneinsane.net (insane@gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15251 for ; Mon, 27 Jul 1998 14:38:03 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id OAA10406; Mon, 27 Jul 1998 14:37:25 -0700 (PDT) Message-ID: <19980727143725.A10319@oneinsane.net> Date: Mon, 27 Jul 1998 14:37:25 -0700 From: "Ron 'The Insane One' Rosson" To: freebsd-hackers@FreeBSD.ORG Cc: et-users@etinc.com Subject: BPF & ETINC cards Mail-Followup-To: freebsd-hackers@freebsd.org, et-users@etinc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i X-Operating-System: FreeBSD the.oneinsane.net 2.2.6-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The FreeBSD GODS I depend on, ----------Post to ETinc Mailing List---------------------- Quick Question, I have a FreeBSD 2.2.6-STABLE box with an et5025 8bit card for my uplink. I have installed the latest driver to get SNMP support and bpf. Using trafshow from FreeBSD's ports collection I dont see any activity through my link(Yes It is Up). ----------Reply Post from ETinc Mailing List-------------- trafshow doesnt seem to work...seemingly because FreeBSD doesnt support filtering of DL_NULL date types and serial encapsulations are not supported either. ---------------------------------------------------------- Ok, Now with that out of the way, I am no programmer I am an end user who likes Both FreeBSD and my Etinc product. I asking if it is possible for it to become a reality to get this to work. TIA Ron P.S. No flames from either vendor please -- -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:41:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16080 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:41:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15943 for ; Mon, 27 Jul 1998 14:40:41 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA12564; Mon, 27 Jul 1998 14:32:41 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpde10903; Mon Jul 27 14:32:18 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id MAA23379; Mon, 27 Jul 1998 12:01:52 -0700 (MST) From: Terry Lambert Message-Id: <199807271901.MAA23379@usr02.primenet.com> Subject: Re: Odd problem we're seeing here To: karl@mcs.net (Karl Denninger) Date: Mon, 27 Jul 1998 19:01:52 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <19980727095806.05337@mcs.net> from "Karl Denninger" at Jul 27, 98 09:58:06 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I'm seeing an interesting problem here. > > > > > > No you're not. You are seeng a problem I already knew about, > > > and provided a patch for, but the patch was not checked in by > > > anyone (no, not the NFS locking patch; that should be checked > > > in, too, though). > > > > Was this issue ever resolved to your satisfaction? > > Not really. I turned off NVSV3 on the affected machines; that "fixed" it, > but its a hack, not a real fix. I didn't realize you had sent this to the list, Mike, or I would have specifically addressed the previous response. Karl's correct; this is the "workaround" I suggested for the problem, and it's somewhat less than satisfying. It gets around the problem with opportunity locking by simply disabling it. This is less than satisfying because opportunity locking (leases) result in a *serious* performance increase. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16164 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:41:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16026 for ; Mon, 27 Jul 1998 14:41:02 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA12601; Mon, 27 Jul 1998 14:32:43 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdf10903; Mon Jul 27 14:32:23 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA23004; Mon, 27 Jul 1998 11:54:34 -0700 (MST) From: Terry Lambert Message-Id: <199807271854.LAA23004@usr02.primenet.com> Subject: Re: Odd problem we're seeing here To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 18:54:34 +0000 (GMT) Cc: tlambert@primenet.com, karl@mcs.net, hackers@FreeBSD.ORG In-Reply-To: <199807270539.WAA14548@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 10:39:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I'm seeing an interesting problem here. > > > > No you're not. You are seeng a problem I already knew about, > > and provided a patch for, but the patch was not checked in by > > anyone (no, not the NFS locking patch; that should be checked > > in, too, though). > > Was this issue ever resolved to your satisfaction? Which issue: the VOP_LEASE issue, or the NFS locking issue? The answer in both cases is "no", but I can't tell from context which one you are talking about. For the lease issue to truly get fixed requires killing vn_rdwr() and calling vn_read() and vn_write(), as appropriate. Then calling VOP_LEASE with the correct arguments on the correct side of a VOP_LOCK. For the NFS locking, I've basically given up on convincing people with the control of the code that moving the lock list to the vnode instead of the inode, and then going veto-based is the way to go. It doesn't seem to matter what I (or John Heidemann) say in this regard, it falls on deaf ears. What I will probably end up doing is, once I finish the stuff at work that I promised myself I'd finish before uncrating my Sun SPARC box, uncrate the box, fully implement the locking so that it interoperates with SunOS, and then put the whole thing up as a mega-patch on a "take it or leave it" basis. PS: It's not necessary to quote the whole article back to me; I save copies of these things for myself. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17263 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:48:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17176 for ; Mon, 27 Jul 1998 14:47:27 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0z0v6S-0001Lq-00; Mon, 27 Jul 1998 16:46:44 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199807271908.MAA23572@usr02.primenet.com> References: <199807271908.MAA23572@usr02.primenet.com> Subject: Re: inetd enhancements To: Terry Lambert cc: hackers@FreeBSD.ORG Date: Mon, 27 Jul 1998 16:46:44 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 27 July 1998 at 19:08, Terry Lambert wrote: > I like the idea; I'd like more information on the implementation > (a 50,000 foot view)... > > * binding selected services to a particular interface > Do you so this by adding an "interface list" field? Yes, where the list length ``n'' is constrained as: 0 <= n <= 1 :-) Seriously, this shouldn't be tough to add if it is deemed useful. You can currently accomplish this with multiple definitions of the service, each with a different interface specified. > > * chroot'ing before exec'ing the service > Do you run as other-than-root before you do this? Yes. I chroot(), then chdir("/"). setusercontext(), sigaction(), and execv() are called afterward. > Root can escape > a chroot jail because of the way the chroot root vnode is (in my > opinion) incorrectly set to NULL instead of the real root for the > non-chroot case (fixing this would incidently simplify the namei code). > > The "ftpd" case is especially vulnerable... I don't follow. Could you give an example scenario of an exploit? - -- Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNbz1RDeRhT8JRySpAQGoTQP/e1yzs5UdlVBYyXq3Smh/W1jW8wVWl+2H sv3dZ7rhxNUzabIoYiK34VdBkMWnNXlGM4bmlL/0Yl4JYHy1Lkpyi//zeLHDAOKd dYx5kSqA5yNqgF1LW/cMMElA3+0xgZgHkSIi9guMi4VHnZarUOb1ryKTFrAl0yry cbIebEsL3CM= =F8Du -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17483 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:49:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (gyndine-62.mdm.mke.execpc.com [169.207.83.62]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA17372 for ; Mon, 27 Jul 1998 14:48:40 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199807272148.OAA17372@hub.freebsd.org> Received: (qmail 18998 invoked from network); 27 Jul 1998 16:50:24 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 27 Jul 1998 16:50:24 -0500 To: David Wolfskill cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-reply-to: Your message of "Mon, 27 Jul 1998 10:45:50 PDT." <199807271745.KAA25470@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 16:50:23 -0500 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG } >> Could someone tell me how you can check the amount of RAM both available } >> and in use at a given time on FreeBSD 2.2.6 ? } } >Try } } >dmesg | more } } >soon after a reboot. Should tell you how much RAM was found on the way up. } } Well, re-booting a production server that's been up for several months } just to find out how much real memory the kernel saw may not be a viable } option. :-} Granted, someone else suggested "top", which is fine for } this particular resource.... Others have pointed out /var/run/dmesg.boot, which will work for what you're looking for, but I think too many people are overlooking the usefulness of sysctl for getting at information like this: [503] hamilton@woodstock hamilton$ sysctl hw.physmem hw.physmem: 65572864 -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 14:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19606 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 14:58:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19475 for ; Mon, 27 Jul 1998 14:57:36 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA01102; Mon, 27 Jul 1998 16:56:46 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA10218; Mon, 27 Jul 1998 16:56:46 -0500 (CDT) Message-ID: <19980727165646.20437@mcs.net> Date: Mon, 27 Jul 1998 16:56:46 -0500 From: Karl Denninger To: Terry Lambert Cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: Odd problem we're seeing here References: <19980727095806.05337@mcs.net> <199807271901.MAA23379@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807271901.MAA23379@usr02.primenet.com>; from Terry Lambert on Mon, Jul 27, 1998 at 07:01:52PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 07:01:52PM +0000, Terry Lambert wrote: > > > > > I'm seeing an interesting problem here. > > > > > > > > No you're not. You are seeng a problem I already knew about, > > > > and provided a patch for, but the patch was not checked in by > > > > anyone (no, not the NFS locking patch; that should be checked > > > > in, too, though). > > > > > > Was this issue ever resolved to your satisfaction? > > > > Not really. I turned off NVSV3 on the affected machines; that "fixed" it, > > but its a hack, not a real fix. > > I didn't realize you had sent this to the list, Mike, or I would have > specifically addressed the previous response. > > Karl's correct; this is the "workaround" I suggested for the problem, > and it's somewhat less than satisfying. It gets around the problem > with opportunity locking by simply disabling it. This is less than > satisfying because opportunity locking (leases) result in a *serious* > performance increase. > > > Terry Lambert > terry@lambert.org Yeah, well, it led to a pretty serious performance issue (which we were able to fix through other means). We run a curious mixture of V2 and V3 now, mostly dictated by whether or not this problem is "real" in a given situation and use. I'd LOVE to see this fixed, but serious attention to this and the MMAP problems appears to be one of those things that just isn't on people's priority lists. If/when I get a chunk of free time I'll probably dig into it, but that's not likely to happen in the immediate future. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 15:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20437 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 15:01:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20347; Mon, 27 Jul 1998 15:01:03 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA12491; Mon, 27 Jul 1998 14:32:33 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdg10903; Mon Jul 27 14:32:27 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA23030; Mon, 27 Jul 1998 11:56:04 -0700 (MST) From: Terry Lambert Message-Id: <199807271856.LAA23030@usr02.primenet.com> Subject: Re: temporary FreeBSD token-ring list. To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 18:56:03 +0000 (GMT) Cc: tlambert@primenet.com, winter@jurai.net, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199807270604.XAA14756@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 11:04:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As a point of interest, MITRE announced a working NetBEUI for > > FreeBSD a number of moths ago on the SAMBA list. > > > > To do this, they must have implemented the 802.3 LLC. > > > > Someone should follow up with MITRE. > > Did they? This would be extremely useful. On or about FreeBSD 2.2.4. Yes, it would be extremely useful if someone would followup with them. Someone with core team credentials would be best. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 15:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22681 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 15:16:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22594 for ; Mon, 27 Jul 1998 15:15:58 -0700 (PDT) (envelope-from moncrg@bt340707.res.ray.com) Received: (mailer@localhost) by gatekeeper.ray.com (8.8.7/8.8.7) id SAA26207 for ; Mon, 27 Jul 1998 18:00:52 -0400 Received: from bt340707.res.ray.com/138.125.142.35() by gatekeeper.ray.com id sma.901560897.008515; Mon Jul 27 13:34:57 1998 Received: from bt340707.res.ray.com (localhost [127.0.0.1]) by bt340707.res.ray.com (8.8.7/8.8.7) with ESMTP id NAA17542 for ; Mon, 27 Jul 1998 13:28:59 -0500 (EST) (envelope-from moncrg@bt340707.res.ray.com) Message-ID: <35BCC6EA.179D01F@bt340707.res.ray.com> Date: Mon, 27 Jul 1998 13:28:58 -0500 From: "Gregory D. Moncreaff" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: how to make buildworld as ordinary user with OBJRIR/MAKEOBJDIRPREFIX? Content-Type: multipart/alternative; boundary="------------2758CCCC0F257077B4928745" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------2758CCCC0F257077B4928745 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit the problem is that it wants to install the bootstrap/tools as bin.bin.555, etc, which an unpriveledged user can't do.... is there a way to override the tools BINOWN, BINGRP for buildworld in a way that doesn't muck it up for installworld? can MK_FLAGS be used for this? MK_FLAGS += BINOWN=`whoami` BINGRP=`whoami` -- Greg Moncreaff, Senior Software Engineer, CNS/ATN Raytheon Systems Company, Mailstop 2.2.2507 Raytheon 1001 Boston Post Road East, Marlboro, MA 01752 USA 508.490.2048, 508.490.2086 fax -- Disclaimer: "this is my personal opinion and not that of my employer" --------------2758CCCC0F257077B4928745 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit the problem is that it wants to install the bootstrap/tools as bin.bin.555, etc, which an
unpriveledged user can't do....

is there a way to override the tools BINOWN, BINGRP for buildworld in a
way that doesn't muck it up for installworld?

can MK_FLAGS be used for this?
MK_FLAGS += BINOWN=`whoami` BINGRP=`whoami` 

-- 
                Greg Moncreaff, Senior Software Engineer, CNS/ATN
                Raytheon Systems Company, Mailstop 2.2.2507
Raytheon        1001 Boston Post Road East, Marlboro, MA 01752 USA
                508.490.2048, 508.490.2086 fax
--
Disclaimer: "this is my personal opinion and not that of my employer"
  --------------2758CCCC0F257077B4928745-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 16:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04417 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 16:18:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04359 for ; Mon, 27 Jul 1998 16:17:35 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA05568; Mon, 27 Jul 1998 16:17:04 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd005451; Mon Jul 27 16:16:53 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA04693; Mon, 27 Jul 1998 16:16:51 -0700 (MST) From: Terry Lambert Message-Id: <199807272316.QAA04693@usr05.primenet.com> Subject: Re: inetd enhancements To: n@nectar.com (Jacques Vidrine) Date: Mon, 27 Jul 1998 23:16:51 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: from "Jacques Vidrine" at Jul 27, 98 04:46:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Root can escape > > a chroot jail because of the way the chroot root vnode is (in my > > opinion) incorrectly set to NULL instead of the real root for the > > non-chroot case (fixing this would incidently simplify the namei code). > > > > The "ftpd" case is especially vulnerable... > > I don't follow. Could you give an example scenario of an exploit? I spared the list my code for doing this, sending it only to the questioner. Thank you, Terry. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 16:23:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05592 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 16:23:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from access.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.141.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05476; Mon, 27 Jul 1998 16:22:26 -0700 (PDT) (envelope-from max_pop@bourbon.sfc.wide.ad.jp) Received: from bourbon ([212.211.24.41]) by access.sfc.wide.ad.jp (8.8.8/3.5Wpl107/15/97) with SMTP id IAA08986; Tue, 28 Jul 1998 08:19:48 +0900 (JST) Date: Tue, 28 Jul 1998 08:19:48 +0900 (JST) Message-Id: <199807272319.IAA08986@access.sfc.wide.ad.jp> From: Masafumi NAKANE To: Mike Smith , Terry Lambert Cc: mike@smith.net.au (Mike Smith), pvernon@purdue.edu, freebsd-hackers@FreeBSD.ORG, max@FreeBSD.ORG Subject: Re: Accessability (was Re: question) X-Mailer: D-Mail v2.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I'm on the road and can't really spend much time on emails at t his point. But, I will be more than happy to help you with this after I get home on 08/09. Since I'm accessing FreeBSD using DOS and screen reader, I'm sure I can be some help. Basically, what Mike suggests will enable the installation using screen reader under dos. What we, as FreeBSD developers, probably should consider is to put -D (or was it -d) in the boot.config of the boot floppy. I will comment on what Terry has written, which is quite important when I get home. Cheers, Max At 24 Jul 17:22 , Mike Smith wrote: > >> > Max; I copied you on this because if anyone knows about how to make this >> > happen, you do. >> > >> > > I want to install 2.2.7 on one of my machines. I have to install it over a >> > > serial port because I am blind and need to read the screen during install. >> > > My speech software runs under dos. Thus, i must install it on my new >> > > machine from my dos box. I'm not sure how to install it on a machine im not >> > > physically at. >> > >> > FreeBSD supports using the first serial port on your system as the >> > console port. If you don't have a video card in the system, it will >> > use the serial port instead. >> > >> > Then you simply connect the serial port from the FreeBSD system to your >> > DOS system, and use a DOS terminal program to provide you with a >> > console. >> >> It seems that it would be a good idea to provide some way to invoke >> this with as little work as possible from a boot floppy. > >There is an option in the bootstrap to probe the keyboard; I'm not sure >if it's the default or not. If the keyboard's not present, it will use >the serial port. > >> It would also be a good idea to start thinking in terms of accessibility >> functions for the console, the keyboard driver, and Free-B.S.D. in >> general. > >Thinking is easy; finding a developer interested in taking on the work >less so. > >Your suggestions are pretty good though (if unoriginal 8) > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 16:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05936 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 16:24:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05577; Mon, 27 Jul 1998 16:22:56 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807272322.QAA05577@hub.freebsd.org> Subject: Re: I/O error on connection from hub.FreeBSD.ORG, anyone else? In-Reply-To: <19980727161311.A17629@ucb.crimea.ua> from Ruslan Ermilov at "Jul 27, 98 04:13:11 pm" To: ru@ucb.crimea.ua (Ruslan Ermilov) Date: Mon, 27 Jul 1998 16:22:53 -0700 (PDT) Cc: hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > Hi! > > Since middle of July my log files are full of messages like these: > > Jul 27 00:16:17 relay sendmail[6631]: AAA06631: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG > Jul 27 00:24:13 relay sendmail[6647]: AAA06647: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG > > What is going on? The only server I see in such messages is hub.freebsd.org. > Are some timeout values were set too small recently on hub.FreeBSD.ORG? could be. of course one might say that connectivity to .ua is too poor ;( a mailertable entry for your domain or all of .ua might solve this problem. with whom do you have good connectivity that would be willing to relay mail for you? jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 17:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15016 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 17:04:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14918 for ; Mon, 27 Jul 1998 17:03:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02225; Mon, 27 Jul 1998 17:01:55 -0700 (PDT) Message-Id: <199807280001.RAA02225@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@FreeBSD.ORG cc: tech-net@netbsd.org Subject: Macronix MX98713 support for 'de'? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 17:01:55 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This posting seeks to locate developers interested in adding support for the Macronix MX98713 and adapters based on this part to the 'de' driver. Such work would be of immediate benefit to both the FreeBSD and NetBSD groups. The Macronix MX98713 is a clone of the Digital DC2114x 'tulip' family. Documentation for these parts is available from Macronix' website (www.macronix.com). Support for these parts already exists in the Linux tulip driver. Cards featuring the MX98713 typically retail around US$35.oo or so in one-off quantities, making them an extremely cheap 100bTX solution for PCI systems. We have already attempted to contact Matt Thomas (the maintainer of this driver), with no response. This may mean that he's not interested, or just too busy, and this solicitation is not meant as a snub, but rather just a widening of the net. If you're interested in working on this, please contact me off these lists to reduce followup noise. You may also want to try contacting Matt (matt@3am-software.com) to coordinate your work. Regards, -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 17:05:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15363 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 17:05:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15109 for ; Mon, 27 Jul 1998 17:04:18 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-146.camalott.com [208.229.74.146]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id TAA12632; Mon, 27 Jul 1998 19:04:45 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id TAA18234; Mon, 27 Jul 1998 19:03:33 -0500 (CDT) (envelope-from joelh) Date: Mon, 27 Jul 1998 19:03:33 -0500 (CDT) Message-Id: <199807280003.TAA18234@detlev.UUCP> To: joelh@gnu.org CC: dhw@whistle.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199807272038.PAA17808@detlev.UUCP> (message from Joel Ray Holveck on Mon, 27 Jul 1998 15:38:04 -0500 (CDT)) Subject: Re: Checking RAM From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807271745.KAA25470@pau-amma.whistle.com> <199807272038.PAA17808@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> Could someone tell me how you can check the amount of RAM both available >>>> and in use at a given time on FreeBSD 2.2.6 ? > I suppose you could add to your own /etc/local: > dmesg | egrep '(real|avail) memory = ' > /var/log/mem > More generally, you may prefer > dmesg > /var/log/dmesg.boot Oh, I forgot to also add that 'sysctl hw.physmem' (and other items under 'sysctl hw') may be useful. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 17:09:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16411 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 17:09:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13305; Mon, 27 Jul 1998 16:57:28 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807272357.QAA13305@hub.freebsd.org> Subject: Re: I/O error on connection from hub.FreeBSD.ORG, anyone else? In-Reply-To: <199807272322.QAA05577@hub.freebsd.org> from "Jonathan M. Bresler" at "Jul 27, 98 04:22:53 pm" To: jmb@hub.freebsd.org (Jonathan M. Bresler) Date: Mon, 27 Jul 1998 16:57:20 -0700 (PDT) Cc: ru@ucb.crimea.ua, hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan M. Bresler wrote: > Ruslan Ermilov wrote: > > Hi! > > > > Since middle of July my log files are full of messages like these: > > > > Jul 27 00:16:17 relay sendmail[6631]: AAA06631: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG > > Jul 27 00:24:13 relay sendmail[6647]: AAA06647: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG > > > > What is going on? The only server I see in such messages is hub.freebsd.org. > > Are some timeout values were set too small recently on hub.FreeBSD.ORG? > > could be. of course one might say that connectivity to > .ua is too poor ;( a mailertable entry for your domain > or all of .ua might solve this problem. > > with whom do you have good connectivity that would be willing > to relay mail for you? its even worse than that: traceroutes to your site vanish from hub: traceroute to relay.ucb.crimea.ua (194.93.177.113), 30 hops max, 40 byte packets 1 gate-free.cdrom.com (204.216.27.17) 1.546 ms 1.329 ms 1.375 ms 2 R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1) 6.597 ms 12.058 ms 6.597 ms 3 * T3-GW1.F0.US.CRL.NET (165.113.55.1) 29.034 ms 4.775 ms 4 T3-GW1.F0.US.CRL.NET (165.113.55.1) 5.560 ms 10.731 ms 4.525 ms 5 * * * 6 * * * from the east coast of the US: traceroute to relay.ucb.crimea.ua (194.93.177.113), 30 hops max, 40 byte packets 1 ma4700a-gw (170.209.32.1) 1.129 ms 0.834 ms 0.801 ms 2 Falls-Church5.VA.ALTER.NET (137.39.238.121) 3.761 ms 3.861 ms 3.81 ms 3 Hssi10-0.CR1.DCA1.Alter.Net (137.39.31.58) 3.281 ms 3.278 ms 3.326 ms 4 411.atm11-0-0.br1.dca1.alter.net (137.39.13.201) 3.608 ms 3.753 ms 3.618 ms 5 core5-hssi5-0.Washington.mci.net (206.157.77.25) 23.728 ms 29.807 ms 5.701 ms 6 core.Boston.mci.net (204.70.4.137) 58.849 ms 187.643 ms 24.627 ms 7 mix1-fddi-0.Boston.mci.net (204.70.2.46) 28.455 ms 26.668 ms 224.137 ms 8 ukrainian-telecom.Boston.mci.net (204.189.128.158) 174.848 ms 179.664 ms 176.466 ms 9 GU-UTC-2048k.gu.net (194.93.170.178) 190.26 ms 185.018 ms 186.882 ms 10 m3-t15.gu.net (194.93.191.37) 193.41 ms 179.178 ms 187.524 ms 11 sport-e0.gu.net (194.93.191.10) 201.157 ms 217.518 ms 202.618 ms 12 cris-gu.gu.net (194.93.170.13) 3932.41 ms 3922.95 ms 2280.36 ms 13 monk.cris.net (194.93.176.70) 656.794 ms 1648.45 ms 2382.25 ms 14 * * * 15 * * * telnet telnet 194.93.177.113 25 works but is very slow. could be that we cant transfer the mail within the timeout period. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 17:15:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17744 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 17:15:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tarsier.ca.sandia.gov (tarsier.ca.sandia.gov [146.246.246.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17574 for ; Mon, 27 Jul 1998 17:14:53 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Received: from tarsier.ca.sandia.gov (localhost [127.0.0.1]) by tarsier.ca.sandia.gov (8.8.8/8.8.8) with ESMTP id RAA08854 for ; Mon, 27 Jul 1998 17:15:09 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Message-Id: <199807280015.RAA08854@tarsier.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: pci_map_mem() failing.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 17:15:09 -0700 From: "Chris Csanady" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I am working on a device driver, and so far have not been able to get this seemingly simple aspect of it to work. I am getting the following error: pci_map_mem failed: bad memory type=0xfffff004 It seems that the pci code does not know how to handle 64bit cards. If I yank the lines in pci.c that check the memory type, it produces no errors, although the mapping still does not work. What am I missing here? This is on a 2.2.6 box. Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 17:31:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21976 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 17:31:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agustina.kjsl.com (Agustina.KJSL.COM [198.137.202.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21910 for ; Mon, 27 Jul 1998 17:30:52 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from uucp@localhost) by agustina.kjsl.com (8.8.7/8.8.8/rchk1.19) with UUCP id RAA21783; Mon, 27 Jul 1998 17:26:34 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.8/rchk1.19) id RAA18750; Mon, 27 Jul 1998 17:08:43 -0700 (PDT) (envelope-from fmc) Message-Id: <199807280008.RAA18750@daemonweed.reanimators.org> To: Robert Swindells Cc: mike@smith.net.au, hackers@FreeBSD.ORG, faber@isi.edu Subject: Re: AMD PCNet/FAST cards; suppliers? References: <199807271201.FAA03886@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 27 Jul 1998 17:08:42 -0700 In-Reply-To: Robert Swindells's message of Mon, 27 Jul 1998 05:01:10 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Swindells wrote: > I may have spoken too soon about the driver in stable being OK. > > There was a change committed on July 20 which looks like it will break > probing of the PCnet-II chip. I seem to have run afoul of another part of this change. I'm not sure if it's due to hardware misconfiguration on my part, but the way it behaves is bothersome. The system is an HP Vectra XM Series 4 5/133 with the "integrated LAN adapter", which looks like a PCI card hidden on the backside of the bus riser where it's hard to look at. I haven't had it out to look at it, and FreeBSD-previous (maybe 2.2.2, definitely 2.2.5-RELEASE and -stable since) just probed and attached it as lnc1 so I never had to think about it before. When I did up a custom kernel configuration for this PC, I commented stuff out of GENERIC for the hardware I didn't have, but left in the "device lnc0"... line (with addresses not matching my card) because I figured that without that the lnc code wouldn't be in the resulting kernel. Saturday morning I did the cvsup+build+install drill (for -stable), and after rebooting with the new kernel I noticed console messages about not being able to resolve names from /etc/exports. "netstat -in" showed no Ethernet interfaces, "dmesg | grep lnc" got me lnc1 rev 22 int a irq 11 on pci0:8:0 (and looking at the entire dmesg output showed nothing amiss) and "ifconfig lnc1" got me ifconfig: interface lnc1 does not exist Saturday evening I scattered debug printf()s around to figure out what was going on, and worked out that lnc_attach_ne2100_pci() was losing due to the new test for sc->nic.ic == PCnet_PCI. So I added the appropriate "device lnc1" line to the config file and rebuilt the kernel, and that worked OK. The annoyances are (a) that it probes and finds the card as a PCI device, then silently discards the info; and (b) the probe message doesn't give you the base I/O address so you know how to fill in the device information (I got that from my debug printf()s). And (c) I've gone from having the miracle of plug-and-play working on my desktop to having to know another I/O address and IRQ, for a card that doesn't make them obvious or let me set them so far as I've noticed. For all I know there is some way to tell the card not to do the ISA emulation, but that's been pushed to the copious free time list so I may not find out soon. Poking through the Vectra's BIOS setup, there is a way to disable the "Integrated LAN Adapter" but that's the only relevant setting I could find. -Frank McConnell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 18:18:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01342 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 18:18:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01329 for ; Mon, 27 Jul 1998 18:18:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02516; Mon, 27 Jul 1998 18:14:53 -0700 (PDT) Message-Id: <199807280114.SAA02516@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Frank McConnell cc: Robert Swindells , mike@smith.net.au, hackers@FreeBSD.ORG, faber@isi.edu Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "27 Jul 1998 17:08:42 PDT." <199807280008.RAA18750@daemonweed.reanimators.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 18:14:52 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Robert Swindells wrote: > > I may have spoken too soon about the driver in stable being OK. > > > > There was a change committed on July 20 which looks like it will break > > probing of the PCnet-II chip. > > I seem to have run afoul of another part of this change. I'm not sure > if it's due to hardware misconfiguration on my part, but the way it > behaves is bothersome. No, you're correct, and I slipped on this. The ID that is tested for is the generic ID for the 79c971, not a Hitachi-specific ID, and I didn't realise that. We do need a better probe for the Hitachi case. > For all I know there is some way to tell the card not to do the ISA > emulation, but that's been pushed to the copious free time list so I > may not find out soon. No. ISA and PCI share an I/O space, but that's about it. I'm sorry; this is breakage in both 2.2.7 and -current, and we're going to need a better way of identifying the problem cases like the Hitachi (or a better workaround). 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 18:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06954 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 18:50:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from send1c.yahoomail.com (send1c.yahoomail.com [205.180.60.38]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA06924 for ; Mon, 27 Jul 1998 18:50:31 -0700 (PDT) (envelope-from giffunip@yahoo.com) Message-ID: <19980728015215.3041.rocketmail@send1c.yahoomail.com> Received: from [168.176.3.40] by send1c; Mon, 27 Jul 1998 18:52:15 PDT Date: Mon, 27 Jul 1998 18:52:15 -0700 (PDT) From: "Pedro F. Giffuni" Reply-To: giffunip@asme.org Subject: Re: inetd enhancements To: hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps xinetd should be added to the base distribution .... when I finish understanding how to use it :-). cheers, Pedro. == --- FreeBSD: The Power to Serve ! http://www.FreeBSD.org _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 19:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10352 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 19:11:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10347 for ; Mon, 27 Jul 1998 19:11:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA02814; Mon, 27 Jul 1998 19:08:59 -0700 (PDT) Message-Id: <199807280208.TAA02814@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG, tech-net@netbsd.org Subject: Re: Macronix MX98713 support for 'de'? In-reply-to: Your message of "Mon, 27 Jul 1998 17:01:55 PDT." <199807280001.RAA02225@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 19:08:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just minutes after posting this, I received a reply from Matt Thomas indicating that the work in question has largely been done. My apologies for the overlap. Hardware is on it's way to Matt; we look forward to hearing his results. > This posting seeks to locate developers interested in adding support > for the Macronix MX98713 and adapters based on this part to the 'de' > driver. Such work would be of immediate benefit to both the FreeBSD > and NetBSD groups. > > The Macronix MX98713 is a clone of the Digital DC2114x 'tulip' family. > Documentation for these parts is available from Macronix' website > (www.macronix.com). Support for these parts already exists in the Linux > tulip driver. Cards featuring the MX98713 typically retail around > US$35.oo or so in one-off quantities, making them an extremely cheap > 100bTX solution for PCI systems. > > We have already attempted to contact Matt Thomas (the maintainer of this > driver), with no response. This may mean that he's not interested, or > just too busy, and this solicitation is not meant as a snub, but rather > just a widening of the net. > > If you're interested in working on this, please contact me off these > lists to reduce followup noise. You may also want to try contacting > Matt (matt@3am-software.com) to coordinate your work. > > Regards, > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 22:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05161 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 22:33:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ilium.troy.msen.com (ilium.troy.msen.com [148.59.4.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA05148 for ; Mon, 27 Jul 1998 22:33:41 -0700 (PDT) (envelope-from wayne@ilium.troy.msen.com) Received: by ilium.troy.msen.com (Smail3.1.28.1 #1) id m0z12NL-0003cUC; Tue, 28 Jul 98 01:32 EDT Message-Id: To: freebsd-hackers@FreeBSD.ORG Subject: BusTek/BusLogic/Mylex driver From: wayne@msen.com Date: Tue, 28 Jul 98 01:32:39 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have number of machines running BSD/OS with likely every model of BusLogic controller ever made. We've started to move services to FreeBSD and I finally took a good, long look at the driver code for these cards. It's highly incomplete (no support for Sync, Fast, Ultra, etc.) In another life, I'd offer to spend the time writing a real driver but that's not an option for a while. While it would be fairly easy to do some upgrades, real performance will require quite a bit of work. Is there ANY active development going on for this product line or should I just go out and buy Adaptec cards? There's no way I'm going to run a news transit server that lives in the freenix top 300 in async SCSI mode! /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 22:59:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07698 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 22:59:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA07692 for ; Mon, 27 Jul 1998 22:59:20 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 828 invoked from network); 28 Jul 1998 05:58:41 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 28 Jul 1998 05:58:41 -0000 Date: Mon, 27 Jul 1998 22:58:41 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: wayne@msen.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Get DPT's or Adaptec's. Development of the Buslogic line seems to have died. Given adaptec's new stance towards free OS's, and Mylex's closed-door policy, I can only imagine that the Adaptec drivers will continue to improve. On Tue, 28 Jul 1998 wayne@msen.com wrote: > > We have number of machines running BSD/OS with likely every model of > BusLogic controller ever made. We've started to move services to > FreeBSD and I finally took a good, long look at the driver code for > these cards. It's highly incomplete (no support for Sync, Fast, Ultra, > etc.) In another life, I'd offer to spend the time writing a real > driver but that's not an option for a while. While it would be fairly > easy to do some upgrades, real performance will require quite a bit > of work. > > Is there ANY active development going on for this product line or > should I just go out and buy Adaptec cards? There's no way I'm going > to run a news transit server that lives in the freenix top 300 in async > SCSI mode! > > /\/\ \/\/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 27 23:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13679 for freebsd-hackers-outgoing; Mon, 27 Jul 1998 23:35:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles301.castles.com [208.214.167.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13673 for ; Mon, 27 Jul 1998 23:35:45 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA01210; Mon, 27 Jul 1998 23:34:45 -0700 (PDT) Message-Id: <199807280634.XAA01210@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: wayne@msen.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-reply-to: Your message of "Tue, 28 Jul 1998 01:32:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 23:34:44 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We have number of machines running BSD/OS with likely every model of > BusLogic controller ever made. We've started to move services to > FreeBSD and I finally took a good, long look at the driver code for > these cards. It's highly incomplete (no support for Sync, Fast, Ultra, > etc.) In another life, I'd offer to spend the time writing a real > driver but that's not an option for a while. While it would be fairly > easy to do some upgrades, real performance will require quite a bit > of work. > > Is there ANY active development going on for this product line or > should I just go out and buy Adaptec cards? There's no way I'm going > to run a news transit server that lives in the freenix top 300 in async > SCSI mode! See ftp.freebsd.org:/pub/FreeBSD/cam/README, and note the snapshot releases in that directory. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 00:23:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21082 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 00:23:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21070 for ; Tue, 28 Jul 1998 00:23:47 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA18827; Tue, 28 Jul 1998 00:13:39 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdu18825; Tue Jul 28 07:13:33 1998 Date: Tue, 28 Jul 1998 00:13:31 -0700 (PDT) From: Julian Elischer To: wayne@msen.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the buslogic cards that conform to the first buslogic interface, e.g. 946C 742, 747, 542, do all that transparently.. (sync etc.) The newest cards which conform to their new interface are only supported by the new CAM layer.. julian On Tue, 28 Jul 1998 wayne@msen.com wrote: > > We have number of machines running BSD/OS with likely every model of > BusLogic controller ever made. We've started to move services to > FreeBSD and I finally took a good, long look at the driver code for > these cards. It's highly incomplete (no support for Sync, Fast, Ultra, > etc.) In another life, I'd offer to spend the time writing a real > driver but that's not an option for a while. While it would be fairly > easy to do some upgrades, real performance will require quite a bit > of work. > > Is there ANY active development going on for this product line or > should I just go out and buy Adaptec cards? There's no way I'm going > to run a news transit server that lives in the freenix top 300 in async > SCSI mode! > > /\/\ \/\/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 03:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15702 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 03:29:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13597; Tue, 28 Jul 1998 03:16:48 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id NAA00929; Tue, 28 Jul 1998 13:15:45 +0300 (EEST) (envelope-from ru) Message-ID: <19980728131545.A698@ucb.crimea.ua> Date: Tue, 28 Jul 1998 13:15:45 +0300 From: Ruslan Ermilov To: "Jonathan M. Bresler" Cc: hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG Subject: Re: I/O error on connection from hub.FreeBSD.ORG, anyone else? Mail-Followup-To: "Jonathan M. Bresler" , hackers@FreeBSD.ORG, postmaster@FreeBSD.ORG References: <199807272322.QAA05577@hub.freebsd.org> <199807272357.QAA13305@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807272357.QAA13305@hub.freebsd.org>; from Jonathan M. Bresler on Mon, Jul 27, 1998 at 04:57:20PM -0700 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Please help me! On Mon, Jul 27, 1998 at 04:57:20PM -0700, Jonathan M. Bresler wrote: > > its even worse than that: traceroutes to your site vanish > > > from the east coast of the US: > > traceroute to relay.ucb.crimea.ua (194.93.177.113), 30 hops max, 40 byte packets > 1 ma4700a-gw (170.209.32.1) 1.129 ms 0.834 ms 0.801 ms [...] > 12 cris-gu.gu.net (194.93.170.13) 3932.41 ms 3922.95 ms 2280.36 ms > 13 monk.cris.net (194.93.176.70) 656.794 ms 1648.45 ms 2382.25 ms > 14 * * * > 15 * * * This is due to firewall restrictions on my site - port greater than 40000 will make traceroute happy. traceroute to hub.freebsd.org (204.216.27.18), 30 hops max, 40 byte packets 1 ferrix (194.93.177.116) 0.878 ms 2 Simferopol-GW-1.CRIS.NET (194.93.177.1) 133.089 ms 3 crisco.cris.net (194.93.176.82) 132.407 ms 4 gu-cris.gu.net (194.93.170.14) 1204.339 ms 5 krysa-e0.gu.net (194.93.191.9) 948.205 ms 6 t15-m3.gu.net (194.93.191.38) 911.884 ms 7 UTC-GU-2048k.gu.net (194.93.170.177) 979.346 ms 8 mix-serial3-3.Boston.mci.net (204.189.128.157) 972.897 ms 9 core-fddi-0.Boston.mci.net (204.70.2.33) 1424.625 ms 10 core2.WestOrange.mci.net (204.70.4.185) 1295.855 ms 11 sprint2-nap.WestOrange.mci.net (204.70.1.50) 1248.639 ms 12 ny-nap.crl.com (192.157.69.56) 1108.558 ms 13 lga-nynap.C.us.crl.net (165.113.50.206) 1669.445 ms 14 sfo-vva.x.atm.us.crl.net (165.113.50.65) 2876.427 ms 15 E0-CRL-SFO-02-E0X0.US.CRL.NET (165.113.55.2) 2303.707 ms 16 T1-CDROM-00-EX.US.CRL.NET (165.113.118.2) 2335.674 ms 17 hub.FreeBSD.ORG (204.216.27.18) 1871.115 ms Are you think this is too slow ? 1. my log files are full of messages like: Jul 28 09:50:07 relay sendmail[28588]: JAA28588: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG Jul 28 09:50:47 relay sendmail[28605]: JAA28605: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG Jul 28 09:52:53 relay sendmail[28635]: JAA28635: SYSERR(root): collect: I/O error on connection from hub.FreeBSD.ORG, from=: Connection reset by hub.FreeBSD.ORG 2. I never receive the message directly from hub.FreeBSD.org. Every message from hub.FreeBSD.org goes thru my secondary MX, which is 3-hop away from me (relay1.crimea.ua == spider.cris.net): traceroute to relay1.crimea.ua (194.93.176.65), 30 hops max, 40 byte packets 1 ferrix (194.93.177.116) 1.047 ms 2 Simferopol-GW-1.CRIS.NET (194.93.177.1) 125.015 ms 3 spider.cris.net (194.93.176.65) 132.281 ms Look at this: Received: from spider.cris.net (root@spider.cris.net [194.93.176.65]) by relay.ucb.crimea.ua (8.8.8/8.8.8) with ESMTP id MAA00717 for ; Tue, 28 Jul 1998 12:46:58 +0300 (EEST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by spider.cris.net (8.8.8/8.8.8) with ESMTP id MAA23796 for ; Tue, 28 Jul 1998 12:46:43 +0300 (EET DST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA00610; Tue, 28 Jul 1998 01:36:53 -0700 (PDT) (envelope-from owner-freebsd-questions) 3. I have no such problems with other big-volume mailing lists and servers: Oracle-L: ~~~~~~~~ Received: from smtp4.teleport.com (smtp4.teleport.com [192.108.254.34]) by relay.ucb.crimea.ua (8.8.8/8.8.8) with ESMTP id SAA23362 for ; Mon, 20 Jul 1998 18:34:50 +0300 (EEST) (envelope-from owner-oracle-l@teleport.com) Received: from localhost (daemon@localhost) by smtp4.teleport.com (8.8.7/8.7.3) BugTraq: ~~~~~~~ Received: from brimstone.netspace.org (brimstone.netspace.org [128.148.157.143]) by relay.ucb.crimea.ua (8.8.8/8.8.8) with ESMTP id UAA19412 for ; Mon, 27 Jul 1998 20:14:48 +0300 (EEST) (envelope-from owner-bugtraq@NETSPACE.ORG) Do you have an idea what may be wrong? Could you please execute the following command for me: echo test | sendmail -v ru@ucb.crimea.ua | sendmail ru@ucb.crimea.ua It will send test message, and will show me how it was sent. Thanks and Regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 06:52:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12571 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 06:52:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (exim@[209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA12566 for ; Tue, 28 Jul 1998 06:52:30 -0700 (PDT) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0z1AAR-00020h-00; Tue, 28 Jul 1998 09:51:51 -0400 Date: Tue, 28 Jul 1998 09:51:50 -0400 (EDT) From: To: freebsd-hackers@FreeBSD.ORG Subject: Informix on linux emulation?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see that Informix SE is now available for caldera and suse versions of linux. Somewhere on Informix's web page it seemed they were very sensitive to the glibc version, which may (?) be a problem for us. Has anyone tried running this under the linuxulator? Thanks, David Miller ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 06:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12946 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 06:55:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12937 for ; Tue, 28 Jul 1998 06:55:08 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id JAA06186; Tue, 28 Jul 1998 09:57:02 -0400 (EDT) Date: Tue, 28 Jul 1998 09:57:02 -0400 (EDT) From: Mike To: "Henry M. Pierce" cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Henry M. Pierce wrote: > Hello. I am interested in helping with the development effort > with the sparc port of FreeBSD with an SS1+ that was recently I'd also be interested in helping out in some way... I am not sure of the status of this port or where to find out more information about it, but I'd like to put this Sparc2 to use somehow. :) -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 07:12:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15750 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 07:12:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from santorini.odyssey.cs.cmu.edu (hmpierce@SANTORINI.ODYSSEY.CS.CMU.EDU [128.2.185.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15745 for ; Tue, 28 Jul 1998 07:12:31 -0700 (PDT) (envelope-from hmpierce@santorini.odyssey.cs.cmu.edu) Received: from localhost (hmpierce@localhost) by santorini.odyssey.cs.cmu.edu (8.8.7/8.8.7) with SMTP id KAA02499; Tue, 28 Jul 1998 10:11:52 -0400 Date: Tue, 28 Jul 1998 10:11:52 -0400 (EDT) From: "Henry M. Pierce" To: Mike cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, I found what little there was in the *BSD FAQ by searching through the freebsd-sparc mail archives. Essentially, the original plan was to port to the UltraSparc Only and not to use the NetBSD/OpenBSD code as a base. There was even a lose plan of action contained in the FAQ. Given the project is dead and I don't want to make any claims as to bringing it alive either, all I can say is I am looking into it from the point of view of merging the NetBSD/OpenBSD sparc support into the FreeBSD kernel. A number of issues, including my own abilities and time will play a large factor. -henry ---------------------------------------------- Henry M. Pierce Research Programmer Department of Computer Science Carnegie Mellon University 5000 Forbes Avenue Pittsburgh, PA email: hmpierce@cs.cmu.edu, hmp@infomagic.com --- Quote for the Millennium: "It seems the most important metric of useful software is not its feature set, but its bug set." On Tue, 28 Jul 1998, Mike wrote: > Date: Tue, 28 Jul 1998 09:57:02 -0400 (EDT) > From: Mike > To: "Henry M. Pierce" > Cc: hackers@FreeBSD.ORG > Subject: Re: FreeBSD for the Sparc > > On Mon, 27 Jul 1998, Henry M. Pierce wrote: > > > Hello. I am interested in helping with the development effort > > with the sparc port of FreeBSD with an SS1+ that was recently > > I'd also be interested in helping out in some way... I am not sure of the > status of this port or where to find out more information about it, but > I'd like to put this Sparc2 to use somehow. :) > > -mike > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 07:20:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17244 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 07:20:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17225 for ; Tue, 28 Jul 1998 07:20:36 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id KAA10778; Tue, 28 Jul 1998 10:22:33 -0400 (EDT) Date: Tue, 28 Jul 1998 10:22:33 -0400 (EDT) From: Mike To: "Henry M. Pierce" cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Henry M. Pierce wrote: > I found what little there was in the *BSD FAQ by searching > through the freebsd-sparc mail archives. Essentially, the original [snip] Thanks for the info. I am certainly not the person to bring life to a seemingly dead project, but what you propose is encouraging... playing around with the idea of getting already existing Net/Open BSD functionality (i.e. the ability to install on my Sparc 2! ;) implemented into FreeBSD is a good thing, IMCO. While these older systems are not 'cutting edge', Sparc 2-4 systems are as prvelent in our University as Ultra Sparcs... and why not be able to run FreeBSD on any system one encounters (a noble, albeit time-consuming goal? :)? Thanks again... -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 07:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17747 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 07:23:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAB17738 for ; Tue, 28 Jul 1998 07:23:28 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.7/8.6.9) with SMTP id KAA20752; Tue, 28 Jul 1998 10:35:00 -0400 (EDT) Message-Id: <199807281435.KAA20752@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 28 Jul 1998 10:32:47 -0400 To: "Ron 'The Insane One' Rosson" , freebsd-hackers@FreeBSD.ORG From: Dennis Subject: Re: [et-users] BPF & ETINC cards In-Reply-To: <19980727143725.A10319@oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >trafshow doesnt seem to work...seemingly because FreeBSD >doesnt support filtering of DL_NULL date types and serial >encapsulations are not supported either. > >---------------------------------------------------------- >Ok, > Now with that out of the way, I am no programmer I am an >end user who likes Both FreeBSD and my Etinc product. I >asking if it is possible for it to become a reality to get >this to work. >TIA >Ron > >P.S. No flames from either vendor please Whats your definition of a flame. Of course it can be fixed, but probably neither of us care enough to fix it. Its probably quite simply, but ET, as policy, doesn't repair OS "deflugalties" because we'd never get anything done if we did. There is no good reason why a NULL header should affect protocol filtering. Because our driver is multiprotocol and can be configured on the fly, its difficult to assign a specific encapsulation because it can change. however, if the serial encaps were supported (ie, frame relay, ppp and cisco hdlc), we could set these dynamically with a little work. Since they are not supported now (except maybe ppp), it makes little sense to use anything other than NULL Dennis > >-- >-------------------------------------------------------- >Ron Rosson ... and a UNIX user said ... >The InSaNe One rm -rf * >insane@oneinsane.net and all was null and void >-------------------------------------------------------- >It's so nice to be insane, nobody asks you to explain. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 07:32:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19450 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 07:32:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19428 for ; Tue, 28 Jul 1998 07:31:54 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA25929; Tue, 28 Jul 1998 16:25:03 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id IAA02170; Tue, 28 Jul 1998 08:24:19 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807280624.IAA02170@semyam.dinoco.de> To: David Wolfskill cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Subject: Re: Checking RAM In-reply-to: Your message of "Mon, 27 Jul 1998 11:42:01 PDT." <199807271842.LAA25740@pau-amma.whistle.com> Date: Tue, 28 Jul 1998 08:24:18 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For example, information about disk partitioning would seem to be > necessary, as well as interpreting the "dmesg" output so someone could > Please recall that the intended purpose is to be able to reconstruct the > environment, assuming that (for whatever reason(s)) access to the I had no problem using disklabel and fdisk to document this informa- tion while the system was up. That I printed out and keep it with my systems documentation. The remaining questions others have already answered. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 07:58:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23415 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 07:58:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from the.oneinsane.net (insane@gw.oneinsane.net [207.113.133.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23410 for ; Tue, 28 Jul 1998 07:58:55 -0700 (PDT) (envelope-from insane@the.oneinsane.net) Received: (from insane@localhost) by the.oneinsane.net (8.9.0/8.9.0) id HAA16980; Tue, 28 Jul 1998 07:58:20 -0700 (PDT) Message-ID: <19980728075820.A16948@oneinsane.net> Date: Tue, 28 Jul 1998 07:58:20 -0700 From: "Ron 'The Insane One' Rosson" To: et-users@etinc.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [et-users] BPF & FreeBSD Mail-Followup-To: et-users@etinc.com, freebsd-hackers@freebsd.org References: <199807281421.KAA20691@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807281421.KAA20691@etinc.com>; from Dennis on Tue, Jul 28, 1998 at 10:18:51AM -0400 X-Operating-System: FreeBSD the.oneinsane.net 2.2.6-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis, My apologies for missing the proper context. Do you know of a prgram that runs under FreeBSD that will let me watch the traafic like trafshow. This is a great thing to have when you are trying to tighten security on your box. any assistance in this would be awesome. TTYL Ron On Tue, Jul 28, 1998 at 10:18:51AM -0400, Dennis wrote: > At 10:41 AM 7/27/98 -0700, you wrote: > >Dennis had mentioned inthe past that the bpf will not work > >with the etinc card. Well since FreeBSD source code is available > >and the code is not for the etinc cards. Is anyone looking > >at changing it from one side of hte fence to the other on making > >it so it will work. Or if someone on the developer of the driver give me > >a good cut and paste of where you think the code needs to be modified > >would be nice. I really miss my bpf . > > The game of Telephone continues. > > I NEVER said that bpf didnt work, only that protocol filtering and trafshow > didnt work. TCPDUMP works fine, which indicated that the driver is working > properly. Apprarently DLT_NULL, which is required for non-supported serial > encapsulations, caused filtering and trafshow to not work. > > Dennis > > > >TIA > >Ron > > > >-- > >-------------------------------------------------------- > >Ron Rosson ... and a UNIX user said ... > >The InSaNe One rm -rf * > >insane@oneinsane.net and all was null and void > >-------------------------------------------------------- > >It's so nice to be insane, nobody asks you to explain. > > -- -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 09:10:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09944 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 09:10:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles227.castles.com [208.214.165.227]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09869 for ; Tue, 28 Jul 1998 09:10:33 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA03485; Tue, 28 Jul 1998 09:09:20 -0700 (PDT) Message-Id: <199807281609.JAA03485@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike cc: "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-reply-to: Your message of "Tue, 28 Jul 1998 09:57:02 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 09:09:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG People, the Sparc port is _dead_ (Sun pulled the plug a while back). At no time was there going to be support for geriatric hardware. If you want to run a real operating system, the NetBSD folks cater to just that sort of nostalgia. > On Mon, 27 Jul 1998, Henry M. Pierce wrote: > > > Hello. I am interested in helping with the development effort > > with the sparc port of FreeBSD with an SS1+ that was recently > > I'd also be interested in helping out in some way... I am not sure of the > status of this port or where to find out more information about it, but > I'd like to put this Sparc2 to use somehow. :) > > -mike > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 09:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18032 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 09:45:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18010 for ; Tue, 28 Jul 1998 09:45:48 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.7/8.6.9) with SMTP id MAA21402 for ; Tue, 28 Jul 1998 12:57:27 -0400 (EDT) Message-Id: <199807281657.MAA21402@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 28 Jul 1998 12:55:12 -0400 To: hackers@FreeBSD.ORG From: Dennis Subject: TCPDUMP In-Reply-To: <19980728080658.B16948@oneinsane.net> References: <199807281435.KAA20752@etinc.com> <19980727143725.A10319@oneinsane.net> <199807281435.KAA20752@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone who understand the bpf code have an idea why filters (and trafshow) done work with a serial device with DLT_NULL header? tcpdump works fine in raw mode, but if you ad an expression it doesnt pass the filter tests. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 09:52:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19618 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 09:52:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19611 for ; Tue, 28 Jul 1998 09:52:36 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA11944; Tue, 28 Jul 1998 09:51:50 -0700 (PDT) Message-Id: <199807281651.JAA11944@tnt.isi.edu> To: Mike Smith Cc: Frank McConnell , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Mon, 27 Jul 1998 18:14:52 PDT." <199807280114.SAA02516@dingo.cdrom.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 09:51:50 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Mike Smith wrote: >> Robert Swindells wrote: >> I seem to have run afoul of another part of this change. I'm not sure >> if it's due to hardware misconfiguration on my part, but the way it >> behaves is bothersome. > >No, you're correct, and I slipped on this. The ID that is tested for >is the generic ID for the 79c971, not a Hitachi-specific ID, and I >didn't realise that. We do need a better probe for the Hitachi case. Blame where blame is due: I slipped on this. Sorry Mike (and others) I should have checked better what was going on. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb4Bo4b4eisfQ5rpAQH+tQP/aRpvNB4Z26EyEXa7D7TbIN7nH8i94fuG aPtg9/zEpyvWIxl5AhG+FtkU94tNCNPgQklUHDyCISu4Srip7ttxFFY10fkkHk8C 9swlICIoioYS69ZtgpolPCMqt1M2fBNhjjMtHzClsPGIeXlVnioUguGOWpRIqRnQ S7ZLEKcNmD0= =kCqi -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 09:55:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20184 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 09:55:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20176 for ; Tue, 28 Jul 1998 09:55:18 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA12085; Tue, 28 Jul 1998 09:54:35 -0700 (PDT) Message-Id: <199807281654.JAA12085@tnt.isi.edu> To: Mike Smith Cc: Frank McConnell , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Mon, 27 Jul 1998 18:14:52 PDT." <199807280114.SAA02516@dingo.cdrom.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 09:54:35 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Mike Smith wrote: >> Robert Swindells wrote: >> For all I know there is some way to tell the card not to do the ISA >> emulation, but that's been pushed to the copious free time list so I >> may not find out soon. > >No. ISA and PCI share an I/O space, but that's about it. > >I'm sorry; this is breakage in both 2.2.7 and -current, and we're going >to need a better way of identifying the problem cases like the Hitachi >(or a better workaround). 8( So, if this is a known chip that works on other machines, what's so different about the Hitachi MX-133? I'm happy to run any diagnostics that you guys think will help find the differences. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb4CSob4eisfQ5rpAQGCoQQAmBh2pX0ZMgpYIFrWS2+r4ItBxHZSntCn FQBLiPygop68iUIEOy4eJSM4RRH01YyiMMX5vDsppWJFkKbVGHmbZv/DJUtnF3E6 yBkqGojfGzaisnyUD5oum5/NeEkjvPBh8f46ymhsYRCGVLH1oje0c5fo8yHd0C1H tax5/x4fQVM= =mzXX -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 09:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20478 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 09:56:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA20472 for ; Tue, 28 Jul 1998 09:56:12 -0700 (PDT) (envelope-from dcmyers@concord.Corp.Sun.COM) Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA09495 for ; Tue, 28 Jul 1998 09:55:10 -0700 Received: from concord.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3) id JAA05793; Tue, 28 Jul 1998 09:55:09 -0700 Received: from concord.corp.sun.com by concord.Corp.Sun.COM (SMI-8.6/SMI-SVR4) id JAA20777; Tue, 28 Jul 1998 09:55:05 -0700 Message-Id: <199807281655.JAA20777@concord.Corp.Sun.COM> Date: Tue, 28 Jul 1998 09:55:05 -0700 (PDT) From: david.myers@Corp.Sun.COM Subject: Questions about vn driver... To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [previously posted to freebsd-questions, to no avail...] Folks: How do you format a vn disk image as a ufs file system? I am attempting to set up a 650 megabyte file for use as scratch space for assembling a CD-ROM image, but cannot figure out how to format the "disk". Newfs reports a pretty obvious error: there's no disktab entry for such a beast. Here's my plan: 1) create ~/cdimage as a 650 megabyte file 2) issue 'vnconfig /dev/vn0c ~/cdimage' 3) newfs /dev/rvn0c -- THIS DOESN'T WORK 4) fill up the new 650MB "disk", then 'mkisofs ~/cdimage | cdrecord' when full... Hints? Suggestions? Or is the vn driver not intended for this sort of thing? -David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 10:11:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23613 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 10:11:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23573 for ; Tue, 28 Jul 1998 10:10:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id KAA07571; Tue, 28 Jul 1998 10:08:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Jul 1998 10:08:56 -0700 (PDT) From: Doug White To: Picanco cc: hackers@FreeBSD.ORG Subject: Re: Fatal trap 12:page fault while in kernel mode In-Reply-To: <000e01bdb9e3$86b27900$e66c0fd0@InternetSolutions.insolwwb.net > Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Picanco wrote: > Intel Pentium 200 non overclocked... socket 7 chip > > the first time I tryed the install I used the 2.2.6 boot.flp file and got > the message below... > then I tryed the install with the 2.2.7 boot.flp file and recieved the same > message > with only a difference in the following line: > > fault virtual address = 0xf4c14003 > Okay, I'm forwarding this up to -hackers. Hopefully the detail below will give them a hint... > > > -----Original Message----- > From: Doug White > To: Picanco > Date: Monday, July 27, 1998 4:21 PM > Subject: Re: Fatal trap 12:page fault while in kernel mode > > > > > >On Sat, 25 Jul 1998, Picanco wrote: > > > >> CPU- Pentium 200 > > > >This is an Intel Pentium 200, or an AMD, or Cyrix? Is your motherboard > >overclocked? > > > >> Motherboard- Tomcat IV S1564S Award BIOS > >> Memory- 8 x 32M 72-pin Full parity SIMM chips > > > >What version of FreeBSD are you on? > > > >> > >> -----Original Message----- > >> From: Doug White > >> To: Picanco > >> Cc: freebsd-questions@FreeBSD.ORG > >> Date: Friday, July 24, 1998 7:09 PM > >> Subject: Re: Fatal trap 12:page fault while in kernel mode > >> > >> > >> > > >> >On Thu, 23 Jul 1998, Picanco wrote: > >> > > >> >> here is the error I recieved when attempting to install Freebsd: > >> >> > >> >> avail memory = 259289088 (253212k bytes) > >> >> > >> >> Fatal trap 12:page fault while in kernel mode > >> >> fault virtual address = 0xf52ca0003 > >> >> fault code = supervisor read, page not present > >> >> instruction pointer = 0x8:0xf01ace43 > >> >> stack pointer = 0x10:0xefbfff70 > >> >> frame pointer = 0x10:0xefbfff80 > >> >> code segment = base 0x0, limit 0xfffff, type 0x1b > >> >> = DPL 0, pres 1, def32 1, gran 1 > >> >> processor eflags = resume, IOPL = 0 > >> >> current process = 0 ( ) > >> >> interupt mask = net tty bio cam > >> >> panic:page fault > >> >> > >> >> Any help or suggestions would be greatly appreciated... if I do not > >> >> recieve a response within 5-10 days, will resend this message Thank > >> >> you for your time > >> > > >> >Please post your system details, inclugin CPU type, motherboard type, > and > >> >memory configuration. > >> > > >> >Doug White | University of Oregon > >> >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > >> >http://gladstone.uoregon.edu/~dwhite | Computer Science Major > >> > > >> > > > >Doug White | University of Oregon > >Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > >http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 10:15:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24446 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 10:15:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from manchester.genrad.com (x159.genrad.co.uk [195.99.3.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24426 for ; Tue, 28 Jul 1998 10:15:33 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Tue, 28 Jul 1998 10:15:33 -0700 (PDT) Message-Id: <199807281715.KAA24426@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id PPD974GV; Tue, 28 Jul 1998 18:14:22 +0100 From: Robert Swindells To: faber@ISI.EDU CC: mike@smith.net.au, fmc@reanimators.org, hackers@FreeBSD.ORG In-reply-to: <199807281654.JAA12085@tnt.isi.edu> (message from Ted Faber on Tue, 28 Jul 1998 09:54:35 -0700) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Mike Smith wrote: >>> Robert Swindells wrote: >>> For all I know there is some way to tell the card not to do the ISA >>> emulation, but that's been pushed to the copious free time list so I >>> may not find out soon. [I didn't write this] >> >>No. ISA and PCI share an I/O space, but that's about it. >> >>I'm sorry; this is breakage in both 2.2.7 and -current, and we're going >>to need a better way of identifying the problem cases like the Hitachi >>(or a better workaround). 8( >So, if this is a known chip that works on other machines, what's so >different about the Hitachi MX-133? I'm happy to run any diagnostics >that you guys think will help find the differences. If I send you an updated version of the driver, are you able to try it out on your VisionBook ? Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 10:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25118 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 10:19:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25064 for ; Tue, 28 Jul 1998 10:18:38 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA14004; Tue, 28 Jul 1998 10:17:47 -0700 (PDT) Message-Id: <199807281717.KAA14004@tnt.isi.edu> To: Robert Swindells Cc: mike@smith.net.au, fmc@reanimators.org, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Tue, 28 Jul 1998 10:14:53 PDT." <199807281714.KAA13786@tnt.isi.edu> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 10:17:47 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Robert Swindells wrote: >>So, if this is a known chip that works on other machines, what's so >>different about the Hitachi MX-133? I'm happy to run any diagnostics >>that you guys think will help find the differences. > >If I send you an updated version of the driver, are you able to try it >out on your VisionBook ? I'm able to try it out on my MX-133, which is the machine I originally, and apparently foolishly, patched the driver for. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb4Huob4eisfQ5rpAQFlcQQAheISaOwUA7UlZWSDvG5icOrSjHM41WNP sfQeGszUJU9OpsJoLXpqjpRqMTEYu3qSnbscr0FYDNQi7uQFy38k2hANcJkCtucf ButE0GopKJQEF48NfKBkHlsiJDY9rablVzfXozwsC7TMlMJY0OkQMIpLHkWL6xm7 52enCND/Db8= =1q1M -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 11:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04841 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 11:02:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agustina.kjsl.com (Agustina.KJSL.COM [198.137.202.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04756 for ; Tue, 28 Jul 1998 11:02:12 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from uucp@localhost) by agustina.kjsl.com (8.8.7/8.8.8/rchk1.19) with UUCP id KAA23328; Tue, 28 Jul 1998 10:57:42 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.8/rchk1.19) id KAA22144; Tue, 28 Jul 1998 10:51:03 -0700 (PDT) (envelope-from fmc) Message-Id: <199807281751.KAA22144@daemonweed.reanimators.org> To: Ted Faber Cc: Mike Smith , Frank McConnell , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? References: <199807281654.JAA12085@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 28 Jul 1998 10:51:02 -0700 In-Reply-To: Ted Faber's message of Tue, 28 Jul 1998 09:54:35 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Faber wrote: > So, if this is a known chip that works on other machines, what's so > different about the Hitachi MX-133? I'm happy to run any diagnostics > that you guys think will help find the differences. Funny, that's what I was thinking to ask you: what is it about the Hitachi Mx133 (and apparently other Hitachi notebooks) that needs this patch? I've looked at the original patch in the mailing list archives and now I think I really don't get it -- does this thing satisfy two different probes and so get attached twice? Likewise, I'm willing to run diagnostics, test patches, on this box. Maybe even look at code and data sheets if I can find the time. -Frank McConnell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 11:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06803 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 11:14:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06695 for ; Tue, 28 Jul 1998 11:13:46 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id LAA18644; Tue, 28 Jul 1998 11:12:59 -0700 (PDT) Message-Id: <199807281812.LAA18644@tnt.isi.edu> To: Frank McConnell Cc: Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "28 Jul 1998 10:51:02 PDT." <199807281751.KAA22144@daemonweed.reanimators.org> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 11:12:59 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Frank McConnell wrote: >Ted Faber wrote: >> So, if this is a known chip that works on other machines, what's so >> different about the Hitachi MX-133? I'm happy to run any diagnostics >> that you guys think will help find the differences. > >Funny, that's what I was thinking to ask you: what is it about the >Hitachi Mx133 (and apparently other Hitachi notebooks) that needs this >patch? The ethernet on the MX-133 is integrated into the case, i.e. it's not a PCMCIA card or an add-on. I haven't opened the thing up, but for all I know the controller's on the motherboard. Apparently they've made some interesting choices about the defaults for the PCNET chip they used. It seems to come up in ISA compatibility mode. If the chip *does* work in native PCI mode, maybe we should concentrate on bringing up the controller in direct PCI mode. I don't have the relevent chip specs, but if you can tell me anything I'll be happy to help. > I've looked at the original patch in the mailing list archives >and now I think I really don't get it -- does this thing satisfy two >different probes and so get attached twice? Here's what I sent Mike Smith about the patch. If other people are successfully using this chip as a pure PCI chip, my comments that there's no way to do so are obviously wrong. - --- Mike Smith said (among other things: >The ne2100_probe() function returns zero if pcnet_probe() fails. >However, you've patched this function to return nonzero, so you >shouldn't need this case. > >Comments? Are you still using this code? I'm still using this code, and here's my rationale behind it: (You'll probably want to open /sys/i386/isa/if_lnc.c up to follow this...) As far as I can tell, there's no support for using the Hitachi's internal PCI lance board in native PCI mode, so the card can only be used in ISA emulation mode. This means that pcnet_probe() is called *twice*, once when PCI cards are probed, and once when ISA cards are probed. When PCI cards are probed, lnc_attach_ne2100_pci() needs an indication that there is a PCI card around in emulation mode so that it doesn't call lnc_attach_sc() to attach the PCI card as a native PCI device. (This is somewhat obfuscated by putting it in a short circuit operator, but that construct was there when I showed up....) The zero from pcnet_probe() serves as a placeholder in lnc_attach_ne2100_pci(), but during ISA probing, lnc_probe() expects pcnet_probe() to return a non-zero value if there is a card in emulation mode. pcnet_probe() can't (easily :-)) tell which function's calling it, so it can't return different values. This patch was the first thing I submitted to the source tree, and as a new kid, I thought that keeping my changes as small as possible would make them more likely to be adopted (and smaller to mail!!). In retrospect, probably not the best parameter to optimize. :-) The problem seems to be that the various probe routines (or at least pcnet_probe()) are doung double duty as both ISA and PCI probe routines. Two answers suggest themselves: 1) Comment the hell out of this so it's not so confusing; 2) add a separate pcnet_probe_pci() routine that returns an appropriate value while reusing as much pcnet_probe() code as possible (all of it, I think). Of course, I could also be way off base, in which case, I hope you'll tell me. I'm happy to leave it as is, implement either of the above solutions, or be persuaded that there's another, better solution. - --- -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb4UqYb4eisfQ5rpAQF10AQAncU9SPLgvMZWVPt8/XYjhQOi4MLFd9of hVoyGzjHsGQ+2jJSajbeAwtJXXwe9QW42X64ReJFVpSxQd5FhthMapAMDFpYkUhA cCsiipT5PEs7REqOY4BDN5rTNnh+KYfP/s/vBdQKQOJVBg28DMqSvFUGVCfmfE8a OP3DDk8bzog= =z/yG -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 11:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07979 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 11:20:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA07743; Tue, 28 Jul 1998 11:19:19 -0700 (PDT) (envelope-from dcmyers@concord.Corp.Sun.COM) Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA06432; Tue, 28 Jul 1998 11:18:10 -0700 Received: from concord.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3) id LAA19382; Tue, 28 Jul 1998 11:18:10 -0700 Received: from concord.corp.sun.com by concord.Corp.Sun.COM (SMI-8.6/SMI-SVR4) id LAA21352; Tue, 28 Jul 1998 11:18:04 -0700 Message-Id: <199807281818.LAA21352@concord.Corp.Sun.COM> Date: Tue, 28 Jul 1998 11:18:04 -0700 (PDT) From: david.myers@Corp.Sun.COM Subject: Questions about vn driver (More info...) To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding my attempt to format a vn disk image as UFS: I found Keith Jones' post (Message-ID: <19980715103538.41845@blueberry.co.uk>) in freebsd-bugs regarding a similar issue. He created a disktab entry for an mfs file system (Ah! MFS! Is that documented somewhere?), and used that to disklabel his vnconfig'd device. But following his recipe exactly, I get the following when issuing the 'disklabel -w /dev/vn0 400M': disklabel: ioctl DIOCWDINFO: Operation not supported by device I'm using FreeBSD-2.2.6 with the PAO-980430 laptop extensions. Keith's recipe is copied below. He apparently didn't have any problems disklabeling his vn disk... Any help appreciated. -David ------------- This is what I did: # dd if=/dev/zero of=/usr/diskimage bs=1024 count=409600 # vnconfig -c -s labels /dev/vn0 /usr/diskimage # disklabel -w /dev/vn0 400M # newfs /dev/vn0a # newfs /dev/vn0e # newfs /dev/vn0f # mount /dev/vn0a /mnt # cd /mnt # mkdir usr # mkdir var # mount /dev/vn0e /mnt/var # mount /dev/vn0f /mnt/usr The /etc/disktab entry for 400M is as follows: 400M|400M Disk:\ :ty=mfs:se#512:nt#16:ns#32:nc#1600: \ :pa#65536:oa#0:ta=4.2BSD:ba#4096:fa#512:\ :pb#65536:ob#65536:tb=swap: \ :pc#819200:oc#0: \ :pe#61440:oe#131072:te=4.2BSD:be#4096:fe#512: \ :pf#626688:of#192512:tf=4.2BSD:bf#4096:ff#512: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 11:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09548 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 11:27:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from manchester.genrad.com (x159.genrad.co.uk [195.99.3.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09416 for ; Tue, 28 Jul 1998 11:27:21 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Tue, 28 Jul 1998 11:27:21 -0700 (PDT) Message-Id: <199807281827.LAA09416@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id PPD97422; Tue, 28 Jul 1998 19:26:10 +0100 From: Robert Swindells To: faber@ISI.EDU CC: fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: <199807281812.LAA18644@tnt.isi.edu> (message from Ted Faber on Tue, 28 Jul 1998 11:12:59 -0700) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The ethernet on the MX-133 is integrated into the case, i.e. it's not >a PCMCIA card or an add-on. I haven't opened the thing up, but for >all I know the controller's on the motherboard. Apparently they've >made some interesting choices about the defaults for the PCNET chip >they used. It seems to come up in ISA compatibility mode. The documentation for the chip doesn't mention anything about there being an ISA mode. >If the chip *does* work in native PCI mode, maybe we should >concentrate on bringing up the controller in direct PCI mode. I don't >have the relevent chip specs, but if you can tell me anything I'll be >happy to help. We have been using this chip on a laptop motherboard & it works fine as a PCI device. I'll send you a driver to try later. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 11:36:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11687 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 11:36:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11562 for ; Tue, 28 Jul 1998 11:35:50 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA28229; Tue, 28 Jul 1998 13:35:03 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA00276; Tue, 28 Jul 1998 13:34:31 -0500 Message-ID: <19980728133430.54771@right.PCS> Date: Tue, 28 Jul 1998 13:34:30 -0500 From: Jonathan Lemon To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: TCPDUMP References: <199807281435.KAA20752@etinc.com> <19980727143725.A10319@oneinsane.net> <199807281435.KAA20752@etinc.com> <199807281657.MAA21402@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199807281657.MAA21402@etinc.com>; from Dennis on Jul 07, 1998 at 12:55:12PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1998 at 12:55:12PM -0400, Dennis wrote: > Does anyone who understand the bpf code have an idea why filters > (and trafshow) done work with a serial device with DLT_NULL header? > > tcpdump works fine in raw mode, but if you ad an expression it > doesnt pass the filter tests. Not sure, but you may want to look at src/contrib/libpcap/gencode.c, at the various switch statements for DLT_NULL. Perhaps the offsets are not correct the framing protocol that you are using? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 12:22:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22048 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 12:22:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tarsier.ca.sandia.gov (tarsier.ca.sandia.gov [146.246.246.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21949 for ; Tue, 28 Jul 1998 12:21:57 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Received: from tarsier.ca.sandia.gov (localhost [127.0.0.1]) by tarsier.ca.sandia.gov (8.8.8/8.8.8) with ESMTP id MAA12801 for ; Tue, 28 Jul 1998 12:22:36 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Message-Id: <199807281922.MAA12801@tarsier.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: pci_map_mem() failing.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 12:22:35 -0700 From: "Chris Csanady" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my second try at sending this message.. the first one did not seem to get through. :\ Anyways.. I am working on a device driver, and so far have not been able to get this seemingly simple aspect of it to work. I am getting the following error: pci_map_mem failed: bad memory type=0xfffff004 It seems that the pci code does not know how to handle 64bit cards. If I yank the lines in pci.c that check the memory type, it produces no errors, although the mapping still does not work. What am I missing here? This is on a 2.2.6 box. Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 13:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08542 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 13:34:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08396 for ; Tue, 28 Jul 1998 13:33:22 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA27573 for hackers@freebsd.org; Tue, 28 Jul 1998 16:35:55 -0400 From: Bill Paul Message-Id: <199807282035.QAA27573@skynet.ctr.columbia.edu> Subject: Call for testers for 3c905B driver To: hackers@FreeBSD.ORG Date: Tue, 28 Jul 1998 16:35:53 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you that care, I have a 3Com 3c905B driver ready for testing for FreeBSD 3.0 and 2.2.x. You can obtain the driver source code from the following places: http://www.freebsd.org/~wpaul/3Com/3.0 FreeBSD 3.0 source code http://www.freebsd.org/~wpaul/3Com/2.2 FreeBSD 2.2.x source code There are two files: if_xl.c and if_xlreg.h, which should go in /sys/pci. The only differences between versions are those associated with differences between FreeBSD 2.2.x and 3.0-current (this includes timeout handling, a little bit of PCI configuration and multicast support). This driver should work with the 3c900, 3c905 and 3c905B Etherlink XL and Fast Etherlink XL boards, as well as integrated 3Com controllers on certain recent Dell systems (Optiplex GX1 and Precision). So far I have only tested it with a 3c905B-TX integrated controller on a Dell Optiplex and 3c900 COMBO card. Note that the vortex driver (if_vx.c) already supports the 3c900 and original 3c905 cards, but it uses PIO to transfer packets to and from the NIC's RAM. My driver uses bus master DMA instead. If you want to use my driver instead of the vortex driver for the 3c900 and 3c905 cards, you should edit /sys/pci/if_vx_pci.c and comment out the portion of vx_pci_probe() that checks the PCI device IDs for the Etherlink XL cards, otherwise the vortex driver may be assigned to them instead of mine. The xl driver includes support for BPF, ifmedia and multicast. For the 3c905B, there is a 64-bit multicast hash filter which will be used if detected. For the 3c900, you only have a 'receive all multicast' mode, which requires software filtering but is better than nothing. I still have a little work to do in the ifmedia support. You may need to force the card into the proper mode to support the connector you're using. For BNC, use ifconfig xl0 media 10base2/BNC. For AUI, use ifconfig xl0 media 10base5/AUI. For RJ-45, use ifconfig xl0 media 10baseT/UTP. For 3c905B cards, the media should be properly autodetected. You can use ifconfig xl0 media autoselect to initiate another autonegotiation session with a link partner. I would appreciate it if people with 3c900, 3c905 and 3c905B hardware could test this driver for me. I'm particularly interested to hear it it works correctly with Fast Etherlink XL boards (3c905 10/100 cards). These cards use a NatSemi 10/100 PHY via the MII interface: I don't have one of these to test, so I can't be sure the MII support will work correctly. If you test the driver, please sent me a note letting me know if it works or not. If it doesn't work, please try to describe the problem you're having throroughly. Specify a way to reproduce the problem, if possible. To add the driver to your kernel, you need to do the following: - Edit /sys/conf/files and add a line that says: pci/if_xl.c optional xl device-driver - Edit your kernel config file and add a line that says: device xl0 - Copy if_xl.c and if_xlreg.h to /sys/pci. - Compile a new kernel and boot it. You may optionally want to edit /sys/pci/if_vx_pci.c to stop it probing the Etherlink XL cards so that if_xl.c can see them. -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 13:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12450 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 13:53:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12363 for ; Tue, 28 Jul 1998 13:52:25 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA15887 for ; Tue, 28 Jul 1998 16:51:48 -0400 (EDT) Date: Tue, 28 Jul 1998 16:51:48 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 To: hackers Subject: Still confused with PTDpde/APTDpde Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I spend another day thinking about the usage of PTDpde/APTDpde in pmap.c and still confused with them. It must have something to do with VA->PA translation and mixed assembly / C programming: (1) First of all, If we have the following lines in GAS: .global _xx .set _xx, 30 We have defined a global (absolute?) symbol _xx whose value is 30. Now, I refer to _xx in C by xx. What is the value (left or right?) of xx? In other words, is the address of xx 30 or is the value of xx 30? (2) If the value of xx is 30. Then look at locore.s where PTDped/APTDpde is defined in the same way. Both PTDpde and APTDpde has very special values (an address whose PDE, PTE, offset parts are the same). The question is what is the meaning of (unsigned)PTDpde & PG_FRAME and (unsigned)APTDpde & PG_FRAME in pmap.c? To make sense, the address (not value) of xx must be 30. (3) If this is correct, only PTDpde works well because we set up the self-referential pde entry in pmap_pinit(). But for APTDpde, it does not work the same way. How can APTDpde used to access other process's page tables? These questions may look stupid, but I am just stuck into them. Any help or hint is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18359 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:24:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18303 for ; Tue, 28 Jul 1998 14:23:52 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA04283; Tue, 28 Jul 1998 15:17:50 -0600 (MDT) Date: Tue, 28 Jul 1998 15:17:50 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807282117.PAA04283@narnia.plutotech.com> To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > Get DPT's or Adaptec's. Development of the Buslogic line seems to have > died. > > Given adaptec's new stance towards free OS's, and Mylex's closed-door > policy, I can only imagine that the Adaptec drivers will continue to > improve. Mylex is hardly closed-door. I had no problem getting the documentation required to write the FreeBSD-CAM BusLogic driver. I believe that specs for their RAID controllers are easy to obtain too. Just look at the Linux DAC960 driver. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:27:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19079 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:27:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19046 for ; Tue, 28 Jul 1998 14:27:30 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA04296; Tue, 28 Jul 1998 15:21:30 -0600 (MDT) Date: Tue, 28 Jul 1998 15:21:30 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807282121.PAA04296@narnia.plutotech.com> To: wayne@msen.com cc: hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > We have number of machines running BSD/OS with likely every model of > BusLogic controller ever made. We've started to move services to > FreeBSD and I finally took a good, long look at the driver code for > these cards. While "highly incomplete" is a little bit of an exageration, the older driver did not support things like tagged queuing and had spotty error recovery. It did support sync/wide/ultra transparently as that is the way the MultiMaster interface works. Anyway, you should try the CAM BusLogic driver I wrote. It handles tagged queuing, uses all available transaction space on the card, and provides for error recovery: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/ We only support Multi-Master cards right now. If you have a FlashPoint card (like a BT-950), you'll have to either write your own driver, or wait for me to get around to it (likely another month or two). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:31:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19794 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:31:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19659 for ; Tue, 28 Jul 1998 14:30:17 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 2315 invoked from network); 28 Jul 1998 21:29:44 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 28 Jul 1998 21:29:44 -0000 Date: Tue, 28 Jul 1998 14:29:44 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: "Justin T. Gibbs" cc: hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: <199807282117.PAA04283@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Possibly. WHen I asked them about it, they would only give me the specs under NDA, and distribute in binary-only form. Granted it was some time ago, but nothing was said that gave me any indication that it changed. Makes no difference to me, I'm an Adaptec/DPT user, and unlikely to change anytime soon. On Tue, 28 Jul 1998, Justin T. Gibbs wrote: > In article you wrote: > > > > Get DPT's or Adaptec's. Development of the Buslogic line seems to have > > died. > > > > Given adaptec's new stance towards free OS's, and Mylex's closed-door > > policy, I can only imagine that the Adaptec drivers will continue to > > improve. > > Mylex is hardly closed-door. I had no problem getting the documentation > required to write the FreeBSD-CAM BusLogic driver. I believe that specs > for their RAID controllers are easy to obtain too. Just look at the > Linux DAC960 driver. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20506 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:34:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts02-119.dublin.indigo.ie [194.125.134.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20368 for ; Tue, 28 Jul 1998 14:33:56 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01426; Tue, 28 Jul 1998 22:28:15 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807282128.WAA01426@indigo.ie> Date: Tue, 28 Jul 1998 22:28:15 +0000 In-Reply-To: <199807272316.QAA04693@usr05.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Terry Lambert , n@nectar.com (Jacques Vidrine) Subject: Re: inetd enhancements Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 27, 11:16pm, Terry Lambert wrote: } Subject: Re: inetd enhancements > > > Root can escape > > > a chroot jail because of the way the chroot root vnode is (in my > > > opinion) incorrectly set to NULL instead of the real root for the > > > non-chroot case (fixing this would incidently simplify the namei code). > > > > > > The "ftpd" case is especially vulnerable... > > > > I don't follow. Could you give an example scenario of an exploit? > > I spared the list my code for doing this, sending it only to the > questioner. Thank you, Terry. You can also effectively break out of chroot with ptrace. Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:52:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24711 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:52:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24632 for ; Tue, 28 Jul 1998 14:52:40 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id OAA14577; Tue, 28 Jul 1998 14:51:53 -0700 (PDT) Message-ID: <19980728145153.B13777@Alameda.net> Date: Tue, 28 Jul 1998 14:51:53 -0700 From: Ulf Zimmermann To: Ted Faber , Frank McConnell Cc: Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? Reply-To: ulf@Alameda.net References: <199807281751.KAA22144@daemonweed.reanimators.org> <199807281812.LAA18644@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807281812.LAA18644@tnt.isi.edu>; from Ted Faber on Tue, Jul 28, 1998 at 11:12:59AM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 11:12:59AM -0700, Ted Faber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > > Frank McConnell wrote: > >Ted Faber wrote: > >> So, if this is a known chip that works on other machines, what's so > >> different about the Hitachi MX-133? I'm happy to run any diagnostics > >> that you guys think will help find the differences. > > > >Funny, that's what I was thinking to ask you: what is it about the > >Hitachi Mx133 (and apparently other Hitachi notebooks) that needs this > >patch? > > The ethernet on the MX-133 is integrated into the case, i.e. it's not > a PCMCIA card or an add-on. I haven't opened the thing up, but for > all I know the controller's on the motherboard. Apparently they've > made some interesting choices about the defaults for the PCNET chip > they used. It seems to come up in ISA compatibility mode. > > If the chip *does* work in native PCI mode, maybe we should > concentrate on bringing up the controller in direct PCI mode. I don't > have the relevent chip specs, but if you can tell me anything I'll be > happy to help. I have a hitachi M100D, which worked with a 2.2.2-STABLE and the lnc1 driver as PCI. I tried to install 2.2.6 but 2.2.6 had very many page faults. I was going to try 2.2.7 again. > > > I've looked at the original patch in the mailing list archives > >and now I think I really don't get it -- does this thing satisfy two > >different probes and so get attached twice? > > Here's what I sent Mike Smith about the patch. If other people are > successfully using this chip as a pure PCI chip, my comments that > there's no way to do so are obviously wrong. > > - --- > Mike Smith said (among other things: > >The ne2100_probe() function returns zero if pcnet_probe() fails. > >However, you've patched this function to return nonzero, so you > >shouldn't need this case. > > > >Comments? Are you still using this code? > > I'm still using this code, and here's my rationale behind it: > > (You'll probably want to open /sys/i386/isa/if_lnc.c up to follow this...) > > As far as I can tell, there's no support for using the Hitachi's > internal PCI lance board in native PCI mode, so the card can only be > used in ISA emulation mode. This means that pcnet_probe() is called > *twice*, once when PCI cards are probed, and once when ISA cards are > probed. When PCI cards are probed, lnc_attach_ne2100_pci() needs an > indication that there is a PCI card around in emulation mode so that > it doesn't call lnc_attach_sc() to attach the PCI card as a native PCI > device. (This is somewhat obfuscated by putting it in a short circuit > operator, but that construct was there when I showed up....) The zero > from pcnet_probe() serves as a placeholder in lnc_attach_ne2100_pci(), > but during ISA probing, lnc_probe() expects pcnet_probe() to return a > non-zero value if there is a card in emulation mode. > > pcnet_probe() can't (easily :-)) tell which function's calling it, so > it can't return different values. > > This patch was the first thing I submitted to the source tree, and as > a new kid, I thought that keeping my changes as small as possible > would make them more likely to be adopted (and smaller to mail!!). > In retrospect, probably not the best parameter to optimize. :-) > > The problem seems to be that the various probe routines (or at least > pcnet_probe()) are doung double duty as both ISA and PCI probe > routines. Two answers suggest themselves: 1) Comment the hell out of > this so it's not so confusing; 2) add a separate pcnet_probe_pci() > routine that returns an appropriate value while reusing as much > pcnet_probe() code as possible (all of it, I think). Of course, I > could also be way off base, in which case, I hope you'll tell me. > > I'm happy to leave it as is, implement either of the above solutions, > or be persuaded that there's another, better solution. > > - --- > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBNb4UqYb4eisfQ5rpAQF10AQAncU9SPLgvMZWVPt8/XYjhQOi4MLFd9of > hVoyGzjHsGQ+2jJSajbeAwtJXXwe9QW42X64ReJFVpSxQd5FhthMapAMDFpYkUhA > cCsiipT5PEs7REqOY4BDN5rTNnh+KYfP/s/vBdQKQOJVBg28DMqSvFUGVCfmfE8a > OP3DDk8bzog= > =z/yG > -----END PGP SIGNATURE----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 14:53:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24904 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 14:53:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24849 for ; Tue, 28 Jul 1998 14:53:13 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA03303; Tue, 28 Jul 1998 14:52:38 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd003278; Tue Jul 28 14:52:31 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA18723; Tue, 28 Jul 1998 14:52:26 -0700 (MST) From: Terry Lambert Message-Id: <199807282152.OAA18723@usr04.primenet.com> Subject: Re: pci_map_mem() failing.. To: cc@tarsier.ca.sandia.gov (Chris Csanady) Date: Tue, 28 Jul 1998 21:52:25 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199807281922.MAA12801@tarsier.ca.sandia.gov> from "Chris Csanady" at Jul 28, 98 12:22:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyways.. I am working on a device driver, and so far have not been able to > get this seemingly simple aspect of it to work. I am getting the following > error: > pci_map_mem failed: bad memory type=0xfffff004 > > It seems that the pci code does not know how to handle 64bit cards. If > I yank the lines in pci.c that check the memory type, it produces no > errors, although the mapping still does not work. What am I missing > here? Information about how you intend to latch a 64 bit address onto a 32 bit bus? Or do you mean "64 bit" the way the video card manufacturers mean it, which is internal data path between video memory and the graphics engine on the card itself? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 15:02:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27672 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 15:02:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27575 for ; Tue, 28 Jul 1998 15:02:19 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id PAA15139; Tue, 28 Jul 1998 15:01:36 -0700 (PDT) Message-ID: <19980728150135.A14581@Alameda.net> Date: Tue, 28 Jul 1998 15:01:35 -0700 From: Ulf Zimmermann To: "Justin T. Gibbs" , Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver Reply-To: ulf@Alameda.net References: <199807282117.PAA04283@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807282117.PAA04283@narnia.plutotech.com>; from Justin T. Gibbs on Tue, Jul 28, 1998 at 03:17:50PM -0600 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 03:17:50PM -0600, Justin T. Gibbs wrote: > In article you wrote: > > > > Get DPT's or Adaptec's. Development of the Buslogic line seems to have > > died. > > > > Given adaptec's new stance towards free OS's, and Mylex's closed-door > > policy, I can only imagine that the Adaptec drivers will continue to > > improve. > > Mylex is hardly closed-door. I had no problem getting the documentation > required to write the FreeBSD-CAM BusLogic driver. I believe that specs > for their RAID controllers are easy to obtain too. Just look at the > Linux DAC960 driver. Mylex gave me the documentation for the DAC960 controller and even a 3 channel DAC960PJ with 8MB EDO/ECC memory. I am still working on learning more about stuff to continue the driver. I have so far the detection complete (PCI, which controller version, memory, channels, system drives, etc.) > > -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 15:08:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29232 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 15:08:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tarsier.ca.sandia.gov (tarsier.ca.sandia.gov [146.246.246.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29136 for ; Tue, 28 Jul 1998 15:08:31 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Received: from tarsier.ca.sandia.gov (localhost [127.0.0.1]) by tarsier.ca.sandia.gov (8.8.8/8.8.8) with ESMTP id PAA13462; Tue, 28 Jul 1998 15:09:12 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Message-Id: <199807282209.PAA13462@tarsier.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: pci_map_mem() failing.. In-reply-to: Your message of "Tue, 28 Jul 1998 21:52:25 -0000." <199807282152.OAA18723@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 15:09:12 -0700 From: "Chris Csanady" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Anyways.. I am working on a device driver, and so far have not been able to >> get this seemingly simple aspect of it to work. I am getting the following >> error: >> pci_map_mem failed: bad memory type=0xfffff004 >> >> It seems that the pci code does not know how to handle 64bit cards. If >> I yank the lines in pci.c that check the memory type, it produces no >> errors, although the mapping still does not work. What am I missing >> here? > >Information about how you intend to latch a 64 bit address onto a 32 >bit bus? > >Or do you mean "64 bit" the way the video card manufacturers mean >it, which is internal data path between video memory and the graphics >engine on the card itself? The card actually is actuall a 64 bit card, so it is possible to address the memory in an alpha or such. The second and third bit of the base address register (0xfffff004) in this case say that the memory mapping may be anywhere in the 64 bit address space. (For 32 bit, they should be zero.) The following case in pci/pci.c throws out all 64 bit cards it seems: /* ** check the type */ if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M && (paddr & ~0xfffff) == 0) && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT){ printf ("pci_map_mem failed: bad memory type=0x%x\n", (unsigned) data); return (0); }; Is this correct? After removing this, it still does not seem to work. Does the pci code need to play with the next 32 bits of the base address register too? I noticed that the current code is much different, although I am not set up to do developement on current now. It is painful enough typing one handed, so I am looking for the quick and dirty solution. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 15:25:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03490 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 15:25:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03401 for ; Tue, 28 Jul 1998 15:25:14 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA02481; Tue, 28 Jul 1998 15:24:39 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd002462; Tue Jul 28 15:24:31 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA20070; Tue, 28 Jul 1998 15:24:28 -0700 (MST) From: Terry Lambert Message-Id: <199807282224.PAA20070@usr04.primenet.com> Subject: Re: pci_map_mem() failing.. To: cc@tarsier.ca.sandia.gov (Chris Csanady) Date: Tue, 28 Jul 1998 22:24:28 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <199807282209.PAA13462@tarsier.ca.sandia.gov> from "Chris Csanady" at Jul 28, 98 03:09:12 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Information about how you intend to latch a 64 bit address onto a 32 > >bit bus? > > > >Or do you mean "64 bit" the way the video card manufacturers mean > >it, which is internal data path between video memory and the graphics > >engine on the card itself? > > The card actually is actuall a 64 bit card, so it is possible to address > the memory in an alpha or such. The second and third bit of the base > address register (0xfffff004) in this case say that the memory mapping may > be anywhere in the 64 bit address space. (For 32 bit, they should be zero.) PCI does not support 64 address lines, only 32. There is a move to extend the PCI specification, but it has yet to be ratified as a standard, AFAIK. > The following case in pci/pci.c throws out all 64 bit cards it seems: > > /* > ** check the type > */ > > if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M > && (paddr & ~0xfffff) == 0) > && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT){ > printf ("pci_map_mem failed: bad memory type=0x%x\n", > (unsigned) data); > return (0); > }; > > Is this correct? After removing this, it still does not seem to work. Does > the pci code need to play with the next 32 bits of the base address register > too? If it was supported, then yes, it would need to, from my knowledge of experimental 64 bit PCI implementations by Intel and another vendor with a competing connector and lead arrangement. Is there a particular reason you are trying to do this in 64 bit mode instead of 32 bit mode? Do you have one of these experimental extended bus connectors that you are using? If the answer to either of these questions is "no", then you should use a 32 bit mapping instead. I don't believe the kernel virtual address space is large enough to cope with 64 bits in any case; the FS code does it by mapping windows onto the file. > I noticed that the current code is much different, although I am not > set up to do developement on current now. It is painful enough typing > one handed, so I am looking for the quick and dirty solution. Q&D would be "use a 32 bit mapping". Sorry about the hand; I broke the pinky of my right hand a while ago, and typing was a bugger (I'm right handed, as well). Very quick route to tendonitus in the other hand. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 15:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06580 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 15:39:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from priscilla.mu.org (paul@priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06500 for ; Tue, 28 Jul 1998 15:39:21 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id RAA25856; Tue, 28 Jul 1998 17:38:07 -0500 (CDT) (envelope-from paul) Message-ID: <19980728173807.A25849@mu.org> Date: Tue, 28 Jul 1998 17:38:07 -0500 From: Paul Saab To: Bill Paul , hackers@FreeBSD.ORG Subject: Re: Call for testers for 3c905B driver References: <199807282035.QAA27573@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807282035.QAA27573@skynet.ctr.columbia.edu>; from Bill Paul on Tue, Jul 28, 1998 at 04:35:53PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So far this is working Great! I'm going to stress test it now.. Whee Thanks! Paul Bill Paul (wpaul@skynet.ctr.columbia.edu) wrote: > For those of you that care, I have a 3Com 3c905B driver ready for > testing for FreeBSD 3.0 and 2.2.x. You can obtain the driver source code > from the following places: > > http://www.freebsd.org/~wpaul/3Com/3.0 FreeBSD 3.0 source code > http://www.freebsd.org/~wpaul/3Com/2.2 FreeBSD 2.2.x source code > > There are two files: if_xl.c and if_xlreg.h, which should go in /sys/pci. > The only differences between versions are those associated with differences > between FreeBSD 2.2.x and 3.0-current (this includes timeout handling, > a little bit of PCI configuration and multicast support). > > This driver should work with the 3c900, 3c905 and 3c905B Etherlink XL > and Fast Etherlink XL boards, as well as integrated 3Com controllers > on certain recent Dell systems (Optiplex GX1 and Precision). So far > I have only tested it with a 3c905B-TX integrated controller on a Dell > Optiplex and 3c900 COMBO card. > > Note that the vortex driver (if_vx.c) already supports the 3c900 and > original 3c905 cards, but it uses PIO to transfer packets to and from > the NIC's RAM. My driver uses bus master DMA instead. If you want to > use my driver instead of the vortex driver for the 3c900 and 3c905 > cards, you should edit /sys/pci/if_vx_pci.c and comment out the > portion of vx_pci_probe() that checks the PCI device IDs for the > Etherlink XL cards, otherwise the vortex driver may be assigned to > them instead of mine. > > The xl driver includes support for BPF, ifmedia and multicast. For > the 3c905B, there is a 64-bit multicast hash filter which will be > used if detected. For the 3c900, you only have a 'receive all multicast' > mode, which requires software filtering but is better than nothing. > > I still have a little work to do in the ifmedia support. You may need > to force the card into the proper mode to support the connector you're > using. For BNC, use ifconfig xl0 media 10base2/BNC. For AUI, use > ifconfig xl0 media 10base5/AUI. For RJ-45, use ifconfig xl0 media > 10baseT/UTP. > > For 3c905B cards, the media should be properly autodetected. You can > use ifconfig xl0 media autoselect to initiate another autonegotiation > session with a link partner. > > I would appreciate it if people with 3c900, 3c905 and 3c905B hardware > could test this driver for me. I'm particularly interested to hear it > it works correctly with Fast Etherlink XL boards (3c905 10/100 cards). > These cards use a NatSemi 10/100 PHY via the MII interface: I don't > have one of these to test, so I can't be sure the MII support will > work correctly. > > If you test the driver, please sent me a note letting me know if it > works or not. If it doesn't work, please try to describe the problem > you're having throroughly. Specify a way to reproduce the problem, > if possible. > > To add the driver to your kernel, you need to do the following: > > - Edit /sys/conf/files and add a line that says: > pci/if_xl.c optional xl device-driver > > - Edit your kernel config file and add a line that says: > device xl0 > > - Copy if_xl.c and if_xlreg.h to /sys/pci. > > - Compile a new kernel and boot it. > > You may optionally want to edit /sys/pci/if_vx_pci.c to stop it > probing the Etherlink XL cards so that if_xl.c can see them. > > -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" > ============================================================================= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 16:03:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11333 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 16:03:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11265 for ; Tue, 28 Jul 1998 16:03:17 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 10188 invoked from network); 28 Jul 1998 23:02:43 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 28 Jul 1998 23:02:43 -0000 Date: Tue, 28 Jul 1998 16:02:43 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Ulf Zimmermann cc: "Justin T. Gibbs" , hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: <19980728150135.A14581@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, like I said, I still have the original email from mylex telling me I had to have an NDA, when I was going to hire somebody to work on the mylex driver because I have 5 of them sitting here. It was cheaper to just chuck 'em, and buy DPT. On Tue, 28 Jul 1998, Ulf Zimmermann wrote: > On Tue, Jul 28, 1998 at 03:17:50PM -0600, Justin T. Gibbs wrote: > > In article you wrote: > > > > > > Get DPT's or Adaptec's. Development of the Buslogic line seems to have > > > died. > > > > > > Given adaptec's new stance towards free OS's, and Mylex's closed-door > > > policy, I can only imagine that the Adaptec drivers will continue to > > > improve. > > > > Mylex is hardly closed-door. I had no problem getting the documentation > > required to write the FreeBSD-CAM BusLogic driver. I believe that specs > > for their RAID controllers are easy to obtain too. Just look at the > > Linux DAC960 driver. > > Mylex gave me the documentation for the DAC960 controller and even > a 3 channel DAC960PJ with 8MB EDO/ECC memory. I am still working on > learning more about stuff to continue the driver. I have so far > the detection complete (PCI, which controller version, memory, > channels, system drives, etc.) > > > > > -- > > Justin > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 17:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26651 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 17:46:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tarsier.ca.sandia.gov (tarsier.ca.sandia.gov [146.246.246.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26496 for ; Tue, 28 Jul 1998 17:45:03 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Received: from tarsier.ca.sandia.gov (localhost [127.0.0.1]) by tarsier.ca.sandia.gov (8.8.8/8.8.8) with ESMTP id RAA14001; Tue, 28 Jul 1998 17:45:44 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Message-Id: <199807290045.RAA14001@tarsier.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: pci_map_mem() failing.. In-reply-to: Your message of "Tue, 28 Jul 1998 22:24:28 -0000." <199807282224.PAA20070@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 17:45:44 -0700 From: "Chris Csanady" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Information about how you intend to latch a 64 bit address onto a 32 >> >bit bus? >> > >> >Or do you mean "64 bit" the way the video card manufacturers mean >> >it, which is internal data path between video memory and the graphics >> >engine on the card itself? >> >> The card actually is actuall a 64 bit card, so it is possible to address >> the memory in an alpha or such. The second and third bit of the base >> address register (0xfffff004) in this case say that the memory mapping may >> be anywhere in the 64 bit address space. (For 32 bit, they should be zero.) > >PCI does not support 64 address lines, only 32. > >There is a move to extend the PCI specification, but it has yet to >be ratified as a standard, AFAIK. I'm pretty sure that the 2.1 spec allows 64 bit 66MHz busses. Or at least this book in front of me says so. :) >> The following case in pci/pci.c throws out all 64 bit cards it seems: >> >> /* >> ** check the type >> */ >> >> if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT _1M >> && (paddr & ~0xfffff) == 0) >> && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BI T){ >> printf ("pci_map_mem failed: bad memory type=0x%x\n", >> (unsigned) data); >> return (0); >> }; >> >> Is this correct? After removing this, it still does not seem to work. Does >> the pci code need to play with the next 32 bits of the base address register >> too? > >If it was supported, then yes, it would need to, from my knowledge of >experimental 64 bit PCI implementations by Intel and another vendor >with a competing connector and lead arrangement. > >Is there a particular reason you are trying to do this in 64 bit mode >instead of 32 bit mode? The low few bits are part of the PCI base mem register, and can't be changed, AFAIK. It simply says that the memory *can* be mapped anywhere in a 64 bit addr space, not that it has to be. So, when the card is used ini 32 bit mode, it will just have to live with the limitation of using the first 4GB. :) Actually, I had a typo and once the above check was fixed, it now works. A diff for the 2.2 branch follows. This is not entirely correct, but should work. >Do you have one of these experimental extended bus connectors that you >are using? We have some alphas that have 64bit PCI. [...] >Sorry about the hand; I broke the pinky of my right hand a while >ago, and typing was a bugger (I'm right handed, as well). Very >quick route to tendonitus in the other hand. 8-(. Me too. :( It is extremely frustrating, and I already have tendonitis to some degree as well. Ugh. Chris Csanady *** /sys/pci/pci.c.old Tue Jul 28 16:23:39 1998 --- /sys/pci/pci.c Tue Jul 28 16:27:46 1998 *************** *** 1087,1093 **** if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M && (paddr & ~0xfffff) == 0) ! && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT){ printf ("pci_map_mem failed: bad memory type=0x%x\n", (unsigned) data); return (0); --- 1087,1094 ---- if (!((data & PCI_MAP_MEMORY_TYPE_MASK) == PCI_MAP_MEMORY_TYPE_32BIT_1M && (paddr & ~0xfffff) == 0) ! && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_32BIT ! && (data & PCI_MAP_MEMORY_TYPE_MASK) != PCI_MAP_MEMORY_TYPE_64BIT){ printf ("pci_map_mem failed: bad memory type=0x%x\n", (unsigned) data); return (0); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 19:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12719 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 19:03:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12587 for ; Tue, 28 Jul 1998 19:02:23 -0700 (PDT) (envelope-from kev@lab321.ru) Received: from localhost (kev@localhost) by lab321.ru (1.0/8.8.5) with SMTP id JAA04524 for ; Wed, 29 Jul 1998 09:01:29 +0700 (OSS) Date: Wed, 29 Jul 1998 09:01:28 +0700 (OSS) From: Eugeny Kuzakov To: hackers@FreeBSD.ORG Subject: PAM4FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! One question. Is FreeBSD will support PAM ? -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 21:13:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03051 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 21:13:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (tc-13.acadiau.ca [131.162.2.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03033 for ; Tue, 28 Jul 1998 21:13:44 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id BAA23939 for ; Wed, 29 Jul 1998 01:13:12 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 29 Jul 1998 01:13:12 -0300 (ADT) From: The Hermit Hacker To: hackers@FreeBSD.ORG Subject: IP masquarading with Ethernet/ADSL? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... On Friday, I finally get ADSL to home. The phone company provides one ethernet card for my machine, and one IP. I have a growing network of computers that I'd like to have hidden behind my "gateway" machine. Now, with PPP, I've done it already, and its pretty simple...but what is involved in doing it with two ethernet cards? Just as easy? Pointers to a WWW page or docs? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 23:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19929 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 23:17:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19922 for ; Tue, 28 Jul 1998 23:17:18 -0700 (PDT) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id PAA07610; Wed, 29 Jul 1998 15:16:34 +0900 (JST) Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.26.2]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id PAA18988; Wed, 29 Jul 1998 15:16:33 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id PAA13818; Wed, 29 Jul 1998 15:16:32 +0900 (JST) Date: Wed, 29 Jul 1998 15:16:32 +0900 (JST) Message-Id: <199807290616.PAA13818@stone.astec.co.jp> From: HAMADA Naoki References: <199807282035.QAA27573@skynet.ctr.columbia.edu> To: wpaul@skynet.ctr.columbia.edu CC: hackers@FreeBSD.ORG In-reply-to: Bill Paul's message of "Tue, 28 Jul 1998 16:35:53 -0400 (EDT)" <199807282035.QAA27573@skynet.ctr.columbia.edu> Subject: Re: Call for testers for 3c905B driver Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: >I would appreciate it if people with 3c900, 3c905 and 3c905B hardware >could test this driver for me. I'm particularly interested to hear it >it works correctly with Fast Etherlink XL boards (3c905 10/100 cards). >These cards use a NatSemi 10/100 PHY via the MII interface: I don't >have one of these to test, so I can't be sure the MII support will >work correctly. I tried my 3C905 (not 3C905B) with new xl driver. It works almost well, but the auto negotiation (under 10M and half-duplex) invoked by 'ifconfig xl0 media autoselect' sometimes fails. xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, waiting a little longer... xl1: autoneg not complete, no carrier After setting 'ifconfig xl0 media 10BaseT/UTP' I tried the auto negotiation again, and it returns a successful message. xl1: selecting MII, 10Mbps, half duplex xl1: autoneg complete, link status good (half-duplex, 10Mbps) But, alas, the network is still dead. I have to explicitly specify the media to enable the network. I am going to look into this problem. By the way, here is my patch for its multicast support, which is not tested yet. - nao --- if_xl.c Wed Jul 29 13:38:04 1998 +++ if_xl.c.new Wed Jul 29 14:58:23 1998 @@ -207,6 +207,7 @@ static int xl_mii_writereg __P((struct xl_softc *, struct xl_mii_frame *)); static u_int16_t xl_phy_readreg __P((struct xl_softc *, int)); static void xl_phy_writereg __P((struct xl_softc *, u_int16_t, u_int16_t)); +static void xl_testpacket __P((struct xl_softc *)); static void xl_autoneg_xmit __P((struct xl_softc *)); static void xl_autoneg_mii __P((struct xl_softc *, int, int)); @@ -581,6 +582,13 @@ XL_SEL_WIN(5); rxfilt = CSR_READ_1(sc, XL_W5_RX_FILTER); + if (sc->arpcom.ac_multicnt == 0) { + /* disable multicast */ + rxfilt &= ~(XL_RXFILTER_ALLMULTI | XL_RXFILTER_MULTIHASH); + CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_RX_SET_FILT|rxfilt); + return; + } + if (sc->arpcom.ac_multicnt > 64 || ifp->if_flags & IFF_ALLMULTI || sc->xl_type == XL_TYPE_90X) { rxfilt |= XL_RXFILTER_ALLMULTI; @@ -591,6 +599,7 @@ CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_RX_SET_HASH|i); /* now program new ones */ rxfilt |= XL_RXFILTER_MULTIHASH; + rxfilt &= ~XL_RXFILTER_ALLMULTI; ETHER_FIRST_MULTI(step, &sc->arpcom, enm); while(enm != NULL) { if (bcmp(enm->enm_addrlo, enm->enm_addrhi, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 23:25:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21139 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 23:25:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21102 for ; Tue, 28 Jul 1998 23:25:42 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00574; Tue, 28 Jul 1998 23:24:12 -0700 (PDT) Message-Id: <199807290624.XAA00574@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: david.myers@Corp.Sun.COM cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions about vn driver... In-reply-to: Your message of "Tue, 28 Jul 1998 09:55:05 PDT." <199807281655.JAA20777@concord.Corp.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:24:10 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [previously posted to freebsd-questions, to no avail...] > > Folks: > > How do you format a vn disk image as a ufs file system? I am attempting > to set up a 650 megabyte file for use as scratch space for assembling a > CD-ROM image, but cannot figure out how to format the "disk". Newfs > reports a pretty obvious error: there's no disktab entry for such a > beast. > > Here's my plan: > > 1) create ~/cdimage as a 650 megabyte file > 2) issue 'vnconfig /dev/vn0c ~/cdimage' That should have '-o slices' in it. 2.5) 'disklabel -rw vn0 auto' > 3) newfs /dev/rvn0c -- THIS DOESN'T WORK > 4) fill up the new 650MB "disk", then 'mkisofs ~/cdimage | cdrecord' > when full... > > Hints? Suggestions? Or is the vn driver not intended for this > sort of thing? > > -David > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 23:27:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21473 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 23:27:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pacman.redwoodsoft.com (redwoodsoft.com [207.181.199.182]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA21430 for ; Tue, 28 Jul 1998 23:26:59 -0700 (PDT) (envelope-from dnelson@pacman.redwoodsoft.com) Received: (qmail 4599 invoked by uid 1000); 29 Jul 1998 06:26:08 -0000 Date: Tue, 28 Jul 1998 23:26:08 -0700 (PDT) From: Dru Nelson To: "Pitcairn, Duncan" cc: freebsd-hackers@FreeBSD.ORG Subject: I added Microsoft VPN / PPTP for NATD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I needed to VPN to work from a machine on my network so I added the code to the NATD today. It works great. (The natd and libalias code is very good, so it wasn't hard) Essentially, I added a command line paramater called 'pptpalias' with an argument of the ip address of the machine on the inside that is to be used for the pptp service (client or server). The firewall should then pass PPTP (IP GRE packets) traffic directly to that machine after translation. I read on one of the posts to this list that the linux version acts similarly. Apparently, there isn't a port number to translate (or the microsoft implmentation doesn't implement it correctly). So, this works for a single machine on the inside to any machine on the outside. This should work fine for telecommuters or a single server behind the firewall. I will be contacting someone who maintains the nat stuff to see if they want it. I'm running on 2.2.5-RELEASE. The changes are to the libalias files and the natd.c. I'm not on this list, so please reply to me in email directly... Take it easy, Dru Nelson Redwood City, California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 23:46:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25559 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 23:46:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25530 for ; Tue, 28 Jul 1998 23:46:29 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00773; Tue, 28 Jul 1998 23:42:30 -0700 (PDT) Message-Id: <199807290642.XAA00773@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eugeny Kuzakov cc: hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-reply-to: Your message of "Wed, 29 Jul 1998 09:01:28 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:42:29 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi ! > > One question. Is FreeBSD will support PAM ? I don't know of anyone with plans to add PAM support, no. I ported the Linux-PAM code some time back, but PAM is inherently flawed and the effort involved in making it work would not necessarily produce a useful result. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 28 23:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25616 for freebsd-hackers-outgoing; Tue, 28 Jul 1998 23:47:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from notabene.zer0.org (sac-port55.jps.net [209.63.114.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25597 for ; Tue, 28 Jul 1998 23:46:55 -0700 (PDT) (envelope-from gsutter@n1.dyn.ml.org) Received: (from gsutter@localhost) by notabene.zer0.org (8.8.7/8.8.8) id XAA15109; Tue, 28 Jul 1998 23:51:33 -0700 (PDT) (envelope-from gsutter) Message-ID: <19980728235132.C14997@notabene.zer0.org> Date: Tue, 28 Jul 1998 23:51:32 -0700 From: Gregory Sutter To: The Hermit Hacker , hackers@FreeBSD.ORG Subject: Re: IP masquarading with Ethernet/ADSL? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from The Hermit Hacker on Wed, Jul 29, 1998 at 01:13:12AM -0300 Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 01:13:12AM -0300, The Hermit Hacker wrote: > > On Friday, I finally get ADSL to home. The phone company provides > one ethernet card for my machine, and one IP. I have a growing network of > computers that I'd like to have hidden behind my "gateway" machine. > > Now, with PPP, I've done it already, and its pretty simple...but > what is involved in doing it with two ethernet cards? Just as easy? > Pointers to a WWW page or docs? Just as easy, except you're using natd instead of ppp's built-in natd aliasing library. Man natd(8). Congrats on your ADSL. I'm still on a 33.6 modem... Greg -- Gregory S. Sutter Bureaucrats cut red tape -- lengthwise. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 00:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28265 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 00:02:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28172 for ; Wed, 29 Jul 1998 00:01:59 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA25105; Wed, 29 Jul 1998 09:01:21 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 29 Jul 1998 09:01:19 +0200 (MET DST) Mime-Version: 1.0 To: Jerry Hicks Cc: hackers@FreeBSD.ORG Subject: Re: bin/7393 References: <199807282135.RAA00754@jhicks.glenatl.glenayre.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 29 Jul 1998 09:01:18 +0200 In-Reply-To: Jerry Hicks's message of "Tue, 28 Jul 1998 17:35:51 -0400" Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA28229 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Cc: to -hackers in case someone there has a bright idea) Jerry Hicks writes: > AHA! jhicks:/etc/malloc.conf was -> AJ > > Move this out of the way and 'du -c' doesn't dump core. Put this onto any > other system and that one will SIGSEGV! Ah, now we're making some progress :) root@niobe /etc# ln -s AJ malloc.conf root@niobe /etc# du -c /tmp 1 /tmp/.X11-unix 1 /tmp/.sockets 2324 /tmp Segmentation fault (core dumped) > Now... what does all this mean? I think there's still a bug lurking > in there somewhere. Definitely, but it's probably in the FTS code. I'll have to start reading that now... DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 00:11:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29641 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 00:11:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29630 for ; Wed, 29 Jul 1998 00:11:27 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id HAA10004; Wed, 29 Jul 1998 07:56:39 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807290656.HAA10004@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: The Hermit Hacker cc: hackers@FreeBSD.ORG Subject: Re: IP masquarading with Ethernet/ADSL? In-reply-to: Your message of "Wed, 29 Jul 1998 01:13:12 -0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 07:56:37 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Natd does the same as ppps -alias switch and runs on an arbitrary interface. If it doesn't come with your release your best bet is to upgrade. > Morning... > > On Friday, I finally get ADSL to home. The phone company provides > one ethernet card for my machine, and one IP. I have a growing network of > computers that I'd like to have hidden behind my "gateway" machine. > > Now, with PPP, I've done it already, and its pretty simple...but > what is involved in doing it with two ethernet cards? Just as easy? > Pointers to a WWW page or docs? > > Thanks... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 00:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06442 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 00:57:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06436 for ; Wed, 29 Jul 1998 00:57:27 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id IAA08172; Wed, 29 Jul 1998 08:58:28 +0100 (BST) Date: Wed, 29 Jul 1998 08:58:28 +0100 (BST) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: Still confused with PTDpde/APTDpde In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, zhihuizhang wrote: > > I spend another day thinking about the usage of PTDpde/APTDpde in pmap.c > and still confused with them. It must have something to do with VA->PA > translation and mixed assembly / C programming: > > (1) First of all, If we have the following lines in GAS: > > .global _xx > .set _xx, 30 > > We have defined a global (absolute?) symbol _xx whose value is 30. Now, I > refer to _xx in C by xx. What is the value (left or right?) of xx? In > other words, is the address of xx 30 or is the value of xx 30? The address of xx is 30. If we declare xx in C as: pd_entry_t xx; then one can use xx to reference the pd_entry_t which is stored at address 30. > > (2) If the value of xx is 30. Then look at locore.s where PTDped/APTDpde > is defined in the same way. Both PTDpde and APTDpde has very special > values (an address whose PDE, PTE, offset parts are the same). The > question is what is the meaning of (unsigned)PTDpde & PG_FRAME and > (unsigned)APTDpde & PG_FRAME in pmap.c? To make sense, the address (not > value) of xx must be 30. That is correct. The meaning of '(unsigned)PTDpde & PG_FRAME' is 'the physical address of the page directory of the current address space' (since PTmap maps the current address space's ptes). The meaning of '(unsigned)APTDpde & PG_FRAME is 'the physical address of the page directory of the alternate address space'. Note that both PTDpde and APTDpde reference pd_entry_t's in the current address space. > > (3) If this is correct, only PTDpde works well because we set up the > self-referential pde entry in pmap_pinit(). But for APTDpde, it does not > work the same way. How can APTDpde used to access other process's page > tables? This confused me as well when I reviewed the i386 pmap before porting it to alpha. When we access an alternate address space's page tables, we install it in APTmap by setting APTDpde to the alternate's page directory. Since the alternate address space has its own self referencial mapping at directory index PTDPTDI, the page directory for it is available at address APTD. This kind of thing is a whole lot easier on the alpha since there is a 1-1 virtual-physical window which can be used to access page tables. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 01:48:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13964 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 01:48:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13957 for ; Wed, 29 Jul 1998 01:48:21 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA02987 ; Wed, 29 Jul 1998 10:46:35 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA29418; Wed, 29 Jul 1998 10:46:34 +0200 To: "Ron 'The Insane One' Rosson" Cc: et-users@etinc.com, freebsd-hackers@FreeBSD.ORG Subject: Re: [et-users] BPF & FreeBSD References: <199807281421.KAA20691@etinc.com> <19980728075820.A16948@oneinsane.net> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 29 Jul 1998 10:46:29 +0200 In-Reply-To: "Ron 'The Insane One' Rosson"'s message of Tue, 28 Jul 1998 07:58:20 -0700 Message-ID: Lines: 11 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron 'The Insane One' Rosson" writes: > Do you know of a prgram that runs under FreeBSD that will let me > watch the traafic like trafshow. This is a great thing to have when > you are trying to tighten security on your box. any assistance in > this would be awesome. How about, for instance, trafshow? DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 01:55:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15226 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 01:55:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15210 for ; Wed, 29 Jul 1998 01:55:10 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA03313 ; Wed, 29 Jul 1998 10:54:07 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA29424; Wed, 29 Jul 1998 10:54:06 +0200 To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Call for testers for 3c905B driver References: <199807282035.QAA27573@skynet.ctr.columbia.edu> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 29 Jul 1998 10:54:05 +0200 In-Reply-To: Bill Paul's message of Tue, 28 Jul 1998 16:35:53 -0400 (EDT) Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul writes: > Note that the vortex driver (if_vx.c) already supports the 3c900 and > original 3c905 cards, but it uses PIO to transfer packets to and from > the NIC's RAM. My driver uses bus master DMA instead. If you want to > use my driver instead of the vortex driver for the 3c900 and 3c905 > cards, you should edit /sys/pci/if_vx_pci.c and comment out the > portion of vx_pci_probe() that checks the PCI device IDs for the > Etherlink XL cards, otherwise the vortex driver may be assigned to > them instead of mine. What's wrong with just leaving it out of the kernel? DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 02:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17610 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 02:12:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17605 for ; Wed, 29 Jul 1998 02:12:33 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id LAA07087; Wed, 29 Jul 1998 11:12:45 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 29 Jul 1998 11:12:45 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Eugeny Kuzakov , hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-Reply-To: <199807290642.XAA00773@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Mike Smith wrote: > > Hi ! > > > > One question. Is FreeBSD will support PAM ? > > I don't know of anyone with plans to add PAM support, no. I ported the > Linux-PAM code some time back, but PAM is inherently flawed and the > effort involved in making it work would not necessarily produce a > useful result. Still, I think something should be decided wrt. the way various auth. schemes can be plugged in without doing it each time from the grounds. Thus far it was done by patching by hand the appropriate programs, which is clumsy and sometimes leaves us with almost indentical sections of auth. code (cf. ftp & login) which have to be maintained together with millions of #ifdef's, etc etc... There is already existing framework of *CAP_AUTH, which was meant to be used together with login_* modules. Is it dead or something? If it's dead, let's bury its remains, and if not - let's start to write login_* modules. Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 02:34:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19735 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 02:34:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19725 for ; Wed, 29 Jul 1998 02:34:05 -0700 (PDT) (envelope-from hamada@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id SAA13906; Wed, 29 Jul 1998 18:33:16 +0900 (JST) Received: from stone.astec.co.jp (stone.astec.co.jp [172.20.26.2]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id SAA28274; Wed, 29 Jul 1998 18:33:15 +0900 (JST) Received: (from hamada@localhost) by stone.astec.co.jp (8.8.5/3.5W-solaris1-1.2) id SAA14287; Wed, 29 Jul 1998 18:33:13 +0900 (JST) Date: Wed, 29 Jul 1998 18:33:13 +0900 (JST) Message-Id: <199807290933.SAA14287@stone.astec.co.jp> From: HAMADA Naoki References: <199807282035.QAA27573@skynet.ctr.columbia.edu> To: smoergrd@oslo.geco-prakla.slb.com CC: wpaul@skynet.ctr.columbia.edu, hackers@FreeBSD.ORG In-reply-to: Dag-Erling Coidan Sm,Ax(Brgrav's message of "29 Jul 1998 10:54:05 +0200" Subject: Re: Call for testers for 3c905B driver Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DES writes: >Bill Paul writes: >> Note that the vortex driver (if_vx.c) already supports the 3c900 and >> original 3c905 cards, but it uses PIO to transfer packets to and from >> the NIC's RAM. My driver uses bus master DMA instead. If you want to >> use my driver instead of the vortex driver for the 3c900 and 3c905 >> cards, you should edit /sys/pci/if_vx_pci.c and comment out the >> portion of vx_pci_probe() that checks the PCI device IDs for the >> Etherlink XL cards, otherwise the vortex driver may be assigned to >> them instead of mine. >What's wrong with just leaving it out of the kernel? If you simply get rid of the vx driver, support for 3C59[0257] drivers is lost. Only its probe code for 3C90[05] must be omitted from the vx driver. - nao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 03:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25913 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 03:23:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25908 for ; Wed, 29 Jul 1998 03:23:31 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA03226; Wed, 29 Jul 1998 05:56:05 -0400 (EDT) From: Peter Dufault Message-Id: <199807290956.FAA03226@hda.hda.com> Subject: Re: sysexits In-Reply-To: <199807262053.NAA15723@usr01.primenet.com> from Terry Lambert at "Jul 26, 98 08:53:52 pm" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 29 Jul 1998 05:56:05 -0400 (EDT) Cc: 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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What's wrong with errx(1, "[mcre]alloc failed")? > > The inherent unportability of such code to non-4.4-BSD derived > systems, perhaps? For me this is a no-brainer: errx et al is an acceptable interface spec when working on system utilities running on a system that dictate using this interface in style(9). One could define (and probably one has defined) a better interface, but one probably has better things to do with one's time. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 03:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26076 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 03:25:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26071 for ; Wed, 29 Jul 1998 03:25:28 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id GAA05922; Wed, 29 Jul 1998 06:24:49 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id GAA03466; Wed, 29 Jul 1998 06:57:20 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id GAA00451; Wed, 29 Jul 1998 06:28:52 -0400 (EDT) Date: Wed, 29 Jul 1998 06:28:52 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807291028.GAA00451@lakes.dignus.com> To: dg@root.com, freebsd-hackers@FreeBSD.ORG, rob@perihelion.co.uk Subject: 'daily panic' reproduction [was re: fsck errors] In-Reply-To: <199807290908.KAA42650@betty.perihelion.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See below... "Rob McIntyre" writes: > > Hi, > > I'm currently trying to debug a version of FreeBSD that has been > ported onto our Helios operating system. > After running newfs on an ide device, fsck produces errors indicating > that some number of inodes are partially allocated and others are of > an unknown file type (shown below). Could you tell me more about > what these messages actually mean and maybe give me some > advice on tracking down such file system errors during the fast file > system creation in newfs. > Any help would be grately appreciated. > > Rob. > > R.A.McIntyre MSc, > > Perihelion Distributed Software > Tel: 44 (0) 1749 344345 > Fax: +44 (0) 1749 344977 > http://www.perihelion.co.uk > > > PARTIALLY ALLOCATED INODE INODE # 0x68 > +++ > +++ INODE DISK BLOCK ADDRESS = 0x342cd0 > +++ > +++ > +++ > +++ CLEAR? yes > +++ UNKNOWN FILE TYPE INODE # 0x6d > +++ > +++ > +++ > +++ CLEAR? yes > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > Rob - I've redirected this to -hackers. But; if you'll look in the mail archives for subjects containing "daily panic", and "freeing free block", you'll see a long running discussing of this problem. Just f.y.i. - a newfs'd partition should fsck completely clean assuming you haven't mounted it and changed it in any way. What you describe is exactly my stand-alone reproduction of the problem. I can write 0xff to a disk partition, newfs that partition and then run fsck on that newfs'd partition to find out some of the bytes didn't actually make it. I believe that in a running system; this particular bug causes the spurious problems some people have seen. I don't know exactly what Helios is... but I hope it can help find this problem... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 03:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27823 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 03:40:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bock.nettek-llc.com (d01a84d8.dip.cdsnet.net [208.26.132.216]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27803; Wed, 29 Jul 1998 03:40:34 -0700 (PDT) (envelope-from stevel@mail.cdsnet.net) Received: from mail.cdsnet.net (localhost.nettek-llc.com [127.0.0.1]) by bock.nettek-llc.com (8.8.8/8.8.8) with ESMTP id DAA14041; Wed, 29 Jul 1998 03:39:51 -0700 (PDT) (envelope-from stevel@mail.cdsnet.net) Message-ID: <35BEFBF6.AB1CA850@mail.cdsnet.net> Date: Wed, 29 Jul 1998 03:39:51 -0700 From: Steve Logue Organization: http://www.nettek-llc.com/ X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: david@sparks.net CC: freebsd-hackers@FreeBSD.ORG, freebsd-database@FreeBSD.ORG Subject: Re: Informix on linux emulation?? References: Content-Type: multipart/alternative; boundary="------------FCC571C30909AE3EC8E3C359" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------FCC571C30909AE3EC8E3C359 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit david@sparks.net wrote: > I see that Informix SE is now available for caldera and suse versions of > linux. Somewhere on Informix's web page it seemed they were very > sensitive to the glibc version, which may (?) be a problem for us. I believe this reference to glibc was related to the ESQL (embedded SQL) portion only. > > > > > Has anyone tried running this under the linuxulator? Yep, and so far things are pretty good. There are no docs to speak of in the bundle, so one has to RTFM Informix's WWW site PDF files. Also, I'm getting a linux emulator error occasionally, but have not completely tracked down what operation is causing it. I think it is the opening of a TCP connection right after starting sqlexecd. This is the error that I get: LINUX: 'ioctl' fd=5, typ=0x89(e), num=0x2 not implemented ^^^ NOTE: The "e" is actually the european "e" with two dots over it. -STEVEl P.S. How does one type special characters in X applications? (Like ALT-### on the console)? --------------FCC571C30909AE3EC8E3C359 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit david@sparks.net wrote:
I see that Informix SE is now available for caldera and suse versions of
linux.  Somewhere on Informix's web page it seemed they were very
sensitive to the glibc version, which may (?) be a problem for us.
I believe this reference to glibc was related to the ESQL (embedded SQL) portion only.
 

 

Has anyone tried running this under the linuxulator?

Yep, and so far things are pretty good.  There are no docs to speak of in the bundle, so one has to RTFM Informix's WWW site PDF files.  Also, I'm getting a linux emulator error occasionally, but have not completely tracked down what operation is causing it.  I think it is the opening of a TCP connection right after starting sqlexecd.  This is the error that I get:
 

LINUX: 'ioctl' fd=5, typ=0x89(e), num=0x2 not implemented
                             ^^^

NOTE: The "e" is actually the european "e" with two dots over it.
 

-STEVEl

P.S.  How does one type special characters in X applications?  (Like ALT-### on the console)? --------------FCC571C30909AE3EC8E3C359-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 07:01:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29317 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 07:01:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29300 for ; Wed, 29 Jul 1998 07:01:13 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA26612; Wed, 29 Jul 1998 10:01:45 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 29 Jul 1998 10:01:45 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: The Hermit Hacker cc: hackers@FreeBSD.ORG Subject: Re: IP masquarading with Ethernet/ADSL? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it might be a bit outdated... but you can look at my page: step by step. http://www.cs.sunyit.edu/~perlsta -> freebsd good luck, -Alfred On Wed, 29 Jul 1998, The Hermit Hacker wrote: > > Morning... > > On Friday, I finally get ADSL to home. The phone company provides > one ethernet card for my machine, and one IP. I have a growing network of > computers that I'd like to have hidden behind my "gateway" machine. > > Now, with PPP, I've done it already, and its pretty simple...but > what is involved in doing it with two ethernet cards? Just as easy? > Pointers to a WWW page or docs? > > Thanks... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 07:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06622 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 07:37:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06615 for ; Wed, 29 Jul 1998 07:37:38 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id JAA09936; Wed, 29 Jul 1998 09:35:08 -0500 (CDT) Message-ID: <35BF331C.F304302D@webwizard.org.mx> Date: Wed, 29 Jul 1998 09:35:08 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Questions about vn driver... References: <199807290624.XAA00574@antipodes.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > [previously posted to freebsd-questions, to no avail...] > > > > Folks: > > > > How do you format a vn disk image as a ufs file system? I am attempting > > to set up a 650 megabyte file for use as scratch space for assembling a > > CD-ROM image, but cannot figure out how to format the "disk". Newfs > > reports a pretty obvious error: there's no disktab entry for such a > > beast. > > > > Here's my plan: > > > > 1) create ~/cdimage as a 650 megabyte file > > 2) issue 'vnconfig /dev/vn0c ~/cdimage' > > That should have '-o slices' in it. > > 2.5) 'disklabel -rw vn0 auto' I cannot get this to work. I get the following on my current as of yesterday. disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device disklabel: auto: unknown disk type Thanks ed > > > > > > 3) newfs /dev/rvn0c -- THIS DOESN'T WORK > > 4) fill up the new 650MB "disk", then 'mkisofs ~/cdimage | cdrecord' > > when full... > > > > Hints? Suggestions? Or is the vn driver not intended for this > > sort of thing? > > > > -David > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 08:54:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18703 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 08:54:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles311.castles.com [208.214.167.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18677 for ; Wed, 29 Jul 1998 08:54:43 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03000; Wed, 29 Jul 1998 08:53:20 -0700 (PDT) Message-Id: <199807291553.IAA03000@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Edwin Culp cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Questions about vn driver... In-reply-to: Your message of "Wed, 29 Jul 1998 09:35:08 CDT." <35BF331C.F304302D@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 08:53:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > > > [previously posted to freebsd-questions, to no avail...] > > > > > > Folks: > > > > > > How do you format a vn disk image as a ufs file system? I am attempting > > > to set up a 650 megabyte file for use as scratch space for assembling a > > > CD-ROM image, but cannot figure out how to format the "disk". Newfs > > > reports a pretty obvious error: there's no disktab entry for such a > > > beast. > > > > > > Here's my plan: > > > > > > 1) create ~/cdimage as a 650 megabyte file > > > 2) issue 'vnconfig /dev/vn0c ~/cdimage' > > > > That should have '-o slices' in it. Actually, that should have been '-s labels'. I was too tired. > > 2.5) 'disklabel -rw vn0 auto' > > I cannot get this to work. I get the following on my current > as of yesterday. > > disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device > disklabel: auto: unknown disk type If you got the 'vnconfig' wrong at any point, you'll have to go pick a new vn device. Are you running on a very old (pre-2.2) system? The lack of 'auto' would imply that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 09:01:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20573 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 09:01:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agustina.kjsl.com (Agustina.KJSL.COM [198.137.202.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20559 for ; Wed, 29 Jul 1998 09:01:17 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from uucp@localhost) by agustina.kjsl.com (8.8.7/8.8.8/rchk1.19) with UUCP id IAA25292; Wed, 29 Jul 1998 08:56:56 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.8/rchk1.19) id IAA03257; Wed, 29 Jul 1998 08:43:18 -0700 (PDT) (envelope-from fmc) Message-Id: <199807291543.IAA03257@daemonweed.reanimators.org> To: Ted Faber Cc: Frank McConnell , Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? References: <199807281812.LAA18644@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 29 Jul 1998 08:43:17 -0700 In-Reply-To: Ted Faber's message of Tue, 28 Jul 1998 11:12:59 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Faber wrote: > If the chip *does* work in native PCI mode, maybe we should > concentrate on bringing up the controller in direct PCI mode. I don't > have the relevent chip specs, but if you can tell me anything I'll be > happy to help. If it's IC data sheets you're looking for, webulate to: http://www.amd.com/products/npd/techdocs/techdocs.html Bring a PDF reader, you'll need it. I've given the register-set for the 79C970A a cursory reading and there seems to be some notion of a software-style setting that can be used to make the chip behave like previous AMD Ethernet chips. My first thought was that maybe the Hitachi BIOS is doing some of the chip setup, but I don't understand what it would do that would let the lnc code work with the device-as-ISA-unit work but not as-PCI-unit. And I still don't get this: >As far as I can tell, there's no support for using the Hitachi's >internal PCI lance board in native PCI mode, so the card can only be >used in ISA emulation mode. What led you to that conclusion? -Frank McConnell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 09:28:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27207 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 09:28:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27194 for ; Wed, 29 Jul 1998 09:28:53 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from ivy.ezo.net (c3po.skylan.net [206.150.211.243]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id MAA05849; Wed, 29 Jul 1998 12:26:36 -0400 (EDT) Message-ID: <002a01bdbb0d$f778cce0$f3d396ce@ivy.ezo.net> From: "Jim Flowers" To: "Robert Swindells" Cc: Subject: Re: AMD PCNet/FAST cards; suppliers? Date: Wed, 29 Jul 1998 12:28:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll be glad to try on my Cyrix with built-in Am79C971 which just started working with the ISA patch. I'm about to put Luigi Rizzo's dummynet on it so I could also look at some transport variations. Jim Flowers -----Original Message----- From: Robert Swindells To: faber@ISI.EDU Cc: mike@smith.net.au ; fmc@reanimators.org ; hackers@FreeBSD.ORG Date: Tuesday, July 28, 1998 8:51 PM Subject: Re: AMD PCNet/FAST cards; suppliers? > >>Mike Smith wrote: >>>> Robert Swindells wrote: >>>> For all I know there is some way to tell the card not to do the ISA >>>> emulation, but that's been pushed to the copious free time list so I >>>> may not find out soon. > >[I didn't write this] > >>> >>>No. ISA and PCI share an I/O space, but that's about it. >>> >>>I'm sorry; this is breakage in both 2.2.7 and -current, and we're going >>>to need a better way of identifying the problem cases like the Hitachi >>>(or a better workaround). 8( > >>So, if this is a known chip that works on other machines, what's so >>different about the Hitachi MX-133? I'm happy to run any diagnostics >>that you guys think will help find the differences. > >If I send you an updated version of the driver, are you able to try it >out on your VisionBook ? > >Robert Swindells > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 09:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02665 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 09:53:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles311.castles.com [208.214.167.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02636 for ; Wed, 29 Jul 1998 09:53:24 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA03255; Wed, 29 Jul 1998 09:51:38 -0700 (PDT) Message-Id: <199807291651.JAA03255@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Thomas David Rivers cc: dg@root.com, freebsd-hackers@FreeBSD.ORG, rob@perihelion.co.uk Subject: Re: 'daily panic' reproduction [was re: fsck errors] In-reply-to: Your message of "Wed, 29 Jul 1998 06:28:52 EDT." <199807291028.GAA00451@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 09:51:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > See below... > > "Rob McIntyre" writes: > > > > Hi, > > > > I'm currently trying to debug a version of FreeBSD that has been > > ported onto our Helios operating system. > > After running newfs on an ide device, fsck produces errors indicating > > that some number of inodes are partially allocated and others are of > > an unknown file type (shown below). Could you tell me more about > > what these messages actually mean and maybe give me some > > advice on tracking down such file system errors during the fast file > > system creation in newfs. The first thing I would be worrying about would be whether you're suffering a subtle problem with your IDE interface; if you're hosting over the top of Helios, I presume that you're using a virtual disk emulation? Failing that, it could be that you have the Dave Rivers Memorial Problem; note that nobody has been able to reproduce his symptoms in a controlled environment so we can't actually tell what's going on. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 10:10:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04920 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 10:10:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from betty.perihelion.co.uk (b5.perihelion.co.uk [195.40.119.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04913; Wed, 29 Jul 1998 10:10:40 -0700 (PDT) (envelope-from rob@perihelion.co.uk) Received: from dilbert.perihelion.co.uk (dilbert.perihelion.co.uk [10.1.1.153]) by betty.perihelion.co.uk (8.7.6/8.6.10) with SMTP id SAA05761; Wed, 29 Jul 1998 18:04:53 +0100 Message-Id: <199807291704.SAA05761@betty.perihelion.co.uk> From: "Rob McIntyre" Organization: PDS To: freebsd-hackers@FreeBSD.ORG, freebds-questions@FreeBSD.ORG Date: Wed, 29 Jul 1998 18:05:08 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: fsck errors: partially allocated inodes Reply-to: rob@perihelion.co.uk X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To my potential saviour, I am trying to debug a version of newfs that has been ported to the Helios operating system. After running newfs on the ide device, I get spurious errors including the following: partially allocated inode = 0x68 unknown file type inode = 0x9a in blkerror The errors seem to come in blocks of partially allocated inodes followed by an arbitrary amount of unknown file types messages. I have experimented useing various disk layouts and still the errors occcur in the same place on the ide disk. I would be grateful for any advice on the true meaning of these errors and for debugging newfs and fsck which is not a very pleasent task with 214MB devices. Thanx Rob. R.A.McIntyre MSc, Perihelion Distributed Software Tel: 44 (0) 1749 344345 Fax: +44 (0) 1749 344977 http://www.perihelion.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 10:54:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13873 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 10:54:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13860 for ; Wed, 29 Jul 1998 10:54:39 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA12867; Wed, 29 Jul 1998 10:53:39 -0700 (PDT) Message-Id: <199807291753.KAA12867@tnt.isi.edu> To: Frank McConnell Cc: Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "29 Jul 1998 08:43:17 PDT." <199807291543.IAA03257@daemonweed.reanimators.org> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 10:53:39 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Frank McConnell wrote: >Ted Faber wrote: >>As far as I can tell, there's no support for using the Hitachi's >>internal PCI lance board in native PCI mode, so the card can only be >>used in ISA emulation mode. > >What led you to that conclusion? As I mentioned, I'm just msireading the code here. I didn't see anything that appeared PCI specific, and wasn't seeing my card work. I'm no expert in either the PCI bus or this chipset - I was just trying to get the laptop's internal ethernet running so it was of some use to me. I understand now that others use the driver with PCI cards. I understand I was wrong. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb9hoYb4eisfQ5rpAQEw8QP+JZU2AqiqLWJQLl5efXPf9qy3Oy/okWwI yMLPKx4J+glIoj323B5kKj+HTMiU1vjEi2hyI05/1XFteldHH7C+B0LC4A2+M7CR cS/PanFVwDB3z5LrXoudjcrHByIitVrrLrnSbKyD3bsurBB3YA1COcMCcrbiyeah uwK1qLI5fqQ= =fMdB -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 11:00:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15554 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 11:00:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15534 for ; Wed, 29 Jul 1998 11:00:37 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA13548; Wed, 29 Jul 1998 10:59:40 -0700 (PDT) Message-Id: <199807291759.KAA13548@tnt.isi.edu> To: Robert Swindells Cc: fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "Tue, 28 Jul 1998 11:26:41 PDT." <199807281826.LAA19784@tnt.isi.edu> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 10:59:40 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I may be using a wrong term here. The interface probed successfully as lnc0 during the ISA device probes after having been probed and discarded as lnc1 during the PCI setup. That sounds like ISA emulation to me, but again, I'm no expert on the two bus specs or the chipset. > >We have been using this chip on a laptop motherboard & it works fine >as a PCI device. > >I'll send you a driver to try later. The driver you sent me works without a hitch (so far). This driver does what I expect a pure PCI driver would do: the interface probes on lnc1 as a PCI device and the subsequent probe at the ISA port fails. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNb9jCob4eisfQ5rpAQFBVgP+JGMNEEPzTy7S32/ygWq/t2M+c9+OfnhO +wMV90mXl5T1ArREW8Yqjh0gtrDidwCRj8aXOHn+2ciWBpumPQi08PssFcD7z4cQ ZnbOcxv5QLsjhj+4UfsS04vXu3o5mwSLbV4baYbvm3nWpyv3lyqcaYncb3XLrK9r ubZ+i/iojoM= =+fn/ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 11:15:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19749 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 11:15:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iq.org (proff@polysynaptic.iq.org [203.4.184.222]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA19695 for ; Wed, 29 Jul 1998 11:15:10 -0700 (PDT) (envelope-from proff@iq.org) From: proff@iq.org Received: (qmail 19520 invoked by uid 110); 29 Jul 1998 18:14:18 -0000 Message-ID: <19980729181418.19519.qmail@iq.org> Subject: Berg coding style (was qpopper trauma) In-Reply-To: <199807291638.AAA02315@spinner.netplex.com.au> from Peter Wemm at "Jul 30, 98 00:38:49 am" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 30 Jul 1998 04:14:17 +1000 (EST) Cc: jkb@best.com, showboat@hotmail.com, 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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The cucipop code truely has to be seen to be believed...... eg: > ======= > } > } > ;{ int namelen=sizeof peername; > if(getpeername(fileno(sockin),(struct sockaddr*)&peername,&namelen)&& > !debug&&(errno==ENOTSOCK||errno==EINVAL)) > { int serverfd,curfd; > signal(SIGHUP,SIG_IGN);signal(SIGPIPE,SIG_IGN);fclose(stdin); > fclose(stdout);serverfd=socket(AF_INET,SOCK_STREAM,TCP_PROT); > peername.sin_family=AF_INET;peername.sin_addr.s_addr=INADDR_ANY; > peername.sin_port=htons(port);curfd=-1; > setsockopt(serverfd,SOL_SOCKET,SO_REUSEADDR,&curfd,sizeof curfd); > if(bind(serverfd,(struct sockaddr*)&peername,sizeof peername)) > ======= > > I've heard 'you can write fortran code in any language'.. I suspect this > is C written by an assembler programmer. The handcrafted optimization > reminds me of dark periods in my past of trying to save every last clock > cycle and/or byte of memory. That's actually pretty tame for Berg code (S. R. van den Berg). My favourite is the following line from bregex.c (Berg's record-beating posix compatible regex pattern matcher included in nntpcache): while((jump=jt[*(jstr+=jump)])); For the uninitiated the above is a full blown Boyer-Moore loop. regexp.c in procmail is worth a glance too. Cheers, Julian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 11:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21189 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 11:19:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21170 for ; Wed, 29 Jul 1998 11:19:30 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from ivy.ezo.net (c3po.skylan.net [206.150.211.243]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id OAA08526; Wed, 29 Jul 1998 14:17:15 -0400 (EDT) Message-ID: <005601bdbb1d$6cca87e0$f3d396ce@ivy.ezo.net> From: "Jim Flowers" To: "Ted Faber" Cc: Subject: Re: AMD PCNet/FAST cards; suppliers? Date: Wed, 29 Jul 1998 14:19:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are also application notes in pdf format that are useful in understanding the configuration requirements and some debugging software at their website. I also found the linux 32 bit lance.c driver to be quite helpful as it is heavily commented (and it works). -----Original Message----- From: Frank McConnell To: Ted Faber Cc: Frank McConnell ; Mike Smith ; Robert Swindells ; hackers@FreeBSD.ORG Date: Wednesday, July 29, 1998 12:51 PM Subject: Re: AMD PCNet/FAST cards; suppliers? >Ted Faber wrote: >> If the chip *does* work in native PCI mode, maybe we should >> concentrate on bringing up the controller in direct PCI mode. I don't >> have the relevent chip specs, but if you can tell me anything I'll be >> happy to help. > >If it's IC data sheets you're looking for, webulate to: > >http://www.amd.com/products/npd/techdocs/techdocs.html > >Bring a PDF reader, you'll need it. > >I've given the register-set for the 79C970A a cursory reading and >there seems to be some notion of a software-style setting that can be >used to make the chip behave like previous AMD Ethernet chips. My >first thought was that maybe the Hitachi BIOS is doing some of the >chip setup, but I don't understand what it would do that would let the >lnc code work with the device-as-ISA-unit work but not as-PCI-unit. >And I still don't get this: > >>As far as I can tell, there's no support for using the Hitachi's >>internal PCI lance board in native PCI mode, so the card can only be >>used in ISA emulation mode. > >What led you to that conclusion? > >-Frank McConnell > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 11:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28457 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 11:45:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (root@lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28430 for ; Wed, 29 Jul 1998 11:45:47 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from ivy.ezo.net (c3po.skylan.net [206.150.211.243]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id OAA09107 for ; Wed, 29 Jul 1998 14:43:32 -0400 (EDT) Message-ID: <008801bdbb21$18cdd760$f3d396ce@ivy.ezo.net> From: "Jim Flowers" To: Subject: SKIP/FreebSD/Win95 Date: Wed, 29 Jul 1998 14:45:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking for some help in modifying the 1.0 reference implementation of SKIP for FreeBSD to use RC2-40 and/or RC4-40 to allow operation with the commercial or evaluation versions of SKIP for Win95 and NT4. I have located code (ActiveX, unfortunately) and documentation for the RC algorithms that indicates it is a drop-in replacement for DES which makes it sound straightforward. Unfortunately, I don't think my skill level is enough to do it. Anybody with the interest and time to tackle this? Jim Flowers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 12:04:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03731 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 12:04:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ultra6 (ultra6.cc.binghamton.edu [128.226.4.26]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA03656 for ; Wed, 29 Jul 1998 12:04:49 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by ultra6 (SMI-8.6/8.6.9) with SMTP id PAA01509; Wed, 29 Jul 1998 15:04:06 -0400 Date: Wed, 29 Jul 1998 15:04:05 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@ultra6 To: Doug Rabson cc: hackers Subject: Re: Still confused with PTDpde/APTDpde In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The address of xx is 30. If we declare xx in C as: > > pd_entry_t xx; > > then one can use xx to reference the pd_entry_t which is stored at address > 30. So the compiler treats .set directives as setting the addresses of absolute symbols. If I understand correctly, PTmap, PTD, PTDpde, APTmap, APTD, and APTDpde are all stored at fixed virtual addresses -- special VAs that are inaccessible to normal use. > > This confused me as well when I reviewed the i386 pmap before porting it > to alpha. When we access an alternate address space's page tables, we > install it in APTmap by setting APTDpde to the alternate's page directory. > Since the alternate address space has its own self referencial mapping at > directory index PTDPTDI, the page directory for it is available at > address APTD. > After hard thinking, I finally notice that APTDpde is set as .set _APTDpde,_PTD + (APTDPTDI * PDESIZE) NOT as .set _APTDpde,_APTD + (APTDPTDI * PDESIZE) So what you said above makes sense to me. Also, I find a possible bug in the same place (locore.s - Stable FreeBSD). Instead of .set _APTD,_APTmap + (APTDPTDI * PAGE_SIZE) we should say .set _APTD,_APTmap + (PTDPTDI * PAGE_SIZE) Fortunately, the symbol _APTD (in assembly) and the variable APTD (in C) are not in actual use. If I do not understand correctly, please let me know. Thanks very much for your help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 12:13:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06036 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 12:13:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05908 for ; Wed, 29 Jul 1998 12:12:36 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id UAA16623; Wed, 29 Jul 1998 20:13:36 +0100 (BST) Date: Wed, 29 Jul 1998 20:13:36 +0100 (BST) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: Still confused with PTDpde/APTDpde In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998, zhihuizhang wrote: > > > > The address of xx is 30. If we declare xx in C as: > > > > pd_entry_t xx; > > > > then one can use xx to reference the pd_entry_t which is stored at address > > 30. > > So the compiler treats .set directives as setting the addresses of > absolute symbols. If I understand correctly, PTmap, PTD, PTDpde, > APTmap, APTD, and APTDpde are all stored at fixed virtual addresses -- > special VAs that are inaccessible to normal use. Thats exactly right, as I understand things. > > This confused me as well when I reviewed the i386 pmap before porting it > > to alpha. When we access an alternate address space's page tables, we > > install it in APTmap by setting APTDpde to the alternate's page directory. > > Since the alternate address space has its own self referencial mapping at > > directory index PTDPTDI, the page directory for it is available at > > address APTD. > > > > After hard thinking, I finally notice that APTDpde is set as > > .set _APTDpde,_PTD + (APTDPTDI * PDESIZE) > NOT as > > .set _APTDpde,_APTD + (APTDPTDI * PDESIZE) > > So what you said above makes sense to me. Also, I find a possible bug > in the same place (locore.s - Stable FreeBSD). Instead of > > .set _APTD,_APTmap + (APTDPTDI * PAGE_SIZE) > > we should say > > .set _APTD,_APTmap + (PTDPTDI * PAGE_SIZE) > > Fortunately, the symbol _APTD (in assembly) and the variable APTD (in C) > are not in actual use. > > If I do not understand correctly, please let me know. I think that you are correct about the definition of APTD being wrong. If the meaning of APTD is intended to be, 'the directory of the alternate address space' then it should be defined in terms of PTDPTDI, not APTDPTDI. > > Thanks very much for your help. You are welcome. I have some of this fairly fresh after working on the alpha pmap and I'm glad to help. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 12:25:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10172 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 12:25:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA10154 for ; Wed, 29 Jul 1998 12:25:48 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA11837 (5.67b/IDA-1.5); Wed, 29 Jul 1998 20:04:29 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA00766; Wed, 29 Jul 1998 19:17:00 +0200 (CEST) From: Wilko Bulte Message-Id: <199807291717.TAA00766@yedi.iaf.nl> Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: <19980728150135.A14581@Alameda.net> from Ulf Zimmermann at "Jul 28, 98 03:01:35 pm" To: ulf@Alameda.net Date: Wed, 29 Jul 1998 19:17:00 +0200 (CEST) Cc: gibbs@narnia.plutotech.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Ulf Zimmermann wrote... > On Tue, Jul 28, 1998 at 03:17:50PM -0600, Justin T. Gibbs wrote: > > In article you wrote: > > > > > > Get DPT's or Adaptec's. Development of the Buslogic line seems to have > > > died. > > > > > > Given adaptec's new stance towards free OS's, and Mylex's closed-door > > > policy, I can only imagine that the Adaptec drivers will continue to > > > improve. > > > > Mylex is hardly closed-door. I had no problem getting the documentation > > required to write the FreeBSD-CAM BusLogic driver. I believe that specs > > for their RAID controllers are easy to obtain too. Just look at the > > Linux DAC960 driver. > > Mylex gave me the documentation for the DAC960 controller and even > a 3 channel DAC960PJ with 8MB EDO/ECC memory. I am still working on > learning more about stuff to continue the driver. I have so far > the detection complete (PCI, which controller version, memory, > channels, system drives, etc.) I also have a DAC960 lying here. But I need to build myself a PCI based test box before I can do anything with it. Short of stuffing in an Alpha box that is ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 13:45:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24040 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 13:45:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24011 for ; Wed, 29 Jul 1998 13:45:08 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 3932 invoked by uid 1001); 29 Jul 1998 20:44:27 +0000 (GMT) To: jlemon@americantv.com Cc: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: TCPDUMP In-Reply-To: Your message of "Tue, 28 Jul 1998 13:34:30 -0500" References: <19980728133430.54771@right.PCS> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 29 Jul 1998 22:44:27 +0200 Message-ID: <3930.901745067@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does anyone who understand the bpf code have an idea why filters > > (and trafshow) done work with a serial device with DLT_NULL header? > > > > tcpdump works fine in raw mode, but if you ad an expression it > > doesnt pass the filter tests. > > Not sure, but you may want to look at src/contrib/libpcap/gencode.c, > at the various switch statements for DLT_NULL. Perhaps the offsets > are not correct the framing protocol that you are using? Yup. DLT_NULL simply has the wrong semantics. It can be kludged, but that requires recompiling libpcap, and commenting out the special case for DLT_NULL in gen_linktype() (patch relative to libpcap-0.4a6): *** gencode.c.orig Thu Jun 12 23:23:01 1997 --- gencode.c Wed Jul 29 20:42:22 1998 *************** *** 607,618 **** --- 607,620 ---- } break; + #if 0 case DLT_NULL: /* XXX */ if (proto == ETHERTYPE_IP) return (gen_cmp(0, BPF_W, (bpf_int32)htonl(AF_INET))); else return gen_false(); + #endif } return gen_cmp(off_linktype, BPF_H, (bpf_int32)proto); } You also have to make sure that your type field is in the first two bytes of the 4-byte DLT_NULL header, in network byte order. Why is DLT_NULL wrong? From looking at the tcpdump/libpcap source code, it looks like it's meant to be used with Irix and Linux, and libcap explicitly checks for AF_INET. Also, it's a 4 byte field. What we'd like to have, is a two byte field - basically the standard Ethernet type, minus source and destination addresses. This needs to be done in cooperation with the tcpdump maintainers, of course. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 13:47:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24528 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 13:47:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24519 for ; Wed, 29 Jul 1998 13:47:41 -0700 (PDT) (envelope-from jim@reptiles.org) Received: from localhost (4043 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Wed, 29 Jul 1998 16:47:08 -0400 (EDT) (Smail-3.2.0.101 1997-Dec-17 #20 built 1998-May-20) Message-Id: From: jim@reptiles.org (Jim Mercer) Subject: proposed modification to /sbin/mount To: freebsd-hackers@FreeBSD.ORG Date: Wed, 29 Jul 1998 16:47:08 -0400 (EDT) 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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ note: i am not subscribed to hackers@freebsd.org, and would appreciate a cc: jim@reptiles.org on any responses ] i just spent some time working out the dependencies of - /etc/hosts - ypbind (NIS hosts) - named - mountd - /etc/rc (mount -vat nfs) my religion dictates that i treat / and /usr as read-only partitions (well, with the exception of /etc and some symlinks for smail3). this religion has served me well when upgrading from release to release. upgrade process: #! /bin/sh kill (sendmail/smail-3) cd /sys/i386/conf config KERNEL cd ../../compile/KERNEL make depend make make install cd /usr/src make world cd /usr/local/src/smail-3 make install reboot works pretty good for me (only problem is integrating new /etc/stuff, but the previous release generally has enough to get the machine booted). my problem is that i have several hosts, which have certain dependancies. as such, i am having some difficulties getting the systems to come up efficiently if they all get power cycled at the same time. i configured all of my nfs mounts to be -b,-i,-s, such that they shouldn't wait on other things before moving along in /etc/rc. unfortuneately, there are still dependencies on named and ypbind, which may or may not be running at the proper time. not to mention the dependencies of mountd and nfsd. for the time being, i have moved "mount -vat nfs" in /etc/rc to the bottom, just before /etc/rc.local is called. this has made things work ok, but it has caused me to spit in the face of my god, in that next time i upgrade, i need to remember to make the same adjustment to /etc/rc. anyways, i got to thinking about how to do this without modifying /etc/rc. one thing i could do is mark all of my nfs mounts as noauto, and then stick a script in /usr/local/etc/rc.d which mounts them at the end of /etc/rc. unfortunately, i have other nfs mounts which are marked noauto, which i don't want mounted on boot (moreso for convienience, or security). this would make the /usr/local/etc/rc.d script rather ugly, and probably dependent on some other table which would mean more maintenance. i could put my nfs hostnames in /etc/hosts or in NIS hosts, but, again, this means more maintenance and/or version skew if i don't keep the hosts file in sync with my DNS. ok, for the meat of my proposal: in /etc/fstab there is a field, pass, which is intended to optimize the fsck passes on boot up. obviously, for NFS (and other filesystems), this field is not used. however, if we modified /sbin/mount such that it had an additional argument to specify a pass #, then we could sprinkle a number of mount -vat nfs type calls in /etc/rc, and have file systems mounted at various points. the modification would be backwards compatable, in that if it is not specified, then the pass field is ignored. it can be done such that the pass field is only used for specific file system types. i gave some thought to having /sbin/mount pass the flag to the next mount process (ie. /sbin/mount_nfs), but that would require changes to each of the sub mount programs, which could cause future problems. in any case, if the powers that be are interested in this, i am willing to put the effort in to make the changes and submit it for review/inclusion in the distribution. if not, then i'll focus my efforts on making a grotty /usr/local/etc/rc.d script. 8^( -- [ Jim Mercer Reptilian Research jim@reptiles.org +1 416 410-5633 ] [ The telephone, for those of you who have forgotten, was a commonly used ] [ communications technology in the days before electronic mail. ] [ They're still easy to find in most large cities. -- Nathaniel Borenstein ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 16:35:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01076 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 16:35:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00981 for ; Wed, 29 Jul 1998 16:34:52 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id TAA22942; Wed, 29 Jul 1998 19:36:15 -0400 (EDT) Date: Wed, 29 Jul 1998 19:36:15 -0400 (EDT) From: Mike To: Mike Smith cc: "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: <199807281609.JAA03485@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Mike Smith wrote: > People, the Sparc port is _dead_ (Sun pulled the plug a while back). Thanks for the info... all of us aren't as enlightened as yourself. Now we know. > At no time was there going to be support for geriatric hardware. If > you want to run a real operating system, the NetBSD folks cater to just > that sort of nostalgia. Not sure *what* you mean by this satement. 'Real operating system'? Are you trying to be sarcastic? Not much is clear other than the fact that you need to calm down... This email list is "a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. This is a technical mailing list for which strictly technical content is expected." --FreeBSD-Hackers List Charter Last I checked, asking about a Sparc port was fairly technical... and it was a FreeBSD port, so it did pertain to FreeBSD... simply saying the project was dead (thanks again) would have been sufficient - no need to bash any OS or get hostile. -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 16:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02680 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 16:43:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02649 for ; Wed, 29 Jul 1998 16:42:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01537; Wed, 29 Jul 1998 16:39:59 -0700 (PDT) Message-Id: <199807292339.QAA01537@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike cc: Mike Smith , "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-reply-to: Your message of "Wed, 29 Jul 1998 19:36:15 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 16:39:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 28 Jul 1998, Mike Smith wrote: > > > People, the Sparc port is _dead_ (Sun pulled the plug a while back). > > Thanks for the info... all of us aren't as enlightened as yourself. Now > we know. This is what the mailing list archives are for. I just noticed that the Sparc port FAQ still doesn't mention this; I guess it should. > > At no time was there going to be support for geriatric hardware. If > > you want to run a real operating system, the NetBSD folks cater to just > > that sort of nostalgia. > > Not sure *what* you mean by this satement. 'Real operating system'? I'm suggesting that if you want a BSD system that will work well on your old Sparc hardware, NetBSD is what you want. > Are you trying to be sarcastic? Not much is clear other than the fact > that you need to calm down... ?! I think you're reading far too much into my response. > Last I checked, asking about a Sparc port was fairly technical... and it > was a FreeBSD port, so it did pertain to FreeBSD... simply saying the > project was dead (thanks again) would have been sufficient - no need to > bash any OS or get hostile. Please don't put words into my mouth. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 16:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04759 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 16:50:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnivax (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA04734 for ; Wed, 29 Jul 1998 16:50:20 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA29655 for hackers@freebsd.org; Wed, 29 Jul 1998 19:40:45 -0400 From: Bill Paul Message-Id: <199807292340.TAA29655@skynet.ctr.columbia.edu> Subject: New version of 3c905B "xl" driver ready To: hackers@FreeBSD.ORG Date: Wed, 29 Jul 1998 19:40:44 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gotten pretty encouraging feedback on the XL driver so far. Today I did a bunch of cleanups and fixed a few things. The new code is in the same place: http://www.freebsd.org/~wpaul/3Com/3.0 http://www.freebsd.org/~wpaul/3Com/2.2 Things that I fixed: - Sorted out a bunch of problems with the ifmedia support; ifconfig should report the correct media now on 3c900 cards. The initial media should be set correctly too. - Correctly detected the transceiver type set in the EEPROM for 10baseT/BNC/AUI transceivers. - Fixed 10baseT transceiver support for 3c900 cards: I forgot to set the 'link beat enable' bit when selecting the 10baseT transceiver. Problem reported by Larry Baird . - Added patch to xl_setmulti() provided by HAMADA Naoki . - Fixed 'xl0: transmission error: 88' problem. This means that TXComplete interrupt was received with a TX error status indicating that more than 16 collisions were encountered while trying to send a frame; the correct way to handle this is to simply make sure the current frame is still there and restart the transmitter. I only saw this in the lab when using a 3c900 card at 10Mbps/half-duplex mode while running a couple of ping -f processes simultaneously. The code was resetting the transmitter before, which is not necessary. Problem reported by Paul Saab . - Fixed a handful of stupid typos and other dumb mistakes in if_xlreg.h. Things I did not fix: - One person reported problems getting a 3c905 10/100 card to autonegotiate properly. I don't have one of these cards yet so I can't easily fix this, but I expect to have one soon so stay tuned. -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 17:03:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07306 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 17:03:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [207.126.97.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07290; Wed, 29 Jul 1998 17:03:57 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id RAA10878; Wed, 29 Jul 1998 17:03:25 -0700 (PDT) (envelope-from sef) Date: Wed, 29 Jul 1998 17:03:25 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199807300003.RAA10878@kithrup.com> To: chat@FreeBSD.ORG, hackers@FreeBSD.ORG Reply-To: chat@FreeBSD.ORG Organization: Kithrup Enterprises, Ltd. Subject: Dr Dobb's Journal, September 1998 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Once again, there is a FreeBSD-related article in DDJ, this time about the design and implementation of select() and poll(). (The code in the article has not yet been checked in, because a slew of problems has conspired to prevent me from installing -current on a usable machine. Bah.) It's not, I think, as good as the first article (which was about adding truss to FreeBSD via procfs), but it is a follow-on. Anyone who finds it useful can thank Nate, who asked me, one day, just how select() worked and inspired me to spend a few hours digging around the code :). Now a rant, a challenge, and some bragging. DDJ paid me $850 for the article, same as the first one. However, with the first one, Walnut Creek CD-ROM provided me with matching funds, which meant that time I spent on the article was actually quite well-paid. It did, in fact, end up paying for my new server (minus tape drive, which was an unexpected expense anyway). But I was, Jordan says, the only person who took advantage of this -- and so it was discontinued (which I did not find out until after I asked when I'd be getting the money from WC 8-)). Had some of you other bright and verbose people (yes, Terry, I mean *you*) written down some of the diatribes (or short novels, in Terry's case), I would be able to buy a luxury this time, instead of simply paying off the credit card debt I acquired due to some emergency hardware purchases. (Yes, I can turn any issue into being about *me*. It's a gift. :)) Look, people: writing an article is not hard. The hard part is coming up with an idea in the first place; I was lucky in that I'd had this idea for a Usenix paper for about four years (truss via procfs), and, on seeing Jordan's matching offer announcement, decided to change the tone slightly, and sell it, instead of presenting it at a conference. For example, here are a few ideas that are probably sellable, to either DDJ or, say, The Linux Journal: Using the MBone Using PostgreSQL Web server design, optimization, and setup News server "" Security concerns with FreeBSD, including using it as a firewall in a predominantly Windows environment All of those, except for the PostgreSQL one, are just off the top of my head. Most of them don't even require a lot of code to be written, and the length of an article is fairly short -- the one in the current DDJ was 443 lines (not counting code) when I submitted it, and they edited it down a bit. And if anyone does want to write an article, I'll offer some help with it (including bouncing ideas off of me and reading the article and offering suggestions). To get that going... if you've got experience with SQL and any of the available databases that use it, the editor I deal with at DDJ is possibly interested in an article. And since there are always security concerns with Win95 and WinNT, that's *always* a good topic. For a few hours worth of work, it's a chance at a few hundred dollars, and the ability to get your name in print around the world. This, by the way, can be a very nice addition to a resume. Linux has enough people writing articles to devote an entire MAGAZINE to -- surely we can come up with a few articles a year? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 18:30:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02487 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 18:30:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from agustina.kjsl.com (Agustina.KJSL.COM [198.137.202.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02482 for ; Wed, 29 Jul 1998 18:30:14 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from uucp@localhost) by agustina.kjsl.com (8.8.7/8.8.8/rchk1.19) with UUCP id RAA26130; Wed, 29 Jul 1998 17:56:49 -0700 (PDT) (envelope-from fmc@reanimators.org) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.8/rchk1.19) id RAA19554; Wed, 29 Jul 1998 17:38:29 -0700 (PDT) (envelope-from fmc) Message-Id: <199807300038.RAA19554@daemonweed.reanimators.org> To: Ted Faber Cc: Frank McConnell , Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? References: <199807291753.KAA12867@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 29 Jul 1998 17:38:28 -0700 In-Reply-To: Ted Faber's message of Wed, 29 Jul 1998 10:53:39 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Faber wrote: > Frank McConnell wrote: > >Ted Faber wrote: > >>As far as I can tell, there's no support for using the Hitachi's > >>internal PCI lance board in native PCI mode, so the card can only be > >>used in ISA emulation mode. > > > >What led you to that conclusion? Whoops. Poor choice of words on my part -- I wasn't questioning your intelligence when I wrote that, I really wanted to know what behavior you saw on your Hitachi that got you thinking along those lines. > As I mentioned, I'm just msireading the code here. I didn't see > anything that appeared PCI specific, and wasn't seeing my card work. > I'm no expert in either the PCI bus or this chipset - I was just > trying to get the laptop's internal ethernet running so it was of some > use to me. Hey, I'm no expert on these things either, just a wannabe looking for enlightenment. Here's what I was thinking. The probing for PCI and ISA cards looks (and largely is) the same -- I can't see why it should work from one code path and fail from the other, except by way of different I/O base addresses where one doesn't address an appropriate device. So there's one potential problem -- if you have a PCI card, and it's getting mapped at some I/O address for which you have a "device lnc[n]" entry in your kernel config (as for an ISA card), it'll get probed and attached twice. There's also the matter that the IC has a couple of different flavors of modes. One is the "software style" that can be set via BCR20. I think this defaults to C-LANCE/PCnet-ISA on hard reset, and the other styles would expect a different initialization block layout, so I think that this is what the driver expects. The other is word (16-bit) I/O vs. double-word (32-bit) I/O mode, which changes some of the register offsets, and again I think the driver expects to see the IC in word I/O mode (where a hard or soft reset will leave it) and just won't work if the chip is in double-word I/O mode. And there's another potential problem -- if the Hitachi BIOS tells the IC to do some other software style, or puts it in double-word I/O mode, I don't think the driver will probe it correctly. But I think that means both the PCI and ISA probes would fail. (Not that I know why the BIOS would do something like that -- this is speculation on my part.) So that's why I was wondering what you were seeing that would make you think you could use it in "ISA emulation" only -- as near as I can tell it should either work from either code path or not work at all. -Frank McConnell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 21:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24991 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 21:22:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24983 for ; Wed, 29 Jul 1998 21:22:56 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA09952; Wed, 29 Jul 1998 21:54:00 -0600 (MDT) Date: Wed, 29 Jul 1998 21:54:00 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807300354.VAA09952@narnia.plutotech.com> To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: pci_map_mem() failing.. Newsgroups: pluto.freebsd.hackers In-Reply-To: <199807282224.PAA20070@usr04.primenet.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807282224.PAA20070@usr04.primenet.com> you wrote: > > PCI does not support 64 address lines, only 32. Say what? 64bit PCI has been speced for awhile now. Since 2.0? Dual-address cycle 32bit PCI has been speced for even longer than that. > If it was supported, then yes, it would need to, from my knowledge of > experimental 64 bit PCI implementations by Intel and another vendor > with a competing connector and lead arrangement. They aren't experimental anymore. There are a few MBs shipping right now with 64bit 66MHz PCI busses on them. Several Alpha and Sun workstations now offer 64bit 33MHz PCI. The spec is such that you can put a 64bit PCI card in a 32bit slot and it works automagically in 32bit mode. > Is there a particular reason you are trying to do this in 64 bit mode > instead of 32 bit mode? I think you misunderstand what the register is trying to say. It is simply saying that the card will accept a mapping in that register anywhere in a 64bit address range. It does not indicate the location of the mapping. For that, you read the value out of the register. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 21:29:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25848 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 21:29:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (congo-82.ppp.hooked.net [206.169.227.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25831 for ; Wed, 29 Jul 1998 21:28:56 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id TAA10252; Wed, 29 Jul 1998 19:19:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 29 Jul 1998 19:19:40 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Mike , "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: <199807281609.JAA03485@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Mike Smith wrote: > > People, the Sparc port is _dead_ (Sun pulled the plug a while back). So that last message I saw about the first Sparc file to be commited was a ruse? Date: Sun, 19 Jul 1998 16:30:40 -0400 (EDT) From: Charles Youse To: freebsd-hackers@FreeBSD.ORG Subject: /usr/src/sys/sparc/include/bsd_openprom.h - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 21:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27794 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 21:50:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27688 for ; Wed, 29 Jul 1998 21:49:59 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id OAA12568 for ; Thu, 30 Jul 1998 14:17:32 +0930 (CST) Message-Id: <199807300447.OAA12568@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Thread safe X libs? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Jul 1998 14:17:31 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anyone know how I can go about making the threaded version of the X libs? I'm trying to compile eMusic, but it wants the thread safe libs, and it appears I don't have them :) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 23:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07789 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 23:04:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tversu.ru (mail.tversu.ru [62.76.80.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07732 for ; Wed, 29 Jul 1998 23:03:33 -0700 (PDT) (envelope-from vadim@gala.tversu.ru) Received: from gala.tversu.ru (vadim@gala.tversu.ru [62.76.80.10]) by tversu.ru (8.8.8/8.8.8) with ESMTP id KAA25978 for ; Thu, 30 Jul 1998 10:02:07 +0400 (MSD) Received: (from vadim@localhost) by gala.tversu.ru (8.8.8/8.8.8) id KAA10053 for freebsd-hackers@freebsd.org; Thu, 30 Jul 1998 10:02:03 +0400 (MSD) Message-ID: <19980730100202.A9992@tversu.ru> Date: Thu, 30 Jul 1998 10:02:02 +0400 From: Vadim Kolontsov To: freebsd-hackers@FreeBSD.ORG Subject: negative offset Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, FreeBSD (2.2.6, at least) allows to have negative offset in file (for example, after lseek(fd, -N, SEEK_END) in file which is smaller than N). What it was intended for? To have a "symmetrical behaviour" for offsets beyond the end or for some more practical reason? Do any other OSes have such behavior (for example, Solaris doesn't). Is it POSIX? Why manpages says nothing about it (am I miss something?) ? It can broke some programs that expects EINVAL on such lseek() and just ignores it, assuming that if N is bigger than filesize, the offset will remain zero (I dislike such practice, but..). Actually, it brokes xlogmaster 1.4.1 (author promised to fix it in a next release). And what is N = filesize + 1? FreeBSD's lseek() returns -1, and now I have to analyze errno to understand if it was an error or just a simple negative offset.. Regards, V. -- Vadim Kolontsov Tver Internet Center NOC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 23:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08364 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 23:07:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tversu.ru (mail.tversu.ru [62.76.80.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08339 for ; Wed, 29 Jul 1998 23:06:53 -0700 (PDT) (envelope-from vadim@gala.tversu.ru) Received: from gala.tversu.ru (vadim@gala.tversu.ru [62.76.80.10]) by tversu.ru (8.8.8/8.8.8) with ESMTP id KAA26052 for ; Thu, 30 Jul 1998 10:05:35 +0400 (MSD) Received: (from vadim@localhost) by gala.tversu.ru (8.8.8/8.8.8) id KAA10066 for freebsd-hackers@freebsd.org; Thu, 30 Jul 1998 10:05:30 +0400 (MSD) Message-ID: <19980730100529.B9992@tversu.ru> Date: Thu, 30 Jul 1998 10:05:29 +0400 From: Vadim Kolontsov To: freebsd-hackers@FreeBSD.ORG Subject: Re: negative offset References: <19980730100202.A9992@tversu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19980730100202.A9992@tversu.ru>; from Vadim Kolontsov on Thu, Jul 30, 1998 at 10:02:03AM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, forgot to say - when you're trying to read from file with negative offset, it returns EFBIG ("File is too large"). Do you think it's a good choice? Regards, V. -- Vadim Kolontsov Tver Internet Center NOC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 23:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11697 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 23:26:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11692 for ; Wed, 29 Jul 1998 23:26:32 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00468; Wed, 29 Jul 1998 23:25:36 -0700 (PDT) Message-Id: <199807300625.XAA00468@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ted Faber cc: Robert Swindells , fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-reply-to: Your message of "Wed, 29 Jul 1998 10:59:40 PDT." <199807291759.KAA13548@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:25:36 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I may be using a wrong term here. The interface probed successfully > as lnc0 during the ISA device probes after having been probed and > discarded as lnc1 during the PCI setup. That sounds like ISA > emulation to me, but again, I'm no expert on the two bus specs or the > chipset. That's odd. Initially I wondered if it was just that it took two probes to find the device (the first failing, but having side effects that let the second work), but when you disabled the first I concluded that there was something more interesting involved. > >I'll send you a driver to try later. > > The driver you sent me works without a hitch (so far). This driver > does what I expect a pure PCI driver would do: the interface probes on > lnc1 as a PCI device and the subsequent probe at the ISA port fails. Is this a completely new driver, or just a variation on the existing one? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 29 23:28:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11977 for freebsd-hackers-outgoing; Wed, 29 Jul 1998 23:28:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org ([204.188.254.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11971 for ; Wed, 29 Jul 1998 23:27:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id XAA00497; Wed, 29 Jul 1998 23:28:32 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 29 Jul 1998 23:28:28 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Mike , "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-Reply-To: <199807300622.XAA00440@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998, Mike Smith wrote: > > On Tue, 28 Jul 1998, Mike Smith wrote: > > > > > > > > People, the Sparc port is _dead_ (Sun pulled the plug a while back). > > > > So that last message I saw about the first Sparc file to be commited > > was a ruse? > > > > Date: Sun, 19 Jul 1998 16:30:40 -0400 (EDT) > > From: Charles Youse > > To: freebsd-hackers@FreeBSD.ORG > > Subject: /usr/src/sys/sparc/include/bsd_openprom.h > > Check your copy of the CVS repo. There is no directory 'src/sys/sparc', > so this must be someone's private repository. Yes it is. This was sent to hackers@ so that someone would submit it. It was billed as an import of the NetBSD file of the same name, plus some tweaks to get it to work. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 00:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17049 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 00:02:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17009 for ; Thu, 30 Jul 1998 00:02:44 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00440; Wed, 29 Jul 1998 23:22:49 -0700 (PDT) Message-Id: <199807300622.XAA00440@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alex cc: Mike Smith , Mike , "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc In-reply-to: Your message of "Wed, 29 Jul 1998 19:19:40 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:22:48 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 28 Jul 1998, Mike Smith wrote: > > > > > People, the Sparc port is _dead_ (Sun pulled the plug a while back). > > So that last message I saw about the first Sparc file to be commited > was a ruse? > > Date: Sun, 19 Jul 1998 16:30:40 -0400 (EDT) > From: Charles Youse > To: freebsd-hackers@FreeBSD.ORG > Subject: /usr/src/sys/sparc/include/bsd_openprom.h Check your copy of the CVS repo. There is no directory 'src/sys/sparc', so this must be someone's private repository. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 00:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23685 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 00:49:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23679 for ; Thu, 30 Jul 1998 00:49:50 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA11114 ; Thu, 30 Jul 1998 09:49:47 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA00746; Thu, 30 Jul 1998 09:49:47 +0200 To: jim@reptiles.org (Jim Mercer) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: proposed modification to /sbin/mount References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 30 Jul 1998 09:49:46 +0200 In-Reply-To: jim@reptiles.org's message of Wed, 29 Jul 1998 16:47:08 -0400 (EDT) Message-ID: Lines: 17 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jim@reptiles.org (Jim Mercer) writes: > cd /sys/i386/conf > config KERNEL > cd ../../compile/KERNEL > make depend > make > make install > cd /usr/src > make world Bzzzt, wrong. You should compile your kernel *after* make world, or it's going to get built with the wrong includes, not to mention potential problems with config being out of sync. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 00:55:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24628 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 00:55:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24621 for ; Thu, 30 Jul 1998 00:55:17 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id IAA23464; Thu, 30 Jul 1998 08:56:48 +0100 (BST) Date: Thu, 30 Jul 1998 08:56:48 +0100 (BST) From: Doug Rabson To: Wilko Bulte cc: ulf@Alameda.net, gibbs@narnia.plutotech.com, mrcpu@internetcds.com, hackers@FreeBSD.ORG Subject: Re: BusTek/BusLogic/Mylex driver In-Reply-To: <199807291717.TAA00766@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998, Wilko Bulte wrote: > > Mylex gave me the documentation for the DAC960 controller and even > > a 3 channel DAC960PJ with 8MB EDO/ECC memory. I am still working on > > learning more about stuff to continue the driver. I have so far > > the detection complete (PCI, which controller version, memory, > > channels, system drives, etc.) > > I also have a DAC960 lying here. But I need to build myself a PCI based > test box before I can do anything with it. Short of stuffing in an Alpha > box that is ;-) Hey, if you want to get the alpha box working with FreeBSD, drop me a line. The port is working quite well at the moment... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 01:23:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28389 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 01:23:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28381 for ; Thu, 30 Jul 1998 01:23:49 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id KAA01278 for ; Thu, 30 Jul 1998 10:30:31 +0200 (SAT) Received: by citadel via recvmail id 1276; Thu Jul 30 10:30:15 1998 From: Graham Wheeler Message-Id: <199807300829.KAA00255@cdsec.com> Subject: Re: Berg coding style (was qpopper trauma) To: hackers@FreeBSD.ORG Date: Thu, 30 Jul 1998 10:29:20 +0200 (SAT) In-Reply-To: <19980729181418.19519.qmail@iq.org> from "proff@iq.org" at Jul 30, 98 04:14:17 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The cucipop code truely has to be seen to be believed...... eg: > > ======= > > } > > } > > ;{ int namelen=sizeof peername; > > if(getpeername(fileno(sockin),(struct sockaddr*)&peername,&namelen)&& > > !debug&&(errno==ENOTSOCK||errno==EINVAL)) > > { int serverfd,curfd; > > signal(SIGHUP,SIG_IGN);signal(SIGPIPE,SIG_IGN);fclose(stdin); > > fclose(stdout);serverfd=socket(AF_INET,SOCK_STREAM,TCP_PROT); > > peername.sin_family=AF_INET;peername.sin_addr.s_addr=INADDR_ANY; > > peername.sin_port=htons(port);curfd=-1; > > setsockopt(serverfd,SOL_SOCKET,SO_REUSEADDR,&curfd,sizeof curfd); > > if(bind(serverfd,(struct sockaddr*)&peername,sizeof peername)) > > ======= All this needs is a bit of whitespace. Run it through GNU indent and it will look pretty normal. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 01:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00643 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 01:34:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00614 for ; Thu, 30 Jul 1998 01:34:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA16980 for ; Thu, 30 Jul 1998 01:32:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Date: Thu, 30 Jul 1998 01:32:56 -0700 Message-ID: <16972.901787576.1@time.cdrom.com> From: "Jordan K. Hubbard" Subject: Re: Dr Dobb's Journal, September 1998 MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: chat@FreeBSD.ORG Subject: Re: Dr Dobb's Journal, September 1998 In-reply-to: Your message of "Wed, 29 Jul 1998 17:03:25 PDT." <199807300003.RAA10878@kithrup.com> Date: Thu, 30 Jul 1998 01:32:56 -0700 Message-ID: <16972.901787576@time.cdrom.com> From: "Jordan K. Hubbard" > DDJ paid me $850 for the article, same as the first one. However, with the > first one, Walnut Creek CD-ROM provided me with matching funds, which meant > that time I spent on the article was actually quite well-paid. It did, in > fact, end up paying for my new server (minus tape drive, which was an > unexpected expense anyway). > > But I was, Jordan says, the only person who took advantage of this -- and so > it was discontinued (which I did not find out until after I asked when I'd > be getting the money from WC 8-)). Had some of you other bright and verbose Actually, just to set the record straight, we'll be "grandfathering" the older articles and will indeed be sending Sean a check for this one as well as one to Rich Morin for his article on FreeBSD in Sun Expert. The point remains, however, that Sean was really the only one to take me up on this and that's pretty sad. - Jordan ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 02:17:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06671 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 02:17:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from manchester.genrad.com (x194.genrad.co.uk [195.99.3.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06663 for ; Thu, 30 Jul 1998 02:17:51 -0700 (PDT) (envelope-from swindellsr@genrad.co.uk) Date: Thu, 30 Jul 1998 02:17:51 -0700 (PDT) Message-Id: <199807300917.CAA06663@hub.freebsd.org> Received: from CDP275.uk.genrad.com by manchester.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id P68L0GNG; Thu, 30 Jul 1998 10:17:42 +0100 From: Robert Swindells To: mike@smith.net.au CC: faber@ISI.EDU, fmc@reanimators.org, mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: <199807300625.XAA00468@antipodes.cdrom.com> (message from Mike Smith on Wed, 29 Jul 1998 23:25:36 -0700) Subject: Re: AMD PCNet/FAST cards; suppliers? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >I'll send you a driver to try later. > > > > The driver you sent me works without a hitch (so far). This driver > > does what I expect a pure PCI driver would do: the interface probes on > > lnc1 as a PCI device and the subsequent probe at the ISA port fails. >Is this a completely new driver, or just a variation on the existing >one? It is just a variation of the existing one. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 02:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08778 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 02:31:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from diamond.waii.com (diamond.waii.com [198.3.192.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08767 for ; Thu, 30 Jul 1998 02:30:55 -0700 (PDT) (envelope-from Rune.Mossige@waii.com) Received: by diamond.waii.com id EAA21639; Thu, 30 Jul 1998 04:30:51 -0500 (CDT) sender Rune.Mossige@waii.com for Received: from mail.wg.waii.com(137.144.128.17) user by diamond.waii.com via smap (3.2) id xma021548; Thu, 30 Jul 98 04:27:07 -0500 Received: from svs01.norway.waii.com (svs01-en1.norway.waii.com [136.250.62.1]) by mail1.wg.waii.com (8.8.7/8.8.7) with ESMTP id EAA51108 for ; Thu, 30 Jul 1998 04:27:04 -0500 Received: from svs03.norway.waii.com (svs03-en1.norway.waii.com [136.250.60.3]) by svs01.norway.waii.com (8.8.4/8.8.4) with ESMTP id LAA59876 for ; Thu, 30 Jul 1998 11:26:59 +0200 Received: from localhost (sttsrm@localhost) by svs03.norway.waii.com (8.8.4/8.8.4) with SMTP id LAA43658 for ; Thu, 30 Jul 1998 11:26:52 +0200 X-Authentication-Warning: svs03.norway.waii.com: sttsrm owned process doing -bs Date: Thu, 30 Jul 1998 11:26:52 +0200 (DST) From: Rune Mossige To: hackers@FreeBSD.ORG Subject: ipfw and 3 network cards Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, For the best part of the last week, I have been trying to get an older 386, 8MB memory, and 3 x 3COM 3C509's to run as a mini firewall between three subnets, two internal and one external via an ascend pipeline 50 router. I am not able to get all three interfaces to work as expected. It appears that ipfw only works good with two interfaces, and I have not been able to locate any info on how to get three interfaces to work properly. I am running FreeBSD 2.2.6 on this box, and presume I need to set it up as my default gateway for all internal hosts, on both internal subnets. Any pointers to where I can get hins/tips on how to set this up would be appreciated. ------------------------------------------------------------------- Our ultimate goal is to make overloaded machines appear to be idle. ------------------------------------------------------------------- Rune Mossige, Systems Support, Western Geophysical, Stavanger, Norway Tel: (+47)51598922 Fax:(+47)51598999 Priv:(+47)51424771 Mobile:(+47)90871024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 04:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19107 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 04:04:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19061 for ; Thu, 30 Jul 1998 04:04:50 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id NAA07949; Thu, 30 Jul 1998 13:11:32 +0200 (SAT) Received: by citadel via recvmail id 7906; Thu Jul 30 13:10:54 1998 From: Graham Wheeler Message-Id: <199807301109.NAA00538@cdsec.com> Subject: Re: ipfw and 3 network cards To: Rune.Mossige@waii.com (Rune Mossige) Date: Thu, 30 Jul 1998 13:09:58 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Rune Mossige" at Jul 30, 98 11:26:52 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hello, > For the best part of the last week, I have been trying to get an older > 386, 8MB memory, and 3 x 3COM 3C509's to run as a mini firewall between > three subnets, two internal and one external via an ascend pipeline 50 > router. > > I am not able to get all three interfaces to work as expected. It appears > that ipfw only works good with two interfaces, and I have not been able > to locate any info on how to get three interfaces to work properly. This is not true; there is no inherent relationship between the number of interfaces and the filtering code. Each NIC driver calls ip_input when it has an IP datagram for processing. ip_input checks the IP version and checksum, and then applies the filters. These are done in a uniform fashion regardless of the NIC on which the datagram arrived. > Any pointers to where I can get hins/tips on how to set this up would be > appreciated. Use the accounting facilities and a controlled test environment. Do a `ipfw -a l' and send the output to a file, run a test, do the `ipfw -a l' again sending the output to a different file, diff the files, and you will be able to see which rules were applied to the packets in your test. You should be able to work things out fairly easily this way. g. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 06:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03044 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 06:02:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA03032 for ; Thu, 30 Jul 1998 06:02:47 -0700 (PDT) (envelope-from jim@reptiles.org) Received: from localhost (1488 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 30 Jul 1998 09:02:44 -0400 (EDT) (Smail-3.2.0.101 1997-Dec-17 #20 built 1998-May-20) Message-Id: From: jim@reptiles.org (Jim Mercer) Subject: Re: proposed modification to /sbin/mount To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: Thu, 30 Jul 1998 09:02:44 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Jul 30, 98 09:49:46 am" 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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > jim@reptiles.org (Jim Mercer) writes: > > cd /sys/i386/conf > > config KERNEL > > cd ../../compile/KERNEL > > make depend > > make > > make install > > cd /usr/src > > make world > > Bzzzt, wrong. You should compile your kernel *after* make world, or > it's going to get built with the wrong includes, not to mention > potential problems with config being out of sync. hmmmm, you are likely right. it's been a little while since i did an upgrade, so i might have gotten that backwards. i did a make buildworld of 2.2.7 last night, so i'll be upgrading to it today. -- [ Jim Mercer Reptilian Research jim@reptiles.org +1 416 410-5633 ] [ The telephone, for those of you who have forgotten, was a commonly used ] [ communications technology in the days before electronic mail. ] [ They're still easy to find in most large cities. -- Nathaniel Borenstein ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 07:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07298 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 07:07:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07280 for ; Thu, 30 Jul 1998 07:07:23 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id IAA00398; Thu, 30 Jul 1998 08:59:00 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.8/8.8.5) with ESMTP id IAA00203; Thu, 30 Jul 1998 08:52:53 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.8/8.6.9) id IAA02724; Thu, 30 Jul 1998 08:24:54 -0400 (EDT) Date: Thu, 30 Jul 1998 08:24:54 -0400 (EDT) From: Thomas David Rivers Message-Id: <199807301224.IAA02724@lakes.dignus.com> To: mike@smith.net.au, rivers@dignus.com Subject: Re: 'daily panic' reproduction [was re: fsck errors] Cc: dg@root.com, freebsd-hackers@FreeBSD.ORG, rob@perihelion.co.uk In-Reply-To: <199807291651.JAA03255@antipodes.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > See below... > > > > "Rob McIntyre" writes: > > > > > > Hi, > > > > > > I'm currently trying to debug a version of FreeBSD that has been > > > ported onto our Helios operating system. > > > After running newfs on an ide device, fsck produces errors indicating > > > that some number of inodes are partially allocated and others are of > > > an unknown file type (shown below). Could you tell me more about > > > what these messages actually mean and maybe give me some > > > advice on tracking down such file system errors during the fast file > > > system creation in newfs. > > The first thing I would be worrying about would be whether you're > suffering a subtle problem with your IDE interface; if you're hosting > over the top of Helios, I presume that you're using a virtual disk > emulation? > > Failing that, it could be that you have the Dave Rivers Memorial > Problem; note that nobody has been able to reproduce his symptoms in a > controlled environment so we can't actually tell what's going on. > Umm... that's not quite the case; I have a machine totally dedicated to the reproduction; which I've made available on the net to anyone interested in trying to debug this problem. The reproduction I have is exactly what Rob reported above, except it's on a 386 with a 1542B SCSI controller. [The system is set up with a sio console; and boots off of the floppy - NFS mounting some things... then you can newfs/fsck the hard disk all you want, and do kernel debugging, reboots, etc...] Currently, it's "off the net" - but I can bring it back at the drop of a hat... If anyone is interested in pursuing this; just let me know. - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 08:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14494 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 08:10:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA14489 for ; Thu, 30 Jul 1998 08:10:51 -0700 (PDT) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig1.att.att.com by cagw1.att.com (AT&T/UPAS) for freebsd.org!hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Thu Jul 30 11:02 EDT 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id LAA09372 for ; Thu, 30 Jul 1998 11:10:36 -0400 (EDT) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Thu, 30 Jul 1998 11:10:33 -0400 Message-ID: To: hackers@FreeBSD.ORG Subject: MP, interlocks and vfs_busy Date: Thu, 30 Jul 1998 11:10:31 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm reading the VFS code and I don't quite understand the following piece of code in vfs_busy(): if (mp->mnt_kern_flag & MNTK_UNMOUNT) { if (flags & LK_NOWAIT) return (ENOENT); mp->mnt_kern_flag |= MNTK_MWAIT; if (interlkp) { simple_unlock(interlkp); } /* * Since all busy locks are shared except the exclusive * lock granted when unmounting, the only place that a * wakeup needs to be done is at the release of the * exclusive lock at the end of dounmount. */ tsleep((caddr_t)mp, PVFS, "vfs_busy", 0); if (interlkp) { simple_lock(interlkp); } return (ENOENT); } The interlocks are used for multiprocessor systems, right ? Then what would be if another CPU that is holding unmount lock will obtain simple lock and call wakeup() when our CPU is running around the comment: in end of simple_unlock() and beginning of tsleep() ? Is not it a race condition (of course, with low probablility because this code will probably take less time to execute than the code on another CPU, but still a possible race condition) ? Must not be the simple lock properly released inside tsleep(), after adding a request to sleep hash ? -Sergey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 08:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16082 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 08:29:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA16077 for ; Thu, 30 Jul 1998 08:29:32 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA17238; Thu, 30 Jul 1998 10:30:56 -0400 Date: Thu, 30 Jul 1998 10:30:56 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Eugeny Kuzakov cc: hackers@FreeBSD.ORG Subject: Re: PAM4FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998, Eugeny Kuzakov wrote: > One question. Is FreeBSD will support PAM ? I certainly hope not. It's awful. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 08:29:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16108 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 08:29:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16101 for ; Thu, 30 Jul 1998 08:29:37 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id LAA03145; Thu, 30 Jul 1998 11:15:24 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Thu, 30 Jul 1998 11:15:24 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: Call for testers for 3c905B driver In-Reply-To: <199807282035.QAA27573@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG seems to be working great for me. well so far, no problems: ---- xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x24 int a irq 3 on pci0.1 5.0 **later** xl0: autoneg complete, link status good (half-duplex, 10Mbps) ---- (this is correct) my workstation should be on a 100mbit link in 2 weeks. but for now i did a few parrallel NFS copies and got decent performance. (~800k/sec over 10bT) so far no problems since the update. connectivity and stability seem reliable. if there are any specific program you'd like to see it tested with, just ask. thank you very much for the time and work, -Alfred On Tue, 28 Jul 1998, Bill Paul wrote: > For those of you that care, I have a 3Com 3c905B driver ready for > testing for FreeBSD 3.0 and 2.2.x. You can obtain the driver source code > from the following places: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 09:57:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20442 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 09:57:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA20433 for ; Thu, 30 Jul 1998 09:57:03 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40671(1)>; Thu, 30 Jul 1998 09:55:39 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id JAA13547; Thu, 30 Jul 1998 09:55:37 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199807301655.JAA13547@mango.parc.xerox.com> To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: TCPDUMP In-reply-to: Your message of "Tue, 28 Jul 1998 09:55:12 PDT." <199807281657.MAA21402@etinc.com> Date: Thu, 30 Jul 1998 09:55:36 PDT From: Bill Fenner Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What are you putting in the DLT_NULL header? Filters work fine with most point-to-point devices with DLT_NULL header, which is a 4-byte value (in host byte order) containing the address family of the packet. tcpdump (well, libpcap) makes sure that this first word contains AF_INET as part of any filter you might create. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 09:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20725 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 09:58:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20687 for ; Thu, 30 Jul 1998 09:58:19 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA16782; Thu, 30 Jul 1998 08:19:31 -0700 (PDT) (envelope-from dhw) Date: Thu, 30 Jul 1998 08:19:31 -0700 (PDT) From: David Wolfskill Message-Id: <199807301519.IAA16782@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG, vadim@tversu.ru Subject: Re: negative offset In-Reply-To: <19980730100202.A9992@tversu.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 30 Jul 1998 10:02:02 +0400 >From: Vadim Kolontsov > FreeBSD (2.2.6, at least) allows to have negative offset in file (for >example, after lseek(fd, -N, SEEK_END) in file which is smaller than N). >What it was intended for? To have a "symmetrical behaviour" for offsets >beyond the end or for some more practical reason? Do any other OSes have >such behavior (for example, Solaris doesn't). Is it POSIX? Why manpages >says nothing about it (am I miss something?) ? >From a Solaris 2.5 "man lseek": On success, lseek() returns the resulting pointer location, as measured in bytes from the beginning of the file. Note that if fildes is a remote file descriptor and offset is negative, lseek() returns the file pointer even if it is negative. Sorry; my Solaris 2.6 machine is at home (where I can't get to it just now). david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 10:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22691 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 10:13:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22685 for ; Thu, 30 Jul 1998 10:13:06 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1vwH-0003Yi-00; Thu, 30 Jul 1998 10:52:25 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA09138; Thu, 30 Jul 1998 10:56:33 -0600 (MDT) Message-Id: <199807301656.KAA09138@harmony.village.org> To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) Subject: Re: proposed modification to /sbin/mount Cc: jim@reptiles.org (Jim Mercer), freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "30 Jul 1998 09:49:46 +0200." References: Date: Thu, 30 Jul 1998 10:56:33 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dag-Erling Coidan Sm rgrav writes: : Bzzzt, wrong. You should compile your kernel *after* make world, or : it's going to get built with the wrong includes, not to mention : potential problems with config being out of sync. No. That is not correct. The entire kernel only uses files in the kernel tree. In fact, I've built several kernels w/o doing a make world. I test booted them until I got one that worked, then booted single user and did a make world. I also switched to CAM from a very old -current system. The only problem with this is that there are some interesting dependencies witht he aic7xxx assembler that really want to have the includes installed. It uses the queue macros, which changed between the Oct -current I was running and the july 20ish cam source base I started installing on this machine. Sadly, there was no simple or trivial fix for this :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28178 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:15:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28160 for ; Thu, 30 Jul 1998 12:15:33 -0700 (PDT) (envelope-from syang@directhit.com) Received: from moe.dirhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id NAA06862 for ; Thu, 30 Jul 1998 13:40:30 -0400 (EDT) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Thu, 30 Jul 1998 13:38:16 -0400 Message-ID: <839A86AB6CE4D111A52200104B938D4303D1A4@MOE> From: Steven Yang To: "'freebsd-hackers@freebsd.org'" Subject: What's the best way to do security? Date: Thu, 30 Jul 1998 13:38:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm interested in finding out how to create secure telnet and ftp connections to a freebsd machine. The following scenario would be great for me: >From windows or freebsd, connect securely to a freebsd machine. Use X-windows. To complicate things, we sit behind a firewall, but a non-firewall solution would be a great start. I am a relative newby, so I'd appreciate any detailed help anybody can offer. Thanks, Steven Yang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:25:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02067 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:25:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from miris.lcs.mit.edu (miris.lcs.mit.edu [18.111.0.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02047 for ; Thu, 30 Jul 1998 12:25:45 -0700 (PDT) (envelope-from beng@miris.lcs.mit.edu) Received: from miris.lcs.mit.edu (beng@localhost [127.0.0.1]) by miris.lcs.mit.edu (8.8.7/8.8.7) with ESMTP id OAA11067 for ; Thu, 30 Jul 1998 14:45:20 -0400 (EDT) Message-Id: <199807301845.OAA11067@miris.lcs.mit.edu> To: freebsd-hackers@FreeBSD.ORG Subject: My apologies on the VX driver From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Date: Thu, 30 Jul 1998 14:45:20 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, As many of you know, I have been working on a new VX driver, off and on, for the past several months which many of you have been waiting for with great anticipation. My apolgies to everyone for this taking so much longer than it should. When I decided to do this, I didn't expect that my work would suddenly pick up and that my wife would fall ill for two months (including a surgery 2 weeks ago). The upside is that my wife is a great deal better, and Bill Paul (wpaul@freebsd.org) is appearantly working on a 3C90x driver of his own. Many thanks to Bill for picking up where I fell behind. Again, I feel simply terrible about this, but my life suddenly became far too complex and something had to give. Thanks to you all for the support and encouragement. -Ben Greenwald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:35:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05037 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:35:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05023 for ; Thu, 30 Jul 1998 12:35:38 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA10360; Thu, 30 Jul 1998 11:05:46 -0700 (PDT) Message-Id: <199807301805.LAA10360@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Mike Smith Cc: Mike , "Henry M. Pierce" , hackers@FreeBSD.ORG Subject: Re: FreeBSD for the Sparc Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 30 Jul 1998 11:05:35 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998 16:39:59 -0700 Mike Smith wrote: > I'm suggesting that if you want a BSD system that will work well on your > old Sparc hardware, NetBSD is what you want. ...and new SPARC hardware... We have an UltraSPARC port now, too :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:43:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07166 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:43:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07159 for ; Thu, 30 Jul 1998 12:43:35 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id KAA22077; Thu, 30 Jul 1998 10:15:57 -0700 (PDT) Date: Thu, 30 Jul 1998 10:15:57 -0700 (PDT) From: Dan Busarow To: Rune Mossige cc: hackers@FreeBSD.ORG Subject: Re: ipfw and 3 network cards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Jul 1998, Rune Mossige wrote: > I am not able to get all three interfaces to work as expected. It appears > that ipfw only works good with two interfaces, and I have not been able > to locate any info on how to get three interfaces to work properly. What kind of problem did you have? I'm sure there are more than a few of us running similar setups succesfully. Dan -- Dan Busarow 949 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07337 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:44:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07266 for ; Thu, 30 Jul 1998 12:44:00 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id PAA69268 for ; Thu, 30 Jul 1998 15:44:07 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: Date: Thu, 30 Jul 1998 15:48:03 -0400 To: hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Fwd: Re: FreeBSD for the Sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:36 PM -0400 7/29/98, Mike wrote: >> At no time was there going to be support for geriatric hardware. If >> you want to run a real operating system, the NetBSD folks cater to >> just that sort of nostalgia. > > Not sure *what* you mean by this satement. 'Real operating system'? > Are you trying to be sarcastic? Not much is clear other than the fact > that you need to calm down... I took it to mean: There is no FreeBSD for SPARC. We would like it to exist, but it does not. It is a nice wish, but it is not real. If you want to run a real, existent, available operating system on a range of SPARC-based machines, you could try NetBSD. That OS will even support some of the older SPARC machines, while the FreeBSD/SPARC project never expected to support them. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 12:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09857 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 12:52:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09775 for ; Thu, 30 Jul 1998 12:52:00 -0700 (PDT) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id KAA24012; Thu, 30 Jul 1998 10:58:53 -0700 (PDT) Message-Id: <199807301758.KAA24012@tnt.isi.edu> To: Frank McConnell Cc: Mike Smith , Robert Swindells , hackers@FreeBSD.ORG Subject: Re: AMD PCNet/FAST cards; suppliers? In-Reply-To: Your message of "29 Jul 1998 17:38:28 PDT." <199807300038.RAA19554@daemonweed.reanimators.org> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Jul 1998 10:58:53 -0700 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Frank McConnell wrote: >Ted Faber wrote: >> Frank McConnell wrote: >> >Ted Faber wrote: >> >>As far as I can tell, there's no support for using the Hitachi's >> >>internal PCI lance board in native PCI mode, so the card can only be >> >>used in ISA emulation mode. >> > >> >What led you to that conclusion? > >Whoops. Poor choice of words on my part -- I wasn't questioning your >intelligence when I wrote that, I really wanted to know what behavior >you saw on your Hitachi that got you thinking along those lines. Sorry, didn't mean to jump down your throat. I misread the code wrt PCI support. As far as the rest of it, because I couldn't find specs for the chipset (this was all done a year or more ago) I treated it as a black box and poked around in the driver. I thought it was coming up in ISA emulation mode because the stock driver attached it as a PCI device which didn't work: it locked up the kernel under load. I tweaked the driver to stop the PCI attach after mapping the chipset in via pci_map_port() (using the pci_conf_read() and a mask fails, too; from the comments in pci_map_port, I'm guessing it's because the latter correctly initializes some bridges). After that the ISA probe succeeded (at the I/O port that a verbose boot revealed) and the driver worked flawlessly. As I said, I may have the term wrong, but that sounds like ISA emulation to me. >Hey, I'm no expert on these things either, just a wannabe looking for >enlightenment. > >Here's what I was thinking. The probing for PCI and ISA cards looks >(and largely is) the same -- I can't see why it should work from one >code path and fail from the other, except by way of different I/O base >addresses where one doesn't address an appropriate device. So there's >one potential problem -- if you have a PCI card, and it's getting >mapped at some I/O address for which you have a "device lnc[n]" entry >in your kernel config (as for an ISA card), it'll get probed and >attached twice. I believe that with the stock driver and default configuration that's roughly what happens, but with a little weirdness in the mix. The PCI probe maps the ethernet to an unconventional port (0xfce0), modulo bridge chip initializations. The ISA probe fails, because it's looking in the wrong place. Probing the correct port also fails without some work. Modifying the driver not to do the rest of the PCI initialization (not assigning the PCI interrupt in the PCI probe routine) allows the ISA probe on port 0xfce0 to succeed, and the driver to run. I avoid the interrupt assignment by passing a NULL pointer out of the lnc_attach_ne2100_pci() routine if I notice the chip ID in my Hitachi. If I either take out the change to from pci_conf_read() to pci_map_port() or restore the assignment of the PCI interrupt (pci_map_int()) in the pci attach routines, the driver fails. >So that's why I was wondering what you were seeing that would make >you think you could use it in "ISA emulation" only -- as near as I can >tell it should either work from either code path or not work at all. There's a nutshell of what I understand and why. There seem to be a couple ways to proceed. If we can determine how the chip is set up that allows my bizarre system to work, we can test for that instead of the chip ID, avoid the interrupt assignment and use the ISA port. This doesn't strike me as the best plan, but it may be feasible. If you want to do this, if you can send me a snippet of code to plunk into the driver to dump the values of the appropriate configuration registers, I'm happy to do it. On the other hand Robert Swindells's driver seems to attach the chip as a PCI device and work fine. If his modifications are small and acceptable, maybe the best plan is to incorporate them. If his mods are too far-sweeping, maybe we can isolate the modifications that he uses to probe and initialize the PCI chip and import them. If you want to incorporate only some of his changes, I'm happy to munge around or help munge and extract the appropriate code. Of the two I'm leaning toward the PCI attach, which seems cleaner. If Robert's driver doesn't break other configurations, importing his changes seems like a good idea. Opinions? Consensus? - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcC0XIb4eisfQ5rpAQEiMwP/ZlT+QtB5DXqJDMOHF7TFd/iuPbo0Yz3a /QI+N1fT10nqGYHr1wqoTM+Mz8KmMm0a7nyWcjdbOUBiomMbNay21PJG3Zf44Rkd JWD/8xPO6qBphOVnlmj0zLsHlCxinFpmoPKPAwo5rNq6OV1MM7UEyWSmVfxK+Q6K qgxmAlzoNzw= =BG3S -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 14:18:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25873 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 14:18:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hancock.k12.mo.us (hancock.k12.mo.us [209.106.13.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25815 for ; Thu, 30 Jul 1998 14:17:57 -0700 (PDT) (envelope-from talon@hancock.k12.mo.us) Received: from localhost (talon@localhost) by hancock.k12.mo.us (8.8.5/8.8.5) with SMTP id QAA09774 for ; Thu, 30 Jul 1998 16:19:39 -0500 (CDT) Date: Thu, 30 Jul 1998 16:19:35 -0500 (CDT) From: bill schaub To: freebsd-hackers@FreeBSD.ORG Subject: you may be intrested in this strange problem i found in 2.2.1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im running 2.2.1 on a 386 for a web and email server ive run 2.2.1 on many diffrent type of machenes and never had this problem but when i decided to use an at&t 6386 /33 wgs system things got really strange really fast the only difffrence i cna see from this machene and others is that it has a real fpu on it the problem is after the system is runnign for a while it stops reporting the cpu useage for any process and systat dies with the alternate system clock has died now reverting to "pigs" display iostat keeps reporting a bogus reading of 92 % idle 3 % user 3% system and 2% interrupt witch is bogus sicne it stays the same even when compileing the kernel im suspecting the fpu chip but since i remotely admin the system at the moment i cant really turn it off to see if useing emulation would solve the problem sigh and id really like to just hack the npx code to work aorund this problem if the fpu is wired strange if ANYONE can help please mail talon@hancock.k12.mo.us i have kernel source online and id be willing ot give anyone a shell to help me in troble shooting this very strange problem witch i know must be hardwhare related i know i dont have good grammer skills but i am not a total moron ive ben useing freebsd for abotu 3 years now and even read the original 4.3 bsd supumentary documents for fun i just am totaly confused with this problem that ive never seen before andi dont understand c and how the freebsd kernel interacts with the hardwhare to even begin to fix this problem thats what brought me here you dont see things like this happen every day so if anyone is intrested in doing some really intresting hacking jsut mail me id love this opertunity to leanr mroe about freebsd internals and will be lurking on this mailing list for a while i also knwo thta a lot of you are thinking get new hardwhare but wheres the leanrign experence in that i want to force this machene to run problerly wether it likes it or not thats that having the os source is all about after all cya later -talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 14:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28127 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 14:29:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27969; Thu, 30 Jul 1998 14:28:36 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id XAA14237; Thu, 30 Jul 1998 23:28:21 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id TAA03507; Thu, 30 Jul 1998 19:08:44 +0200 (CEST) X-Face: " Date: Thu, 30 Jul 1998 19:08:43 +0200 From: Stefan Esser To: Chris Csanady , hackers@FreeBSD.ORG Cc: Stefan Esser Subject: Re: pci_map_mem() failing.. Mail-Followup-To: Chris Csanady , hackers@FreeBSD.ORG References: <199807281922.MAA12801@tarsier.ca.sandia.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807281922.MAA12801@tarsier.ca.sandia.gov>; from Chris Csanady on Tue, Jul 28, 1998 at 12:22:35PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-28 12:22 -0700, Chris Csanady wrote: > This is my second try at sending this message.. the first one did not > seem to get through. :\ > > Anyways.. I am working on a device driver, and so far have not been able to > get this seemingly simple aspect of it to work. I am getting the following > error: > pci_map_mem failed: bad memory type=0xfffff004 > > It seems that the pci code does not know how to handle 64bit cards. If > I yank the lines in pci.c that check the memory type, it produces no > errors, although the mapping still does not work. What am I missing > here? > > This is on a 2.2.6 box. Ummm, I see ... Well, this should work under 3.0-current, but I didn't find a card to actually verify this ... ;-) It shouldn't be too hard to make the 2.2.x PCI code deal with 64bit maps, provided the high address bits are just zero (I expect the address to be "unsigned"). I'll try to provide you with a patch, which will DTRT if the map register is 64 bits long and the map resides in the first 4GB of address space. Sorry, I'm still overloaded (fetched mail from my ISP for the first time after more than a week for lack of time all those previous days ...) and it may be only after the weekend that I can offer a fix ... Regards, STefan PS: I'd love to know whether the PCI code in -current can deal with that 64 bit map. If you can't boot a -current kernel, then please send "pciconf -r" results for the map registers of that device (instructions on request :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 14:51:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03553 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 14:51:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from albert.osu.cz (albert.osu.cz [195.113.106.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03538 for ; Thu, 30 Jul 1998 14:51:22 -0700 (PDT) (envelope-from belkovic@albert.osu.cz) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id XAA00325 for ; Thu, 30 Jul 1998 23:54:09 +0200 (MET DST) Date: Thu, 30 Jul 1998 23:54:07 +0200 (MET DST) From: Josef Belkovics To: freebsd-hackers@FreeBSD.ORG Subject: syslogd bug? In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1A4@MOE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you see the same on your pc? (syslogd -d) logmsg: pri 2, flags 17, from ix074, msg sc0 at 0x60-0x6f irq 1 on motherboard Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg sc0: VGA color <8 virtual consoles, flags=0x0> Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg s Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg io1 at 0x2f8-0x2ff irq 3 on isa Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg sio1: type 16550A (/var/log/messages) Jul 30 23:27:51 ix074 /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 30 23:27:51 ix074 /kernel: sc0: VGA color <8 virtual consoles, flags=0x0> Jul 30 23:27:51 ix074 /kernel: s Jul 30 23:27:51 ix074 /kernel: io1 at 0x2f8-0x2ff irq 3 on isa Jul 30 23:27:51 ix074 /kernel: sio1: type 16550A (dmesg) sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A Josef Belkovics To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 14:56:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04309 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 14:56:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from albert.osu.cz (albert.osu.cz [195.113.106.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04300 for ; Thu, 30 Jul 1998 14:56:43 -0700 (PDT) (envelope-from belkovic@albert.osu.cz) Received: from localhost (belkovic@localhost) by albert.osu.cz (8.8.5/8.6.12) with SMTP id XAA00334 for ; Thu, 30 Jul 1998 23:59:04 +0200 (MET DST) Date: Thu, 30 Jul 1998 23:59:04 +0200 (MET DST) From: Josef Belkovics To: freebsd-hackers@FreeBSD.ORG Subject: syslogd bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you see the same on your pc? With 2.2.7-RELEASE. (syslogd -d) logmsg: pri 2, flags 17, from ix074, msg sc0 at 0x60-0x6f irq 1 on motherboard Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg sc0: VGA color <8 virtual consoles, flags=0x0> Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg s Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg io1 at 0x2f8-0x2ff irq 3 on isa Logging to FILE /var/log/xkernlog logmsg: pri 2, flags 17, from ix074, msg sio1: type 16550A (/var/log/messages) Jul 30 23:27:51 ix074 /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 30 23:27:51 ix074 /kernel: sc0: VGA color <8 virtual consoles, flags=0x0> Jul 30 23:27:51 ix074 /kernel: s Jul 30 23:27:51 ix074 /kernel: io1 at 0x2f8-0x2ff irq 3 on isa Jul 30 23:27:51 ix074 /kernel: sio1: type 16550A (dmesg) sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A Josef Belkovics To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 15:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04941 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 15:03:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts02-107.dublin.indigo.ie [194.125.134.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04883 for ; Thu, 30 Jul 1998 15:02:45 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA02068; Thu, 30 Jul 1998 22:57:25 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807302157.WAA02068@indigo.ie> Date: Thu, 30 Jul 1998 22:57:24 +0000 In-Reply-To: <199807300829.KAA00255@cdsec.com>; Graham Wheeler Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Berg coding style (was qpopper trauma) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 30, 10:29am, Graham Wheeler wrote: } Subject: Re: Berg coding style (was qpopper trauma) > > > } > > > } > > > ;{ int namelen=sizeof peername; > > > if(getpeername(fileno(sockin),(struct sockaddr*)&peername,&namelen)&& > > > !debug&&(errno==ENOTSOCK||errno==EINVAL)) > > > { int serverfd,curfd; > > > signal(SIGHUP,SIG_IGN);signal(SIGPIPE,SIG_IGN);fclose(stdin); > > > fclose(stdout);serverfd=socket(AF_INET,SOCK_STREAM,TCP_PROT); > > > peername.sin_family=AF_INET;peername.sin_addr.s_addr=INADDR_ANY; > > > peername.sin_port=htons(port);curfd=-1; > > > setsockopt(serverfd,SOL_SOCKET,SO_REUSEADDR,&curfd,sizeof curfd); > > > if(bind(serverfd,(struct sockaddr*)&peername,sizeof peername)) > > > ======= > > All this needs is a bit of whitespace. Run it through GNU indent and it > will look pretty normal. I think thats the point, it needs a *lot* of whitespace. Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 15:21:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07903 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 15:21:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07890 for ; Thu, 30 Jul 1998 15:21:30 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA28429 for freebsd-hackers@FreeBSD.ORG; Fri, 31 Jul 1998 00:21:23 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 14266C383; Fri, 31 Jul 1998 00:00:44 +0200 (CEST) Message-ID: <19980731000044.A11648@keltia.freenix.fr> Date: Fri, 31 Jul 1998 00:00:44 +0200 From: Ollivier Robert To: "'freebsd-hackers@freebsd.org'" Subject: Re: What's the best way to do security? Mail-Followup-To: "'freebsd-hackers@freebsd.org'" References: <839A86AB6CE4D111A52200104B938D4303D1A4@MOE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <839A86AB6CE4D111A52200104B938D4303D1A4@MOE>; from Steven Yang on Thu, Jul 30, 1998 at 01:38:14PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4503 AMD-K6 MMX @ 233 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Steven Yang: > >From windows or freebsd, connect securely to a freebsd machine. > Use X-windows. Forget telnet, SSH[1][2] is your friend. It is a complete replacement for rlogin/rsh/telnet/rcp with automatic X11 tunneling. It uses encryption to ensure privacy and has several authentication schemes. > To complicate things, we sit behind a firewall, but a non-firewall > solution would be a great start. Just let open the port 22 for SSH and you're in. [1] /usr/ports/security/ssh [2] -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 15:26:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08546 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 15:26:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA08513 for ; Thu, 30 Jul 1998 15:26:45 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id SAA20197; Thu, 30 Jul 1998 18:26:42 -0400 Date: Thu, 30 Jul 1998 18:26:41 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: freebsd mmap: does the offset have to be blocksize-aligned Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here's a cute one from linux: (generic_file_mmap) if (vma->vm_offset & (inode->i_sb->s_blocksize - 1)) return -EINVAL; This is all 2.0.x kernels I have seen. It means that the offset for an mmap has to be file-system-block-aligned. There are cases where the linux ld.so double-maps libc.so, and in one case maps part of it on an 8k boundary. If you have a file system (such as mine) which can support 16384 or larger (65536? sure) blocksizes, elf programs can't run due to this kernel restriction. Doesn't hurt, e.g., statically linked a.out, as weird mmaps don't happen for them. Easy to work around, map your /lib with 4k blocks, problem solved, but funny. any block-aligned restrictions like this in freebsd mmap? I can't think of having seen it, but you here know better than me. I'm curious. thanks ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 17:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28450 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 17:08:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from localhost.my.domain (ppp7266.on.bellglobal.com [206.172.249.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28427 for ; Thu, 30 Jul 1998 17:08:38 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id TAA07933; Thu, 30 Jul 1998 19:48:03 -0400 (EDT) (envelope-from tim) Message-ID: <19980730194803.B7903@zappo> Date: Thu, 30 Jul 1998 19:48:03 -0400 From: Tim Vanderhoek To: bill schaub , freebsd-hackers@FreeBSD.ORG Subject: Re: you may be intrested in this strange problem i found in 2.2.1 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from bill schaub on Thu, Jul 30, 1998 at 04:19:35PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 30, 1998 at 04:19:35PM -0500, bill schaub wrote: > > i also knwo thta a lot of you are thinking get new hardwhare but wheres > the leanrign experence in that i want to force this machene to run Actually, I was thinking "Get a new OS version." FreeBSD 2.2.7 has recently been released and fixes many bugs since 2.2.1. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 17:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29840 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 17:19:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29835 for ; Thu, 30 Jul 1998 17:19:48 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.7/8.6.9) with SMTP id UAA05268; Thu, 30 Jul 1998 20:29:23 -0400 (EDT) Message-Id: <199807310029.UAA05268@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 30 Jul 1998 20:29:38 -0400 To: Bill Fenner From: Dennis Subject: Re: TCPDUMP Cc: hackers@FreeBSD.ORG In-Reply-To: <199807301655.JAA13547@mango.parc.xerox.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:55 AM 7/30/98 -0700, Bill Fenner wrote: >What are you putting in the DLT_NULL header? Filters work fine >with most point-to-point devices with DLT_NULL header, which is a >4-byte value (in host byte order) containing the address family of >the packet. tcpdump (well, libpcap) makes sure that this first word >contains AF_INET as part of any filter you might create. This has been fixed. Thanks anyway. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 17:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00824 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 17:25:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00811 for ; Thu, 30 Jul 1998 17:24:55 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA03224; Thu, 30 Jul 1998 17:22:39 -0700 (PDT) Message-Id: <199807310022.RAA03224@implode.root.com> To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: freebsd mmap: does the offset have to be blocksize-aligned In-reply-to: Your message of "Thu, 30 Jul 1998 18:26:41 EDT." From: David Greenman Reply-To: dg@root.com Date: Thu, 30 Jul 1998 17:22:39 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >any block-aligned restrictions like this in freebsd mmap? I can't think of >having seen it, but you here know better than me. I'm curious. In the MAP_FIXED case, the mapping address, after adjusting it for the requested file offset, must be page-aligned. This is the only alignment restriction. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 17:28:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01333 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 17:28:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA01318 for ; Thu, 30 Jul 1998 17:27:57 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA01432 for hackers@freebsd.org; Thu, 30 Jul 1998 20:31:07 -0400 From: Bill Paul Message-Id: <199807310031.UAA01432@skynet.ctr.columbia.edu> Subject: Yet another 3c905B driver update To: hackers@FreeBSD.ORG Date: Thu, 30 Jul 1998 20:31:06 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I place yet another version of the 3Com Etherlink XL driver at http://www.freebsd.org/~wpaul/3Com/3.0 and http://www.freebsd.org/~wpaul/3Com/2.2 This version has some more ifmedia fixes that should allow manual media selection not to screw up autoselection on the 3c905B. I've also been able to test a 3c905-TX card and make a few small tweaks for that as well. As always, feedback is encouraged. I think I'm only one or two more revisions away from committing this code to the -current branch. Share and enjoy. -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 17:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05906 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 17:59:32 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05888 for ; Thu, 30 Jul 1998 17:59:20 -0700 (PDT) (envelope-from peter.jeremy@AUSS2.ALCATEL.COM.AU) Received: by border.alcanet.com.au id <40343>; Fri, 31 Jul 1998 10:58:51 +1000 Date: Fri, 31 Jul 1998 10:59:02 +1000 From: Peter Jeremy Subject: Re: TCPDUMP To: hackers@FreeBSD.ORG Message-Id: <98Jul31.105851est.40343@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998 22:44:27 +0200, sthaug@nethelp.no wrote: >Why is DLT_NULL wrong? ... > >What we'd like to have, is a two byte field - basically the standard >Ethernet type, minus source and destination addresses. This needs to be >done in cooperation with the tcpdump maintainers, of course. I had a similar problem with LPIP and wrote a set of patches to tcpdump and libpcap to support a 2-byte header. They're in my PR bin/7241. Bill Fenner solved the same problem by modifying LPIP to use 4-byte headers (his code is also in the above PR, but needs to have 'ifp' changed to '&sc->sc_if' in two places to work - the compiler will point out the places). Overall, I think Bill's approach is probably the correct one. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 21:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26020 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 21:16:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26011 for ; Thu, 30 Jul 1998 21:16:09 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for hackers@FreeBSD.ORG id 0z26bm-0004HW-00; Thu, 30 Jul 1998 23:15:58 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: biggest mail server To: hackers@FreeBSD.ORG Date: Thu, 30 Jul 1998 23:15:58 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi Folks, Who is running the biggest FreeBSD-based mail system out there? How many mailboxes? How does it scale? Jacques Vidrine -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcFE/jeRhT8JRySpAQFZEwQAm93YWVKC8rEOGb31YCEFPhRl6HmjvU11 s68tYQVIlrsXfgecf5OYKq0g0FlHXJK/uVAycGoX6St4qWmNRU1vnYdH9LTzC+EO o/5lbPqV3sqBchd/jCeyCyW55C7WtjwQfBI3piPLovjEdeiGXERm0UA+o8ml4tPW NB5Ms6br4ok= =0Bm/ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 21:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26911 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 21:23:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thrintun.epilogue.com (thrintun.epilogue.com [128.224.2.28]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA26906 for ; Thu, 30 Jul 1998 21:23:32 -0700 (PDT) (envelope-from sra@epilogue.com) Received: from localhost.epilogue.com ([127.0.0.1]:17670 "EHLO epilogue.com" ident: "IDENT-NOT-QUERIED [port 17670]") by thrintun.epilogue.com with ESMTP id <23162-213>; Fri, 31 Jul 1998 00:23:10 -0400 To: freebsd-hackers@FreeBSD.ORG Subject: syscons keymap "us.emacs.kbd" Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: multipart/mixed; boundary="Multipart_Fri_Jul_31_00:17:08_1998-1" Content-Transfer-Encoding: 7bit Date: Fri, 31 Jul 1998 00:23:09 -0400 From: Rob Austein Message-Id: <19980731042314Z23162-213+60@thrintun.epilogue.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Fri_Jul_31_00:17:08_1998-1 Content-Type: text/plain; charset=US-ASCII Apologies if this is the wrong place to send this, it seemed the least inappropriate based on the list summary in the handbook. The enclosed is a syscons keymap file, suitable for loading with kbdcontrol. It implements a varient on the standard US ASCII keyboard; in particular, it turns the ALT keys into meta keys, and makes a few other tweaks so that the keyboard will work nicely with bash and emacs. Or that's the theory, anyway, your milage may vary radically if you didn't grow up with the MIT Chaosnet, ITS, SUPDUP, and Lisp Machines.... I've been using this keymap since FreeBSD 1.0.1 or thereabouts (yes, it predates the current textual form of .kbd files). Every time I install FreeBSD on a new machine, I make a mental note to send this along to you guys, then promptly forget about it. Finally remembered. Share and enjoy. --Multipart_Fri_Jul_31_00:17:08_1998-1 Content-Type: application/octet-stream; type=gzip Content-Disposition: attachment; filename="us.emacs.kbd.gz" Content-Transfer-Encoding: base64 H4sICE/gKS4CA3VzLmVtYWNzLmtiZAClmGl/GzUQh9/3UywUWK6CNNqTG8p9tNw3BcdxmhLX aW2nNFyfHWn+M81srf39cDYv8mRj69E1Gml1tbjsz2y5vXK12Mxnq5EvzFfb9XLw/Qvgs+Xp /CQ65qeHi6I4mG3i72JzfOdo+6iwPEnZ3Geb7Wy7iJJrk3+uFIVzLlazOr1XXAbFTVb4+Ndi My8uA1FQ/Kv0ZfpH+US5W5NvW0bjR1sRUlmC4i0ozpYGvu0YPTGoMxBFlcoGKK5mW9GjFWG0 FXUqW0HxVE7ROSiqUUWTytZQPJ1VeCjqUUUarLKB4hZjvSkMfMeDQISxqDsDUaS/yxaKZ7Kt CGhFM9qKNFhlB8XzWUWFUXVjCp8+KXsons0qarSiG1WkwSodFM9lJ7WBoh9VcHReg+JXKDCO At8GDCeGpO4NRMHR+ToUL2Q7gkLtaID7NFiHC45lwQGqF1BdG/jQGIgifXLMmSUPH9pRiIKj 8z468gXjcO4NqAIc+lPVBsV1VnB0/gHFd4zF9sCAKq6QPMrW3kAUHJ0LKN6DYnXfgAjV99KD YCAKjs41FF9KR8iAKsBjwVaNARTE0bmF4mtRVAZUAR7LrOoMRMHReQ7FD+jI3cKAqh4KdKQO BqLg6DyD4huE1uzEgDD45FG26g1EwdF5B4qPyt24IIwcOZ+JCyg4d55CcZOxuVMYUEBHHMpW wUAUnDvvQfE5hnO5MKDKQSHjWBmIgqPzJyj+Kne3G/JohcZUbYAAJ47OX6D4h3Eb60tAhADX qWgNRJHaN1/jTACslhYea0QROgNRpGYu57zt7w0oAkfnDB15GzNyemxAhN736IisGDJxETg6 N1B8JQEeDAjzR1760xqIgqPzEIp3MSOnWwOSjbiXdEUGouDoPILifcZsfmJAAUu0l3GsDETB 0Xkbig8YB5JCAQroQY9BCLWBKDg6j6H4sMykX7SZnMukXyg4On+H4uNyNy4IbSZHmbiAgqPz BIpPGA+wRB/oSsVid5LxegNRcO5cQvEp4+ioMCC0mZysL2cgCs6dr0LxSnY3QyR0o4cD1pUl FE/mFI2c+GhUwdH5GxT/ZhREGM569KzFKX6Jc/XeEAVH589oxd8YTgTEkeYLZK1azlqNgSg4 Ov+E4kes1LMDA6qh8HJOqwwwI5ziy4dQfM+Q9xQBYdchL9WTgSg4OudQXJdt+aEBEWakl8Xh DUTB0fkAim/RkfOVAWH7JC89cAai4Og8gOIdKFD9RluBHvSyyp2BKDg6V1DckMRXGBBWFDnZ 0skACm5ReReKz8piJ58T9j5y9W4+FwVH54tQvJY9d6LebvToyrNTvgTFG1kFBqEfPUDzJlW+ DMWbWYVsAqPnTg6zNUJ+b4iivngF0DeB4YaIVwBFZkPk9bLEa/HeEAVHZ4FWFLk3xMZZZN4Q +Q1pnt7iLwFRpOg8Olmcx7NUQjyVJcS9OCGG1Wa+TsesCA+YJyi4fawgKCooGig6LkQoBJgn UXhVoHqP6uMKZ0XPhQIKAeZJFKQKVO9RfRyuhJjfU6EKhQDzJIqgClTvUX08grDCc6EahQDz JIpKFajeo/qYD1hBXKhBIcA8iaJWBar3qD5gfmJ+T4XaIg9RNKpA9YTqA+Yn5vf07a7IQxSt KlA9ofqA+Yn5PX27L/IQRScKj+oJ1QfMT0y9qduuyEMUPS9Kjte9AQWv4Q3+szdEodEZU7ne QQyglw85FDdYodEZU7neQQyglw85iEKjM6ZyvYMYQC8fchCFRmdM5XqBMIDcHGQhCo3OmMr1 YmkAvVHKQRQanTGV68XSAHqjlIMoNDpjKteLpQHkRikLUWh0xlQuVyBDyN1HFqLQ3BlTud4W DqDXhDlA0WnujKlcbwsH0GvCHESh0RlTud4WDqDXhDmIQqMzpnK9mxpAL6VyEEW42Kj1jDCA Hg5yEEW1c5P1/4GVysE+7fqY3xEmKjQ6PZImIWkG7CpVazbTXYjiUe5E0iQkzYBdperMZroL UfQX7RqeFgWPvfYPD408I3yQW+Mtfm+gFXyQ07iQg98AeuLLQVpBRjE4tQkeO64NIIoUnWuc vvaGdKSavAn09eRNoG8mbwJ9OzmD993k9NtPzp3eTc6d3k3Ond5Nzp3ehakboufLkUmnHO8m 5s7/AGkX+kHKHAAA --Multipart_Fri_Jul_31_00:17:08_1998-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 21:26:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27352 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 21:26:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27347 for ; Thu, 30 Jul 1998 21:26:10 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA01892; Thu, 30 Jul 1998 21:26:04 -0700 (PDT) (envelope-from jdp) Message-Id: <199807310426.VAA01892@austin.polstra.com> To: woods@zeus.leitch.com Subject: Re: why does CVSup sometimes "Touch" every file in the repository? In-Reply-To: <199807241540.LAA03611@brain.zeus.leitch.com> References: <199807241540.LAA03611@brain.zeus.leitch.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Thu, 30 Jul 1998 21:26:04 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807241540.LAA03611@brain.zeus.leitch.com>, Greg A. Woods wrote: > Occasionally, esp. after global tagging, etc., CVSup wants to "Touch" > every file in the repository. Why? I can't think of any CVS operation > that would do this unless someone deletes a tag and re-applies it > between the times I run CVSup -- and I know Jordan mentioned he had > moved a tag forward on a couple of files yesterday (I assumed he would > have done this on only those individual files though). Normally, a "touch" indicates that the modtime of the file changed, but not its contents. I've seen what you describe before too, including on the most recent tagging for 2.2.7. But I can't really explain it, except that the files on the server must have had their modtimes changed somehow. One user action that might cause this: If you run cvsup in non-GUI mode (-g), and kill it before it's finished, and then run it again, I think you'll see a "touch" on all the files that were updated in the first run. That's appropriately viewed as a bug; cvsup doesn't clean up correctly if it's killed by a signal. With the GUI, pressing the "stop" button does clean up properly. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 22:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04941 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 22:42:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04935; Thu, 30 Jul 1998 22:42:07 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA20531; Thu, 30 Jul 1998 23:36:40 -0600 (MDT) Date: Thu, 30 Jul 1998 23:36:40 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807310536.XAA20531@narnia.plutotech.com> To: Stefan Esser cc: hackers@FreeBSD.ORG Subject: Re: pci_map_mem() failing.. Newsgroups: pluto.freebsd.hackers In-Reply-To: <199807281922.MAA12801@tarsier.ca.sandia.gov> <19980730190843.A3467@mi.uni-koeln.de> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PS: I'd love to know whether the PCI code in -current can > deal with that 64 bit map. If you can't boot a -current > kernel, then please send "pciconf -r" results for the > map registers of that device (instructions on request :) It seems to allow memory mapping of my aic7890 and aic7897 controllers just fine. The aic7897 is actually a full 64bit card. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 30 22:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05037 for freebsd-hackers-outgoing; Thu, 30 Jul 1998 22:42:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05020 for ; Thu, 30 Jul 1998 22:42:30 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id PAA11388; Fri, 31 Jul 1998 15:41:57 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma011380; Fri, 31 Jul 98 15:41:49 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA17444; Fri, 31 Jul 1998 15:41:48 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA26276; Fri, 31 Jul 1998 15:41:48 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA11224; Fri, 31 Jul 1998 15:41:46 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199807310541.PAA11224@nymph.dtir.qld.gov.au> To: bill schaub cc: freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: you may be intrested in this strange problem i found in 2.2.1 References: In-Reply-To: from bill schaub at "Thu, 30 Jul 1998 16:19:35 -0500" Date: Fri, 31 Jul 1998 15:41:45 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 30th July 1998, bill schaub wrote: >im running 2.2.1 on a 386 for a web and email server ... >the problem is after the system is runnign for a while it stops reporting >the cpu useage for any process and systat dies with the alternate system >clock has died now reverting to "pigs" display iostat keeps reporting a >bogus reading of 92 % idle 3 % user 3% system and 2% interrupt witch is >bogus sicne it stays the same even when compileing the kernel Upgrade to 2.2.7. This problem was fixed in 2.2.2. But if you want a quick fix, apply this patch to /sys/i386/isa/clock.c: Index: clock.c =================================================================== RCS file: /cvs/src/sys/i386/isa/clock.c,v retrieving revision 1.72.2.3 retrieving revision 1.72.2.4 diff -u -r1.72.2.3 -r1.72.2.4 --- clock.c 1997/03/05 08:19:02 1.72.2.3 +++ clock.c 1997/04/27 13:44:19 1.72.2.4 @@ -34,7 +34,7 @@ * SUCH DAMAGE. * * from: @(#)clock.c 7.2 (Berkeley) 5/12/91 - * $Id: clock.c,v 1.72.2.3 1997/03/05 08:19:02 bde Exp $ + * $Id: clock.c,v 1.72.2.4 1997/04/27 13:44:19 mckay Exp $ */ /* @@ -311,15 +311,20 @@ * * The RTC chip requires that we read status register C (RTC_INTR) * to acknowledge an interrupt, before it will generate the next one. + * Under high interrupt load, rtcintr() can be indefinitely delayed and + * the clock can tick immediately after the read from RTC_INTR. In this + * case, the mc146818A interrupt signal will not drop for long enough + * to register with the 8259 PIC. If an interrupt is missed, the stat + * clock will halt, considerably degrading system performance. This is + * why we use 'while' rather than a more straightforward 'if' below. + * Stat clock ticks can still be lost, causing minor loss of accuracy + * in the statistics, but the stat clock will no longer stop. */ static void rtcintr(struct clockframe frame) { - u_char stat; - stat = rtcin(RTC_INTR); - if(stat & RTCIR_PERIOD) { + while (rtcin(RTC_INTR) & RTCIR_PERIOD) statclock(&frame); - } } #include "opt_ddb.h" >i know i dont have good grammer skills but i am not a total moron Don't skimp on the capitalisation and punctuation, or most people will assume the worst. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 00:07:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13771 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 00:07:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13766 for ; Fri, 31 Jul 1998 00:07:50 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA20745 ; Fri, 31 Jul 1998 09:07:30 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA01614; Fri, 31 Jul 1998 09:07:29 +0200 To: Warner Losh Cc: jim@reptiles.org (Jim Mercer), freebsd-hackers@FreeBSD.ORG Subject: Re: proposed modification to /sbin/mount References: <199807301656.KAA09138@harmony.village.org> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 31 Jul 1998 09:07:28 +0200 In-Reply-To: Warner Losh's message of Thu, 30 Jul 1998 10:56:33 -0600 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message Dag-Erling Coidan Sm rgrav writes: > : Bzzzt, wrong. You should compile your kernel *after* make world, or > : it's going to get built with the wrong includes, not to mention > : potential problems with config being out of sync. > No. That is not correct. The entire kernel only uses files in the > kernel tree. ...and /usr/share/mk/bsd.kern.mk, and /usr/sbin/config, and probably a couple of other "sensitive" files or programs outside the /usr/src/sys tree. You're right about the includes though, my bad. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 04:33:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10459 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 04:33:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10454 for ; Fri, 31 Jul 1998 04:33:07 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.8) id MAA13247; Fri, 31 Jul 1998 12:32:45 +0100 (BST) (envelope-from joe) Message-ID: <19980731123244.B26485@pavilion.net> Date: Fri, 31 Jul 1998 12:32:44 +0100 From: Josef Karthauser To: Doug White , Nick Hibma Cc: hackers@FreeBSD.ORG Subject: Re: NetBSD now has USB .. References: <19980721155151.L26364@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19980721155151.L26364@pavilion.net>; from Josef Karthauser on Tue, Jul 21, 1998 at 03:51:51PM +0100 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 21, 1998 at 03:51:51PM +0100, Josef Karthauser wrote: > > > > Someone want to take on a porting project? (and don't say me, I don't > > > > have time or the technical expertice.) > > I'm actually building a USB device at the moment (including device firmware > and NT device driver), so I'm up to speed on this. If anyone wants my > help (i.e. we do it together) drop me a line. I'd love to help, but don't > have the full amount of time to do it myself at the moment. Has anyone progressed on this? No one mailed me back :( Joe -- Josef Karthauser Technical Manager FreeBSD: The power to serve (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 05:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20468 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 05:56:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20463 for ; Fri, 31 Jul 1998 05:56:35 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 2349 invoked by uid 3759); 31 Jul 1998 12:57:20 -0000 Date: Fri, 31 Jul 1998 08:57:20 -0400 (EDT) From: "B. Richardson" To: Jacques Vidrine cc: hackers@FreeBSD.ORG Subject: Re: biggest mail server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think hotmail.com may satisfy your curiosities. Maybe the webmaster there give you some info. - Barrett Richardson rabtter@orion.aye.net On Thu, 30 Jul 1998, Jacques Vidrine wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hi Folks, > > Who is running the biggest FreeBSD-based mail system out > there? How many mailboxes? How does it scale? > > Jacques Vidrine > > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBNcFE/jeRhT8JRySpAQFZEwQAm93YWVKC8rEOGb31YCEFPhRl6HmjvU11 > s68tYQVIlrsXfgecf5OYKq0g0FlHXJK/uVAycGoX6St4qWmNRU1vnYdH9LTzC+EO > o/5lbPqV3sqBchd/jCeyCyW55C7WtjwQfBI3piPLovjEdeiGXERm0UA+o8ml4tPW > NB5Ms6br4ok= > =0Bm/ > -----END PGP SIGNATURE----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 06:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24298 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 06:33:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24286 for ; Fri, 31 Jul 1998 06:33:51 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id JAA08183; Fri, 31 Jul 1998 09:33:34 -0400 (EDT) Date: Fri, 31 Jul 1998 09:33:34 -0400 (EDT) From: The Hermit Hacker To: "B. Richardson" cc: Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998, B. Richardson wrote: > > I think hotmail.com may satisfy your curiosities. Maybe the webmaster > there give you some info. hotmail.com is running Solaris, last I heard... > > - > > Barrett Richardson rabtter@orion.aye.net > > On Thu, 30 Jul 1998, Jacques Vidrine wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hi Folks, > > > > Who is running the biggest FreeBSD-based mail system out > > there? How many mailboxes? How does it scale? > > > > Jacques Vidrine > > > > > > > > -----BEGIN PGP SIGNATURE----- > > Version: 2.6.2 > > > > iQCVAwUBNcFE/jeRhT8JRySpAQFZEwQAm93YWVKC8rEOGb31YCEFPhRl6HmjvU11 > > s68tYQVIlrsXfgecf5OYKq0g0FlHXJK/uVAycGoX6St4qWmNRU1vnYdH9LTzC+EO > > o/5lbPqV3sqBchd/jCeyCyW55C7WtjwQfBI3piPLovjEdeiGXERm0UA+o8ml4tPW > > NB5Ms6br4ok= > > =0Bm/ > > -----END PGP SIGNATURE----- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 06:35:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24515 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 06:35:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24493 for ; Fri, 31 Jul 1998 06:34:53 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id PAA08990 ; Fri, 31 Jul 1998 15:34:38 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id PAA01776; Fri, 31 Jul 1998 15:34:37 +0200 To: "B. Richardson" Cc: Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 31 Jul 1998 15:34:36 +0200 In-Reply-To: "B. Richardson"'s message of Fri, 31 Jul 1998 08:57:20 -0400 (EDT) Message-ID: Lines: 11 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "B. Richardson" writes: > I think hotmail.com may satisfy your curiosities. Maybe the webmaster > there give you some info. Hotmail is owned by Microsoft, and is running Solaris until their engineers can find a way to make NT sustain that kind of load without crashing more than once an hour or so. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 06:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24916 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 06:37:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from plaidsocks.com (c657209-a.cstvl1.sfba.home.com [24.1.81.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24898 for ; Fri, 31 Jul 1998 06:37:09 -0700 (PDT) (envelope-from stefan@csudsu.com) Received: from localhost (stefan@localhost) by plaidsocks.com (8.8.8/1.3.2) with SMTP id GAA04949; Fri, 31 Jul 1998 06:36:15 -0700 (PDT) (envelope-from stefan@csudsu.com) Date: Fri, 31 Jul 1998 06:36:15 -0700 (PDT) From: Stefan Molnar X-Sender: stefan@c657209-a.cstvl1.sfba.home.com To: "B. Richardson" cc: Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The FreeBSD side is the web servers. The Mail side are Solaris. That is from what I saw in a job posting from them. On Fri, 31 Jul 1998, B. Richardson wrote: > > I think hotmail.com may satisfy your curiosities. Maybe the webmaster > there give you some info. > > - > > Barrett Richardson rabtter@orion.aye.net > > On Thu, 30 Jul 1998, Jacques Vidrine wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hi Folks, > > > > Who is running the biggest FreeBSD-based mail system out > > there? How many mailboxes? How does it scale? > > > > Jacques Vidrine > > > > > > > > -----BEGIN PGP SIGNATURE----- > > Version: 2.6.2 > > > > iQCVAwUBNcFE/jeRhT8JRySpAQFZEwQAm93YWVKC8rEOGb31YCEFPhRl6HmjvU11 > > s68tYQVIlrsXfgecf5OYKq0g0FlHXJK/uVAycGoX6St4qWmNRU1vnYdH9LTzC+EO > > o/5lbPqV3sqBchd/jCeyCyW55C7WtjwQfBI3piPLovjEdeiGXERm0UA+o8ml4tPW > > NB5Ms6br4ok= > > =0Bm/ > > -----END PGP SIGNATURE----- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 07:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29965 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 07:17:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA29953 for ; Fri, 31 Jul 1998 07:17:45 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 3459 invoked by uid 3759); 31 Jul 1998 14:18:55 -0000 Date: Fri, 31 Jul 1998 10:18:55 -0400 (EDT) From: "B. Richardson" To: Stefan Molnar cc: Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My bad. - Barrett Richardson rabtter@orion.aye.net On Fri, 31 Jul 1998, Stefan Molnar wrote: > > The FreeBSD side is the web servers. The Mail side are Solaris. > That is from what I saw in a job posting from them. > > > On Fri, 31 Jul 1998, B. Richardson wrote: > > > > > I think hotmail.com may satisfy your curiosities. Maybe the webmaster > > there give you some info. > > > > - > > > > Barrett Richardson rabtter@orion.aye.net > > > > On Thu, 30 Jul 1998, Jacques Vidrine wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > > > Hi Folks, > > > > > > Who is running the biggest FreeBSD-based mail system out > > > there? How many mailboxes? How does it scale? > > > > > > Jacques Vidrine > > > > > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > Version: 2.6.2 > > > > > > iQCVAwUBNcFE/jeRhT8JRySpAQFZEwQAm93YWVKC8rEOGb31YCEFPhRl6HmjvU11 > > > s68tYQVIlrsXfgecf5OYKq0g0FlHXJK/uVAycGoX6St4qWmNRU1vnYdH9LTzC+EO > > > o/5lbPqV3sqBchd/jCeyCyW55C7WtjwQfBI3piPLovjEdeiGXERm0UA+o8ml4tPW > > > NB5Ms6br4ok= > > > =0Bm/ > > > -----END PGP SIGNATURE----- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 07:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00100 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 07:17:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29994 for ; Fri, 31 Jul 1998 07:17:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA23635; Fri, 31 Jul 1998 07:16:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) cc: "B. Richardson" , Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server In-reply-to: Your message of "31 Jul 1998 15:34:36 +0200." Date: Fri, 31 Jul 1998 07:16:11 -0700 Message-ID: <23632.901894571@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought hotmail was running FreeBSD for at least some of their stuff; why else would they have paid Justin over at Pluto Technologies to port the CAM driver to 2.2.x? - Jordan > "B. Richardson" writes: > > I think hotmail.com may satisfy your curiosities. Maybe the webmaster > > there give you some info. > > Hotmail is owned by Microsoft, and is running Solaris until their > engineers can find a way to make NT sustain that kind of load without > crashing more than once an hour or so. > > DES > -- > Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 07:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02015 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 07:29:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01999 for ; Fri, 31 Jul 1998 07:28:48 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA11429 ; Fri, 31 Jul 1998 16:27:53 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA01800; Fri, 31 Jul 1998 16:27:51 +0200 To: "Jordan K. Hubbard" Cc: "B. Richardson" , Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server References: <23632.901894571@time.cdrom.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 31 Jul 1998 16:27:51 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of Fri, 31 Jul 1998 07:16:11 -0700 Message-ID: Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > I thought hotmail was running FreeBSD for at least some of their > stuff; why else would they have paid Justin over at Pluto Technologies > to port the CAM driver to 2.2.x? Good question. But I remember poring over some of the press coverage at the time when they were bought by Microsoft, looking for references to FreeBSD, and I didn't see any mention of it - only Solaris and NT (they'd tried to convert to the latter, but failed) Whatever OS they run, their mail server does not run Sendmail (or if it does, it's customised - the prompts aren't right for Sendmail) DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 09:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14035 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 09:14:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA14028 for ; Fri, 31 Jul 1998 09:14:48 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z2HpL-00043w-00; Fri, 31 Jul 1998 10:14:43 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id JAA14350; Fri, 31 Jul 1998 09:57:20 -0600 (MDT) Message-Id: <199807311557.JAA14350@harmony.village.org> To: Rob Austein Subject: Re: syscons keymap "us.emacs.kbd" Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Jul 1998 00:23:09 EDT." <19980731042314Z23162-213+60@thrintun.epilogue.com> References: <19980731042314Z23162-213+60@thrintun.epilogue.com> Date: Fri, 31 Jul 1998 09:57:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980731042314Z23162-213+60@thrintun.epilogue.com> Rob Austein writes: : The enclosed is a syscons keymap file, suitable for loading with : kbdcontrol. It implements a varient on the standard US ASCII : keyboard; in particular, it turns the ALT keys into meta keys, and : makes a few other tweaks so that the keyboard will work nicely with : bash and emacs. Or that's the theory, anyway, your milage may vary : radically if you didn't grow up with the MIT Chaosnet, ITS, SUPDUP, : and Lisp Machines.... How does this differ from the us.unix.kbd that I checked in a while ago? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 09:22:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15027 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 09:22:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15022 for ; Fri, 31 Jul 1998 09:22:39 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id SAA06616; Fri, 31 Jul 1998 18:22:07 +0200 (MET DST) Date: Fri, 31 Jul 1998 18:22:05 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Josef Karthauser cc: FreeBSD hackers mailing list Subject: Re: NetBSD now has USB .. In-Reply-To: <19980731123244.B26485@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone progressed on this? No one mailed me back :( Guess what I am going to do this weeked? Nick -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 09:25:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15397 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 09:25:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatewayb.anheuser-busch.com (gatewayb.anheuser-busch.com [151.145.250.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA15392 for ; Fri, 31 Jul 1998 09:25:10 -0700 (PDT) (envelope-from Matthew.Alton@anheuser-busch.com) Received: by gatewayb.anheuser-busch.com; id LAA03761; Fri, 31 Jul 1998 11:23:02 -0500 Received: from stlabcexg006.anheuser-busch.com( 151.145.101.161) by gatewayb via smap (V2.1) id xma002704; Fri, 31 Jul 98 11:22:37 -0500 Received: by STLABCEXG006 with Internet Mail Service (5.5.1960.3) id ; Fri, 31 Jul 1998 11:24:34 -0500 Message-ID: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> From: "Alton, Matthew" To: "'Hackers@FreeBSD.ORG'" Cc: "'chrisa@commlet.com'" Subject: This changes everything Date: Fri, 31 Jul 1998 11:24:42 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm reevaluating the relevance factor of my current work in filesystems in light of the following earthshattering news: http://www.accpc.com/tcapstore.htm This page outlines a radical advance in solid-state mass storage which will replace both conventional HDDs and RAM, thoroughly obsoleting large chunks of kernel code. Granted, the device is currently vapor-hardware and, like many another gadget (bubble memory, protein drive, async processor...), it may well stall indefinitely on the drawing board while the marketroids trumpet its inexorable conquest of the planet, I think it prudent to assume that this one is for real. At any rate, it is certainly safe to assume that devices with the capabilities claimed for this one are very close to taking shape. We should prepare for this inevitable eventuality now and design a prototype kernel which will be able to maximize the benefits of such devices. Perhaps better still, we should negotiate to have FreeBSD installed on each unit at the fab ;-) Matthew Alton Computer Services - UNIX Systems Administration (314)632-6644 matthew.alton@anheuser-busch.com alton@plantnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 10:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19786 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 10:01:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19780 for ; Fri, 31 Jul 1998 10:01:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA24171; Fri, 31 Jul 1998 10:00:35 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Alton, Matthew" cc: "'Hackers@FreeBSD.ORG'" , "'chrisa@commlet.com'" Subject: Re: This changes everything In-reply-to: Your message of "Fri, 31 Jul 1998 11:24:42 CDT." <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> Date: Fri, 31 Jul 1998 10:00:35 -0700 Message-ID: <24167.901904435@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm reevaluating the relevance factor of my current work in > filesystems in light of the following earthshattering news: > http://www.accpc.com/tcapstore.htm Ummmmmm. Reading the copy from this website makes me think of UFOs, Area 51 and the Return Of Elvis though. One would think that if it were for real, there would be far more people talking about it and in much more sober academic journals. "Brandon DeWitt, IIId"? Who the hell is that? I wouldn't sell my Seagate stock just yet, folks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 10:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25674 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 10:40:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pascal.ravel.ufrj.br (pascal.ravel.ufrj.br [146.164.32.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25665 for ; Fri, 31 Jul 1998 10:40:07 -0700 (PDT) (envelope-from rodolfo@ravel.ufrj.br) Received: from galileo.ravel.ufrj.br (galileo.ravel.ufrj.br [146.164.32.68]) by pascal.ravel.ufrj.br (8.9.0/8.9.0) with ESMTP id OAA21119; Fri, 31 Jul 1998 14:33:19 -0300 (EST) From: Rodolfo Heitor Gevaerd de Faria Received: (from rodolfo@localhost) by galileo.ravel.ufrj.br (8.8.8/8.8.8) id OAA00295; Fri, 31 Jul 1998 14:33:19 -0300 (EST) (envelope-from rodolfo@ravel.ufrj.br) Message-Id: <199807311733.OAA00295@galileo.ravel.ufrj.br> Subject: Re: Yet another 3c905B driver update In-Reply-To: <199807311507.MAA15807@protheus.ravel.ufrj.br> from Rodolfo Heitor Gevaerd de Faria at "Jul 31, 98 12:07:18 pm" To: wpaul@skynet.ctr.columbia.edu, hackers@FreeBSD.ORG Date: Fri, 31 Jul 1998 14:33:19 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried your driver and got the following: xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 10 on pci0. 10.0 xl0: Ethernet address: 00:10:4b:64:e6:30 xl0: MII without any phy! xl0: autonegotiation not supported ifmedia_set: no match for 0x20/0xffffffff panic: ifmedia_set Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Any ideas ? Bill Paul was saying that, ^ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 30 22:10:46 1998 ^ From: Bill Paul ^ Message-Id: <199807310031.UAA01432@skynet.ctr.columbia.edu> ^ Subject: Yet another 3c905B driver update ^ To: hackers@FreeBSD.ORG ^ Date: Thu, 30 Jul 1998 20:31:06 -0400 (EDT) ^ X-Mailer: ELM [version 2.4 PL24] ^ Content-Type: text ^ Sender: owner-freebsd-hackers@FreeBSD.ORG ^ X-Loop: FreeBSD.ORG ^ I place yet another version of the 3Com Etherlink XL driver at ^ ^ http://www.freebsd.org/~wpaul/3Com/3.0 and ^ http://www.freebsd.org/~wpaul/3Com/2.2 ^ ^ This version has some more ifmedia fixes that should allow manual media ^ selection not to screw up autoselection on the 3c905B. I've also been able ^ to test a 3c905-TX card and make a few small tweaks for that as well. ^ ^ As always, feedback is encouraged. I think I'm only one or two more ^ revisions away from committing this code to the -current branch. ^ ^ Share and enjoy. ^ ^ -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" ^ ============================================================================= ^ ^ To Unsubscribe: send mail to majordomo@FreeBSD.org ^ with "unsubscribe freebsd-hackers" in the body of the message ^ Rodolfo H G Faria To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 10:44:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26151 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 10:44:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26145 for ; Fri, 31 Jul 1998 10:44:42 -0700 (PDT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id NAA13956 for ; Fri, 31 Jul 1998 13:44:35 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199807311744.NAA13956@spoon.beta.com> To: hackers@FreeBSD.ORG Subject: O_SHLOCK and O_EXLOCK during open... (locking for devices?) Date: Fri, 31 Jul 1998 13:44:35 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, me again with another dumb programming question.... I seem to be running in to problems when opeing up a device special file with either O_SHLOCK or O_EXLOCK. I get an error back (45) that the operation is not supported. My question, then, is, how can I lock, lets say a serial port, without having to go the route of lock-file creation, as many applications ignore these files anyhow? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 11:40:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03380 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 11:40:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mixer.visi.com (mixer.visi.com [209.98.98.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03371 for ; Fri, 31 Jul 1998 11:40:12 -0700 (PDT) (envelope-from khuber@visi.com) Received: from isis.visi.com (khuber@isis.visi.com [209.98.98.8]) by mixer.visi.com (8.8.8/8.7.5) with ESMTP id NAA21839; Fri, 31 Jul 1998 13:40:04 -0500 (CDT) Posted-Date: Fri, 31 Jul 1998 13:40:04 -0500 (CDT) Received: (from khuber@localhost) by isis.visi.com (8.8.8/8.8.8) id NAA27644; Fri, 31 Jul 1998 13:40:02 -0500 (CDT) Date: Fri, 31 Jul 1998 13:40:02 -0500 (CDT) Message-Id: <199807311840.NAA27644@isis.visi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Kevin Huber To: "Alton, Matthew" Cc: "'Hackers@FreeBSD.ORG'" Subject: Re: This changes everything In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> References: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> X-Mailer: VM 6.34 under Emacs 19.34.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alton" == Alton, Matthew writes: Alton> I'm reevaluating the relevance factor of my current work in Alton> filesystems in light of the following earthshattering news: Alton> http://www.accpc.com/tcapstore.htm I believe this is the technology that they got from the aliens. Presumably the aliens have a really stable version of *BSD since they are much more advanced. They apparently have very smart people working for them. It's too bad that Tesla has been reduced to being a system administrator; he showed so much promise as a scientist. -Kevin [root@jedi:~] whois accpc.com Registrant: accpc (ACCPC-DOM) c/o American Computer Company 6 Commerce Dr. Cranford, NJ 07016 US Domain Name: ACCPC.COM Administrative Contact, Technical Contact, Zone Contact: Sysop, Java (JS5587) nicolai_tesla@MSN.COM 908-272-3330 (FAX) 908-272-6297 Billing Contact: Sysop, Java (JS5587) nicolai_tesla@MSN.COM 908-272-3330 (FAX) 908-272-6297 Record last updated on 12-Dec-97. Record created on 12-Dec-97. Database last updated on 31-Jul-98 04:37:55 EDT. Domain servers in listed order: NS1.SYSTEMV.COM 206.214.38.13 SYSV1.SYSTEMV.COM 199.35.37.2 The InterNIC Registration Services database contains ONLY non-military and non-US Government Domains and contacts. Other associated whois servers: American Registry for Internet Numbers - whois.arin.net European IP Address Allocations - whois.ripe.net Asia Pacific IP Address Allocations - whois.apnic.net US Military - whois.nic.mil US Government - whois.nic.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 11:44:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03943 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 11:44:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA03913 for ; Fri, 31 Jul 1998 11:43:53 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA02847; Fri, 31 Jul 1998 14:43:13 -0400 From: Bill Paul Message-Id: <199807311843.OAA02847@skynet.ctr.columbia.edu> Subject: Re: Yet another 3c905B driver update To: rodolfo@ravel.ufrj.br (Rodolfo Heitor Gevaerd de Faria) Date: Fri, 31 Jul 1998 14:43:12 -0400 (EDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199807311733.OAA00295@galileo.ravel.ufrj.br> from "Rodolfo Heitor Gevaerd de Faria" at Jul 31, 98 02:33:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Rodolfo Heitor Gevaerd de Faria had to walk into mine and say: > > I tried your driver and got the following: > > xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 10 on pci0. > 10.0 > xl0: Ethernet address: 00:10:4b:64:e6:30 > xl0: MII without any phy! > xl0: autonegotiation not supported > ifmedia_set: no match for 0x20/0xffffffff > panic: ifmedia_set > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > Any ideas ? I need more information. Exactly what model card is this? (I mean, what does it say on the packaging.) What modes is it supposed to support? This is very odd: my understanding is that all the 3c905B cards support autoneg through a faked-up MII interface. You can temporarily avoid the panic by commenting out the call to ifmedia_set() at the end of xl_attach(). -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" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 12:14:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07484 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:14:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tarsier.domain.net (tarsier.domain.net [204.107.140.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07479 for ; Fri, 31 Jul 1998 12:14:23 -0700 (PDT) (envelope-from eric@tarsier.domain.net) Received: (from eric@localhost) by tarsier.domain.net (8.8.7/8.8.5) id MAA14727; Fri, 31 Jul 1998 12:14:09 -0700 (PDT) Message-ID: <19980731121409.14537@tarsier.domain.net> Date: Fri, 31 Jul 1998 12:14:09 -0700 From: eric To: "Jordan K. Hubbard" Cc: "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" , "'chrisa@commlet.com'" Subject: Re: This changes everything References: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> <24167.901904435@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e In-Reply-To: <24167.901904435@time.cdrom.com>; from Jordan K. Hubbard on Fri, Jul 31, 1998 at 10:00:35AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are a couple of things in there that seem to violate the laws of physics, as well. :) I don't think moving a megabit of data in a nanosecond can take "negligible" power, for instance. :) Also, the picture of the "wafer" looks like a piece of monopoly money that someone photoshopped badly. It's pretty entertaining though. Oh, also power consumption isn't measured in mA per hour. :) eric On Fri, Jul 31, 1998 at 10:00:35AM -0700, Jordan K. Hubbard wrote: > > I'm reevaluating the relevance factor of my current work in > > filesystems in light of the following earthshattering news: > > http://www.accpc.com/tcapstore.htm > > Ummmmmm. Reading the copy from this website makes me think of UFOs, > Area 51 and the Return Of Elvis though. One would think that if it > were for real, there would be far more people talking about it and in > much more sober academic journals. "Brandon DeWitt, IIId"? Who the > hell is that? > > I wouldn't sell my Seagate stock just yet, folks. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 12:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08309 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:16:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08301 for ; Fri, 31 Jul 1998 12:16:46 -0700 (PDT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id PAA14142; Fri, 31 Jul 1998 15:16:37 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199807311916.PAA14142@spoon.beta.com> To: Open Systems Networking cc: hackers@FreeBSD.ORG Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) In-reply-to: Your message of "Fri, 31 Jul 1998 14:55:19 EDT." Date: Fri, 31 Jul 1998 15:16:36 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the feedback... uu_lock and family is possible to use, but it will fail with applications that don't check or use the facility ( a lot of poorly written ones). I need something thats more kernel-oriented, that will catch a lock issue during the open() call. I'd even make the changes in the driver(s), if required, but it appears the error is caused outside of the driver open() call, and therefore I really can't hook in to it until its too late. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 12:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11690 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:41:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11685 for ; Fri, 31 Jul 1998 12:41:00 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA353 for ; Fri, 31 Jul 1998 12:54:45 -0600 Received: (from chanders@localhost) by count.timing.com (8.8.7/8.8.7) id MAA04187 for freebsd-hackers@FreeBSD.ORG; Fri, 31 Jul 1998 12:53:12 -0600 (MDT) (envelope-from chanders) Date: Fri, 31 Jul 1998 12:53:12 -0600 (MDT) From: chanders@timing.com (Craig Anderson) Message-Id: <199807311853.MAA04187@count.timing.com> To: freebsd-hackers@FreeBSD.ORG Subject: Using FreeBSD for data acquisition? (long) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My company is considering using FreeBSD for a data acquisition application. We want to know if an upper bound be placed on the latency of an application reading data from a data acquisition board? FreeBSD is being considered first and then commercial RTOS's will be tried. A test project is being done. The project uses an ISA data acquisition board. The board interrupts 500 times a second, an 8 byte data block is read from the board on each interrupt. There is a driver lkm for the board: a) driver buffers 4k data blocks. b) driver interrupt function reads 1 data block, stores data block in buffer, wakes the reader. c) driver read function waits for at least 1 data block, returns minimum of requested data blocks and available data blocks. A test application: a) Loops forever requesting 4096 data blocks. b) Saves the number of data blocks returned on each read to a file. Because the interrupts/data blocks arrive at 500 HZ, I am interpreting the number of data blocks returned on a read as a measure of read latency of the application. If the read returns 50 data blocks, it has been .1 second since the last read. (50/500 = .1) Below are code fragments from the test application. The rtprio() call is to put the process into RTP_PRIO_REALTIME. Should this make a difference? Is the code correct? At the end of the message is histogram data for a test run of about 15 hours. I plot the data with gnuplot, using a logscale for y. Note that the longest read is 480 (480/500 = .960 seconds). Note that the most common read is 50 (50/500 = .100 seconds). I'd like comments from FreeBSD hackers out there. Can an upper bound be put on the read latency? An upper bound of about .100 seconds is probably acceptable. Why is a read latency of .100 seconds (50 data blocks) so common? Should RTP_PRIO_REALTIME help? Does FreeBSD 3 have realtime features that will help? Is there a problem with the code or a better approach? Thanks in advance for any comments. Code from test application -------------------------- rtp.type = RTP_PRIO_REALTIME; rtp.prio = 0; istat = rtprio (RTP_SET, 0, &rtp); ... fd = open (DEV_PATH, O_RDONLY, 0); ... istat = ioctl(fd,GT401_START_EVENTS,&arg_ioctl); ... for (;;) { istat = read (fd,(void *)&(ttag_buf[0]),read_req); read_data_count = istat / sizeof(gt401_read); printf ("%d\n",read_data_count); fflush(stdout); } /* for (;;) */ Histogram: number of data blocks returned on a read --------------------------------------------------- col1=number of data blocks returned by a read col2=number of reads that returned this many data blocks # 1 compute bound, slow interrupt # Thu Jul 30 17:47:58 MDT 1998 # period=0.002000 freq=500.000000 RTPRIO # max count=480 total count=28303071 1.000000 134048 2.000000 27911 3.000000 4324 4.000000 2003 5.000000 5564 6.000000 4066 7.000000 3911 8.000000 2695 9.000000 2714 10.000000 5091 11.000000 2536 12.000000 2016 13.000000 298 14.000000 657 15.000000 3808 16.000000 1651 17.000000 1489 18.000000 62 19.000000 7897 20.000000 49226 21.000000 1406 22.000000 1432 23.000000 47 24.000000 404 25.000000 3190 26.000000 1537 27.000000 1346 28.000000 64 29.000000 5054 30.000000 51876 31.000000 1413 32.000000 1254 33.000000 50 34.000000 327 35.000000 2890 36.000000 1454 37.000000 1230 38.000000 44 39.000000 367 40.000000 2960 41.000000 1469 42.000000 1312 43.000000 29 44.000000 397 45.000000 2821 46.000000 1570 47.000000 1123 48.000000 184 49.000000 55950 50.000000 412800 51.000000 5 52.000000 6 53.000000 0 54.000000 2 55.000000 1 56.000000 0 57.000000 0 58.000000 2 59.000000 0 60.000000 1 61.000000 3 62.000000 2 63.000000 6 64.000000 4 65.000000 8 66.000000 19 67.000000 22 68.000000 26 69.000000 29 70.000000 8 71.000000 0 72.000000 1 73.000000 0 74.000000 1 75.000000 0 76.000000 1 77.000000 0 78.000000 1 79.000000 2 80.000000 18 81.000000 12 82.000000 25 83.000000 23 84.000000 0 85.000000 1 86.000000 0 87.000000 0 88.000000 0 89.000000 1 90.000000 0 91.000000 0 92.000000 0 93.000000 0 94.000000 0 95.000000 2 96.000000 2 97.000000 2 98.000000 0 99.000000 0 100.000000 6 101.000000 1 102.000000 0 103.000000 0 104.000000 1 105.000000 1 106.000000 1 107.000000 0 108.000000 0 109.000000 1 110.000000 0 111.000000 0 112.000000 0 113.000000 4 114.000000 5 115.000000 7 116.000000 16 117.000000 24 118.000000 28 119.000000 26 120.000000 11 121.000000 0 122.000000 0 123.000000 0 124.000000 0 125.000000 0 126.000000 0 127.000000 0 128.000000 1 129.000000 3 130.000000 14 131.000000 17 132.000000 23 133.000000 13 134.000000 0 135.000000 0 136.000000 1 137.000000 1 138.000000 0 139.000000 0 140.000000 0 141.000000 0 142.000000 3 143.000000 1 144.000000 5 145.000000 1 146.000000 0 147.000000 1 148.000000 0 149.000000 2 150.000000 4 151.000000 0 152.000000 5 153.000000 0 154.000000 0 155.000000 2 156.000000 0 157.000000 1 158.000000 1 159.000000 0 160.000000 0 161.000000 0 162.000000 0 163.000000 5 164.000000 9 165.000000 6 166.000000 9 167.000000 21 168.000000 12 169.000000 20 170.000000 10 171.000000 0 172.000000 0 173.000000 0 174.000000 0 175.000000 0 176.000000 0 177.000000 1 178.000000 0 179.000000 1 180.000000 12 181.000000 19 182.000000 13 183.000000 16 184.000000 0 185.000000 0 186.000000 1 187.000000 0 188.000000 0 189.000000 0 190.000000 0 191.000000 0 192.000000 0 193.000000 0 194.000000 0 195.000000 0 196.000000 0 197.000000 1 198.000000 0 199.000000 2 200.000000 5 201.000000 1 202.000000 0 203.000000 0 204.000000 0 205.000000 2 206.000000 0 207.000000 0 208.000000 0 209.000000 3 210.000000 0 211.000000 1 212.000000 1 213.000000 3 214.000000 4 215.000000 4 216.000000 9 217.000000 14 218.000000 25 219.000000 19 220.000000 10 221.000000 1 222.000000 0 223.000000 0 224.000000 0 225.000000 0 226.000000 0 227.000000 0 228.000000 0 229.000000 0 230.000000 24 231.000000 26 232.000000 21 233.000000 22 234.000000 0 235.000000 0 236.000000 0 237.000000 1 238.000000 1 239.000000 1 240.000000 0 241.000000 0 242.000000 0 243.000000 0 244.000000 0 245.000000 3 246.000000 0 247.000000 0 248.000000 0 249.000000 1 250.000000 3 251.000000 0 252.000000 0 253.000000 0 254.000000 1 255.000000 0 256.000000 0 257.000000 0 258.000000 0 259.000000 0 260.000000 0 261.000000 2 262.000000 1 263.000000 4 264.000000 6 265.000000 1 266.000000 10 267.000000 23 268.000000 11 269.000000 25 270.000000 10 271.000000 0 272.000000 0 273.000000 0 274.000000 0 275.000000 0 276.000000 0 277.000000 1 278.000000 0 279.000000 0 280.000000 27 281.000000 23 282.000000 21 283.000000 19 284.000000 0 285.000000 0 286.000000 0 287.000000 0 288.000000 0 289.000000 0 290.000000 0 291.000000 0 292.000000 0 293.000000 0 294.000000 0 295.000000 3 296.000000 0 297.000000 2 298.000000 1 299.000000 1 300.000000 1 301.000000 0 302.000000 0 303.000000 0 304.000000 2 305.000000 2 306.000000 0 307.000000 0 308.000000 0 309.000000 0 310.000000 0 311.000000 1 312.000000 1 313.000000 2 314.000000 1 315.000000 5 316.000000 6 317.000000 9 318.000000 19 319.000000 12 320.000000 7 321.000000 0 322.000000 0 323.000000 0 324.000000 0 325.000000 0 326.000000 0 327.000000 0 328.000000 0 329.000000 0 330.000000 19 331.000000 25 332.000000 37 333.000000 25 334.000000 0 335.000000 0 336.000000 0 337.000000 0 338.000000 0 339.000000 0 340.000000 0 341.000000 0 342.000000 0 343.000000 0 344.000000 0 345.000000 1 346.000000 0 347.000000 1 348.000000 0 349.000000 0 350.000000 1 351.000000 0 352.000000 0 353.000000 2 354.000000 2 355.000000 1 356.000000 0 357.000000 0 358.000000 0 359.000000 0 360.000000 0 361.000000 0 362.000000 0 363.000000 1 364.000000 1 365.000000 4 366.000000 6 367.000000 24 368.000000 21 369.000000 11 370.000000 11 371.000000 0 372.000000 0 373.000000 0 374.000000 0 375.000000 0 376.000000 0 377.000000 0 378.000000 0 379.000000 0 380.000000 33 381.000000 33 382.000000 30 383.000000 24 384.000000 1 385.000000 0 386.000000 0 387.000000 0 388.000000 0 389.000000 0 390.000000 0 391.000000 0 392.000000 0 393.000000 0 394.000000 0 395.000000 1 396.000000 0 397.000000 0 398.000000 0 399.000000 0 400.000000 0 401.000000 0 402.000000 0 403.000000 0 404.000000 1 405.000000 1 406.000000 0 407.000000 0 408.000000 0 409.000000 1 410.000000 0 411.000000 0 412.000000 0 413.000000 1 414.000000 0 415.000000 1 416.000000 1 417.000000 19 418.000000 13 419.000000 15 420.000000 34 421.000000 0 422.000000 0 423.000000 0 424.000000 0 425.000000 0 426.000000 1 427.000000 0 428.000000 0 429.000000 0 430.000000 55 431.000000 19 432.000000 21 433.000000 22 434.000000 0 435.000000 0 436.000000 0 437.000000 3 438.000000 0 439.000000 0 440.000000 0 441.000000 0 442.000000 1 443.000000 0 444.000000 0 445.000000 1 446.000000 0 447.000000 0 448.000000 0 449.000000 0 450.000000 82 451.000000 0 452.000000 1 453.000000 0 454.000000 0 455.000000 0 456.000000 0 457.000000 0 458.000000 0 459.000000 0 460.000000 0 461.000000 0 462.000000 0 463.000000 0 464.000000 0 465.000000 0 466.000000 0 467.000000 2 468.000000 0 469.000000 1 470.000000 34 471.000000 1 472.000000 0 473.000000 0 474.000000 0 475.000000 1 476.000000 0 477.000000 0 478.000000 0 479.000000 0 480.000000 31 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 12:43:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12234 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:43:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12224 for ; Fri, 31 Jul 1998 12:43:18 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA07690; Fri, 31 Jul 1998 14:43:13 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA12846; Fri, 31 Jul 1998 14:42:41 -0500 Message-ID: <19980731144241.44313@right.PCS> Date: Fri, 31 Jul 1998 14:42:41 -0500 From: Jonathan Lemon To: "Alton, Matthew" Cc: "'Hackers@FreeBSD.ORG'" , "'chrisa@commlet.com'" Subject: Re: This changes everything References: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011>; from Alton, Matthew on Jul 07, 1998 at 11:24:42AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1998 at 11:24:42AM -0500, Alton, Matthew wrote: > I'm reevaluating the relevance factor of my current work in > filesystems in light of the following earthshattering news: > http://www.accpc.com/tcapstore.htm Gah. I think that Jordan got this one right. Do you really trust a company that also has a page like the following? http://www.accpc.com/publications.htm Go and read . This one should at least bring some hilarity to the proceedings. I really wonder if they also have Professor "time and space are equivalent" Abian working there as well. :-) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 12:48:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13420 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 12:48:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ppp1609.on.bellglobal.com (ppp1609.on.bellglobal.com [206.172.249.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13415 for ; Fri, 31 Jul 1998 12:48:55 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: (from tim@localhost) by ppp1609.on.bellglobal.com (8.8.8/8.8.8) id PAA12512; Fri, 31 Jul 1998 15:49:05 -0400 (EDT) (envelope-from tim) Message-ID: <19980731154905.B12343@zappo> Date: Fri, 31 Jul 1998 15:49:05 -0400 From: Tim Vanderhoek To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , "Jordan K. Hubbard" Cc: "B. Richardson" , Jacques Vidrine , hackers@FreeBSD.ORG Subject: Re: biggest mail server References: <23632.901894571@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: =?iso-8859-1?Q?=3Crx4iukew0wo=2Efsf=40oslo=2Egeco-prakla=2Eslb=2Ecom=3E?= =?iso-8859-1?Q?=3B_from_Dag-Erling_Coidan_Sm=F8rgrav_on_Fri=2C_Jul_31=2C?= =?iso-8859-1?Q?_1998_at_04:27:51PM_+0200?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 04:27:51PM +0200, Dag-Erling Coidan Smørgrav wrote: > > Whatever OS they run, their mail server does not run Sendmail (or if > it does, it's customised - the prompts aren't right for Sendmail) qmail, judging from the Message-IDs they attach to messages that pass through them. Eg. Message-ID: <19971031040318.27155.qmail@hotmail.com> -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 13:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18496 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 13:24:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18486; Fri, 31 Jul 1998 13:24:48 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807312024.NAA18486@hub.freebsd.org> Subject: Re: biggest mail server In-Reply-To: <19980731154905.B12343@zappo> from Tim Vanderhoek at "Jul 31, 98 03:49:05 pm" To: ac199@hwcn.org (Tim Vanderhoek) Date: Fri, 31 Jul 1998 13:24:48 -0700 (PDT) Cc: smoergrd@oslo.geco-prakla.slb.com, jkh@time.cdrom.com, rabtter@aye.net, n@nectar.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Vanderhoek wrote: > On Fri, Jul 31, 1998 at 04:27:51PM +0200, Dag-Erling Coidan Smørgrav wrote: > > > > Whatever OS they run, their mail server does not run Sendmail (or if > > it does, it's customised - the prompts aren't right for Sendmail) > > qmail, judging from the Message-IDs they attach to messages that pass > through them. Eg. > > Message-ID: <19971031040318.27155.qmail@hotmail.com> they may be using some other software to receive mail which is then passed off to ........ and so on till qmail is used to send it out? Trying 209.1.112.253... Connected to mail.hotmail.com. Escape character is '^]'. 220 m33.hotmail.com Server SMTP ready at Fri, 31 Jul 1998 13:24:14 +0100 help 241-Copyright 1997 Hotmail Corp. 241- 241-The following commands are recognized: 241- helo, mail, rcpt, data, send, soml, saml, rset, vrfy, expn, help 241- noop, quit, turn, onex, tick, emal, esnd, esom, esam, evfy 241- 241-The normal sequence is: helo (mail rcpt+ data)+ quit. 241- 241-This mailer always accepts 8-bit and binary message data. 241- 241-For local information contact: postmaster@m33.hotmail.com 241 SMTP server comments and bug reports to: zmhacks@cs.toronto.edu quit 221 m33.hotmail.com Out Connection closed by foreign host. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 13:29:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19350 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 13:29:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19341 for ; Fri, 31 Jul 1998 13:29:22 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA19016; Fri, 31 Jul 1998 14:29:10 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA11338; Fri, 31 Jul 1998 14:28:55 -0600 Date: Fri, 31 Jul 1998 14:28:55 -0600 Message-Id: <199807312028.OAA11338@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jonathan Lemon Cc: "Alton, Matthew" , "'Hackers@FreeBSD.ORG'" , "'chrisa@commlet.com'" Subject: Re: This changes everything In-Reply-To: <19980731144241.44313@right.PCS> References: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> <19980731144241.44313@right.PCS> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm reevaluating the relevance factor of my current work in > > filesystems in light of the following earthshattering news: > > http://www.accpc.com/tcapstore.htm > > Gah. > > I think that Jordan got this one right. Do you really trust > a company that also has a page like the following? > > http://www.accpc.com/publications.htm Agreed. Look at their homepage, and note the similarity of the package of a Pentium-II chip and their 'hardware' disk. A couple of minutes with a paint program and you've got your new disk. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 13:56:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24876 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 13:56:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24871 for ; Fri, 31 Jul 1998 13:56:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00498; Fri, 31 Jul 1998 13:55:30 -0700 (PDT) Message-Id: <199807312055.NAA00498@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: chanders@timing.com (Craig Anderson) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) In-reply-to: Your message of "Fri, 31 Jul 1998 12:53:12 MDT." <199807311853.MAA04187@count.timing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 13:55:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My company is considering using FreeBSD for a data acquisition > application. We want to know if an upper bound be placed on the > latency of an application reading data from a data acquisition > board? FreeBSD is being considered first and then commercial RTOS's > will be tried. No, there is no upper bound. Your response time will vary depending on a large number of factors, eg. swap activity, other driver activity, hardware errors, etc. > A test project is being done. The project uses an ISA data > acquisition board. The board interrupts 500 times a second, an 8 > byte data block is read from the board on each interrupt. > > There is a driver lkm for the board: a) driver buffers 4k data > blocks. b) driver interrupt function reads 1 data block, stores > data block in buffer, wakes the reader. c) driver read function > waits for at least 1 data block, returns minimum of requested data > blocks and available data blocks. > > A test application: a) Loops forever requesting 4096 data blocks. > b) Saves the number of data blocks returned on each read to a file. > > Because the interrupts/data blocks arrive at 500 HZ, I am interpreting > the number of data blocks returned on a read as a measure of read > latency of the application. If the read returns 50 data blocks, it > has been .1 second since the last read. (50/500 = .1) > > Below are code fragments from the test application. The rtprio() > call is to put the process into RTP_PRIO_REALTIME. Should this > make a difference? Is the code correct? You haven't included enough code to be certain that your device driver is working properly. I suspect that it might not be. > At the end of the message is histogram data for a test run of about > 15 hours. I plot the data with gnuplot, using a logscale for y. > Note that the longest read is 480 (480/500 = .960 seconds). Note > that the most common read is 50 (50/500 = .100 seconds). This would tend to indicate a possible problem with the interaction between your interrupt handler and the read handler, but it's impossible to tell without seeing the code. > I'd like comments from FreeBSD hackers out there. Can an upper > bound be put on the read latency? An upper bound of about .100 seconds > is probably acceptable. Why is a read latency of .100 seconds (50 > data blocks) so common? Should RTP_PRIO_REALTIME help? Does FreeBSD > 3 have realtime features that will help? Is there a problem with > the code or a better approach? In a soft-realtime project I was working on last year, we used the rtprio facility to expedite the data handling process. We were able to meet a hardware-mandated 100msec delay with light loading under some circumstances, but this was not sustainable if disk I/O was being performed (we were saving incoming data at >1MB/sec). There are enhanced realtime facilities in FreeBSD 3.0 which would help in some cases, however it's not clear from your message what your real goals are. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 14:00:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25867 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 14:00:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bangkok.office.cdsnet.net (bangkok.office.cdsnet.net [204.118.245.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25758 for ; Fri, 31 Jul 1998 14:00:08 -0700 (PDT) (envelope-from cts@bangkok.office.cdsnet.net) Received: (from cts@localhost) by bangkok.office.cdsnet.net (8.8.8/8.8.5) id NAA18156; Fri, 31 Jul 1998 13:59:56 -0700 (PDT) Date: Fri, 31 Jul 1998 13:59:56 -0700 (PDT) Message-Id: <199807312059.NAA18156@bangkok.office.cdsnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Craig Spannring To: chanders@timing.com (Craig Anderson) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) In-Reply-To: <199807311853.MAA04187@count.timing.com> References: <199807311853.MAA04187@count.timing.com> X-Mailer: VM 6.31 under Emacs 20.2.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That pretty much matches what I'm seeing for a server I'm writing. My server must respond in less than 3 seconds. Normally it is able to respond in a millisecond or two, but occasionally it takes around 1000 milliseconds. I've duplicated the problem occurring even under real time priority with no other processes on the machine except for init, pagedaemon, vmdaemon, update, and one csh. I had virtual memory disabled to eliminate any paging activity. I tracked the problem down to the fact that I'm not getting any CPU time for a substantial (at least up to 500 milliseconds) amount of time even though I'm using rtprio and there is nothing else that should be running. For years I've said that Unix is not a RTOS. For my application I think I can get by with FreeBSD. Your application sounds like it is more critical RT and I would recommend you go with a RTOS. In regards to your question of why 0.100 seconds is so common, FreeBSD uses a 10msec quantum. I suspect if you change kern.quantum to some other value then the other value will become more common. Let me know if you find some way that helps the latency. -- ======================================================================= Life is short. | Craig Spannring Ski hard, Bike fast. | cts@internetcds.com --------------------------------+------------------------------------ Any sufficiently perverted technology is indistinguishable from Perl. ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 14:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27476 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 14:04:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27449; Fri, 31 Jul 1998 14:04:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA00599; Fri, 31 Jul 1998 14:04:06 -0700 (PDT) Message-Id: <199807312104.OAA00599@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jonathan M. Bresler" cc: ac199@hwcn.org (Tim Vanderhoek), smoergrd@oslo.geco-prakla.slb.com, jkh@time.cdrom.com, rabtter@aye.net, n@nectar.com, hackers@FreeBSD.ORG Subject: Re: biggest mail server In-reply-to: Your message of "Fri, 31 Jul 1998 13:24:48 PDT." <199807312024.NAA18486@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 31 Jul 1998 14:04:05 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA27451 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tim Vanderhoek wrote: > > On Fri, Jul 31, 1998 at 04:27:51PM +0200, Dag-Erling Coidan Smørgrav wrote: > > > > > > Whatever OS they run, their mail server does not run Sendmail (or if > > > it does, it's customised - the prompts aren't right for Sendmail) > > > > qmail, judging from the Message-IDs they attach to messages that pass > > through them. Eg. > > > > Message-ID: <19971031040318.27155.qmail@hotmail.com> > > they may be using some other software to receive mail > which is then passed off to ........ and so on till > qmail is used to send it out? > > Trying 209.1.112.253... > Connected to mail.hotmail.com. > Escape character is '^]'. > 220 m33.hotmail.com Server SMTP ready at Fri, 31 Jul 1998 13:24:14 +0100 > help > 241-Copyright 1997 Hotmail Corp. > 241- > 241-The following commands are recognized: > 241- helo, mail, rcpt, data, send, soml, saml, rset, vrfy, expn, help > 241- noop, quit, turn, onex, tick, emal, esnd, esom, esam, evfy > 241- > 241-The normal sequence is: helo (mail rcpt+ data)+ quit. > 241- > 241-This mailer always accepts 8-bit and binary message data. > 241- > 241-For local information contact: postmaster@m33.hotmail.com > 241 SMTP server comments and bug reports to: zmhacks@cs.toronto.edu ^^^^^^^^^^^^^^^^^^^^^^ Looks like Zmailer or something else 'z'ish to me. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 14:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05201 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 14:39:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05196 for ; Fri, 31 Jul 1998 14:39:14 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA21223; Fri, 31 Jul 1998 14:39:02 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd021197; Fri Jul 31 14:38:59 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA00938; Fri, 31 Jul 1998 14:38:53 -0700 (MST) From: Terry Lambert Message-Id: <199807312138.OAA00938@usr09.primenet.com> Subject: Re: biggest mail server To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm?rgrav) Date: Fri, 31 Jul 1998 21:38:53 +0000 (GMT) Cc: jkh@time.cdrom.com, rabtter@aye.net, n@nectar.com, hackers@FreeBSD.ORG In-Reply-To: from "Dag-Erling Coidan Sm?rgrav" at Jul 31, 98 04:27:51 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I thought hotmail was running FreeBSD for at least some of their > > stuff; why else would they have paid Justin over at Pluto Technologies > > to port the CAM driver to 2.2.x? > > Good question. But I remember poring over some of the press coverage > at the time when they were bought by Microsoft, looking for references > to FreeBSD, and I didn't see any mention of it - only Solaris and NT > (they'd tried to convert to the latter, but failed) That was a Sun press release being covered. Unfortunately, FreeBSD didn't make press releases at the same time, and now everyone thinks they are a pure Solaris shop, and ignores FreeBSD. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 14:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05600 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 14:41:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from timingpdc.timing.com (timingpdc.timing.com [208.203.137.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05585 for ; Fri, 31 Jul 1998 14:41:30 -0700 (PDT) (envelope-from chanders@timing.com) Received: from count.timing.com ([208.203.137.222]) by timingpdc.timing.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 103-49575U100L2S100) with ESMTP id AAA317; Fri, 31 Jul 1998 15:33:07 -0600 Received: from count.timing.com (localhost.timing.com [127.0.0.1]) by count.timing.com (8.8.7/8.8.7) with ESMTP id PAA04940; Fri, 31 Jul 1998 15:31:37 -0600 (MDT) (envelope-from chanders@count.timing.com) Message-Id: <199807312131.PAA04940@count.timing.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) In-reply-to: Your message of "Fri, 31 Jul 1998 13:55:30 PDT." <199807312055.NAA00498@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_18363059200" Date: Fri, 31 Jul 1998 15:31:37 -0600 From: chanders@timing.com (Craig Anderson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_18363059200 Content-Type: text/plain; charset=us-ascii I've attached all the source. Thanks again. > > > > My company is considering using FreeBSD for a data acquisition > > application. We want to know if an upper bound be placed on the > > latency of an application reading data from a data acquisition > > board? FreeBSD is being considered first and then commercial RTOS's > > will be tried. > > No, there is no upper bound. Your response time will vary depending on > a large number of factors, eg. swap activity, other driver activity, > hardware errors, etc. > > > A test project is being done. The project uses an ISA data > > acquisition board. The board interrupts 500 times a second, an 8 > > byte data block is read from the board on each interrupt. > > > > There is a driver lkm for the board: a) driver buffers 4k data > > blocks. b) driver interrupt function reads 1 data block, stores > > data block in buffer, wakes the reader. c) driver read function > > waits for at least 1 data block, returns minimum of requested data > > blocks and available data blocks. > > > > A test application: a) Loops forever requesting 4096 data blocks. > > b) Saves the number of data blocks returned on each read to a file. > > > > Because the interrupts/data blocks arrive at 500 HZ, I am interpreting > > the number of data blocks returned on a read as a measure of read > > latency of the application. If the read returns 50 data blocks, it > > has been .1 second since the last read. (50/500 = .1) > > > > Below are code fragments from the test application. The rtprio() > > call is to put the process into RTP_PRIO_REALTIME. Should this > > make a difference? Is the code correct? > > You haven't included enough code to be certain that your device driver > is working properly. I suspect that it might not be. > > > At the end of the message is histogram data for a test run of about > > 15 hours. I plot the data with gnuplot, using a logscale for y. > > Note that the longest read is 480 (480/500 = .960 seconds). Note > > that the most common read is 50 (50/500 = .100 seconds). > > This would tend to indicate a possible problem with the interaction > between your interrupt handler and the read handler, but it's > impossible to tell without seeing the code. > > > I'd like comments from FreeBSD hackers out there. Can an upper > > bound be put on the read latency? An upper bound of about .100 seconds > > is probably acceptable. Why is a read latency of .100 seconds (50 > > data blocks) so common? Should RTP_PRIO_REALTIME help? Does FreeBSD > > 3 have realtime features that will help? Is there a problem with > > the code or a better approach? > > In a soft-realtime project I was working on last year, we used the > rtprio facility to expedite the data handling process. We were able to > meet a hardware-mandated 100msec delay with light loading under some > circumstances, but this was not sustainable if disk I/O was being > performed (we were saving incoming data at >1MB/sec). > > There are enhanced realtime facilities in FreeBSD 3.0 which would help > in some cases, however it's not clear from your message what your real > goals are. > > > --==_Exmh_18363059200 Content-Type: text/plain ; name="gt401.h"; charset=us-ascii Content-Description: gt401.h Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="gt401.h" #if !defined(gt401_h) # define gt401_h #include /* units of pt4 are 0.4 x 10^-6 sec */ #define D_TYPE_NONE 99 #define D_TYPE_ERROR 1 #define D_TYPE_TIMETAG 2 #define MIN_PERIOD_X_10000 1 #define MAX_PERIOD_X_10000 50000 typedef struct gt401_read_s { short overflow; short d_type; union { struct { unsigned int board_index; long long board_time_tag_usec; unsigned int driver_index; long long driver_board_usec; } tt; struct { short err_code; char err_str[58]; } ee; } dd; } gt401_read; #define GT401_START_EVENTS \ _IOW('G', 1, int) #define GT401_STOP_EVENTS \ _IO('G', 2) #define GT401_GET_HIGH_WATER \ _IOR('G', 3, int) #define GT401_CLEAR_HIGH_WATER \ _IO('G', 4) #endif /* #if !defined(gt401_h) */ --==_Exmh_18363059200 Content-Type: text/plain ; name="Makefile"; charset=us-ascii Content-Description: Makefile Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Makefile" # $Id: Makefile,v 1.12 1998/07/30 17:19:23 chanders Exp $ =2EPATH: . KMOD =3D gt401_mod SRCS =3D gt401.c gt401.h ngt401.h #MAN4 =3D gt401.4 #MAN8 =3D gt401in.8 LN =3D ln -f -s CFLAGS +=3D \ -I. \ -I/usr/src/sys \ -DGT401_MODULE CLEANFILES +=3D ngt401.h ngt401.h: echo "#define NGT401 1" > ngt401.h r0: gt401_mod.o cp gt401_mod.o \ /usr/local/tsc/rel/bin test03: test03.c cc -o test03 test03.c test04: test04.c cc -o test04 test04.c test05: test05.c cc -o test05 test05.c test06: test06.c cc -g -o test06 test06.c test07: test07.c cc -g -o test07 test07.c test08: test08.c cc -g -o test08 test08.c log_read_counts_980726: log_read_counts_980726.c cc -g -o log_read_counts_980726 log_read_counts_980726.c counts_to_histogram: counts_to_histogram.c cc -g -o counts_to_histogram counts_to_histogram.c kmem_gt401: kmem_gt401.c cc -g -o kmem_gt401 kmem_gt401.c =2Einclude --==_Exmh_18363059200 Content-Type: text/plain ; name="gt401.c"; charset=us-ascii Content-Description: gt401.c Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="gt401.c" #include #include #include #include #include #include #include #include #include #include #include #include #include #include "ngt401.h" #include "gt401.h" #define UNIT(d) (minor(d) >> 16) #define CDEV_MAJOR 90 #define MAX_GT401_RBUF (4*1024) enum { io_addr_status_reg =3D 0, io_addr_ram_addr_reg =3D 0, io_addr_cont_reg_1 =3D 1, io_addr_cont_reg_2 =3D 2, io_addr_mux_addr_reg =3D 3, io_addr_mux_data_reg =3D 4, io_addr_8254_data_reg =3D 5, io_addr_us_count0 =3D 6, io_addr_us_count1 =3D 7, io_addr_cmd_ready =3D 7, io_addr_dp_ram =3D 8, io_addr_err_reg =3D 13, dp_ram_lus_page =3D 0, dp_ram_command_first_page =3D 144, dp_ram_status_page =3D 146, mux_54_ctr_0 =3D 0, mux_54_ctr_1 =3D 8, mux_54_ctr_2 =3D 16, mux_54_cont =3D 24, cmd_poll_inner_loop =3D 512, cmd_poll_sleep_loop =3D 20, cmd_poll_usleep =3D 10000, cmd_buf_sz =3D 20, cmd_init =3D 1, cmd_self_test =3D 2, cmd_nop =3D 3, cmd_ext_osc =3D 7, cmd_pulse =3D 8, cmd_tt =3D 9, cmd_chan_off =3D 12, cmd_tt_size =3D 13, cmd_clr_tt =3D 15, cmd_clr_err =3D 20, cont_reg1_src_mask =3D 7, cont_reg1_pulse_en =3D 0x08, cont_reg1_sw_pulse =3D 0x10, status_reg_ready_for_cmd =3D 1, cont_reg2_irq_src_mask =3D 7, cont_reg2_irq_src_chan0 =3D 0, cont_reg2_irq_src_chan1 =3D 1, cont_reg2_irq_src_chan2 =3D 2, cont_reg2_irq_src_chan3 =3D 3, cont_reg2_irq_src_board_proc =3D 4, cont_reg2_irq_src_out0 =3D 5, cont_reg2_irq_src_out1 =3D 6, cont_reg2_irq_src_out2 =3D 7, cont_reg2_intr_en_bit =3D 0x08, cont_reg2_intr_edge_bit =3D 0x10, conn_CLK0 =3D 0, /* All CLKn values must be consecutive */ conn_CLK1 =3D 1, conn_CLK2 =3D 2, conn_EXT_CLK0 =3D 3, /* All EXT_CLKn values must be consecutive */ conn_EXT_CLK1 =3D 4, conn_EXT_CLK2 =3D 5, conn_GATE0 =3D 6, /* All GATEn values must be consecutive */ conn_GATE1 =3D 7, conn_GATE2 =3D 8, conn_EXT_GATE0 =3D 9, /* All EXT_GATEn values must be consecutive */ conn_EXT_GATE1 =3D 10, conn_EXT_GATE2 =3D 11, conn_OUT0 =3D 12, /* All OUTn values must be consecutive */ conn_OUT1 =3D 13, conn_OUT2 =3D 14, conn_IO_CHAN0 =3D 15, /* All IO_CHANn values must be consecutive */ conn_IO_CHAN1 =3D 16, conn_IO_CHAN2 =3D 17, conn_IO_CHAN3 =3D 18, conn_EXT_CHAN0 =3D 19, /* all EXT_CHANNn values must be consecutive */= conn_EXT_CHAN1 =3D 20, conn_EXT_CHAN2 =3D 21, conn_EXT_CHAN3 =3D 22, conn_TEN_MHZ =3D 23, conn_GATED_TEN_MHZ =3D 24, conn_SW_LOW =3D 25, /* To force an input low */ conn_SW_HIGH =3D 26, /* To force an input high */ conn_SW_INTR =3D 27, /* For selecting interrupts from */ tt_ptr_reg =3D 12, /* in dpram status page */ err_reg =3D 13, /* in dpram status page */ tt_edge_neg =3D 0x08, tt_edge_pos =3D 0x10, ten_int =3D 2, ten_int_out =3D 3, ten_ext =3D 4, err_success =3D 0, err_no_io_fd =3D 1, err_timeout =3D 2, err_cmd_sz =3D 3, err_invalid_8254_ctr =3D 4, err_connect_dst =3D 5, err_connect_src =3D 6, err_io_open =3D 7, err_ten_mhz =3D 8, err_irq_src =3D 9 }; /* One dev per board */ static struct isa_device devices[NGT401]; /* * Setup the per-device structure defining routines used at 'boot' time. */ static int gt401attach(struct isa_device* devices); static int gt401probe(struct isa_device* devices); void gt401intr(int unit); static int get_lus (int base_io_port, long long *lus); static int mux_matrix_connect (int unit, u_short src, u_short dst); static int pulse_out (int unit, int enable, int src); static int removeIntr(int irq); static int send_cmd (int unit, u_char *cmd_buf, u_int size); static int set_8254 (int unit, u_short counter, u_short mode, u_short initial_count); static int set_irq (int unit, int enable, int src, int edge); static int setupIntr(struct isa_device* device, int irq, inthand2_t* hand, int unit, u_int* maskp); static int start_tt (int unit); static int stop_tt (int unit); static int get_tt_count (int unit); static int get_tt (int unit, long long *tt); static int get_status(int unit); struct isa_driver gt401driver =3D { gt401probe, gt401attach, "gt401" }; static d_open_t gt401open; static d_close_t gt401close; static d_read_t gt401read; static d_ioctl_t gt401ioctl; static d_select_t gt401select; static struct cdevsw gt401_cdevsw =3D { gt401open, gt401close, gt401read, nowrite, gt401ioctl, nostop, nullreset, nodevtotty, gt401select, nommap, NULL, "gt401", NULL, -1 }; struct gt401Unit { short inuse; short tagging_active; char * sleep_address; u_char cont_reg1; u_char cont_reg2; u_char mux_control[8]; int counts_8254[2]; u_int driver_index; u_int max_rbuf_count; /* rbuf_XXX is a ring buffer for reads */ short rbuf_count; short rbuf_first; short rbuf_last; gt401_read rbuf [MAX_GT401_RBUF]; }; #if 1 /* debug */ static char * save_sleep_address =3D 0; #endif static struct gt401Unit gt401Unit[NGT401]; static int get_lus (int base_io_port, long long *lus) { char us_count[8] =3D {0}; char bb[8] =3D {0}; long long *ll_us =3D (long long *)&(us_count[0]); long long *ll_bb =3D (long long *)&(bb[0]); us_count [0] =3D inb (base_io_port + io_addr_us_count0); outb((base_io_port + io_addr_ram_addr_reg), dp_ram_lus_page); inb(base_io_port); /* need a 1us delay */ inb(base_io_port); us_count [1] =3D inb (base_io_port + io_addr_us_count1); bb[0] =3D inb (base_io_port + io_addr_dp_ram + 0); bb[1] =3D inb (base_io_port + io_addr_dp_ram + 1); bb[2] =3D inb (base_io_port + io_addr_dp_ram + 2); bb[3] =3D inb (base_io_port + io_addr_dp_ram + 3); bb[4] =3D inb (base_io_port + io_addr_dp_ram + 4); bb[5] =3D inb (base_io_port + io_addr_dp_ram + 5); bb[6] =3D inb (base_io_port + io_addr_dp_ram + 6); bb[7] =3D inb (base_io_port + io_addr_dp_ram + 7); *lus =3D *ll_bb + *ll_us; return 0; } static int gt401attach(struct isa_device* devices) { int ii,jj; uprintf ("gt401attach\n"); for (ii=3D0; ii=3D NGT401)) return (ENODEV); if (!(devices[unit].id_alive)) return (ENODEV); if (!gt401Unit[unit].inuse) return (ENODEV); switch (cmd) { case GT401_START_EVENTS: { int * count_x_10000_i; int max_counter =3D 0xffff; double period; double period_x_10000; double target_counts_d; int target_counts_i; #if 0 stop_tt(unit); #endif count_x_10000_i =3D ((int *)data); #if 1 /* debug */ uprintf("gt401ioctl: GT401_START_EVENTS arg=3D%d\n",*count_x_10000_i); #endif if (*count_x_10000_i < MIN_PERIOD_X_10000) { return (EINVAL); } if (*count_x_10000_i > MAX_PERIOD_X_10000) { return (EINVAL); } period_x_10000 =3D (double)(*count_x_10000_i); period =3D period_x_10000 / 10000.; target_counts_d =3D period * 10e6; target_counts_i =3D (int)target_counts_d; if (target_counts_i < max_counter) { gt401Unit[unit].counts_8254[0] =3D target_counts_i; gt401Unit[unit].counts_8254[1] =3D 0; } else { gt401Unit[unit].counts_8254[0] =3D target_counts_i / max_counter; ++gt401Unit[unit].counts_8254[0]; gt401Unit[unit].counts_8254[1] =3D (target_counts_i / gt401Unit[unit].counts_8254[0]); } #if 1 /* debug */ uprintf("gt401ioctl: 8254[0]=3D%d 8254[1]=3D%d\n", gt401Unit[unit].counts_8254[0], gt401Unit[unit].counts_8254[1]); #endif if (gt401Unit[unit].counts_8254[1] <=3D 0) { /* using one 8254 */ mux_matrix_connect (unit, conn_TEN_MHZ, conn_CLK1); mux_matrix_connect (unit, conn_SW_HIGH, conn_GATE1); set_8254 (unit, 1, 3, gt401Unit[unit].counts_8254[0]); set_irq (unit, 1, conn_OUT1, 1); } /* using one 8254 */ else { /* using two 8254's */ mux_matrix_connect (unit, conn_TEN_MHZ, conn_CLK0); mux_matrix_connect (unit, conn_SW_HIGH, conn_GATE0); set_8254 (unit, 0, 3, gt401Unit[unit].counts_8254[0]); mux_matrix_connect (unit, conn_OUT0, conn_CLK1); mux_matrix_connect (unit, conn_SW_HIGH, conn_GATE1); set_8254 (unit, 1, 3, gt401Unit[unit].counts_8254[1]); set_irq (unit, 1, conn_OUT1, 1); } /* using two 8254's */ #if 0 /* debug */ uprintf("gt401ioctl: disable 8254 clock for debug.\n"); mux_matrix_connect (unit, conn_SW_LOW, conn_GATE0); mux_matrix_connect (unit, conn_SW_LOW, conn_GATE1); #endif gt401Unit[unit].tagging_active =3D 1; #if 0 /* not yet */ start_tt(unit); #endif } break; case GT401_STOP_EVENTS: gt401Unit[unit].tagging_active =3D 0; #if 1 /* debug */ uprintf("gt401ioctl: GT401_STOP_EVENTS\n"); #endif #if 0 /* not yet */ stop_tt(unit); #endif set_irq (unit, 0, -1, 1); break; case GT401_GET_HIGH_WATER: { int * iarg =3D ((int *)data); *iarg =3D gt401Unit[unit].max_rbuf_count; } break; case GT401_CLEAR_HIGH_WATER: gt401Unit[unit].max_rbuf_count =3D 0; break; default: return (ENODEV); break; } return 0; } void gt401intr(int unit) { int base_io_port; int io_cont_reg2; long long btime_intr; int rbuf_index; unit =3D 0; /* debug */ base_io_port =3D devices[0].id_iobase; get_lus(base_io_port,&btime_intr); if (gt401Unit[0].tagging_active =3D=3D 0) return; ++gt401Unit[0].driver_index; rbuf_index =3D gt401Unit[0].rbuf_last + 1; if (rbuf_index >=3D MAX_GT401_RBUF) rbuf_index =3D 0; if (gt401Unit[0].rbuf_count >=3D MAX_GT401_RBUF) { gt401Unit[0].rbuf_count =3D MAX_GT401_RBUF - 1; ++gt401Unit[0].rbuf_first; if(gt401Unit[0].rbuf_first >=3D MAX_GT401_RBUF) gt401Unit[0].rbuf_first =3D 0; gt401Unit[0].rbuf [gt401Unit[0].rbuf_first].overflow =3D 1; } gt401Unit[0].rbuf[rbuf_index].d_type =3D D_TYPE_TIMETAG; gt401Unit[0].rbuf[rbuf_index].dd.tt.driver_index =3D gt401Unit[0].drive= r_index; gt401Unit[0].rbuf[rbuf_index].dd.tt.driver_board_usec =3D btime_intr; ++gt401Unit[0].rbuf_count; gt401Unit[0].rbuf_last =3D rbuf_index; if (gt401Unit[0].max_rbuf_count < gt401Unit[0].rbuf_count) gt401Unit[0].max_rbuf_count =3D gt401Unit[0].rbuf_count; io_cont_reg2 =3D base_io_port + io_addr_cont_reg_2; gt401Unit[0].cont_reg2 &=3D ~(cont_reg2_intr_en_bit); outb (io_cont_reg2, gt401Unit[0].cont_reg2); send_cmd (unit, NULL, 0); if (gt401Unit[0].tagging_active !=3D 0) { gt401Unit[0].cont_reg2 |=3D cont_reg2_intr_en_bit; outb (io_cont_reg2, gt401Unit[0].cont_reg2); } #if 1 /* debug */ if (gt401Unit[0].sleep_address !=3D save_sleep_address) { panic("gt401intr: sleep_address %x !=3D %x", gt401Unit[0].sleep_address, save_sleep_address); } #endif wakeup (gt401Unit[0].sleep_address); } static int gt401open (dev_t dev, int flags, int fmt, struct proc* p) { int unit =3D UNIT(dev); int jj; #if 1 /* debug */ uprintf("gt401open unit=3D%d\n",unit); #endif if ((unit < 0) || (unit >=3D NGT401)) return (ENXIO); if (!(devices[unit].id_alive)) return (ENXIO); if (gt401Unit[unit].inuse) return (EBUSY); gt401Unit[unit].inuse =3D 1; gt401Unit[unit].tagging_active =3D 0; gt401Unit[unit].rbuf_count =3D 0; gt401Unit[unit].rbuf_first =3D 0; gt401Unit[unit].rbuf_last =3D MAX_GT401_RBUF - 1; for (jj=3D0; jj time_diffs[ii]) duration_min =3D time_diffs[ii]; } min_max_range_check =3D duration_min / 2; min_max_range =3D duration_max - duration_min; #if 1 /* debug */ uprintf("gt401probe addr 0x%x min %d max %d check %d range %d\n", addr, (int)duration_min, (int)duration_max, (int)min_max_range_check, (int)min_max_range); #endif if (duration_min < 5000) { uprintf("gt401probe time diff too small\n"); return 0; } if (min_max_range > min_max_range_check) { uprintf("gt401probe time diff too variable\n"); return 0; } devices[0].id_unit =3D 0; devices[0].id_iobase =3D addr; devices[0].id_driver =3D >401driver; devices[0].id_irq =3D 0; devices[0].id_intr =3D gt401intr; devices[0].id_drq =3D -1; #if 0 /* debug */ devices[0].id_ri_flags =3D RI_FAST; #endif devices[0].id_alive =3D 1; devices[0].id_enabled =3D 1; ++units; return units; } static int gt401read (dev_t dev, struct uio* uio, int flag) { int left_to_move =3D 0; int status; int unit =3D UNIT(dev); int i_timeout =3D hz / 4; if ((unit < 0) || (unit >=3D NGT401)) return (ENODEV); if (!(devices[0].id_alive)) return (ENODEV); if (!gt401Unit[0].inuse) return (ENODEV); disable_intr(); for (;;) { if (gt401Unit[0].rbuf_count > 0) break; enable_intr(); status =3D tsleep (gt401Unit[0].sleep_address, (PSWP | PCATCH), "gt401", i_timeout); if (!((status =3D=3D 0) || (status =3D=3D EWOULDBLOCK))) { return (status); } disable_intr(); } left_to_move =3D uio->uio_resid / sizeof(struct gt401_read_s); while (left_to_move > 0) { if (gt401Unit[0].rbuf_count <=3D 0) break; status =3D uiomove((caddr_t)&(gt401Unit[0].rbuf[gt401Unit[0].rbuf_f= irst]), sizeof(struct gt401_read_s), uio); if (status) { enable_intr(); return (EFAULT); } --left_to_move; --gt401Unit[0].rbuf_count; ++gt401Unit[0].rbuf_first; if(gt401Unit[0].rbuf_first >=3D MAX_GT401_RBUF) gt401Unit[0].rbuf_first =3D 0; if (gt401Unit[0].rbuf_count <=3D 0) break; } enable_intr(); return 0; } static int gt401select (dev_t dev, int rw, struct proc* p) { return 0; } /* * = */ #ifdef GT401_MODULE #include #include #include #include MOD_DEV(gt401, LM_DT_CHAR, CDEV_MAJOR, >401_cdevsw); int = gt401_load(struct lkm_table* lkmtp, int cmd) { int units; int irq =3D 11; int istat; uprintf("Gt401 driver loading, capable of %d board(s)\n", NGT401); units =3D gt401probe (&devices[0]); if (units <=3D 0) { uprintf("gt401 driver: probe failed\n"); return (1); } gt401attach (&devices[0]); istat =3D setupIntr (&devices[0], irq, gt401intr, 0, NULL); if (istat !=3D irq) { uprintf ("gt401 driver: INT %d register failed\n",irq); return (1); } return (0); } int gt401_unload(struct lkm_table* lkmtp, int cmd) { int unit; uprintf("Gt401 driver unloading...\n"); for (unit=3D0; unitid_ri_flags; if (maskp) INTRMASK(*maskp, mask); if (register_intr(irq, 0, flags, hand, maskp, unit) =3D=3D 0) { device->id_irq =3D mask; INTREN(mask); return (irq); } if (maskp) INTRUNMASK(*maskp, mask); return (-1); } /* * Unregister the appropriate INTerrupt. */ static int removeIntr(int irq) { if (unregister_intr(irq, intr_handler[irq])) { uprintf("\tINT #%d failed to unregister\n", irq); return (EPERM); } else { INTRDIS(1 << irq); uprintf("\tINT #%d unregistered\n", irq); return (0); } } static int send_cmd (int unit, u_char *cmd_buf, u_int size) { int base_io_port; u_short cmd_ready_reg; u_short dual_port_bank_index; u_short dual_port_bank_reg; u_short dual_port_data_reg; int err; int ii; int jj; u_short status_reg; u_char status_val; int ready; int ready_loop_max =3D 5000; err =3D err_success; base_io_port =3D devices[unit].id_iobase; // Wait for command ready bit status_reg =3D base_io_port + io_addr_status_reg; ready =3D 0; for (ii=3D0; ii ready_loop_max) break; status_val =3D inb(status_reg); if ((status_val & status_reg_ready_for_cmd) !=3D 0) { ready =3D 1; break; } } if (ready) break; } if (!ready) { err =3D err_timeout; return err; } if (size =3D=3D 0) { return err; } if (size > cmd_buf_sz) { err =3D err_cmd_sz; return err; } // place command bytes into dual port ram dual_port_bank_reg =3D base_io_port + io_addr_ram_addr_reg; dual_port_bank_index =3D dp_ram_command_first_page; for (ii=3D0; ii=3D size) break; ++dual_port_data_reg; } if (ii >=3D size) break; ++dual_port_bank_index; } // signal command cmd_ready_reg =3D base_io_port + io_addr_cmd_ready; outb(cmd_ready_reg, 0); return err; } static int set_8254 (int unit, u_short counter, u_short mode, u_short initial_count) { u_short addr54; int base_io_port; u_char control_byte; int err; u_char ic_hi; u_char ic_lo; u_short i8254_data_reg; u_short mux_addr_reg; err =3D err_success; base_io_port =3D devices[unit].id_iobase; switch (counter) { case 0: addr54 =3D mux_54_ctr_0; break; case 1: addr54 =3D mux_54_ctr_1; break; case 2: addr54 =3D mux_54_ctr_2; break; default: err =3D err_invalid_8254_ctr; return err; } mux_addr_reg =3D base_io_port + io_addr_mux_addr_reg; i8254_data_reg =3D base_io_port + io_addr_8254_data_reg; control_byte =3D 0; control_byte |=3D ((counter & 3) << 6); control_byte |=3D (3 << 4); control_byte |=3D ((mode & 7) << 1); // BCD bit is 0, meaning counter it 16 bit unsigned binary outb(mux_addr_reg, mux_54_cont); // map in 8254 control register outb(i8254_data_reg, control_byte); outb(mux_addr_reg, addr54); // map in 8254 counter register. ic_lo =3D initial_count & 0xff; ic_hi =3D (initial_count >> 8) & 0xff; outb(i8254_data_reg, ic_lo); outb(i8254_data_reg, ic_hi); return err; } static int start_tt (int unit) { u_char cmd_buf[8] =3D {0}; int istat; cmd_buf[0] =3D cmd_clr_err; send_cmd(unit,cmd_buf,1); istat =3D get_status(unit); printf ("start_tt after clr_err stat=3D%d\n",istat); cmd_buf[0] =3D cmd_tt_size; cmd_buf[1] =3D 12; cmd_buf[2] =3D 0; /* no wrap */ send_cmd(unit, cmd_buf, 3); istat =3D get_status(unit); printf ("start_tt tt_size stat=3D%d\n",istat); cmd_buf[0] =3D cmd_tt; cmd_buf[1] =3D tt_edge_pos; /* chan=3D0 << 6 | edge */ send_cmd(unit, cmd_buf, 2); istat =3D get_status(unit); printf ("start_tt tt stat=3D%d\n",istat); return 0; } static int stop_tt (int unit) { u_char cmd_buf[8] =3D {0}; int istat; cmd_buf[0] =3D cmd_clr_err; send_cmd(unit,cmd_buf,1); istat =3D get_status(unit); printf ("stop_tt stat after cmd_clr_err=3D%d\n",istat); cmd_buf[0] =3D cmd_chan_off; cmd_buf[1] =3D 0xc0; send_cmd(unit, cmd_buf, 2); istat =3D get_status(unit); printf ("stop_tt stat after cmd_chan_off=3D%d\n",istat); #if 0 cmd_buf[0] =3D cmd_clr_tt; cmd_buf[1] =3D 0; /* clear time tag buffer and time tag counter */ send_cmd(unit, cmd_buf, 2); istat =3D get_status(unit); printf ("stop_tt stat after cmd_clr_tt=3D%d\n",istat); #endif return 0; } static int get_tt_count (int unit) { return 0; } static int get_tt (int unit, long long *tt) { int base_io_port; int ram_addr_reg; int next_tt; send_cmd(unit,NULL,0); base_io_port =3D devices[unit].id_iobase; ram_addr_reg =3D base_io_port + io_addr_ram_addr_reg; outb (ram_addr_reg, dp_ram_status_page); { int ii; printf ("status page : "); for (ii=3D0; ii<8; ++ii) { next_tt =3D inb(base_io_port + 8 + ii); printf (" 0x%x"); } printf ("\n"); } { int ii; printf ("tag buf :"); outb (ram_addr_reg, 156); for (ii=3D0; ii<8; ++ii) { next_tt =3D inb(base_io_port + 8 + ii); printf (" 0x%x"); } outb (ram_addr_reg, 157); for (ii=3D0; ii<4; ++ii) { next_tt =3D inb(base_io_port + 8 + ii); printf (" 0x%x"); } printf ("\n"); } return 0; } static int get_status(int unit) { int base_io_port; int ram_addr_reg; int status_reg; int istat; base_io_port =3D devices[unit].id_iobase; ram_addr_reg =3D base_io_port + io_addr_ram_addr_reg; send_cmd(unit,NULL,0); outb (ram_addr_reg, dp_ram_status_page); status_reg =3D base_io_port + err_reg; istat =3D inb(status_reg) & 0xff; return istat; } --==_Exmh_18363059200 Content-Type: text/plain ; name="log_read_counts_980726.c"; charset=us-ascii Content-Description: log_read_counts_980726.c Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="log_read_counts_980726.c" #if 0 cc -o test04 test04.c Experiment with /dev/gt401 not doing time tags Run continuously #endif #include #include #include #include #include "gt401.h" #define DEV_PATH "/dev/gt401" int fd =3D -1; int arg_ioctl =3D 0; int read_count =3D 0; #define MAX_TTAG_BUF (4*1024) main (int argc, char **argv) { int istat; int ii; gt401_read * ttag; gt401_read ttag_buf[MAX_TTAG_BUF], last_ttag; int log_mod; double period_d; double freq_d; int first_flag =3D 1; int read_req =3D (sizeof(gt401_read) * MAX_TTAG_BUF); int read_data_count; int max_read_data_count =3D 0; long long sample_period =3D -1; long long sample_period_hi; long long sample_period_low; int read_dropped =3D 0; int driver_dropped =3D 0; long long index_diff_driver; long long index_diff_read_error; long long calc_usec_diff_driver; long long calc_index_diff_driver; long long index_diff_driver_error; struct rtprio rtp; int rtp_flag =3D 0; #if 1 rtp_flag =3D 1; rtp.type =3D RTP_PRIO_REALTIME; rtp.prio =3D 0; istat =3D rtprio (RTP_SET, 0, &rtp); if (istat !=3D 0) { perror("rtprio"); exit (1); } fprintf (stderr,"rtprio\n"); #else fprintf (stderr, "No rtprio\n"); #endif fd =3D open (DEV_PATH, O_RDONLY, 0); if (fd < 0) { fprintf(stderr,"open of %s failed\n",DEV_PATH); exit (__LINE__); } arg_ioctl =3D 20; period_d =3D ((double)arg_ioctl) / 10000.0; freq_d =3D 1.0 / period_d; log_mod =3D (int)(freq_d * 30.0); sample_period =3D (long long)(period_d * 1e6); sample_period_low =3D sample_period - (sample_period / 8); sample_period_hi =3D sample_period + (sample_period / 8); fprintf (stderr,"periodX10000=3D%d period=3D%f freq=3D%f\n",arg_ioctl,p= eriod_d,freq_d); fprintf (stderr,"sizeof(gt401_read) =3D %d\n",sizeof(gt401_read)); for (ii=3D1; ii #include #include #include #include "gt401.h" #define DEV_PATH "/dev/gt401" int fd =3D -1; int arg_ioctl =3D 0; int read_count =3D 0; #define MAX_TTAG_BUF (4*1024) main (int argc, char **argv) { int istat; int ii; gt401_read * ttag; gt401_read ttag_buf[MAX_TTAG_BUF], last_ttag; int log_mod; double period_d; double freq_d; int first_flag =3D 1; int read_req =3D (sizeof(gt401_read) * MAX_TTAG_BUF); int read_data_count; int max_read_data_count =3D 0; long long sample_period =3D -1; long long sample_period_hi; long long sample_period_low; int read_dropped =3D 0; int driver_dropped =3D 0; long long index_diff_driver; long long index_diff_read_error; long long calc_usec_diff_driver; long long calc_index_diff_driver; long long index_diff_driver_error; struct rtprio rtp; int rtp_flag =3D 0; #if 1 rtp_flag =3D 1; rtp.type =3D RTP_PRIO_REALTIME; rtp.prio =3D 0; istat =3D rtprio (RTP_SET, 0, &rtp); if (istat !=3D 0) { perror("rtprio"); exit (1); } fprintf (stderr,"rtprio\n"); #else fprintf (stderr, "No rtprio\n"); #endif fd =3D open (DEV_PATH, O_RDONLY, 0); if (fd < 0) { fprintf(stderr,"open of %s failed\n",DEV_PATH); exit (__LINE__); } arg_ioctl =3D 20; period_d =3D ((double)arg_ioctl) / 10000.0; freq_d =3D 1.0 / period_d; log_mod =3D (int)(freq_d * 30.0); sample_period =3D (long long)(period_d * 1e6); sample_period_low =3D sample_period - (sample_period / 8); sample_period_hi =3D sample_period + (sample_period / 8); fprintf (stderr,"periodX10000=3D%d period=3D%f freq=3D%f\n",arg_ioctl,p= eriod_d,freq_d); fprintf (stderr,"sizeof(gt401_read) =3D %d\n",sizeof(gt401_read)); for (ii=3D1; ii Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06997 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 14:52:31 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06986 for ; Fri, 31 Jul 1998 14:52:25 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA05453; Fri, 31 Jul 1998 14:51:53 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd005435; Fri Jul 31 14:51:50 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA01770; Fri, 31 Jul 1998 14:51:45 -0700 (MST) From: Terry Lambert Message-Id: <199807312151.OAA01770@usr09.primenet.com> Subject: Re: This changes everything To: jlemon@americantv.com (Jonathan Lemon) Date: Fri, 31 Jul 1998 21:51:45 +0000 (GMT) Cc: Matthew.Alton@anheuser-busch.com, Hackers@FreeBSD.ORG, chrisa@commlet.com In-Reply-To: <19980731144241.44313@right.PCS> from "Jonathan Lemon" at Jul 31, 98 02:42:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Go and read . This one should at > least bring some hilarity to the proceedings. I really wonder if > they also have Professor "time and space are equivalent" Abian working > there as well. :-) What if Archimedes Plutonium and Jesus Monroy, Jr. had a Piper Cub? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 15:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09030 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 15:09:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA09023; Fri, 31 Jul 1998 15:09:09 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40690(2)>; Fri, 31 Jul 1998 15:09:02 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 31 Jul 1998 15:08:45 -0700 From: Bill Fenner To: ac199@hwcn.org, jmb@FreeBSD.ORG Subject: Re: biggest mail server Cc: hackers@FreeBSD.ORG, jkh@time.cdrom.com, n@nectar.com, rabtter@aye.net, smoergrd@oslo.geco-prakla.slb.com Message-Id: <98Jul31.150845pdt.177515@crevenia.parc.xerox.com> Date: Fri, 31 Jul 1998 15:08:36 PDT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's zmailer, which was big for a while in certain circles but never quite seemed to catch on. I was under the impression that it hasn't been maintained in a number of years; our zmailer installation's help message starts out 241-Copyright 1990 Rayan S. Zachariassen and I think that was Zachariassen's last release. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 15:56:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18011 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 15:56:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18006 for ; Fri, 31 Jul 1998 15:56:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01058; Fri, 31 Jul 1998 15:54:44 -0700 (PDT) Message-Id: <199807312254.PAA01058@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Craig Spannring cc: chanders@timing.com (Craig Anderson), freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) In-reply-to: Your message of "Fri, 31 Jul 1998 13:59:56 PDT." <199807312059.NAA18156@bangkok.office.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 15:54:44 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That pretty much matches what I'm seeing for a server I'm writing. > My server must respond in less than 3 seconds. Normally it is able > to respond in a millisecond or two, but occasionally it takes around > 1000 milliseconds. > > I've duplicated the problem occurring even under real time priority > with no other processes on the machine except for init, pagedaemon, > vmdaemon, update, and one csh. I had virtual memory disabled to > eliminate any paging activity. If you're doing this over the net, it looks like you're seeing the TCP slow-start. Try turning it off; it makes a huge difference. 8) > I tracked the problem down to the fact that I'm not getting any CPU > time for a substantial (at least up to 500 milliseconds) amount of > time even though I'm using rtprio and there is nothing else that > should be running. So what is running? > In regards to your question of why 0.100 seconds is so common, FreeBSD > uses a 10msec quantum. I suspect if you change kern.quantum to some > other value then the other value will become more common. 0.1s != 10msec. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 16:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21648 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 16:15:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA21642 for ; Fri, 31 Jul 1998 16:15:51 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40680(1)>; Fri, 31 Jul 1998 16:15:42 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177515>; Fri, 31 Jul 1998 16:15:29 -0700 To: Jonathan Lemon cc: "'Hackers@FreeBSD.ORG'" Subject: Re: This changes everything In-reply-to: Your message of "Fri, 31 Jul 98 12:42:41 PDT." <19980731144241.44313@right.PCS> Date: Fri, 31 Jul 1998 16:15:26 PDT From: Bill Fenner Message-Id: <98Jul31.161529pdt.177515@crevenia.parc.xerox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to mention the not-very-well-photoshop'd Pentium II posing as the shot of the product. Didn't quite get the shading right under and to the left of the "A"... and the hologram over to the right looks like it was just effected to death... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 16:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23622 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 16:25:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23608 for ; Fri, 31 Jul 1998 16:25:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01183; Fri, 31 Jul 1998 16:22:51 -0700 (PDT) Message-Id: <199807312322.QAA01183@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: chanders@timing.com (Craig Anderson) cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) In-reply-to: Your message of "Fri, 31 Jul 1998 15:31:37 MDT." <199807312131.PAA04940@count.timing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 16:22:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like you might have some race conditions here; see commentary. Also check the sleep priority; it looks like you might be seeing a number of situations where you're coming up only when the timeout expires. > > #if !defined(gt401_h) > # define gt401_h > > #include > > /* units of pt4 are 0.4 x 10^-6 sec */ > > #define D_TYPE_NONE 99 > #define D_TYPE_ERROR 1 > #define D_TYPE_TIMETAG 2 > > #define MIN_PERIOD_X_10000 1 > #define MAX_PERIOD_X_10000 50000 > > typedef struct gt401_read_s > { > short overflow; > short d_type; > union > { > struct > { > unsigned int board_index; > long long board_time_tag_usec; > unsigned int driver_index; > long long driver_board_usec; > } tt; > struct > { > short err_code; > char err_str[58]; > } ee; > } dd; > } > gt401_read; > > #define GT401_START_EVENTS \ > _IOW('G', 1, int) > #define GT401_STOP_EVENTS \ > _IO('G', 2) > #define GT401_GET_HIGH_WATER \ > _IOR('G', 3, int) > #define GT401_CLEAR_HIGH_WATER \ > _IO('G', 4) > > #endif /* #if !defined(gt401_h) */ > > --==_Exmh_18363059200 > Content-Type: text/plain ; name="Makefile"; charset=us-ascii > Content-Description: Makefile > Content-Transfer-Encoding: quoted-printable > Content-Disposition: attachment; filename="Makefile" > > # $Id: Makefile,v 1.12 1998/07/30 17:19:23 chanders Exp $ > > =2EPATH: . > KMOD =3D gt401_mod > SRCS =3D gt401.c gt401.h ngt401.h > #MAN4 =3D gt401.4 > #MAN8 =3D gt401in.8 > LN =3D ln -f -s > > CFLAGS +=3D \ > -I. \ > -I/usr/src/sys \ > -DGT401_MODULE > > CLEANFILES +=3D ngt401.h > > ngt401.h: > echo "#define NGT401 1" > ngt401.h > > r0: gt401_mod.o > cp gt401_mod.o \ > /usr/local/tsc/rel/bin > > > test03: test03.c > cc -o test03 test03.c > > test04: test04.c > cc -o test04 test04.c > > test05: test05.c > cc -o test05 test05.c > > test06: test06.c > cc -g -o test06 test06.c > > test07: test07.c > cc -g -o test07 test07.c > > test08: test08.c > cc -g -o test08 test08.c > > log_read_counts_980726: log_read_counts_980726.c > cc -g -o log_read_counts_980726 log_read_counts_980726.c > > counts_to_histogram: counts_to_histogram.c > cc -g -o counts_to_histogram counts_to_histogram.c > > kmem_gt401: kmem_gt401.c > cc -g -o kmem_gt401 kmem_gt401.c > > =2Einclude > > > --==_Exmh_18363059200 > Content-Type: text/plain ; name="gt401.c"; charset=us-ascii > Content-Description: gt401.c > Content-Transfer-Encoding: quoted-printable > Content-Disposition: attachment; filename="gt401.c" > > > #include > #include > #include > #include > #include > #include > #include > > #include > #include > > #include > #include > #include > #include > > #include "ngt401.h" > #include "gt401.h" > > #define UNIT(d) (minor(d) >> 16) > > #define CDEV_MAJOR 90 > #define MAX_GT401_RBUF (4*1024) > > enum > { > io_addr_status_reg =3D 0, > io_addr_ram_addr_reg =3D 0, > io_addr_cont_reg_1 =3D 1, > io_addr_cont_reg_2 =3D 2, > io_addr_mux_addr_reg =3D 3, > io_addr_mux_data_reg =3D 4, > io_addr_8254_data_reg =3D 5, > io_addr_us_count0 =3D 6, > io_addr_us_count1 =3D 7, > io_addr_cmd_ready =3D 7, > io_addr_dp_ram =3D 8, > io_addr_err_reg =3D 13, > > dp_ram_lus_page =3D 0, > dp_ram_command_first_page =3D 144, > dp_ram_status_page =3D 146, > > mux_54_ctr_0 =3D 0, > mux_54_ctr_1 =3D 8, > mux_54_ctr_2 =3D 16, > mux_54_cont =3D 24, > > cmd_poll_inner_loop =3D 512, > cmd_poll_sleep_loop =3D 20, > cmd_poll_usleep =3D 10000, > cmd_buf_sz =3D 20, > > cmd_init =3D 1, > cmd_self_test =3D 2, > cmd_nop =3D 3, > cmd_ext_osc =3D 7, > cmd_pulse =3D 8, > cmd_tt =3D 9, > cmd_chan_off =3D 12, > cmd_tt_size =3D 13, > cmd_clr_tt =3D 15, > cmd_clr_err =3D 20, > > cont_reg1_src_mask =3D 7, > cont_reg1_pulse_en =3D 0x08, > cont_reg1_sw_pulse =3D 0x10, > > status_reg_ready_for_cmd =3D 1, > > cont_reg2_irq_src_mask =3D 7, > cont_reg2_irq_src_chan0 =3D 0, > cont_reg2_irq_src_chan1 =3D 1, > cont_reg2_irq_src_chan2 =3D 2, > cont_reg2_irq_src_chan3 =3D 3, > cont_reg2_irq_src_board_proc =3D 4, > cont_reg2_irq_src_out0 =3D 5, > cont_reg2_irq_src_out1 =3D 6, > cont_reg2_irq_src_out2 =3D 7, > cont_reg2_intr_en_bit =3D 0x08, > cont_reg2_intr_edge_bit =3D 0x10, > > conn_CLK0 =3D 0, /* All CLKn values must be consecutive */ > conn_CLK1 =3D 1, > conn_CLK2 =3D 2, > conn_EXT_CLK0 =3D 3, /* All EXT_CLKn values must be consecutive */ > conn_EXT_CLK1 =3D 4, > conn_EXT_CLK2 =3D 5, > conn_GATE0 =3D 6, /* All GATEn values must be consecutive */ > conn_GATE1 =3D 7, > conn_GATE2 =3D 8, > conn_EXT_GATE0 =3D 9, /* All EXT_GATEn values must be consecutive */ > conn_EXT_GATE1 =3D 10, > conn_EXT_GATE2 =3D 11, > conn_OUT0 =3D 12, /* All OUTn values must be consecutive */ > conn_OUT1 =3D 13, > conn_OUT2 =3D 14, > conn_IO_CHAN0 =3D 15, /* All IO_CHANn values must be consecutive */ > conn_IO_CHAN1 =3D 16, > conn_IO_CHAN2 =3D 17, > conn_IO_CHAN3 =3D 18, > conn_EXT_CHAN0 =3D 19, /* all EXT_CHANNn values must be consecutive */= > > conn_EXT_CHAN1 =3D 20, > conn_EXT_CHAN2 =3D 21, > conn_EXT_CHAN3 =3D 22, > conn_TEN_MHZ =3D 23, > conn_GATED_TEN_MHZ =3D 24, > conn_SW_LOW =3D 25, /* To force an input low */ > conn_SW_HIGH =3D 26, /* To force an input high */ > conn_SW_INTR =3D 27, /* For selecting interrupts from */ > > tt_ptr_reg =3D 12, /* in dpram status page */ > err_reg =3D 13, /* in dpram status page */ > > tt_edge_neg =3D 0x08, > tt_edge_pos =3D 0x10, > > ten_int =3D 2, > ten_int_out =3D 3, > ten_ext =3D 4, > > err_success =3D 0, > err_no_io_fd =3D 1, > err_timeout =3D 2, > err_cmd_sz =3D 3, > err_invalid_8254_ctr =3D 4, > err_connect_dst =3D 5, > err_connect_src =3D 6, > err_io_open =3D 7, > err_ten_mhz =3D 8, > err_irq_src =3D 9 > }; > > /* One dev per board */ > static struct isa_device devices[NGT401]; > > /* > * Setup the per-device structure defining routines used at 'boot' time. > */ > static int gt401attach(struct isa_device* devices); > static int gt401probe(struct isa_device* devices); > > void gt401intr(int unit); > > static int get_lus (int base_io_port, long long *lus); > static int mux_matrix_connect (int unit, > u_short src, > u_short dst); > static int pulse_out (int unit, > int enable, > int src); > static int removeIntr(int irq); > static int send_cmd (int unit, u_char *cmd_buf, u_int size); > static int set_8254 (int unit, > u_short counter, > u_short mode, > u_short initial_count); > static int set_irq (int unit, > int enable, > int src, > int edge); > static int setupIntr(struct isa_device* device, > int irq, > inthand2_t* hand, > int unit, > u_int* maskp); > > static int start_tt (int unit); > static int stop_tt (int unit); > static int get_tt_count (int unit); > static int get_tt (int unit, long long *tt); > static int get_status(int unit); > > struct isa_driver gt401driver =3D > { > gt401probe, > gt401attach, > "gt401" > }; > > static d_open_t gt401open; > static d_close_t gt401close; > static d_read_t gt401read; > static d_ioctl_t gt401ioctl; > static d_select_t gt401select; > > static struct cdevsw gt401_cdevsw =3D > { > gt401open, > gt401close, > gt401read, > nowrite, > gt401ioctl, > nostop, > nullreset, > nodevtotty, > gt401select, > nommap, > NULL, > "gt401", > NULL, > -1 > }; > > struct gt401Unit > { > short inuse; > short tagging_active; > > char * sleep_address; > > u_char cont_reg1; > u_char cont_reg2; > u_char mux_control[8]; > int counts_8254[2]; > > u_int driver_index; > u_int max_rbuf_count; > > /* rbuf_XXX is a ring buffer for reads */ > short rbuf_count; > short rbuf_first; > short rbuf_last; > gt401_read rbuf [MAX_GT401_RBUF]; > }; > > #if 1 /* debug */ > static char * save_sleep_address =3D 0; > #endif > static struct gt401Unit gt401Unit[NGT401]; > > static int > get_lus (int base_io_port, long long *lus) > { > char us_count[8] =3D {0}; > char bb[8] =3D {0}; > long long *ll_us =3D (long long *)&(us_count[0]); > long long *ll_bb =3D (long long *)&(bb[0]); > > us_count [0] =3D inb (base_io_port + io_addr_us_count0); > > outb((base_io_port + io_addr_ram_addr_reg), dp_ram_lus_page); > > inb(base_io_port); /* need a 1us delay */ > inb(base_io_port); > > us_count [1] =3D inb (base_io_port + io_addr_us_count1); > > bb[0] =3D inb (base_io_port + io_addr_dp_ram + 0); > bb[1] =3D inb (base_io_port + io_addr_dp_ram + 1); > bb[2] =3D inb (base_io_port + io_addr_dp_ram + 2); > bb[3] =3D inb (base_io_port + io_addr_dp_ram + 3); > bb[4] =3D inb (base_io_port + io_addr_dp_ram + 4); > bb[5] =3D inb (base_io_port + io_addr_dp_ram + 5); > bb[6] =3D inb (base_io_port + io_addr_dp_ram + 6); > bb[7] =3D inb (base_io_port + io_addr_dp_ram + 7); > > *lus =3D *ll_bb + *ll_us; > > return 0; > } > > static int > gt401attach(struct isa_device* devices) > { > int ii,jj; > > uprintf ("gt401attach\n"); > > for (ii=3D0; ii { > gt401Unit[ii].inuse =3D 0; > gt401Unit[ii].tagging_active =3D 0; > gt401Unit[ii].sleep_address =3D (char *)&(gt401Unit[ii].inuse); > gt401Unit[ii].cont_reg1 =3D 0; > gt401Unit[ii].cont_reg2 =3D 0; > for (jj=3D0; jj<8; ++jj) > gt401Unit[ii].mux_control[jj] =3D 0; > gt401Unit[ii].counts_8254[0] =3D 0; > gt401Unit[ii].counts_8254[1] =3D 0; > gt401Unit[ii].driver_index =3D 0; > gt401Unit[ii].max_rbuf_count =3D 0; > gt401Unit[ii].rbuf_count =3D 0; > gt401Unit[ii].rbuf_first =3D 0; > gt401Unit[ii].rbuf_last =3D MAX_GT401_RBUF - 1; > for (jj=3D0; jj { > gt401Unit[ii].rbuf[jj].d_type =3D D_TYPE_NONE; > gt401Unit[ii].rbuf[jj].overflow =3D 0; > } > } > #if 1 /* debug */ > save_sleep_address =3D gt401Unit[0].sleep_address; > #endif > return 1; > } > > static int > gt401close (dev_t dev, > int flags, > int fmt, > struct proc* p) > { > int unit =3D UNIT(dev); > > #if 1 /* debug */ > uprintf ("gt401close unit=3D%d\n",unit); > #endif > > gt401Unit[unit].tagging_active =3D 0; > gt401Unit[unit].inuse =3D 0; > set_irq (unit, > 0, > -1, > 1); > > return 0; > } > static int > gt401ioctl (dev_t dev, > int cmd, > caddr_t data, > int flag, > struct proc* p) > { > int unit =3D UNIT(dev); > > if ((unit < 0) || (unit >=3D NGT401)) > return (ENODEV); > > if (!(devices[unit].id_alive)) > return (ENODEV); > > if (!gt401Unit[unit].inuse) > return (ENODEV); > > switch (cmd) > { > case GT401_START_EVENTS: > { > int * count_x_10000_i; > int max_counter =3D 0xffff; > double period; > double period_x_10000; > double target_counts_d; > int target_counts_i; > > #if 0 > stop_tt(unit); > #endif > > count_x_10000_i =3D ((int *)data); > > #if 1 /* debug */ > uprintf("gt401ioctl: GT401_START_EVENTS arg=3D%d\n",*count_x_10000_i); > #endif > > if (*count_x_10000_i < MIN_PERIOD_X_10000) > { > return (EINVAL); > } > if (*count_x_10000_i > MAX_PERIOD_X_10000) > { > return (EINVAL); > } > period_x_10000 =3D (double)(*count_x_10000_i); > period =3D period_x_10000 / 10000.; > target_counts_d =3D period * 10e6; > target_counts_i =3D (int)target_counts_d; > > if (target_counts_i < max_counter) > { > gt401Unit[unit].counts_8254[0] =3D target_counts_i; > gt401Unit[unit].counts_8254[1] =3D 0; > } > else > { > gt401Unit[unit].counts_8254[0] =3D target_counts_i / max_counter; > ++gt401Unit[unit].counts_8254[0]; > gt401Unit[unit].counts_8254[1] =3D (target_counts_i > / gt401Unit[unit].counts_8254[0]); > } > #if 1 /* debug */ > uprintf("gt401ioctl: 8254[0]=3D%d 8254[1]=3D%d\n", > gt401Unit[unit].counts_8254[0], > gt401Unit[unit].counts_8254[1]); > #endif > if (gt401Unit[unit].counts_8254[1] <=3D 0) > { /* using one 8254 */ > mux_matrix_connect (unit, > conn_TEN_MHZ, > conn_CLK1); > mux_matrix_connect (unit, > conn_SW_HIGH, > conn_GATE1); > set_8254 (unit, > 1, > 3, > gt401Unit[unit].counts_8254[0]); > set_irq (unit, > 1, > conn_OUT1, > 1); > } /* using one 8254 */ > else > { /* using two 8254's */ > mux_matrix_connect (unit, > conn_TEN_MHZ, > conn_CLK0); > mux_matrix_connect (unit, > conn_SW_HIGH, > conn_GATE0); > set_8254 (unit, > 0, > 3, > gt401Unit[unit].counts_8254[0]); > mux_matrix_connect (unit, > conn_OUT0, > conn_CLK1); > mux_matrix_connect (unit, > conn_SW_HIGH, > conn_GATE1); > set_8254 (unit, > 1, > 3, > gt401Unit[unit].counts_8254[1]); > set_irq (unit, > 1, > conn_OUT1, > 1); > } /* using two 8254's */ > > #if 0 /* debug */ > uprintf("gt401ioctl: disable 8254 clock for debug.\n"); > mux_matrix_connect (unit, > conn_SW_LOW, > conn_GATE0); > mux_matrix_connect (unit, > conn_SW_LOW, > conn_GATE1); > #endif > gt401Unit[unit].tagging_active =3D 1; > > #if 0 /* not yet */ > start_tt(unit); > #endif > > } > break; > case GT401_STOP_EVENTS: > gt401Unit[unit].tagging_active =3D 0; > #if 1 /* debug */ > uprintf("gt401ioctl: GT401_STOP_EVENTS\n"); > #endif > #if 0 /* not yet */ > stop_tt(unit); > #endif > set_irq (unit, > 0, > -1, > 1); > break; > case GT401_GET_HIGH_WATER: > { > int * iarg =3D ((int *)data); > *iarg =3D gt401Unit[unit].max_rbuf_count; > } > break; > case GT401_CLEAR_HIGH_WATER: > gt401Unit[unit].max_rbuf_count =3D 0; > break; > default: > return (ENODEV); > break; > } > return 0; > } > > void > gt401intr(int unit) > { > int base_io_port; > int io_cont_reg2; > long long btime_intr; > int rbuf_index; > > unit =3D 0; /* debug */ > base_io_port =3D devices[0].id_iobase; > get_lus(base_io_port,&btime_intr); > > if (gt401Unit[0].tagging_active =3D=3D 0) > return; > > ++gt401Unit[0].driver_index; > > rbuf_index =3D gt401Unit[0].rbuf_last + 1; > if (rbuf_index >=3D MAX_GT401_RBUF) > rbuf_index =3D 0; rbuf_index = (gt401Unit[0].rbuf_last + 1) % MAX_GT401_RBUF; > if (gt401Unit[0].rbuf_count >=3D MAX_GT401_RBUF) > { > gt401Unit[0].rbuf_count =3D MAX_GT401_RBUF - 1; > ++gt401Unit[0].rbuf_first; > if(gt401Unit[0].rbuf_first >=3D MAX_GT401_RBUF) > gt401Unit[0].rbuf_first =3D 0; > gt401Unit[0].rbuf [gt401Unit[0].rbuf_first].overflow =3D 1; > } > gt401Unit[0].rbuf[rbuf_index].d_type =3D D_TYPE_TIMETAG; > gt401Unit[0].rbuf[rbuf_index].dd.tt.driver_index =3D gt401Unit[0].drive= > r_index; > gt401Unit[0].rbuf[rbuf_index].dd.tt.driver_board_usec =3D btime_intr; > ++gt401Unit[0].rbuf_count; > gt401Unit[0].rbuf_last =3D rbuf_index; > if (gt401Unit[0].max_rbuf_count < gt401Unit[0].rbuf_count) > gt401Unit[0].max_rbuf_count =3D gt401Unit[0].rbuf_count; > > io_cont_reg2 =3D base_io_port + io_addr_cont_reg_2; > > gt401Unit[0].cont_reg2 &=3D ~(cont_reg2_intr_en_bit); > outb (io_cont_reg2, > gt401Unit[0].cont_reg2); > > send_cmd (unit, NULL, 0); > > if (gt401Unit[0].tagging_active !=3D 0) > { > gt401Unit[0].cont_reg2 |=3D cont_reg2_intr_en_bit; > outb (io_cont_reg2, > gt401Unit[0].cont_reg2); > } > #if 1 /* debug */ > if (gt401Unit[0].sleep_address !=3D save_sleep_address) > { > panic("gt401intr: sleep_address %x !=3D %x", > gt401Unit[0].sleep_address, > save_sleep_address); > } > #endif > wakeup (gt401Unit[0].sleep_address); > } > > static int > gt401open (dev_t dev, > int flags, > int fmt, > struct proc* p) > { > int unit =3D UNIT(dev); > int jj; > > #if 1 /* debug */ > uprintf("gt401open unit=3D%d\n",unit); > #endif > > if ((unit < 0) || (unit >=3D NGT401)) > return (ENXIO); > > if (!(devices[unit].id_alive)) > return (ENXIO); > > if (gt401Unit[unit].inuse) > return (EBUSY); > > gt401Unit[unit].inuse =3D 1; > gt401Unit[unit].tagging_active =3D 0; > gt401Unit[unit].rbuf_count =3D 0; > gt401Unit[unit].rbuf_first =3D 0; > gt401Unit[unit].rbuf_last =3D MAX_GT401_RBUF - 1; > for (jj=3D0; jj { > gt401Unit[unit].rbuf[jj].d_type =3D D_TYPE_NONE; > gt401Unit[unit].rbuf[jj].overflow =3D 0; > } > > #if 1 /* debug */ > { > int addr =3D devices[unit].id_iobase; > uprintf("gt401open unit=3D%d io_addr=3D0x%x\n",unit,addr); > } > #endif > > return 0; > } > > static int > gt401probe(struct isa_device* devices) > { > int addr =3D 0x100; > int ii; > long long time_check[9]; > long long time_diffs[8]; > int units =3D 0; > long long duration_max; > long long duration_min; > long long min_max_range; > long long min_max_range_check; > > for (ii=3D0; ii { > devices[ii].id_alive =3D 0; > devices[ii].id_enabled =3D 0; > } > > /* check for gt401 at addr by reading it's time */ > for (ii=3D0; ii<9; ++ii) > { > get_lus (addr,&(time_check[ii])); > tsleep (&ii, PZERO, "gt401", 10); > } > > for (ii=3D1; ii<9; ++ii) > { > time_diffs[ii-1] =3D time_check[ii] - time_check[ii-1]; > } > duration_max =3D duration_min =3D time_diffs[0]; > for (ii=3D0; ii<8; ++ii) > { > if (duration_max < time_diffs[ii]) > duration_max =3D time_diffs[ii]; > if (duration_min > time_diffs[ii]) > duration_min =3D time_diffs[ii]; > } > min_max_range_check =3D duration_min / 2; > min_max_range =3D duration_max - duration_min; > > #if 1 /* debug */ > uprintf("gt401probe addr 0x%x min %d max %d check %d range %d\n", > addr, > (int)duration_min, > (int)duration_max, > (int)min_max_range_check, > (int)min_max_range); > #endif > > if (duration_min < 5000) > { > uprintf("gt401probe time diff too small\n"); > return 0; > } > if (min_max_range > min_max_range_check) > { > uprintf("gt401probe time diff too variable\n"); > return 0; > } > > devices[0].id_unit =3D 0; > devices[0].id_iobase =3D addr; > devices[0].id_driver =3D >401driver; > devices[0].id_irq =3D 0; > devices[0].id_intr =3D gt401intr; > devices[0].id_drq =3D -1; > #if 0 /* debug */ > devices[0].id_ri_flags =3D RI_FAST; You do not want to do this with your current architecture; you can never call wakeup() from inside a fast interrupt handler. > #endif > > devices[0].id_alive =3D 1; > devices[0].id_enabled =3D 1; > > ++units; > > return units; > } > > static int > gt401read (dev_t dev, > struct uio* uio, > int flag) > { > int left_to_move =3D 0; > int status; > int unit =3D UNIT(dev); > int i_timeout =3D hz / 4; > > if ((unit < 0) || (unit >=3D NGT401)) > return (ENODEV); > if (!(devices[0].id_alive)) > return (ENODEV); > if (!gt401Unit[0].inuse) > return (ENODEV); > > disable_intr(); This is very bad; don't do this. Add the driver to one of the 'standard' interrupt masks and then use splfoo(), or create your own interrupt mask. > for (;;) > { > if (gt401Unit[0].rbuf_count > 0) > break; > enable_intr(); ... because there is a race window here. > status =3D tsleep (gt401Unit[0].sleep_address, > (PSWP | PCATCH), > "gt401", > i_timeout); > if (!((status =3D=3D 0) > || (status =3D=3D EWOULDBLOCK))) > { > return (status); > } > disable_intr(); > } > > left_to_move =3D uio->uio_resid / sizeof(struct gt401_read_s); > > while (left_to_move > 0) > { > if (gt401Unit[0].rbuf_count <=3D 0) > break; > > status =3D uiomove((caddr_t)&(gt401Unit[0].rbuf[gt401Unit[0].rbuf_f= > irst]), > sizeof(struct gt401_read_s), > uio); > if (status) > { > enable_intr(); > return (EFAULT); > } > > --left_to_move; > > --gt401Unit[0].rbuf_count; > ++gt401Unit[0].rbuf_first; > if(gt401Unit[0].rbuf_first >=3D MAX_GT401_RBUF) > gt401Unit[0].rbuf_first =3D 0; gt401Unit[0].rbuf_first = (gt401Unit[0].rbuf_first + 1) % MAX_GT401_RBUF; > if (gt401Unit[0].rbuf_count <=3D 0) > break; > } > > enable_intr(); > return 0; > } Actually, you can simplify this drastically; there's no need to lock the ringbuffer unless you are particularly concerned about the overflow case. Disabling interrupts for a long time like you do here may cause loss of timer interrupts, as well as the race above. static int gt401read (dev_t dev, struct uio* uio, int flag) { int left_to_move = 0; int status; int unit = UNIT(dev); int i_timeout = hz / 4; int s, ofs; if ((unit < 0) || (unit >= NGT401)) return (ENODEV); if (!(devices[0].id_alive)) return (ENODEV); if (!gt401Unit[0].inuse) return (ENODEV); s = splfoo(); while (gt401Unit[0].rbuf_count == 0) { status = tsleep(gt401Unit[0].sleep_address, PRIBIO | PCATCH, "gt401", i_timeout); if (!((status == 0) || (status == EWOULDBLOCK))) { splx(s); return(status); } } splx(s); left_to_move = min(gt401Unit[0].rbuf_count, (uio->uio_resid / sizeof(struct gt401_read_s)); ofs = gt401Unit[0].rbuf_first; for (; left_to_move > 0; left_to_move --) { if (uiomove((caddr_t)>401Unit[0].rbuf[ofs], sizeof(struct gt401_read_s, uio) return(EFAULT); ofs = (ofs + 1) % GT401_MAX_RBUF; gt401Unit[0].rbuf_count--; } gt401Unit[0].rbuf_first = ofs; return(0); } > static int > gt401select (dev_t dev, > int rw, > struct proc* p) > { > return 0; > } > > /* > * = > > */ > #ifdef GT401_MODULE > > #include > #include > #include > #include > > MOD_DEV(gt401, LM_DT_CHAR, CDEV_MAJOR, >401_cdevsw); > > int = > > gt401_load(struct lkm_table* lkmtp, int cmd) > { > int units; > int irq =3D 11; > int istat; > > uprintf("Gt401 driver loading, capable of %d board(s)\n", NGT401); > > units =3D gt401probe (&devices[0]); > if (units <=3D 0) > { > uprintf("gt401 driver: probe failed\n"); > return (1); > } > > gt401attach (&devices[0]); > > istat =3D setupIntr (&devices[0], > irq, > gt401intr, > 0, > NULL); > if (istat !=3D irq) > { > uprintf ("gt401 driver: INT %d register failed\n",irq); > return (1); > } > > return (0); > } > > int > gt401_unload(struct lkm_table* lkmtp, int cmd) > { > int unit; > > uprintf("Gt401 driver unloading...\n"); > > for (unit=3D0; unit { > if (devices[unit].id_alive =3D=3D 1) > { > /** disable interrupts on board */ > > if (devices[unit].id_irq !=3D 0) > { > uprintf ("removeINTR 0x%x\n",(ffs(devices[unit].id_irq) - 1)); > removeIntr(ffs(devices[unit].id_irq) - 1); > } > } > } > > return (0); > } > > /** XXX: /usr/include/lkm.h fails to define this: */ > int gt401_stat(struct lkm_table* lkmtp, int cmd); > int > gt401_stat(struct lkm_table* lkmtp, int cmd) > { > return (0); > } > > int > gt401_mod(struct lkm_table* lkmtp, int cmd, int ver) > { > DISPATCH(lkmtp, cmd, ver, gt401_load, gt401_unload, gt401_stat); > } > > #endif /* GT401_MODULE */ > > static int > mux_matrix_connect (int unit, > u_short src, > u_short dst) > { > int base_io_port; > int err; > u_short mux_addr_reg; > u_char mux_addr_reg_val; > u_short mux_data_reg; > u_char src_val; > > base_io_port =3D devices[unit].id_iobase; > > err =3D 0; > > mux_addr_reg =3D base_io_port + io_addr_mux_addr_reg; > mux_data_reg =3D base_io_port + io_addr_mux_data_reg; > > // verify that dst is valid > switch (dst) > { > case conn_IO_CHAN0: > case conn_IO_CHAN1: > case conn_IO_CHAN2: > case conn_IO_CHAN3: > case conn_EXT_CHAN0: > case conn_EXT_CHAN1: > case conn_EXT_CHAN2: > case conn_EXT_CHAN3: > case conn_CLK0: > case conn_CLK1: > case conn_CLK2: > case conn_GATE0: > case conn_GATE1: > case conn_GATE2: > break; > default: > err =3D err_connect_dst; > return err; > } > > // verify that src is valid > switch (dst) > { > case conn_IO_CHAN0: > case conn_IO_CHAN1: > case conn_IO_CHAN2: > case conn_IO_CHAN3: > switch (src) > { > case conn_EXT_CHAN0: > src_val =3D 0; > break; > case conn_EXT_CHAN1: > src_val =3D 1; > break; > case conn_EXT_CHAN2: > src_val =3D 2; > break; > case conn_EXT_CHAN3: > src_val =3D 3; > break; > case conn_OUT0: > src_val =3D 4; > break; > case conn_OUT1: > src_val =3D 5; > break; > case conn_OUT2: > src_val =3D 6; > break; > case conn_SW_LOW: > src_val =3D 7; > break; > case conn_SW_HIGH: > src_val =3D 7; > break; > default: > err =3D err_connect_src; > return err; > } > break; > case conn_EXT_CHAN0: > if (src !=3D conn_IO_CHAN0) > { > err =3D err_connect_src; > return err; > } > break; > case conn_EXT_CHAN1: > if (src !=3D conn_IO_CHAN1) > { > err =3D err_connect_src; > return err; > } > break; > case conn_EXT_CHAN2: > if (src !=3D conn_IO_CHAN2) > { > err =3D err_connect_src; > return err; > } > break; > case conn_EXT_CHAN3: > if (src !=3D conn_IO_CHAN3) > { > err =3D err_connect_src; > return err; > } > break; > case conn_CLK0: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT2: > src_val =3D 4; > break; > case conn_TEN_MHZ: > src_val =3D 5; > break; > case conn_GATED_TEN_MHZ: > src_val =3D 6; > break; > case conn_EXT_CLK2: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > case conn_CLK1: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT0: > src_val =3D 4; > break; > case conn_TEN_MHZ: > src_val =3D 5; > break; > case conn_GATED_TEN_MHZ: > src_val =3D 6; > break; > case conn_EXT_CLK2: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > case conn_CLK2: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT1: > src_val =3D 4; > break; > case conn_TEN_MHZ: > src_val =3D 5; > break; > case conn_GATED_TEN_MHZ: > src_val =3D 6; > break; > case conn_EXT_CLK2: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > case conn_GATE0: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT1: > src_val =3D 4; > break; > case conn_OUT2: > src_val =3D 5; > break; > case conn_SW_LOW: > src_val =3D 6; > break; > case conn_SW_HIGH: > src_val =3D 6; > break; > case conn_EXT_GATE0: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > case conn_GATE1: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT0: > src_val =3D 5; > break; > case conn_OUT2: > src_val =3D 4; > break; > case conn_SW_LOW: > src_val =3D 6; > break; > case conn_SW_HIGH: > src_val =3D 6; > break; > case conn_EXT_GATE1: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > case conn_GATE2: > switch (src) > { > case conn_IO_CHAN0: > src_val =3D 0; > break; > case conn_IO_CHAN1: > src_val =3D 1; > break; > case conn_IO_CHAN2: > src_val =3D 2; > break; > case conn_IO_CHAN3: > src_val =3D 3; > break; > case conn_OUT0: > src_val =3D 4; > break; > case conn_OUT1: > src_val =3D 5; > break; > case conn_SW_LOW: > src_val =3D 6; > break; > case conn_SW_HIGH: > src_val =3D 6; > break; > case conn_EXT_GATE2: > src_val =3D 7; > break; > default: > err =3D err_connect_dst; > return err; > } > break; > } > > // handle sw set gate and chan > switch (src) > { > case conn_SW_LOW: > switch (dst) > { > case conn_IO_CHAN0: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~1); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN1: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~2); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN2: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~4); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN3: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~8); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE0: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~1); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE1: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~2); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE2: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~4); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > } > break; > case conn_SW_HIGH: > switch (dst) > { > case conn_IO_CHAN0: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 1; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN1: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 2; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN2: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 4; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN3: > mux_addr_reg_val =3D 6; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 8; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE0: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 1; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE1: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 2; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE2: > mux_addr_reg_val =3D 3; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 4; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > } > break; > } > > // make the connection > > switch (dst) > { > case conn_IO_CHAN0: > mux_addr_reg_val =3D 4; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~7; > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D src_val; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~1; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN1: > mux_addr_reg_val =3D 4; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~0x38; > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D (src_val << 3); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~2; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN2: > mux_addr_reg_val =3D 5; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~7; > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D src_val; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~4; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_IO_CHAN3: > mux_addr_reg_val =3D 5; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~0x38; > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D (src_val << 3); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D ~8; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > > case conn_EXT_CHAN0: > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 1; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_EXT_CHAN1: > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 2; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_EXT_CHAN2: > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 4; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_EXT_CHAN3: > mux_addr_reg_val =3D 7; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D 8; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > > case conn_CLK0: > mux_addr_reg_val =3D 0; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~7); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D src_val; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_CLK1: > mux_addr_reg_val =3D 1; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~7); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D src_val; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_CLK2: > mux_addr_reg_val =3D 2; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~7); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D src_val; > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE0: > mux_addr_reg_val =3D 0; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~0x38); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D (src_val << 3); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE1: > mux_addr_reg_val =3D 1; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~0x38); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D (src_val << 3); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > case conn_GATE2: > mux_addr_reg_val =3D 2; > outb (mux_addr_reg, mux_addr_reg_val); > gt401Unit[unit].mux_control[mux_addr_reg_val] &=3D (~0x38); > gt401Unit[unit].mux_control[mux_addr_reg_val] |=3D (src_val << 3); > outb(mux_data_reg, gt401Unit[unit].mux_control[mux_addr_reg_val]); > break; > } > > return err; > } > > static int > pulse_out (int unit, > int enable, > int src) > { > int base_io_port; > u_short cont_reg1; > int err; > u_char src_code; > > base_io_port =3D devices[unit].id_iobase; > err =3D err_success; > > cont_reg1 =3D base_io_port + io_addr_cont_reg_1; > if (enable =3D=3D 0) > { /* disable pulse output */ > gt401Unit[unit].cont_reg1 &=3D (~cont_reg1_pulse_en); > outb (cont_reg1, gt401Unit[unit].cont_reg1); > return err; > } > > // enable pulse output > switch (src) > { > case conn_IO_CHAN0: > src_code =3D 0; > break; > case conn_IO_CHAN1: > src_code =3D 1; > break; > case conn_IO_CHAN2: > src_code =3D 2; > break; > case conn_IO_CHAN3: > src_code =3D 3; > break; > case conn_SW_LOW: > case conn_SW_HIGH: > src_code =3D 4; > break; > case conn_OUT0: > src_code =3D 5; > break; > case conn_OUT1: > src_code =3D 6; > break; > case conn_OUT2: > src_code =3D 7; > break; > default: > err =3D err_connect_src; > return err; > } > > gt401Unit[unit].cont_reg1 &=3D cont_reg1_src_mask; > gt401Unit[unit].cont_reg1 |=3D src_code; > > switch (src) > { > case conn_SW_LOW: > gt401Unit[unit].cont_reg1 &=3D (~cont_reg1_sw_pulse); > break; > case conn_SW_HIGH: > gt401Unit[unit].cont_reg1 |=3D cont_reg1_sw_pulse; > break; > } > > outb (cont_reg1, > gt401Unit[unit].cont_reg1); > > tsleep (&err, PZERO, "gt401", 100); > > gt401Unit[unit].cont_reg1 |=3D cont_reg1_pulse_en; // then enable pulse= > out > > outb (cont_reg1, > gt401Unit[unit].cont_reg1); > > return err; > } > > static int > set_irq (int unit, > int enable, > int src, > int edge) > { > int base_io_port; > int err; > int io_cont_reg2; > int src_code; > > base_io_port =3D devices[unit].id_iobase; > err =3D err_success; > > io_cont_reg2 =3D base_io_port + io_addr_cont_reg_2; > > if (enable =3D=3D 0) > { /* turn off interrupts */ > gt401Unit[unit].cont_reg2 &=3D ~(cont_reg2_intr_en_bit); > #if 0 /* debug */ > printf ("outb (%x,%x)\n", > io_cont_reg2, > gt401Unit[unit].cont_reg2); > #endif > outb (io_cont_reg2, > gt401Unit[unit].cont_reg2); > return err; > } /* turn off interrupts */ > > /* turn on interrupts */ > switch (src) > { > case conn_IO_CHAN0: > src_code =3D cont_reg2_irq_src_chan0; > break; > case conn_IO_CHAN1: > src_code =3D cont_reg2_irq_src_chan1; > break; > case conn_IO_CHAN2: > src_code =3D cont_reg2_irq_src_chan2; > break; > case conn_IO_CHAN3: > src_code =3D cont_reg2_irq_src_chan3; > break; > case conn_OUT0: > src_code =3D cont_reg2_irq_src_out0; > break; > case conn_OUT1: > src_code =3D cont_reg2_irq_src_out1; > break; > case conn_OUT2: > src_code =3D cont_reg2_irq_src_out2; > break; > default: > err =3D err_irq_src; > return err; > } > gt401Unit[unit].cont_reg2 &=3D ~(cont_reg2_irq_src_mask); > gt401Unit[unit].cont_reg2 |=3D src_code; > > if (edge =3D=3D 0) > gt401Unit[unit].cont_reg2 &=3D ~(cont_reg2_intr_edge_bit); > else > gt401Unit[unit].cont_reg2 |=3D cont_reg2_intr_edge_bit; > > gt401Unit[unit].cont_reg2 &=3D ~(cont_reg2_intr_en_bit); > #if 0 /* debug */ > printf ("outb (%x,%x)\n", > io_cont_reg2, > gt401Unit[unit].cont_reg2); > #endif > outb (io_cont_reg2, > gt401Unit[unit].cont_reg2); > > gt401Unit[unit].cont_reg2 |=3D cont_reg2_intr_en_bit; > #if 0 /* debug */ > printf ("outb (%x,%x)\n", > io_cont_reg2, > gt401Unit[unit].cont_reg2); > #endif > outb (io_cont_reg2, > gt401Unit[unit].cont_reg2); > > return err; > } > > /* > * Register the appropriate INTerrupt. > */ > static int > setupIntr(struct isa_device* device, > int irq, inthand2_t* hand, int unit, u_int* maskp) > { > u_int mask; > u_int flags; > > mask =3D 1ul << irq; > flags =3D device->id_ri_flags; > > if (maskp) > INTRMASK(*maskp, mask); > > if (register_intr(irq, 0, flags, hand, maskp, unit) =3D=3D 0) { > device->id_irq =3D mask; > INTREN(mask); > return (irq); > } > > if (maskp) > INTRUNMASK(*maskp, mask); > > return (-1); > } > > > /* > * Unregister the appropriate INTerrupt. > */ > static int > removeIntr(int irq) > { > if (unregister_intr(irq, intr_handler[irq])) { > uprintf("\tINT #%d failed to unregister\n", irq); > return (EPERM); > } > else { > INTRDIS(1 << irq); > uprintf("\tINT #%d unregistered\n", irq); > return (0); > } > } > > static int > send_cmd (int unit, u_char *cmd_buf, u_int size) > { > int base_io_port; > u_short cmd_ready_reg; > u_short dual_port_bank_index; > u_short dual_port_bank_reg; > u_short dual_port_data_reg; > int err; > int ii; > int jj; > u_short status_reg; > u_char status_val; > int ready; > int ready_loop_max =3D 5000; > > err =3D err_success; > > base_io_port =3D devices[unit].id_iobase; > > // Wait for command ready bit > status_reg =3D base_io_port + io_addr_status_reg; > ready =3D 0; > for (ii=3D0; ii { > for (jj=3D0; jj { > if (jj > ready_loop_max) > break; > status_val =3D inb(status_reg); > if ((status_val & status_reg_ready_for_cmd) !=3D 0) > { > ready =3D 1; > break; > } > } > if (ready) > break; > } > if (!ready) > { > err =3D err_timeout; > return err; > } > if (size =3D=3D 0) > { > return err; > } > if (size > cmd_buf_sz) > { > err =3D err_cmd_sz; > return err; > } > > // place command bytes into dual port ram > dual_port_bank_reg =3D base_io_port + io_addr_ram_addr_reg; > dual_port_bank_index =3D dp_ram_command_first_page; > for (ii=3D0; ii { > dual_port_data_reg =3D base_io_port + io_addr_dp_ram; > outb(dual_port_bank_reg, dual_port_bank_index); > > for (jj=3D0; jj<8; ++jj) > { // 8 bytes in each bank > outb(dual_port_data_reg, cmd_buf[ii]); > ++ii; > if (ii >=3D size) > break; > ++dual_port_data_reg; > } > if (ii >=3D size) > break; > ++dual_port_bank_index; > } > > // signal command > cmd_ready_reg =3D base_io_port + io_addr_cmd_ready; > outb(cmd_ready_reg, 0); > > return err; > } > > static int > set_8254 (int unit, > u_short counter, > u_short mode, > u_short initial_count) > { > u_short addr54; > int base_io_port; > u_char control_byte; > int err; > u_char ic_hi; > u_char ic_lo; > u_short i8254_data_reg; > u_short mux_addr_reg; > > err =3D err_success; > > base_io_port =3D devices[unit].id_iobase; > > switch (counter) > { > case 0: > addr54 =3D mux_54_ctr_0; > break; > case 1: > addr54 =3D mux_54_ctr_1; > break; > case 2: > addr54 =3D mux_54_ctr_2; > break; > default: > err =3D err_invalid_8254_ctr; > return err; > } > > mux_addr_reg =3D base_io_port + io_addr_mux_addr_reg; > i8254_data_reg =3D base_io_port + io_addr_8254_data_reg; > > control_byte =3D 0; > control_byte |=3D ((counter & 3) << 6); > control_byte |=3D (3 << 4); > control_byte |=3D ((mode & 7) << 1); > // BCD bit is 0, meaning counter it 16 bit unsigned binary > > outb(mux_addr_reg, mux_54_cont); // map in 8254 control register > outb(i8254_data_reg, control_byte); > outb(mux_addr_reg, addr54); // map in 8254 counter register. > > ic_lo =3D initial_count & 0xff; > ic_hi =3D (initial_count >> 8) & 0xff; > > outb(i8254_data_reg, ic_lo); > outb(i8254_data_reg, ic_hi); > > return err; > } > > static int start_tt (int unit) > { > u_char cmd_buf[8] =3D {0}; > int istat; > > cmd_buf[0] =3D cmd_clr_err; > send_cmd(unit,cmd_buf,1); > istat =3D get_status(unit); > printf ("start_tt after clr_err stat=3D%d\n",istat); > > cmd_buf[0] =3D cmd_tt_size; > cmd_buf[1] =3D 12; > cmd_buf[2] =3D 0; /* no wrap */ > send_cmd(unit, cmd_buf, 3); > istat =3D get_status(unit); > printf ("start_tt tt_size stat=3D%d\n",istat); > > cmd_buf[0] =3D cmd_tt; > cmd_buf[1] =3D tt_edge_pos; /* chan=3D0 << 6 | edge */ > send_cmd(unit, cmd_buf, 2); > istat =3D get_status(unit); > printf ("start_tt tt stat=3D%d\n",istat); > > return 0; > } > > static int stop_tt (int unit) > { > u_char cmd_buf[8] =3D {0}; > int istat; > > cmd_buf[0] =3D cmd_clr_err; > send_cmd(unit,cmd_buf,1); > istat =3D get_status(unit); > printf ("stop_tt stat after cmd_clr_err=3D%d\n",istat); > > cmd_buf[0] =3D cmd_chan_off; > cmd_buf[1] =3D 0xc0; > send_cmd(unit, cmd_buf, 2); > istat =3D get_status(unit); > printf ("stop_tt stat after cmd_chan_off=3D%d\n",istat); > > #if 0 > cmd_buf[0] =3D cmd_clr_tt; > cmd_buf[1] =3D 0; /* clear time tag buffer and time tag counter */ > send_cmd(unit, cmd_buf, 2); > istat =3D get_status(unit); > printf ("stop_tt stat after cmd_clr_tt=3D%d\n",istat); > #endif > > return 0; > } > > static int get_tt_count (int unit) > { > return 0; > } > > static int get_tt (int unit, long long *tt) > { > int base_io_port; > int ram_addr_reg; > int next_tt; > > send_cmd(unit,NULL,0); > base_io_port =3D devices[unit].id_iobase; > > ram_addr_reg =3D base_io_port + io_addr_ram_addr_reg; > outb (ram_addr_reg, dp_ram_status_page); > > { > int ii; > printf ("status page : "); > for (ii=3D0; ii<8; ++ii) > { > next_tt =3D inb(base_io_port + 8 + ii); > printf (" 0x%x"); > } > printf ("\n"); > } > > { > int ii; > printf ("tag buf :"); > outb (ram_addr_reg, 156); > for (ii=3D0; ii<8; ++ii) > { > next_tt =3D inb(base_io_port + 8 + ii); > printf (" 0x%x"); > } > outb (ram_addr_reg, 157); > for (ii=3D0; ii<4; ++ii) > { > next_tt =3D inb(base_io_port + 8 + ii); > printf (" 0x%x"); > } > printf ("\n"); > } > > return 0; > } > > static int get_status(int unit) > { > int base_io_port; > int ram_addr_reg; > int status_reg; > int istat; > > base_io_port =3D devices[unit].id_iobase; > ram_addr_reg =3D base_io_port + io_addr_ram_addr_reg; > > send_cmd(unit,NULL,0); > > outb (ram_addr_reg, dp_ram_status_page); > > status_reg =3D base_io_port + err_reg; > istat =3D inb(status_reg) & 0xff; > > return istat; > } > > > --==_Exmh_18363059200 > Content-Type: text/plain ; name="log_read_counts_980726.c"; charset=us-ascii > Content-Description: log_read_counts_980726.c > Content-Transfer-Encoding: quoted-printable > Content-Disposition: attachment; filename="log_read_counts_980726.c" > > #if 0 > cc -o test04 test04.c > > Experiment with /dev/gt401 not doing time tags > Run continuously > #endif > > #include > #include > #include > > #include > #include "gt401.h" > > #define DEV_PATH "/dev/gt401" > int fd =3D -1; > > int arg_ioctl =3D 0; > > int read_count =3D 0; > > #define MAX_TTAG_BUF (4*1024) > > main (int argc, char **argv) > { > int istat; > int ii; > gt401_read * ttag; > gt401_read ttag_buf[MAX_TTAG_BUF], last_ttag; > int log_mod; > double period_d; > double freq_d; > int first_flag =3D 1; > int read_req =3D (sizeof(gt401_read) * MAX_TTAG_BUF); > int read_data_count; > int max_read_data_count =3D 0; > > long long sample_period =3D -1; > long long sample_period_hi; > long long sample_period_low; > int read_dropped =3D 0; > int driver_dropped =3D 0; > > long long index_diff_driver; > long long index_diff_read_error; > long long calc_usec_diff_driver; > long long calc_index_diff_driver; > long long index_diff_driver_error; > > struct rtprio rtp; > int rtp_flag =3D 0; > > #if 1 > rtp_flag =3D 1; > rtp.type =3D RTP_PRIO_REALTIME; > rtp.prio =3D 0; > istat =3D rtprio (RTP_SET, > 0, > &rtp); > if (istat !=3D 0) > { > perror("rtprio"); > exit (1); > } > fprintf (stderr,"rtprio\n"); > #else > fprintf (stderr, "No rtprio\n"); > #endif > > fd =3D open (DEV_PATH, O_RDONLY, 0); > if (fd < 0) > { > fprintf(stderr,"open of %s failed\n",DEV_PATH); > exit (__LINE__); > } > > arg_ioctl =3D 20; > > period_d =3D ((double)arg_ioctl) / 10000.0; > freq_d =3D 1.0 / period_d; > log_mod =3D (int)(freq_d * 30.0); > > sample_period =3D (long long)(period_d * 1e6); > sample_period_low =3D sample_period - (sample_period / 8); > sample_period_hi =3D sample_period + (sample_period / 8); > > fprintf (stderr,"periodX10000=3D%d period=3D%f freq=3D%f\n",arg_ioctl,p= > eriod_d,freq_d); > fprintf (stderr,"sizeof(gt401_read) =3D %d\n",sizeof(gt401_read)); > > for (ii=3D1; ii { > printf ("# %s\n",argv[ii]); /* gnuplot comment line */ > } > printf ("# period=3D%f freq=3D%f", > period_d, freq_d); > if (rtp_flag) > printf(" RTPRIO"); > else > printf(" NO RTPRIO"); > printf ("\n"); > > istat =3D ioctl(fd,GT401_START_EVENTS,&arg_ioctl); > > for (;;) > { > istat =3D read (fd,(void *)&(ttag_buf[0]),read_req); > if (istat <=3D 0) > { > fprintf (stderr,"read fail istat=3D%d\n",istat); > perror("read fail"); > exit (__LINE__); > } > read_data_count =3D istat / sizeof(gt401_read); > printf ("%d\n",read_data_count); > fflush(stdout); > } /* for (;;) */ > > istat =3D ioctl(fd,GT401_STOP_EVENTS,&arg_ioctl); > > return (0); > } > > --==_Exmh_18363059200 > Content-Type: text/plain; name="log_read_counts_980726.c"; charset=us-ascii > Content-Description: log_read_counts_980726.c > Content-Transfer-Encoding: quoted-printable > Content-Disposition: attachment; filename="log_read_counts_980726.c" > > #if 0 > cc -o test04 test04.c > > Experiment with /dev/gt401 not doing time tags > Run continuously > #endif > > #include > #include > #include > > #include > #include "gt401.h" > > #define DEV_PATH "/dev/gt401" > int fd =3D -1; > > int arg_ioctl =3D 0; > > int read_count =3D 0; > > #define MAX_TTAG_BUF (4*1024) > > main (int argc, char **argv) > { > int istat; > int ii; > gt401_read * ttag; > gt401_read ttag_buf[MAX_TTAG_BUF], last_ttag; > int log_mod; > double period_d; > double freq_d; > int first_flag =3D 1; > int read_req =3D (sizeof(gt401_read) * MAX_TTAG_BUF); > int read_data_count; > int max_read_data_count =3D 0; > > long long sample_period =3D -1; > long long sample_period_hi; > long long sample_period_low; > int read_dropped =3D 0; > int driver_dropped =3D 0; > > long long index_diff_driver; > long long index_diff_read_error; > long long calc_usec_diff_driver; > long long calc_index_diff_driver; > long long index_diff_driver_error; > > struct rtprio rtp; > int rtp_flag =3D 0; > > #if 1 > rtp_flag =3D 1; > rtp.type =3D RTP_PRIO_REALTIME; > rtp.prio =3D 0; > istat =3D rtprio (RTP_SET, > 0, > &rtp); > if (istat !=3D 0) > { > perror("rtprio"); > exit (1); > } > fprintf (stderr,"rtprio\n"); > #else > fprintf (stderr, "No rtprio\n"); > #endif > > fd =3D open (DEV_PATH, O_RDONLY, 0); > if (fd < 0) > { > fprintf(stderr,"open of %s failed\n",DEV_PATH); > exit (__LINE__); > } > > arg_ioctl =3D 20; > > period_d =3D ((double)arg_ioctl) / 10000.0; > freq_d =3D 1.0 / period_d; > log_mod =3D (int)(freq_d * 30.0); > > sample_period =3D (long long)(period_d * 1e6); > sample_period_low =3D sample_period - (sample_period / 8); > sample_period_hi =3D sample_period + (sample_period / 8); > > fprintf (stderr,"periodX10000=3D%d period=3D%f freq=3D%f\n",arg_ioctl,p= > eriod_d,freq_d); > fprintf (stderr,"sizeof(gt401_read) =3D %d\n",sizeof(gt401_read)); > > for (ii=3D1; ii { > printf ("# %s\n",argv[ii]); /* gnuplot comment line */ > } > printf ("# period=3D%f freq=3D%f", > period_d, freq_d); > if (rtp_flag) > printf(" RTPRIO"); > else > printf(" NO RTPRIO"); > printf ("\n"); > > istat =3D ioctl(fd,GT401_START_EVENTS,&arg_ioctl); > > for (;;) > { > istat =3D read (fd,(void *)&(ttag_buf[0]),read_req); > if (istat <=3D 0) > { > fprintf (stderr,"read fail istat=3D%d\n",istat); > perror("read fail"); > exit (__LINE__); > } > read_data_count =3D istat / sizeof(gt401_read); > printf ("%d\n",read_data_count); > fflush(stdout); > } /* for (;;) */ > > istat =3D ioctl(fd,GT401_STOP_EVENTS,&arg_ioctl); > > return (0); > } > > --==_Exmh_18363059200-- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 18:02:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06225 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 18:02:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06129 for ; Fri, 31 Jul 1998 18:02:34 -0700 (PDT) (envelope-from witr@spooky.rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id VAA29841; Fri, 31 Jul 1998 21:02:53 -0400 (EDT) (envelope-from witr@spooky.rwwa.com) Message-Id: <199808010102.VAA29841@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Craig Spannring cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using FreeBSD for data acquisition? (long) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 21:02:53 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I manufacture a coordinate measuring machine that measures jet engine rotor and stator radii. I collects 16 bytes of data at 200 HZ when scanning. I havn't had any *major* problems, but it took some careful design. The motion control and all emergency condition processing is done in the kernel. The system doesn't (typically) do disk access when scanning, and all heavy computations are done when the system isn't moving or scanning. It does manage to maintain an X display with a 10 Hz update frequency. I've used proprietary RTOSes for projects like this in the past, and I prefer FreeBSD because of the source code access and the ability of readily ported data-reduction and display tools, etc... --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 18:07:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07338 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 18:07:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thrintun.epilogue.com (thrintun.epilogue.com [128.224.2.28]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA07302 for ; Fri, 31 Jul 1998 18:07:33 -0700 (PDT) (envelope-from sra@epilogue.com) Received: from localhost.epilogue.com ([127.0.0.1]:51462 "EHLO epilogue.com" ident: "IDENT-NOT-QUERIED [port 51462]") by thrintun.epilogue.com with ESMTP id <23162-213>; Fri, 31 Jul 1998 21:07:06 -0400 To: Warner Losh cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscons keymap "us.emacs.kbd" In-Reply-To: Message from Warner Losh dated "Fri, 31 Jul 1998 09:57:20 MDT" <199807311557.JAA14350@harmony.village.org> References: <199807311557.JAA14350@harmony.village.org> <19980731042314Z23162-213+60@thrintun.epilogue.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Fri, 31 Jul 1998 21:07:05 -0400 From: Rob Austein Message-Id: <19980801010719Z23162-213+67@thrintun.epilogue.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Fri, 31 Jul 1998 09:57:20 -0600 From: Warner Losh In message <19980731042314Z23162-213+60@thrintun.epilogue.com> Rob Austein writes: : The enclosed is a syscons keymap file, suitable for loading with : kbdcontrol. It implements a varient on the standard US ASCII : keyboard; in particular, it turns the ALT keys into meta keys, and : makes a few other tweaks so that the keyboard will work nicely with : bash and emacs. Or that's the theory, anyway, your milage may vary : radically if you didn't grow up with the MIT Chaosnet, ITS, SUPDUP, : and Lisp Machines.... How does this differ from the us.unix.kbd that I checked in a while ago? Other than being completely different, you mean :)? Primarily the meta bit support (ALT key turns on the most significant bit for most character codes, which isn't in the version of us.unix.kbd that I just downloaded via cvsweb). Secondarily, a different set of remappings to the standard keyboard layout (us.unix.kbd seems to remap a lot of the auxiliary keys, eg, it remaps my escape key to be `~). The easiest way to see all the differences is probably to load both files into emacs and use M-x compare-windows. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 18:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12637 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 18:58:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12628 for ; Fri, 31 Jul 1998 18:58:11 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id VAA11841; Fri, 31 Jul 1998 21:57:56 -0400 (EDT) Date: Fri, 31 Jul 1998 21:57:55 -0400 (EDT) From: "Matthew N. Dodd" To: "Alton, Matthew" cc: "'Hackers@FreeBSD.ORG'" , "'chrisa@commlet.com'" Subject: Re: This changes everything In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF901776623@STLABCEXG011> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The link at the bottom of the page makes me highly skeptical. I should expect that this device, if reality, will meet the same fate as the 100mpg car; there is just too much R&D money tied up in conventional technology. We could talk all day about cheaper, denser mass storage solutions that 'didn't make it'. For ~$1k I'm sure everyone would want a 90 gig hard drive. On Fri, 31 Jul 1998, Alton, Matthew wrote: > I'm reevaluating the relevance factor of my current work in > filesystems in light of the following earthshattering news: > http://www.accpc.com/tcapstore.htm > > This page outlines a radical advance in solid-state mass > storage which will replace both conventional HDDs and > RAM, thoroughly obsoleting large chunks of kernel code. > Granted, the device is currently vapor-hardware and, like > many another gadget (bubble memory, protein drive, async > processor...), it may well stall indefinitely on the drawing > board while the marketroids trumpet its inexorable conquest > of the planet, I think it prudent to assume that this one is > for real. At any rate, it is certainly safe to assume that > devices with the capabilities claimed for this one are very > close to taking shape. We should prepare for this inevitable > eventuality now and design a prototype kernel which will be able > to maximize the benefits of such devices. Perhaps better still, > we should negotiate to have FreeBSD installed on each unit > at the fab ;-) > > Matthew Alton > Computer Services - UNIX Systems Administration > (314)632-6644 matthew.alton@anheuser-busch.com > alton@plantnet.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 19:06:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13662 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 19:06:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA13654 for ; Fri, 31 Jul 1998 19:06:31 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z2R3q-0004OO-00; Fri, 31 Jul 1998 20:06:18 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id UAA19168; Fri, 31 Jul 1998 20:06:34 -0600 (MDT) Message-Id: <199808010206.UAA19168@harmony.village.org> To: Rob Austein Subject: Re: syscons keymap "us.emacs.kbd" Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Jul 1998 21:07:05 EDT." <19980801010719Z23162-213+67@thrintun.epilogue.com> References: <19980801010719Z23162-213+67@thrintun.epilogue.com> <199807311557.JAA14350@harmony.village.org> <19980731042314Z23162-213+60@thrintun.epilogue.com> Date: Fri, 31 Jul 1998 20:06:33 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980801010719Z23162-213+67@thrintun.epilogue.com> Rob Austein writes: : Primarily the meta bit support (ALT key turns on the most significant : bit for most character codes, which isn't in the version of : us.unix.kbd that I just downloaded via cvsweb). Secondarily, a : different set of remappings to the standard keyboard layout : (us.unix.kbd seems to remap a lot of the auxiliary keys, eg, it remaps : my escape key to be `~). OK. Sounds like a very different keymap. us.unix.kbd is intended to mimic the "traditional" layout of keyboards found in the unix world where the escape key is just above the tab key, the <- key generates DEL and the control key is immediately under the Tab key. I can't see any reason not to commit your keymap. What's the take of others on the list? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 19:07:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13874 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 19:07:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13868 for ; Fri, 31 Jul 1998 19:07:43 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA16820 for hackers@FreeBSD.ORG; Sat, 1 Aug 1998 04:07:37 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 1401EBF86; Sat, 1 Aug 1998 01:21:23 +0200 (CEST) Message-ID: <19980801012123.A24391@keltia.freenix.fr> Date: Sat, 1 Aug 1998 01:21:23 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: biggest mail server Mail-Followup-To: hackers@FreeBSD.ORG References: <98Jul31.150845pdt.177515@crevenia.parc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <98Jul31.150845pdt.177515@crevenia.parc.xerox.com>; from Bill Fenner on Fri, Jul 31, 1998 at 03:08:36PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4515 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bill Fenner: > never quite seemed to catch on. I was under the impression that > it hasn't been maintained in a number of years; our zmailer > installation's help message starts out Someone said the same thing the other day on Usenet and somebody answered that it was still maintained and alive. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 19:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18092 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 19:49:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18074 for ; Fri, 31 Jul 1998 19:49:18 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA07064; Sat, 1 Aug 1998 12:18:32 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA17729; Sat, 1 Aug 1998 12:18:19 +0930 (CST) Message-ID: <19980801121819.V11960@freebie.lemis.com> Date: Sat, 1 Aug 1998 12:18:19 +0930 From: Greg Lehey To: Warner Losh , Rob Austein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscons keymap "us.emacs.kbd" References: <19980801010719Z23162-213+67@thrintun.epilogue.com> <199807311557.JAA14350@harmony.village.org> <19980731042314Z23162-213+60@thrintun.epilogue.com> <19980801010719Z23162-213+67@thrintun.epilogue.com> <199808010206.UAA19168@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808010206.UAA19168@harmony.village.org>; from Warner Losh on Fri, Jul 31, 1998 at 08:06:33PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 31 July 1998 at 20:06:33 -0600, Warner Losh wrote: > In message <19980801010719Z23162-213+67@thrintun.epilogue.com> Rob Austein writes: > : Primarily the meta bit support (ALT key turns on the most significant > : bit for most character codes, which isn't in the version of > : us.unix.kbd that I just downloaded via cvsweb). Secondarily, a > : different set of remappings to the standard keyboard layout > : (us.unix.kbd seems to remap a lot of the auxiliary keys, eg, it remaps > : my escape key to be `~). > > OK. Sounds like a very different keymap. us.unix.kbd is intended to > mimic the "traditional" layout of keyboards found in the unix world > where the escape key is just above the tab key, the <- key generates > DEL and the control key is immediately under the Tab key. > > I can't see any reason not to commit your keymap. What's the take of > others on the list? OK, I've finally tried it (I don't normally use syscons). Yes, it does what I expect. I vote to have it committed. About the only question I have is: what does the standard keymap do that this one doesn't? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 20:16:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20704 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 20:16:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smok.apk.net (mail.apk.net [207.54.158.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20699 for ; Fri, 31 Jul 1998 20:16:38 -0700 (PDT) (envelope-from stuart@junior.apk.net) Received: from junior.apk.net (stuart@junior.apk.net [207.54.158.20]) by smok.apk.net (8.9.1/8.9.1/ts-apk-rel.980722) with ESMTP id XAA16474; Fri, 31 Jul 1998 23:16:33 -0400 (EDT) Received: from localhost by junior.apk.net (8.9.1/8.9.1) with SMTP id XAA02467; Fri, 31 Jul 1998 23:16:26 -0400 (EDT) Date: Fri, 31 Jul 1998 23:16:26 -0400 (EDT) From: Stuart Krivis To: "Matthew N. Dodd" cc: "'Hackers@FreeBSD.ORG'" Subject: Re: This changes everything In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998, Matthew N. Dodd wrote: > > The link at the bottom of the page makes me highly skeptical. I think they're completely and utterly bogus. Take a look at their connectivity claims. They make it sound like they are a backbone provider or something. Then do a whois on their domain. Why would anyone with that much connectivity host their web site on someone else's server - across the country yet! And the contact info is suspect too, given the msn addresses. And the dns is done by this systemv.com, plus a traceroute shows what looks to me like a vif on one of systemv.com's servers. And the reference to web-tv makes me wonder even more. :-) -- Stuart Krivis stuart@krivis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 22:30:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04083 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 22:30:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04066 for ; Fri, 31 Jul 1998 22:30:14 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA20880; Fri, 31 Jul 1998 22:30:07 -0700 (PDT) Message-ID: <19980731223007.E17037@Alameda.net> Date: Fri, 31 Jul 1998 22:30:07 -0700 From: Ulf Zimmermann To: Stuart Krivis , "Matthew N. Dodd" Cc: "'Hackers@FreeBSD.ORG'" Subject: Re: This changes everything Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Stuart Krivis on Fri, Jul 31, 1998 at 11:16:26PM -0400 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 11:16:26PM -0400, Stuart Krivis wrote: > On Fri, 31 Jul 1998, Matthew N. Dodd wrote: > > > > > The link at the bottom of the page makes me highly skeptical. > > I think they're completely and utterly bogus. Take a look at their > connectivity claims. They make it sound like they are a backbone provider > or something. Then do a whois on their domain. Why would anyone with that > much connectivity host their web site on someone else's server - across > the country yet! And the contact info is suspect too, given the msn > addresses. And the dns is done by this systemv.com, plus a traceroute > shows what looks to me like a vif on one of systemv.com's servers. And the > reference to web-tv makes me wonder even more. :-) We could call Intel if they licensed the slot 1 technology to them. We could also call Adaptec if they licensed ATAPI to them. ;-) > > > > > -- > > Stuart Krivis stuart@krivis.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 31 23:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09495 for freebsd-hackers-outgoing; Fri, 31 Jul 1998 23:38:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09490 for ; Fri, 31 Jul 1998 23:38:35 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id OAA07707 for ; Sat, 1 Aug 1998 14:37:28 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id OAA04884; Sat, 1 Aug 1998 14:37:59 +0800 Message-Id: <199808010637.OAA04884@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Fast FFT routines with source? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 14:37:58 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm part way through porting this company's seismic data processing code to FreeBSD and have got most things sorted out except for the fact that there doesn't seem to be any carefully optimised fft routines available. I do have the fftpack as found in ports, but I was wondering if there was anything faster than taht available with source. Oh, and if anyone knows where to find the source of X widgets that'll display seismic traces, power spectrums and the like, I'd be most grateful. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 03:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27037 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:13:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27024 for ; Sat, 1 Aug 1998 03:12:59 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA13588; Sat, 1 Aug 1998 06:10:44 -0400 (EDT) From: Peter Dufault Message-Id: <199808011010.GAA13588@hda.hda.com> Subject: Re: Using FreeBSD for data acquisition? (long) In-Reply-To: <199807312055.NAA00498@dingo.cdrom.com> from Mike Smith at "Jul 31, 98 01:55:30 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 1 Aug 1998 06:10:43 -0400 (EDT) Cc: chanders@timing.com, freebsd-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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > At the end of the message is histogram data for a test run of about > > 15 hours. I plot the data with gnuplot, using a logscale for y. > > Note that the longest read is 480 (480/500 = .960 seconds). Note > > that the most common read is 50 (50/500 = .100 seconds). > > This would tend to indicate a possible problem with the interaction > between your interrupt handler and the read handler, but it's > impossible to tell without seeing the code. .1 seconds is the round robin scheduling interval. It appears the wakeup from the driver isn't preempting the current process, but waiting until the next roundrobin call. As far as I can tell, wakeup should preempt it. We do large continuous data collection on FreeBSD. However, we don't try to meet any latency requirements - the data is time stamped by the different pieces of hardware and we just don't lose any of it. It is difficult to guarantee response in FreeBSD without: 1. Having a way to know you missed your deadline, either in hardware or using the CPU time stamps, for debugging your system and testing new releases; 2. Doing your latency critical work in the kernel. You still have to keep an eye out for misbehaving device drivers turning off interrupts, etc. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 03:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27608 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:19:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27603 for ; Sat, 1 Aug 1998 03:19:08 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA13606; Sat, 1 Aug 1998 06:17:06 -0400 (EDT) From: Peter Dufault Message-Id: <199808011017.GAA13606@hda.hda.com> Subject: Re: Using FreeBSD for data acquisition? (long) In-Reply-To: <199807311853.MAA04187@count.timing.com> from Craig Anderson at "Jul 31, 98 12:53:12 pm" To: chanders@timing.com (Craig Anderson) Date: Sat, 1 Aug 1998 06:17:06 -0400 (EDT) Cc: freebsd-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-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... Should RTP_PRIO_REALTIME help? Does FreeBSD > 3 have realtime features that will help? Is there a problem with > the code or a better approach? I put some fixes in FreeBSD-Current to avoid round robin context switches between equal priority RTP_PRIO_REALTIME processes, and it offers the POSIX interface as well as the RTP_PRIO interface, and I've tested it to see it works as advertised. You could try it and see if it behaves the same. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 03:26:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28388 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:26:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28383 for ; Sat, 1 Aug 1998 03:26:20 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.8) id LAA28466; Sat, 1 Aug 1998 11:26:12 +0100 (BST) (envelope-from joe) Message-ID: <19980801112611.B27976@pavilion.net> Date: Sat, 1 Aug 1998 11:26:12 +0100 From: Josef Karthauser To: Nick Hibma Cc: FreeBSD hackers mailing list Subject: Re: NetBSD now has USB .. References: <19980731123244.B26485@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Nick Hibma on Fri, Jul 31, 1998 at 06:22:05PM +0200 X-NCC-RegID: uk.pavilion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 06:22:05PM +0200, Nick Hibma wrote: > > Has anyone progressed on this? No one mailed me back :( > > Guess what I am going to do this weeked? > > Nick Great, keep us informed as to how it's going.. and in the mean time it's heads down at my end in the land of USB and Cypress microcontrollers and alas NT(WDM) device drivers. Bahh, the drivers have to be written under NT but can't be run because NT has no USB support! Dualboot NT and 98 is the only solution. Joe -- Josef Karthauser Technical Manager FreeBSD: The power to serve (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 03:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29396 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:38:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29381 for ; Sat, 1 Aug 1998 03:38:49 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA17075; Sat, 1 Aug 1998 12:38:43 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sat, 1 Aug 1998 12:38:42 +0200 (MET DST) Mime-Version: 1.0 To: Ollivier Robert Cc: hackers@FreeBSD.ORG Subject: Re: biggest mail server References: <98Jul31.150845pdt.177515@crevenia.parc.xerox.com> <19980801012123.A24391@keltia.freenix.fr> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 01 Aug 1998 12:38:41 +0200 In-Reply-To: Ollivier Robert's message of "Sat, 1 Aug 1998 01:21:23 +0200" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA29384 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: > According to Bill Fenner: > > never quite seemed to catch on. I was under the impression that > > it hasn't been maintained in a number of years; our zmailer > > installation's help message starts out > Someone said the same thing the other day on Usenet and somebody answered > that it was still maintained and alive. http://www.zmailer.org/ DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 03:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00292 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 03:46:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA00261 for ; Sat, 1 Aug 1998 03:46:12 -0700 (PDT) (envelope-from malte.lance@gmx.net) Received: from neuron.webmore.de (unverified [194.95.214.164]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Sat, 01 Aug 1998 12:47:21 +0200 Received: (from malte.lance@gmx.net) by neuron.webmore.de (8.8.8/8.8.8) id MAA04978; Sat, 1 Aug 1998 12:44:24 +0200 (CEST) From: Malte Lance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 1 Aug 1998 12:44:23 +0200 (CEST) To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? In-Reply-To: <199808010637.OAA04884@ariadne.tensor.pgs.com> References: <199808010637.OAA04884@ariadne.tensor.pgs.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13762.61682.42402.946437@neuron.webmore.de> Reply-To: malte.lance@gmx.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth writes: > I'm part way through porting this company's seismic data processing code to > FreeBSD and have got most things sorted out except for the fact that there > doesn't seem to be any carefully optimised fft routines available. I do have > the fftpack as found in ports, but I was wondering if there was anything > faster than taht available with source. Have a look at fftw: http://theory.lcs.mit.edu/~fftw/ > > Oh, and if anyone knows where to find the source of X widgets that'll display > seismic traces, power spectrums and the like, I'd be most grateful. Have a look at geomview. It's in the ports-collection. Malte. > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 05:37:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10085 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 05:37:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10080 for ; Sat, 1 Aug 1998 05:37:40 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.5]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA200; Sat, 1 Aug 1998 14:36:03 +0200 Message-ID: <35C30C0E.62EFC375@pipeline.ch> Date: Sat, 01 Aug 1998 14:37:34 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Stephen Hocking-Senior Programmer PGS Tensor Perth CC: hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? References: <199808010637.OAA04884@ariadne.tensor.pgs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I'm part way through porting this company's seismic data processing code to > FreeBSD and have got most things sorted out except for the fact that there > doesn't seem to be any carefully optimised fft routines available. I do have > the fftpack as found in ports, but I was wondering if there was anything > faster than taht available with source. You might take a look at: ftp://koobera.math.uic.edu/www/djbfft.html "djbfft is the fastest available code for small power-of-2 complex DFTs on a Pentium" "Current record for 256-point double-precision complex FFT: 18272 Pentium cycle" -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 08:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21484 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 08:50:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts02-067.dublin.indigo.ie [194.125.134.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21479 for ; Sat, 1 Aug 1998 08:50:17 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id QAA00755; Sat, 1 Aug 1998 16:44:37 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808011544.QAA00755@indigo.ie> Date: Sat, 1 Aug 1998 16:44:35 +0000 In-Reply-To: <23632.901894571@time.cdrom.com>; "Jordan K. Hubbard" Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: "Jordan K. Hubbard" , smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) Subject: Re: biggest mail server Cc: "B. Richardson" , Jacques Vidrine , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 31, 7:16am, "Jordan K. Hubbard" wrote: } Subject: Re: biggest mail server > I thought hotmail was running FreeBSD for at least some of their > stuff; why else would they have paid Justin over at Pluto Technologies > to port the CAM driver to 2.2.x? I recall reading about them switching at least part of their operation to Solaris because of its SMP performance. Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 09:53:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26705 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 09:53:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nash.pr.mcs.net (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26692 for ; Sat, 1 Aug 1998 09:53:03 -0700 (PDT) (envelope-from alex@nash.pr.mcs.net) Received: (from alex@localhost) by nash.pr.mcs.net (8.8.8/8.8.7) id LAA23973; Sat, 1 Aug 1998 11:51:27 -0500 (CDT) (envelope-from alex) Message-ID: <19980801115127.A23827@pr.mcs.net> Date: Sat, 1 Aug 1998 11:51:27 -0500 From: Alex Nash To: hackers@FreeBSD.ORG, tech@OpenBSD.org, tech-kern@NetBSD.org Subject: Second McKusick Video Course (Data Structures and Algorithms) Mail-Followup-To: hackers@FreeBSD.org, tech@OpenBSD.org, tech-kern@NetBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i X-Operating-System: FreeBSD 3.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Please do not follow up to the lists. Thank you. ] Apologies to everyone for the wide crosspost. There was sufficient interest in the first course that I think this is ok. Due to the success of Kirk's first video class (4.4BSD Kernel Internals: An Intensive Code Walkthrough) earlier this year, he has decided to produce a similar set of tapes for his introductory course: Unix Kernel Internals: Data Structures and Algorithms. Those interested may find more information about both courses and a signup form at: http://www.mckusick.com/courses/ Alex P.S - Thanks to everyone who signed up and made the production of the previous tape actually happen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 10:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02197 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 10:47:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02160 for ; Sat, 1 Aug 1998 10:47:26 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA02952; Sat, 1 Aug 1998 10:46:26 -0700 (PDT) Message-Id: <199808011746.KAA02952@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? In-reply-to: Your message of "Sat, 01 Aug 1998 14:37:58 +0800." <199808010637.OAA04884@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 10:46:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm part way through porting this company's seismic data processing code to > FreeBSD and have got most things sorted out except for the fact that there > doesn't seem to be any carefully optimised fft routines available. I do have > the fftpack as found in ports, but I was wondering if there was anything > faster than taht available with source. > > Oh, and if anyone knows where to find the source of X widgets that'll display > seismic traces, power spectrums and the like, I'd be most grateful. Go to Research Systems Inc (www.rsinc.com) and get a copy of IDL. The Linux version of IDL 5 should work fine. You will have to learn their bastardised Fortran/Motif mix, but as a tool for what you're trying to do it's *very* difficult to beat. This will, of course, mean beating on your company's code quite a bit... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 12:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11941 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 12:21:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from usc.usc.unal.edu.co ([200.21.26.65]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11930 for ; Sat, 1 Aug 1998 12:21:44 -0700 (PDT) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from unalmodem18.usc.unal.edu.co by usc.usc.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA12522; Sat, 1 Aug 1998 15:00:47 -0400 Message-Id: <35C36A35.635E7089@bachue.usc.unal.edu.co> Date: Sat, 01 Aug 1998 14:19:17 -0500 From: "Pedro F. Giffuni" Reply-To: giffunip@asme.org Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) Mime-Version: 1.0 To: Mike Smith Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: Fast FFT routines with source? References: <199808011746.KAA02952@antipodes.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, there was also khoros, http://www.khoral.com, but I don't know if they still have a non-commercial license for the older version of their code. Pedro. Mike Smith wrote: > > I'm part way through porting this company's seismic data processing code to > > FreeBSD and have got most things sorted out except for the fact that there > > doesn't seem to be any carefully optimised fft routines available. I do have > > the fftpack as found in ports, but I was wondering if there was anything > > faster than taht available with source. > > > > Oh, and if anyone knows where to find the source of X widgets that'll display > > seismic traces, power spectrums and the like, I'd be most grateful. > > Go to Research Systems Inc (www.rsinc.com) and get a copy of IDL. The > Linux version of IDL 5 should work fine. You will have to learn their > bastardised Fortran/Motif mix, but as a tool for what you're trying to > do it's *very* difficult to beat. > > This will, of course, mean beating on your company's code quite a bit... > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 14:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21490 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 14:01:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21468; Sat, 1 Aug 1998 14:01:34 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id XAA20551; Sat, 1 Aug 1998 23:01:20 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id VAA01099; Sat, 1 Aug 1998 21:15:33 +0200 (CEST) X-Face: " Date: Sat, 1 Aug 1998 21:15:33 +0200 From: Stefan Esser To: Ted Faber , Frank McConnell Cc: Mike Smith , Robert Swindells , hackers@FreeBSD.ORG, Stefan Esser Subject: Re: AMD PCNet/FAST cards; suppliers? Mail-Followup-To: Ted Faber , Frank McConnell , Mike Smith , Robert Swindells , hackers@FreeBSD.ORG References: <199807300038.RAA19554@daemonweed.reanimators.org> <199807301758.KAA24012@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807301758.KAA24012@tnt.isi.edu>; from Ted Faber on Thu, Jul 30, 1998 at 10:58:53AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-30 10:58 -0700, Ted Faber wrote: > I believe that with the stock driver and default configuration that's > roughly what happens, but with a little weirdness in the mix. The PCI > probe maps the ethernet to an unconventional port (0xfce0), modulo > bridge chip initializations. The ISA probe fails, because it's looking > in the wrong place. Probing the correct port also fails without some > work. This is how it's supposed to work. > Modifying the driver not to do the rest of the PCI initialization (not > assigning the PCI interrupt in the PCI probe routine) allows the ISA > probe on port 0xfce0 to succeed, and the driver to run. I avoid the > interrupt assignment by passing a NULL pointer out of the > lnc_attach_ne2100_pci() routine if I notice the chip ID in my Hitachi. You could just disable "if_lnc_p.c" (replace with an empty file, or wrap into "#if 0 / #endif"). > If I either take out the change to from pci_conf_read() to > pci_map_port() or restore the assignment of the PCI interrupt > (pci_map_int()) in the pci attach routines, the driver fails. Ahhh, you are running under 2.2.x ? Depending on your PCI BIOS, the chip will need some initialization that is performed by pci_map_port(). (The IO_ENABLE and/or MASTER_ENABLE bits in the device's PCI command register may be left off by the BIOS.) > There seem to be a couple ways to proceed. If we can determine how > the chip is set up that allows my bizarre system to work, we can test > for that instead of the chip ID, avoid the interrupt assignment and > use the ISA port. This doesn't strike me as the best plan, but it may > be feasible. If you want to do this, if you can send me a snippet of > code to plunk into the driver to dump the values of the appropriate > configuration registers, I'm happy to do it. The COMMAND register as initialized by the PCI BIOS would be most interesting. I guess, that the MASTER enable bit is not set. > On the other hand Robert Swindells's driver seems to attach the chip > as a PCI device and work fine. If his modifications are small and > acceptable, maybe the best plan is to incorporate them. If his mods I'd like to understand what's different in that new driver. The current driver worked well with the AMD PCnet found on many motherboards, and IMHO we need to make sure that the new driver supports the whole range of Lance chips ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 15:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25943 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 15:03:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25934 for ; Sat, 1 Aug 1998 15:03:03 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA25057; Sat, 1 Aug 1998 15:02:58 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd025043; Sat Aug 1 15:02:57 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id PAA26932; Sat, 1 Aug 1998 15:02:49 -0700 (MST) From: Terry Lambert Message-Id: <199808012202.PAA26932@usr07.primenet.com> Subject: Re: Using FreeBSD for data acquisition? (long) To: dufault@hda.com (Peter Dufault) Date: Sat, 1 Aug 1998 22:02:49 +0000 (GMT) Cc: mike@smith.net.au, chanders@timing.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199808011010.GAA13588@hda.hda.com> from "Peter Dufault" at Aug 1, 98 06:10:43 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This would tend to indicate a possible problem with the interaction > > between your interrupt handler and the read handler, but it's > > impossible to tell without seeing the code. > > 1 seconds is the round robin scheduling interval. It appears > the wakeup from the driver isn't preempting the current process, > but waiting until the next roundrobin call. As far as I can tell, > wakeup should preempt it. Kernel preemption is topologically equivalent to any other reason for kernel reentrancy, from kernel threading to allowing all the processors in an SMP system simultaneous entry. When you wakeup a process, you put it on the read-to-run queue, you *don't* context switch it to be active. This is because a wakeup can occur at interrupt level. In the case of a process on the RTPRIO queue, it gets to run first after the quantum is ceded by the process that did the waking; or rather it gets in line to run first, if you are running many things at RTPRIO. One thing you could do would be an explicit yield after the wakeup, to put the waking process to sleep immediately. If you have stuff that need to get done before the next cycle, however, this would be a mistake, since that would mean your processes were in fact coprocesses. This will also not help you in the case of a wakeup not under your control; such processes will not relinquish quantum voluntarily (you don't want voluntary cooperation in RT in any case; it requires too much trust). For interrupt level wakeups, this is more complicated; if you have extra work to do, it should be done before the yield, or it should be queued for deliveray as a software interrupt once you exit interrupt context back to the scheduler. One could argue that there are such things as RT soft interrupts, which sould result in the preemption of the interrupted process by the soft handler. 8-(. What you really need are serious modifications to support RT via scheduler and wakeup changes for kernel preemption; even then, the best latency you can guarantee is the latency you get when you wait for everyone to either be in the kernel asleep, or out of the kernel. This avoids cases where you try to preempt, for example, an FS operation on the kernel stack, and end up with priority inversion over access to a directory vnode. That is, your maximum latency is the most expensive interrupt handler, or the longest possible non-blocking call path not protected by an explicit nod in a lock graph. I believe you did some of this code a long time ago on the unofficiall (not hosted centrally) FreeBSD RT list. 8-). > 1. Having a way to know you missed your deadline, either in hardware > or using the CPU time stamps, for debugging your system and > testing new releases; Deadlining has different requirements. It implies full kernel reentrancy. If deadlining is to start, rather than to completion, it's much easier; otherwise you must also know the maximum amount of time the code that is going to be run will take to run, so you can reverse-bias the deadline to an earlier point. The difference between the minimum and maximum time *must* be such that, if you start at the earliest required time, you don't finish before you are permitted to finish -- in other words, "get done after X, but beofre X + N" is a bitch of a constraint. 8-(. You end up with contstraint-based data structures instead of just deadline-based structures. Do not expect completion deadlining in FreeBSD in excess of latency, if all you do is the necessary wakeup/scheduler hacks. > 2. Doing your latency critical work in the kernel. > > You still have to keep an eye out for misbehaving device drivers > turning off interrupts, etc. Right. This implies a hardware event, rather than a software event is the trigger that sets the deadline. If it's software, then you have to use a virtual event, probably shoddily derived from a timer interrupt at some point. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 18:13:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12234 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 18:13:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12229 for ; Sat, 1 Aug 1998 18:13:17 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for hackers@FreeBSD.ORG id 0z2mhy-0000xx-00; Sat, 1 Aug 1998 20:13:10 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: sysctl example To: hackers@FreeBSD.ORG Date: Sat, 01 Aug 1998 20:13:10 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi Folks, I'm looking for a good example of implementing a sysctl in the kernel that returns a table or list of structs. If there's an elegant way to set such things, I'd like to here about it, also. Thanks in advance! Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcO9JjeRhT8JRySpAQETcwP/a6f1YOMsXqJTR5vSnyrJsXfvntPcOIOY R3bEChhGUczVYf2WZZYxDx+zGffmcuIg/rvrEnecXWi184OVE9V9L997uoMR5EEL bQqG/KXR4+sjzFD8qRQhOC+39vYHAT0Q6295gFeoixKi8giifUxZU2oHePsfLFIx I/zCH9U14NY= =uC9F -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 19:05:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17762 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 19:05:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17745 for ; Sat, 1 Aug 1998 19:05:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA05424; Sat, 1 Aug 1998 19:03:59 -0700 (PDT) Message-Id: <199808020203.TAA05424@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: hackers@FreeBSD.ORG Subject: Re: sysctl example In-reply-to: Your message of "Sat, 01 Aug 1998 20:13:10 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 19:03:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----BEGIN PGP SIGNED MESSAGE----- > > Hi Folks, > > I'm looking for a good example of implementing a sysctl in > the kernel that returns a table or list of structs. > > If there's an elegant way to set such things, I'd like to > here about it, also. > > Thanks in advance! Is your table statically-sized, or does it vary in size at runtime? Do you want to return just the entire table, or optionally just one entry? Look for SYSCTL_NODE() declarations eg. in the networking code. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 19:05:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17801 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 19:05:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17789 for ; Sat, 1 Aug 1998 19:05:30 -0700 (PDT) (envelope-from howardjp@dragon.ham.muohio.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.8.5/8.8.5) with SMTP id WAA09825 for ; Sat, 1 Aug 1998 22:10:30 -0400 Date: Sat, 1 Aug 1998 22:10:30 -0400 (EDT) From: Jamie Howard To: freebsd-hackers@FreeBSD.ORG Subject: SCSI ZIP problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just purchased a new system to run FreeBSD and I pulled the SCSI ZIP drive (using the ZIP Zoom card) I had in my old system (a dual-boot FreeBSD/Win95 system) and put it in there. I did not change any of the hardware configuration on the ZIP drive or card however, and I rebuilt the kernel on this system for support for the ZIP Zoom card. It even recognizes it fine at start up. However, when I try to mount or otherwise reference (cat, etc) the device (sd0), the command just hangs and when I go to kill the process from another terminal, the process won't die. Eventually, I start seeing console messages saying aic(0:5:0) timed out and it will keep trying. The output of dmesg doesn't show any obvious IRQ or I/O address conflicts at boot time. The rest of my configuration looks like this: K6-3D-266 128M RAM 6.4G (Western Digital) HD (primary master) 1.2G (Western Digital) HD (secondary master) 36x CDROM drive Matrox Millenium 2 PCI card NE2000 clone 10/100 card Sound Blaster 16 This same drive and card worked fine under FreeBSD in the other system just last night. Does anyone know what might be wrong? Thanks, Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 19:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18362 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 19:10:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18357 for ; Sat, 1 Aug 1998 19:10:47 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) id 0z2nbN-0001Zs-00; Sat, 1 Aug 1998 21:10:25 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199808020203.TAA05424@antipodes.cdrom.com> References: <199808020203.TAA05424@antipodes.cdrom.com> Subject: Re: sysctl example To: Mike Smith cc: hackers@FreeBSD.ORG Date: Sat, 01 Aug 1998 21:10:25 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- It's a TAILQ, and returning the whole enchilada is what I want. Although it might be useful to grab one at a time someday. I'll look at the SYSCTL_NODE stuff, thanks! Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org On 1 August 1998 at 19:03, Mike Smith wrote: > Is your table statically-sized, or does it vary in size at runtime? Do > you want to return just the entire table, or optionally just one entry? > > Look for SYSCTL_NODE() declarations eg. in the networking code. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcPKkTeRhT8JRySpAQEFMgQAhskJBGtuoWOrbxNxDEbcGgYoNf7bW2no 1v0qrrcCJVf4Y0cFsIiS9bVERAH43GDgKQ9d2giz+uIX5xk47gN+b7NnAvUCSPSe yhHOHtS2zzEXfYO48oN6i3pZDPZFUzwhh4XQjHmIt5qda/jIbBOkHRIAg2FwihEw eAF9STstTXA= =cuEm -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 19:33:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20453 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 19:33:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20445 for ; Sat, 1 Aug 1998 19:33:35 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA05554; Sat, 1 Aug 1998 19:32:39 -0700 (PDT) Message-Id: <199808020232.TAA05554@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: sysctl example In-reply-to: Your message of "Sat, 01 Aug 1998 21:10:25 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 19:32:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's a TAILQ, and returning the whole enchilada is what I want. > Although it might be useful to grab one at a time someday. > > I'll look at the SYSCTL_NODE stuff, thanks! That's really only necessary if you need to return parts of the object. Perhaps consider SYSCTL_STRING or SYSCTL_OPAQUE instead. See sys/sys/sysctl.h for more ideas. > Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org > > On 1 August 1998 at 19:03, Mike Smith wrote: > > Is your table statically-sized, or does it vary in size at runtime? Do > > you want to return just the entire table, or optionally just one entry? > > > > Look for SYSCTL_NODE() declarations eg. in the networking code. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 21:29:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29057 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 21:29:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29050 for ; Sat, 1 Aug 1998 21:29:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA07081; Sat, 1 Aug 1998 23:29:24 -0500 (EST) (envelope-from toor) Message-Id: <199808020429.XAA07081@dyson.iquest.net> Subject: Re: Fast FFT routines with source? In-Reply-To: <199808010637.OAA04884@ariadne.tensor.pgs.com> from Stephen Hocking-Senior Programmer PGS Tensor Perth at "Aug 1, 98 02:37:58 pm" To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Date: Sat, 1 Aug 1998 23:29:24 -0500 (EST) Cc: hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth said: > I'm part way through porting this company's seismic data processing code to > FreeBSD and have got most things sorted out except for the fact that there > doesn't seem to be any carefully optimised fft routines available. I do have > the fftpack as found in ports, but I was wondering if there was anything > faster than taht available with source. > > Oh, and if anyone knows where to find the source of X widgets that'll display > seismic traces, power spectrums and the like, I'd be most grateful. > For fun, there is also a site http://www.jjj.de/fxt for FFT's. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 22:09:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01924 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 22:09:29 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spawn.nectar.com (spawn.nectar.com [204.27.67.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01918 for ; Sat, 1 Aug 1998 22:09:28 -0700 (PDT) (envelope-from nectar@spawn.nectar.com) Received: from localhost.nectar.com ([127.0.0.1] helo=spawn.nectar.com) by spawn.nectar.com with esmtp (Exim 1.92 #1) for hackers@FreeBSD.ORG id 0z2qOX-0000GC-00; Sun, 2 Aug 1998 00:09:21 -0500 X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: Another sysctl question To: hackers@FreeBSD.ORG Date: Sun, 02 Aug 1998 00:09:21 -0500 Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- kern_sysctl.c is not easy to follow for me ... How can I tell inside a sysctl handler whether or not I've been invoked from userland via a system call or from some other part of the kernel? I want to muck about with what sysctl_kern_proc does when called ultimately from a user process, based on some info in the proc structure. At least the code in kern_proc.c has been a good enough example for me to figure out my previous sysctl question ;-) Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNcP0gTeRhT8JRySpAQF0ogP/SyibaVhXqSzotRr1DAwsfCasnoUnGqeP DcvOmmsfPMYvWOOBPAXxLKXBXCc1awZV6XT9Zo28jMhsUGZM5PCngdrCExJv3ltW VSA5iUvJutAi78tY/stZ0I34zHhqEZKFX3ASb6Le9Cd9dvt3t+en7HJA335eYzO0 wncat2X05bs= =WbBW -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 22:18:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02687 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 22:18:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02680 for ; Sat, 1 Aug 1998 22:18:32 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA06146; Sat, 1 Aug 1998 22:17:44 -0700 (PDT) Message-Id: <199808020517.WAA06146@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jacques Vidrine cc: hackers@FreeBSD.ORG Subject: Re: Another sysctl question In-reply-to: Your message of "Sun, 02 Aug 1998 00:09:21 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 22:17:43 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > kern_sysctl.c is not easy to follow for me ... > > How can I tell inside a sysctl handler whether or not I've > been invoked from userland via a system call or from some other > part of the kernel? As a general rule, you shouldn't. If you think you should, it's likely that you're going about things the wrong way. > I want to muck about with what sysctl_kern_proc does when called > ultimately from a user process, based on some info in the proc > structure. This sounds like you want to add some form of access control for your sysctl. That's not something you should be doing inside your handler, IMHO. You might want to consider using curproc rather than the proc handed to you by the sysctl syscall, as you can check this for validity and then use it without having to pass it around. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 1 23:57:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08294 for freebsd-hackers-outgoing; Sat, 1 Aug 1998 23:57:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za (picasso.wcape.school.za [196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08267 for ; Sat, 1 Aug 1998 23:57:44 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) id 0z2s5B-0006Y2-00; Sun, 2 Aug 1998 08:57:29 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id IAA19823; Sun, 2 Aug 1998 08:50:02 +0200 (SAT) Date: Sun, 2 Aug 1998 08:50:00 +0200 (SAT) From: Peter van Heusden To: hackers@FreeBSD.ORG cc: Stephen Hocking-Senior Programmer PGS Tensor Perth Subject: Re: Fast FFT routines with source? In-Reply-To: <199808011746.KAA02952@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 Aug 1998, Mike Smith wrote: > > I'm part way through porting this company's seismic data processing code to > > FreeBSD and have got most things sorted out except for the fact that there > > doesn't seem to be any carefully optimised fft routines available. I do have > > the fftpack as found in ports, but I was wondering if there was anything > > faster than taht available with source. > > > > Oh, and if anyone knows where to find the source of X widgets that'll display > > seismic traces, power spectrums and the like, I'd be most grateful. > > Go to Research Systems Inc (www.rsinc.com) and get a copy of IDL. The > Linux version of IDL 5 should work fine. You will have to learn their > bastardised Fortran/Motif mix, but as a tool for what you're trying to > do it's *very* difficult to beat. > > This will, of course, mean beating on your company's code quite a bit... And if you are interested in IDL, have a look at the perl PDL module (actually mostly written in C, with a XS interface to perl), which also includes FFT code (and has a good reputation for speed, as I recall). Peter -- Peter van Heusden | Its the 90's, and collective action is STILL cool! pvh@leftside.wcape.school.za | Get active in your union today! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message