From owner-freebsd-current Sun Sep 19 1:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 0185A14F59 for ; Sun, 19 Sep 1999 01:51:39 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id AA43E1914; Sun, 19 Sep 1999 10:51:28 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id A1D6F49EC; Sun, 19 Sep 1999 10:51:28 +0200 (CEST) Date: Sun, 19 Sep 1999 10:51:28 +0200 (CEST) From: Andrzej Bialecki To: Adam Strohl Cc: Garrett Wollman , "Rodney W. Grimes" , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Adam Strohl wrote: > OK, Upgraded my Asus P2B-D machien from BIOS version 1008 to 1010, the > problem disappeared. Popped back to my old 1008 BIOS, problem came back. > > Looks like there was some wierd issue that got resolved in 1009 or 1010. Good! Thanks for the info. Now we have a solution. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 2: 3:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4F21E15103 for ; Sun, 19 Sep 1999 02:03:36 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:9LSmKDhvqUF53XrLKxDzSWtO+hPAbqRF@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA23126 for ; Sun, 19 Sep 1999 18:03:35 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA02241; Sun, 19 Sep 1999 18:07:54 +0900 (JST) Message-Id: <199909190907.SAA02241@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: HEADS UP: console code change Date: Sun, 19 Sep 1999 18:07:54 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Becase of the following change in /sys/dev/syscons, you need to recompile both the kernel, the vesa module and screen savers. # Well, if you don't use the vesa module and the screen savers, # you can forget about this :-) Thank you for your cooperation. Kazu >yokota 1999/09/19 01:58:54 PDT > > Modified files: > sys/dev/syscons schistory.c scmouse.c scvesactl.c > scvidctl.c syscons.c syscons.h > Log: > - Hang the scr_stat struct from dev_t. > - Remove sc_get_scr_stat(). It's not necessary anymore. > - Call ttymalloc() to allocate the struct tty for each vty, rather than > statically declaring an array of struct tty. We still need a statically > allocated struct tty for the first vty which is used for the kernel > console I/O, though. > - Likewise, call ttymalloc() for /dev/sysmouse and /dev/consolectl. > - Delete unnecessary test on the pointer struct tty *tp in some functions. > - Delete unused code in scmouse.c. > > WARNING: this change requires you to recompile screen savers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 3:11:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (Postfix) with ESMTP id 636101563B for ; Sun, 19 Sep 1999 03:11:43 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id MAA18824; Sun, 19 Sep 1999 12:11:32 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by paula.panke.de.freebsd.org (8.9.3/8.8.8) id MAA03838; Sun, 19 Sep 1999 12:07:09 +0200 (CEST) (envelope-from wosch) Message-ID: <19990919120709.23486@panke.de.freebsd.org> Date: Sun, 19 Sep 1999 12:07:09 +0200 From: Wolfram Schneider To: "Rodney W. Grimes" , "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: optional 'make release' speed-up patch References: <199909090404.AAA71015@bb01f39.unx.sas.com> <199909090635.XAA16842@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199909090635.XAA16842@gndrsh.dnsmgr.net>; from Rodney W. Grimes on Wed, Sep 08, 1999 at 11:35:04PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-09-08 23:35:04 -0700, Rodney W. Grimes wrote: > > Hi, > > > > The following patch to /usr/src/release/Makefile allows the > > specification of the variable FASTCLEAN, which instead of doing > > a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of > > course, this is only useful if your CHROOTDIR location is a > > separate mount point (which mine is: /snap). > > > > Comments and critiques welcome. > > And how about a similiar patch to /usr/src/Makefile that is > FASTCLEANDIR that brings back a patched up version of > my original CLEANDIR. Something like > -rm -rf /usr/obj/${.CURDIR}/tmp > chflags -R noschg /usr/obj/${.CURDIR}/tmp > rm -rf /usr/obj/${.CURDIR} You could also rename the old obj directory and then run the remove command as background process: mv /usr/obj/${.CURDIR} /usr/obj/${.CURDIR}.foobar ( rm -rf /usr/obj/${.CURDIR}.foobar; \ chflags -R noschg /usr/obj/${.CURDIR}.foobar; \ rm -rf /usr/obj/${.CURDIR}.foobar ) & -- Wolfram Schneider http://wolfram.schneider.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 5:33:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 74B8E15154 for ; Sun, 19 Sep 1999 05:33:28 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA12911 for current@FreeBSD.org; Sun, 19 Sep 1999 14:26:25 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sun, 19 Sep 1999 14:26:18 +0200 From: Marcel Moolenaar Message-ID: <37E4D66A.FE5D758@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: man(1): error while formatting page Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Man(1) produces the following error before displaying the manpage: Formatting page, please wait.../usr/share/tmac/tmac.doc:63: can't find macro file `mdoc/locale/locale-list' Done. The following patch solves the problem, although it is probably not suitable for being committed as it is: Index: Makefile.sub =================================================================== RCS file: /home/ncvs/src/contrib/groff/tmac/Makefile.sub,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 Makefile.sub --- Makefile.sub 1996/09/07 16:18:25 1.1.1.1 +++ Makefile.sub 1999/09/14 08:26:38 @@ -5,7 +5,8 @@ tmac.lj4 eqnrc troffrc tmac.safer SPECIALFILES=tmac.an tmac.s STRIPFILES=tmac.e tmac.doc tmac.doc.old -MDOCFILES=doc-common doc-ditroff doc-nroff doc-syms +MDOCFILES=doc-common doc-ditroff doc-nroff doc-syms \ + locale/locale-list locale/koi8-r mdocdir=$(tmacdir)/mdoc CLEANADD=stamp-strip stamp-wrap tmac.e-s tmac.doc-s tmac.doc.old-s \ doc-common-s doc-ditroff-s doc-nroff-s doc-syms-s *-wrap Andrey didn't reply to my mail about it, so if nobody else has any objections (or beat me to it), I'll fix it this week. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 5:45:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from drago.cert.org.tw (drago.cert.org.tw [140.117.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 542961515C for ; Sun, 19 Sep 1999 05:45:30 -0700 (PDT) (envelope-from foxfair@drago.cert.org.tw) Received: from foxfair (foxfair.cc.nsysu.edu.tw [140.117.100.101]) by drago.cert.org.tw (8.9.3/8.9.3) with SMTP id UAA03805; Sun, 19 Sep 1999 20:43:31 +0800 (CST) Date: Sun, 19 Sep 1999 20:44:41 +0800 From: Foxfair Hu To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: man(1): error while formatting page In-Reply-To: <37E4D66A.FE5D758@scc.nl> References: <37E4D66A.FE5D758@scc.nl> Message-Id: <37E4DAB935C.6BC5FOXFAIR@drago.cert.org.tw> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.25.04 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999 14:26:18 +0200 Marcel Moolenaar wrote: > Hi, > > Man(1) produces the following error before displaying the manpage: > > Formatting page, please wait.../usr/share/tmac/tmac.doc:63: can't find > macro file `mdoc/locale/locale-list' > Done. > > The following patch solves the problem, although it is probably not > suitable for being committed as it is: > [patch deleted...] > Andrey didn't reply to my mail about it, so if nobody else has any > objections (or beat me to it), I'll fix it this week. > Yeah! Go for it, please. > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org Cheers, -Foxfair. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 6:51:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from web116.yahoomail.com (web116.yahoomail.com [205.180.60.89]) by hub.freebsd.org (Postfix) with SMTP id 0AFBB15040 for ; Sun, 19 Sep 1999 06:51:33 -0700 (PDT) (envelope-from padequoi@yahoo.com) Message-ID: <19990919135001.16583.rocketmail@web116.yahoomail.com> Received: from [208.153.11.101] by web116.yahoomail.com; Sun, 19 Sep 1999 06:50:01 PDT Date: Sun, 19 Sep 1999 06:50:01 -0700 (PDT) From: gramond lamoureux Subject: mount: ufs filesystem not available To: current@freebsd.org Cc: newbies@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to upgrade from 2.2.6 to current using cvsup, then used make world. All went well, ( I was in single user mode) then I tried to reboot and I get the message mount: ufs filesystem not available. if I do fsck and see all my mount points and they have no errors but I can't reboot. mount -a gives me 3 (mount: ufs filesystem not available) modload: creating procfs-mod: Read-only file system procfs: vsfload(procfs): operation not permitted mount: ufs filesystem not available You'll probably say, he newbies should not be doing this, but everything goes so well I thaugh id try something more exiting. Any ideas before I go back to my 2.2.6 cd and start over? Mario... thanks __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 6:53:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from web116.yahoomail.com (web116.yahoomail.com [205.180.60.89]) by hub.freebsd.org (Postfix) with SMTP id AE09F1520E for ; Sun, 19 Sep 1999 06:53:03 -0700 (PDT) (envelope-from padequoi@yahoo.com) Message-ID: <19990919135130.16641.rocketmail@web116.yahoomail.com> Received: from [208.153.11.101] by web116.yahoomail.com; Sun, 19 Sep 1999 06:51:30 PDT Date: Sun, 19 Sep 1999 06:51:30 -0700 (PDT) From: Subject: subscribe To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 9:38:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id EF19214CB2 for ; Sun, 19 Sep 1999 09:38:37 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FIB00E26FKBN4@mta4.rcsntx.swbell.net> for current@FreeBSD.org; Sun, 19 Sep 1999 11:38:36 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA26056; Sun, 19 Sep 1999 11:38:42 -0500 (CDT envelope-from chris) Date: Sun, 19 Sep 1999 11:38:41 -0500 From: Chris Costello Subject: Re: mount: ufs filesystem not available In-reply-to: <19990919135001.16583.rocketmail@web116.yahoomail.com> To: gramond lamoureux Cc: current@FreeBSD.org Reply-To: chris@calldei.com Message-id: <19990919113841.J12328@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i References: <19990919135001.16583.rocketmail@web116.yahoomail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 19, 1999, gramond lamoureux wrote: > Any ideas before I go back to my 2.2.6 cd and start over? You should probably back up your important data and install 3.3 directly. -- |Chris Costello |New: It comes in different colors from the previous version. `------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 12: 5:30 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id CB807152B7; Sun, 19 Sep 1999 12:05:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BC42F1CD486; Sun, 19 Sep 1999 12:05:27 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Sun, 19 Sep 1999 12:05:27 -0700 (PDT) From: Kris Kennaway To: gramond lamoureux Cc: current@freebsd.org, newbies@freebsd.org Subject: Re: mount: ufs filesystem not available In-Reply-To: <19990919135001.16583.rocketmail@web116.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, gramond lamoureux wrote: > I was trying to upgrade from 2.2.6 to current using cvsup, then used > make world. All went well, ( I was in single user mode) then I tried > to reboot and I get the message > mount: ufs filesystem not available. You probably forgot to update at least one of: your kernel, or /etc (see mergemaster port). You're right that you shouldn't be running -current if you have to cross-post to -newbies as well. If you really want to do this, then fine, but please don't expect help with any problems you run into; you're expected to know what you're doing on this mailing list. You might want to play with 3.3 instead, since that's different enough from 2.2.6 to give you something to do. Thanks! Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 12:27:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 97712152BA for ; Sun, 19 Sep 1999 12:27:36 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-2-66.ucdavis.edu [169.237.16.194]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA58273 for ; Sun, 19 Sep 1999 12:27:35 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA01109 for freebsd-current@freebsd.org; Sun, 19 Sep 1999 12:27:34 -0700 (PDT) (envelope-from obrien) Date: Sun, 19 Sep 1999 12:27:32 -0700 From: "David O'Brien" To: freebsd-current@freebsd.org Subject: *** HEADS UP *** cvs commit: src/sys/i386/isa if_ep.c Message-ID: <19990919122732.D52195@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have added Jason Young support for the 3Com Megahertz 574B ethernet 16-bit PC-Card to the ``ep'' Ethernet driver. I tested it best I could, but I don't have access to all the 3Com cards (mostly ISA and PC-Card) this driver supports. Please let me know ASAP if these changes causes you problems. -- -- David (obrien@freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 13: 2: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E32BE14D64; Sun, 19 Sep 1999 13:01:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA17981; Sun, 19 Sep 1999 22:01:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: smp@freebsd.org, current@freebsd.org Subject: Testers please! From: Poul-Henning Kamp Date: Sun, 19 Sep 1999 22:01:52 +0200 Message-ID: <17979.937771312@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you have a PIIX4 based SMP system and run current, could you please try out this patch: http://phk.freebsd.dk/piix/ I'm very interested in hearing if there are any measurable difference apart from clock granularity being 3 times better. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 13:49:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 92A0E15721 for ; Sun, 19 Sep 1999 13:49:09 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 13137 invoked from network); 19 Sep 1999 20:49:09 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 19 Sep 1999 20:49:09 -0000 Date: Sun, 19 Sep 1999 15:49:08 -0500 (CDT) From: David Scheidt To: Poul-Henning Kamp Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-Reply-To: <17979.937771312@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Poul-Henning Kamp wrote: > > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. What sort of tests would you like done before and after? David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 14: 0:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DB05D14BCD; Sun, 19 Sep 1999 14:00:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA18309; Sun, 19 Sep 1999 22:59:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: David Scheidt Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-reply-to: Your message of "Sun, 19 Sep 1999 15:49:08 CDT." Date: Sun, 19 Sep 1999 22:59:55 +0200 Message-ID: <18307.937774795@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dav id Scheidt writes: >On Sun, 19 Sep 1999, Poul-Henning Kamp wrote: > >> >> If you have a PIIX4 based SMP system and run current, could you >> please try out this patch: >> >> http://phk.freebsd.dk/piix/ >> >> I'm very interested in hearing if there are any measurable difference >> apart from clock granularity being 3 times better. > >What sort of tests would you like done before and after? Any test you can think of really. I don't expect any problems, but I am very interested in the performance difference if any, since that would give me a good indication if it is a worthwhile job to spend more time on obfuscat^H^H^H^H^H^H^Hptimizing the timecounter code. As far as I can tell, access to the PIIX timecounter is about 2.5 microseconds faster than to the i8254. In relative terms it is about a factor 3 faster. You can flip forth and back between the old and new behaviour with: New: sysctl -w kern.timecounter.hardware=PIIX (if it refuses you probably don't have the PIIX4 hardware) Old: sysctl -w kern.timecounter.hardware=i8254 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 14:33:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 60AE215270 for ; Sun, 19 Sep 1999 14:33:47 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id RAA05287; Sun, 19 Sep 1999 17:33:25 -0400 (EDT) Date: Sun, 19 Sep 1999 17:33:24 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: "Jordan K. Hubbard" Cc: Doug Rabson , A.Leidinger@WJPServer.CS.Uni-SB.de, Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: newpcm and Vibra16X In-Reply-To: <82214.937301085@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an extra Vibra16X if you haven't gotten one yet, I'm dying to have my sound working again. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Tue, 14 Sep 1999, Jordan K. Hubbard wrote: > > If this is a card you own, please just wrap it up and put it in the post > > to Cameron so that he has a chance to see what is going on. > > If only it were - it's the on-board sound on my Tyan Thunder 100 Mobo. > If you or anyone else knows of a particular card which uses this chip, > however, then I'd be happy to pick one up. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 15:28:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182]) by hub.freebsd.org (Postfix) with ESMTP id 2C39E14CA6 for ; Sun, 19 Sep 1999 15:28:33 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA11059; Sun, 19 Sep 1999 15:41:11 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37E56363.FAC3E52A@gorean.org> Date: Sun, 19 Sep 1999 15:27:47 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: gramond lamoureux Cc: current@freebsd.org Subject: Re: mount: ufs filesystem not available References: <19990919135001.16583.rocketmail@web116.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gramond lamoureux wrote: > > I was trying to upgrade from 2.2.6 to current using cvsup, then used > make world. As someone already mentioned, you shouldn't cross post. As a new user you also shouldn't be running -current. :) That said, it sounds like you could benefit from what's available at http://freebsd.simplenet.com/make-upgrade.html. You will have to reinstall your 2.2.6, then follow ALL of the instructions on that page. You should also subscribe to and read the freebsd-stable mailing list, and your upgrade should be to 3.3-Stable. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 16:42:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id DAD7614BE9 for ; Sun, 19 Sep 1999 16:42:28 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FIB003HLZ6O5L@mta2.rcsntx.swbell.net> for current@FreeBSD.ORG; Sun, 19 Sep 1999 18:42:25 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id SAA37587; Sun, 19 Sep 1999 18:42:26 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sun, 19 Sep 1999 18:42:26 -0500 From: Chris Costello Subject: Re: mount: ufs filesystem not available In-reply-to: <37E56363.FAC3E52A@gorean.org> To: Doug Cc: gramond lamoureux , current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19990919184226.C37345@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19990919135001.16583.rocketmail@web116.yahoomail.com> <37E56363.FAC3E52A@gorean.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 19, 1999, Doug wrote: > As someone already mentioned, you shouldn't cross post. As a new user you > also shouldn't be running -current. :) That said, it sounds like you could > benefit from what's available at > http://freebsd.simplenet.com/make-upgrade.html. You will have to reinstall > your 2.2.6, then follow ALL of the instructions on that page. You should Why do that when he could just install 3.3? -- |Chris Costello |One if by LAN, 2 if by C, 3 if by ERR. `---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 17:37:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id A3B9A14EA0 for ; Sun, 19 Sep 1999 17:37:25 -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 UAA29575 for current@freebsd.org; Sun, 19 Sep 1999 20:39:30 -0400 From: Bill Paul Message-Id: <199909200039.UAA29575@skynet.ctr.columbia.edu> Subject: HEADS UP: 3Com xl driver changes To: current@freebsd.org Date: Sun, 19 Sep 1999 20:39:29 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2429 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just committed some changes to the xl driver to implement an alternate and hopefully more efficient transmit queueing scheme for 3c90xB adapters. The changes are based on the mechanism used in the 3Com 3c90xB driver for Linux which was just recently released (I didn't use any of the actual 3Com driver code though since it's GPLed). The changes involve using transmit descriptor polling; the NIC is set up to poll the transmit descriptor ring in order to determine when new packets are ready for transmission. The advantage to this is that the host doesn't have to perform any register accesses to the NIC during transmissions: it basically just queues the packets into the transmit ring and the card takes care of the rest. By contrast, the old mechanism requires several register accesses in order to stall the TX engine, queue new packets, update the transmit list pointer register, and then unstall the TX engine again. I've had good results with these changes here, however Murphy's Law applies, which means somebody somewhere will probably stumble over a bug that I missed. If people find that things are horribly broken, I'm prepared to back everything out. The cards for which these changes will have an effect are: - 3c900B-TPO - 3c900B-TPC - 3c900B-COMBO - 3c900B-FL - 3c905B-TX - 3c905B-FX - 3cSOHO100-TX - 3c905C-TX - 3c980-TX - 3c980B-TX - 3c980C-TX If you have one of these cards, you might want to try the following: run systat -iostat 1 and generate some heavy traffic on the xl interface both before upgrading the driver and after. Ideally, CPU and interrupt load should be lower after the driver has been updated. At the very least, there should not be any problems with packet transmission that weren't present before. If somebody notices a problem, please let me know immediately. For that matter, if you notice an improvement, let me know as well. -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-current" in the body of the message From owner-freebsd-current Sun Sep 19 18:24:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 78C8514BB8; Sun, 19 Sep 1999 18:24:48 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C1C1B1CC5; Mon, 20 Sep 1999 09:24:47 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-reply-to: Your message of "Sun, 19 Sep 1999 22:01:52 +0200." <17979.937771312@critter.freebsd.dk> Date: Mon, 20 Sep 1999 09:24:47 +0800 From: Peter Wemm Message-Id: <19990920012447.C1C1B1CC5@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. There is a problem with it as it tries to claim the same device as claimed by pcisupport.c and intpm.c.. pcisupport.c is where some folks have been hanging Tor Egge's RTC SMI trap patch from.. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 19:25:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from roadwarrior.stanford.edu (roadwarrior.Stanford.EDU [36.118.0.69]) by hub.freebsd.org (Postfix) with ESMTP id E7DA514C39 for ; Sun, 19 Sep 1999 19:25:15 -0700 (PDT) (envelope-from techie@roadwarrior.stanford.edu) Received: (from techie@localhost) by roadwarrior.stanford.edu (8.9.3/8.9.2) id TAA00388 for current@freebsd.org; Sun, 19 Sep 1999 19:25:19 -0700 (PDT) (envelope-from techie) Date: Sun, 19 Sep 1999 19:25:19 -0700 (PDT) From: Bob Vaughan Message-Id: <199909200225.TAA00388@roadwarrior.stanford.edu> To: current@freebsd.org Subject: boot problems with recent kernels. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been unable to get a kernel built after late august to boot on my laptop.. i'm currently running a kernel built on 24 august, with world from last week.. background details: the laptop is a chembook 3300, based on a pentium 233 MMX, with 96mb ram, a 4gb ide disk, and a ide cdrom. it also has a ESS1868 sound chip, which seems to have something to do with the problem. the laptop runs only freebsd, and was delivered without windoze installed. if i try booting a kernel built from my custom config, everything goes fine until just after pcm0 (ess1868) is probed. immediately after that, it finds unknown0, identified as ES1869 plug and play audiodrive. it appears to sit on address 0x201, which makes me think it's a game port or something like that. this probe is new, and dosen't appear in the kernel from 24 aug. if i try booting a kernel built from PCCARD, i get a page fault. ditto for GENERIC. here's the page fault (from notes..) fatal trap 12: page fault while in kernel mode fault virtual address 0x0 fault code : supervisor read, page not present instruction pointer: 0x8:0x0 stack pointer: 0x10:0xc03f5f54 frame pointer: 0x10:0xc03f5f68 code segment: base 0x0, limit 0xfffff, type 0x1b, DPL 0, pres 1, def32 1, gran 1 processor eflags: interrupt enabled, resume IOPL = 0 current process: 0 (swapper) interrupt mask: none trap number: 12 here's my custom config: # # ROADWARRIOR -- Laptop machine with ide/usb/pcmcia/tools # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # $Id: ROADWARRIOR,v 1.143.2.6.3 1999/09/08 20:20:00 techie Exp $ machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident ROADWARRIOR maxusers 30 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores ## options from LINT options MD5 options PERFMON options NETATALK options ICMP_BANDLIM options PCIC_RESUME_RESET options MROUTING # Multicast routing options COMPAT_LINUX options POWERFAIL_NMI options INCLUDE_CONFIG_FILE options DDB options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) controller isa0 controller pnp0 controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device wcd0 #IDE CD-ROM # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor device npx0 at isa? port IO_NPX irq 13 device apm0 at nexus? flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 controller miibus0 device ep0 at isa? port 0x240 irq 11 conflicts device ed0 at isa? port 0x320 irq 11 conflicts iomem 0xd8000 # audio device pcm0 at isa? port 0x220 irq 9 drq 1 flags 0x0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 4 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf 4 # Berkeley packet filter pseudo-device snp # USB support controller uhci0 # UHCI PCI->USB interface controller usb0 # USB Bus (required) device ugen0 # Generic device uhid0 # "Human Interface Devices" device ukbd0 # Keyboard device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 device ums0 # Mouse and here's the verbose output from the aug 24th kernel. (i've been unable to capture any of the failures) Sep 19 18:57:56 roadwarrior /kernel.bak: lave recovery = 4 Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: IORDY sampling disabled, Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: fast PIO disabled Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: IORDY sampling disabled, Sep 19 18:57:56 roadwarrior /kernel.bak: intel_piix_status: fast PIO disabled Sep 19 18:57:57 roadwarrior /kernel.bak: ide_pci: busmaster 0 status: 04 from port: 00001102 Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: IORDY sampling enabled, Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: fast PIO enabled Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: IORDY sampling disabled, Sep 19 18:57:57 roadwarrior /kernel.bak: intel_piix_status: fast PIO disabled Sep 19 18:57:57 roadwarrior /kernel.bak: ide_pci: busmaster 1 status: 04 from port: 0000110a Sep 19 18:57:57 roadwarrior /kernel.bak: uhci0: irq 0 at device 1.2 on pci0 Sep 19 18:57:57 roadwarrior /kernel.bak: uhci0: could not map ports Sep 19 18:57:57 roadwarrior /kernel.bak: device_probe_and_attach: uhci0 attach returned 6 Sep 19 18:57:57 roadwarrior /kernel.bak: chip1: at device 1.3 on pci0 Sep 19 18:57:57 roadwarrior /kernel.bak: vga-pci0: at device 2.0 on pci0 Sep 19 18:57:57 roadwarrior /kernel.bak: pcic0: irq 10 at device 3.0 on pci0 Sep 19 18:57:57 roadwarrior /kernel.bak: PCI Config space: Sep 19 18:57:57 roadwarrior /kernel.bak: 00: ac17104c 02100007 06070002 00824008 Sep 19 18:57:57 roadwarrior /kernel.bak: 10: 00000000 020000a0 20000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 20: 00000000 00000000 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 30: 00000000 00000000 00000000 07c0010a Sep 19 18:57:57 roadwarrior /kernel.bak: 40: 00000000 000003e1 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 50: 00000000 00000000 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 60: 00000000 00000000 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 70: 00000000 00000000 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: 80: 0044f060 00000000 00000000 01dc1722 Sep 19 18:57:57 roadwarrior /kernel.bak: 90: 616402c0 00000000 00000000 00000000 Sep 19 18:57:57 roadwarrior /kernel.bak: Cardbus Socket registers: Sep 19 18:57:57 roadwarrior /kernel.bak: 00: 00000000: 00000000: f000e2c3: f000c8e1: Sep 19 18:57:57 roadwarrior /kernel.bak: 10: 00000000: f000ff54: f000c8e1: f000c8e2: Sep 19 18:57:57 roadwarrior /kernel.bak: ExCa registers: Sep 19 18:57:57 roadwarrior /kernel.bak: 00: fb 77 c5 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 Sep 19 18:57:57 roadwarrior /kernel.bak: 10: 8a 66 03 38 e0 72 02 88 e0 bf 05 00 c4 5e 04 50 Sep 19 18:57:57 roadwarrior /kernel.bak: 20: b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 93 eb Sep 19 18:57:57 roadwarrior /kernel.bak: 30: eb 0f b6 c3 01 46 08 73 03 ff 46 0a d0 e3 00 5e Sep 19 18:57:57 roadwarrior /kernel.bak: pcic1: irq 10 at device 3.1 on pci0 Sep 19 18:57:57 roadwarrior /kernel.bak: PCI Config space: Sep 19 18:57:57 roadwarrior /kernel.bak: 00: ac17104c 02100007 06070002 00824008 Sep 19 18:57:57 roadwarrior /kernel.bak: 10: 00000000 020000a0 20000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 20: 00000000 00000000 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 30: 00000000 00000000 00000000 07c0020a Sep 19 18:57:58 roadwarrior /kernel.bak: 40: 00000000 000003e1 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 50: 00000000 00000000 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 60: 00000000 00000000 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 70: 00000000 00000000 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: 80: 0044d060 00000000 00000000 01dc1722 Sep 19 18:57:58 roadwarrior /kernel.bak: 90: 616402c0 00000000 00000000 00000000 Sep 19 18:57:58 roadwarrior /kernel.bak: Cardbus Socket registers: Sep 19 18:57:58 roadwarrior /kernel.bak: 00: 00000000: 00000000: f000e2c3: f000c8e1: Sep 19 18:57:58 roadwarrior /kernel.bak: 10: 00000000: f000ff54: f000c8e1: f000c8e2: Sep 19 18:57:58 roadwarrior /kernel.bak: ExCa registers: Sep 19 18:57:58 roadwarrior /kernel.bak: 00: fb 77 c5 86 c4 c0 c8 02 08 e8 40 91 88 fe 28 e0 Sep 19 18:57:58 roadwarrior /kernel.bak: 10: 8a 66 03 38 e0 72 02 88 e0 bf 05 00 c4 5e 04 50 Sep 19 18:57:58 roadwarrior /kernel.bak: 20: b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 93 eb Sep 19 18:57:58 roadwarrior /kernel.bak: 30: eb 0f b6 c3 01 46 08 73 03 ff 46 0a d0 e3 00 5e Sep 19 18:57:58 roadwarrior /kernel.bak: Initializing PnP override table Sep 19 18:57:58 roadwarrior /kernel.bak: Probing for PnP devices: Sep 19 18:57:58 roadwarrior /kernel.bak: Trying Read_Port at 203 Sep 19 18:57:58 roadwarrior /kernel.bak: PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 Sep 19 18:57:58 roadwarrior /kernel.bak: CSN 1 Vendor ID: ESS0003 [0x03007316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Sep 19 18:57:58 roadwarrior /kernel.bak: Called nullpnp_probe with tag 0x00000001, type 0x03007316 Sep 19 18:57:58 roadwarrior /kernel.bak: Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Sep 19 18:57:58 roadwarrior /kernel.bak: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Sep 19 18:57:58 roadwarrior /kernel.bak: fdc0: FIFO enabled, 8 bytes threshold Sep 19 18:57:58 roadwarrior /kernel.bak: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Sep 19 18:57:58 roadwarrior /kernel.bak: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 Sep 19 18:57:58 roadwarrior /kernel.bak: wdc0: unit 0 (wd0): Sep 19 18:57:58 roadwarrior /kernel.bak: wd0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S Sep 19 18:57:58 roadwarrior /kernel.bak: wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 Sep 19 18:57:58 roadwarrior /kernel.bak: wdc1 at port 0x170-0x177 irq 15 on isa0 Sep 19 18:57:58 roadwarrior /kernel.bak: wdc1: unit 0 (atapi): , removable, accel, dma, iordy Sep 19 18:57:58 roadwarrior /kernel.bak: wcd0: drive speed 2416KB/sec, 128KB cache Sep 19 18:57:58 roadwarrior /kernel.bak: wcd0: supported read types: CD-DA Sep 19 18:57:58 roadwarrior /kernel.bak: wcd0: Audio: play, 16 volume levels Sep 19 18:57:59 roadwarrior /kernel.bak: wcd0: Mechanism: ejectable tray Sep 19 18:57:59 roadwarrior /kernel.bak: wcd0: Medium: no/blank disc inside, unlocked Sep 19 18:57:59 roadwarrior /kernel.bak: atkbdc0: at port 0x60-0x6f on isa0 Sep 19 18:57:59 roadwarrior /kernel.bak: atkbd0: irq 1 on atkbdc0 Sep 19 18:57:59 roadwarrior /kernel.bak: atkbd: the current kbd controller command byte 0067 Sep 19 18:57:59 roadwarrior /kernel.bak: atkbd: keyboard ID 0x41ab (2) Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: RESET_KBD return code:00fa Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: RESET_KBD status:00aa Sep 19 18:57:59 roadwarrior /kernel.bak: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Sep 19 18:57:59 roadwarrior /kernel.bak: psm0: current command byte:0067 Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: TEST_AUX_PORT status:0000 Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: RESET_AUX return code:00fa Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: RESET_AUX status:00aa Sep 19 18:57:59 roadwarrior /kernel.bak: kbdc: RESET_AUX ID:0000 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: status 00 02 64 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: status 1c 03 3c Sep 19 18:57:59 roadwarrior last message repeated 2 times Sep 19 18:57:59 roadwarrior /kernel.bak: psm: status 10 00 64 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: data 08 00 00 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: status 00 02 64 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: data 08 00 00 Sep 19 18:57:59 roadwarrior /kernel.bak: psm: status 00 02 64 Sep 19 18:57:59 roadwarrior /kernel.bak: psm0: irq 12 on atkbdc0 Sep 19 18:57:59 roadwarrior /kernel.bak: psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons Sep 19 18:57:59 roadwarrior /kernel.bak: psm0: config:00000000, flags:00000000, packet size:3 Sep 19 18:57:59 roadwarrior /kernel.bak: psm0: syncmask:c0, syncbits:00 Sep 19 18:57:59 roadwarrior /kernel.bak: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Sep 19 18:57:59 roadwarrior /kernel.bak: fb0: vga0, vga, type:VGA (5), flags:0x7007f Sep 19 18:57:59 roadwarrior /kernel.bak: fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 Sep 19 18:57:59 roadwarrior /kernel.bak: fb0: init mode:24, bios mode:3, current mode:24 Sep 19 18:57:59 roadwarrior /kernel.bak: fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k Sep 19 18:57:59 roadwarrior /kernel.bak: VGA parameters upon power-up Sep 19 18:57:59 roadwarrior /kernel.bak: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Sep 19 18:57:59 roadwarrior /kernel.bak: bf 1f 00 4f 0d 0e 00 00 07 80 9c 0e 8f 28 1f 96 Sep 19 18:57:59 roadwarrior /kernel.bak: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Sep 19 18:57:59 roadwarrior /kernel.bak: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Sep 19 18:57:59 roadwarrior /kernel.bak: VGA parameters in BIOS for mode 24 Sep 19 18:57:59 roadwarrior /kernel.bak: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Sep 19 18:57:59 roadwarrior /kernel.bak: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Sep 19 18:57:59 roadwarrior /kernel.bak: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Sep 19 18:57:59 roadwarrior /kernel.bak: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Sep 19 18:58:00 roadwarrior /kernel.bak: EGA/VGA parameters to be used for mode 24 Sep 19 18:58:00 roadwarrior /kernel.bak: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Sep 19 18:58:00 roadwarrior /kernel.bak: bf 1f 00 4f 0d 0e 00 00 07 80 9c 0e 8f 28 1f 96 Sep 19 18:58:00 roadwarrior /kernel.bak: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Sep 19 18:58:00 roadwarrior /kernel.bak: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Sep 19 18:58:00 roadwarrior /kernel.bak: sc0: on isa0 Sep 19 18:58:00 roadwarrior /kernel.bak: sc0: VGA <16 virtual consoles, flags=0x200> Sep 19 18:58:00 roadwarrior /kernel.bak: sc0: fb0 kbd0 Sep 19 18:58:00 roadwarrior /kernel.bak: sio0: irq maps: 0x41 0x51 0x41 0x41 Sep 19 18:58:00 roadwarrior /kernel.bak: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Sep 19 18:58:00 roadwarrior /kernel.bak: sio0: type 16550A Sep 19 18:58:00 roadwarrior /kernel.bak: sio1: configured irq 3 not in bitmap of probed irqs 0 Sep 19 18:58:00 roadwarrior /kernel.bak: sio1: irq maps: 0x41 0x41 0x41 0x41 Sep 19 18:58:00 roadwarrior /kernel.bak: sio1: probe failed test(s): 0 1 2 4 6 7 9 Sep 19 18:58:00 roadwarrior /kernel.bak: sio2: not probed (disabled) Sep 19 18:58:00 roadwarrior /kernel.bak: sio3: not probed (disabled) Sep 19 18:58:00 roadwarrior /kernel.bak: ppc: parallel port found at 0x378 Sep 19 18:58:00 roadwarrior /kernel.bak: ppc: chipset forced to generic Sep 19 18:58:00 roadwarrior /kernel.bak: ppc0: EPP SPP Sep 19 18:58:00 roadwarrior /kernel.bak: ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 Sep 19 18:58:00 roadwarrior /kernel.bak: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Sep 19 18:58:00 roadwarrior /kernel.bak: plip: irq 7 Sep 19 18:58:00 roadwarrior /kernel.bak: plip0: on ppbus 0 Sep 19 18:58:00 roadwarrior /kernel.bak: bpf: lp0 attached Sep 19 18:58:00 roadwarrior /kernel.bak: lpt0: on ppbus 0 Sep 19 18:58:00 roadwarrior /kernel.bak: lpt0: Interrupt-driven port Sep 19 18:58:00 roadwarrior /kernel.bak: ppi0: on ppbus 0 Sep 19 18:58:00 roadwarrior /kernel.bak: mss_detect error - IREG (0x00/0x00) want 0xaa/0x45 Sep 19 18:58:00 roadwarrior /kernel.bak: pcm0 at port 0x220 irq 9 drq 1 on isa0 Sep 19 18:58:00 roadwarrior /kernel.bak: ESS1868 (rev 11) Sep 19 18:58:00 roadwarrior /kernel.bak: device combination doesn't support shared irq4 Sep 19 18:58:00 roadwarrior /kernel.bak: intr_connect(irq4) failed, result=-1 Sep 19 18:58:00 roadwarrior /kernel.bak: device combination doesn't support shared irq7 Sep 19 18:58:00 roadwarrior /kernel.bak: intr_connect(irq7) failed, result=-1 Sep 19 18:58:00 roadwarrior /kernel.bak: device combination doesn't support shared irq9 Sep 19 18:58:01 roadwarrior /kernel.bak: intr_connect(irq9) failed, result=-1 Sep 19 18:58:01 roadwarrior /kernel.bak: device combination doesn't support shared irq12 Sep 19 18:58:01 roadwarrior /kernel.bak: intr_connect(irq12) failed, result=-1 Sep 19 18:58:01 roadwarrior /kernel.bak: device combination doesn't support shared irq14 Sep 19 18:58:01 roadwarrior /kernel.bak: intr_connect(irq14) failed, result=-1 Sep 19 18:58:01 roadwarrior /kernel.bak: device combination doesn't support shared irq15 Sep 19 18:58:01 roadwarrior /kernel.bak: intr_connect(irq15) failed, result=-1 Sep 19 18:58:01 roadwarrior /kernel.bak: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) Sep 19 18:58:01 roadwarrior /kernel.bak: pcic: controller irq 10 Sep 19 18:58:01 roadwarrior /kernel.bak: Initializing PC-card drivers: ed ep Sep 19 18:58:01 roadwarrior /kernel.bak: BIOS Geometries: Sep 19 18:58:01 roadwarrior /kernel.bak: 0:03df7f3f 0..991=992 cylinders, 0..127=128 heads, 1..63=63 sectors Sep 19 18:58:01 roadwarrior /kernel.bak: 1:03feff00 0..1022=1023 cylinders, 0..255=256 heads, 1..0=0 sectors Sep 19 18:58:01 roadwarrior /kernel.bak: 2:03fdfe3f 0..1021=1022 cylinders, 0..254=255 heads, 1..63=63 sectors Sep 19 18:58:01 roadwarrior /kernel.bak: 3:00fe0203 0..254=255 cylinders, 0..2=3 heads, 1..3=3 sectors Sep 19 18:58:01 roadwarrior /kernel.bak: 0 accounted for Sep 19 18:58:01 roadwarrior /kernel.bak: Device configuration finished. Sep 19 18:58:01 roadwarrior /kernel.bak: Considering MFS root f/s. Sep 19 18:58:01 roadwarrior /kernel.bak: No MFS image available as root f/s. Sep 19 18:58:01 roadwarrior /kernel.bak: bpf: sl0 attached Sep 19 18:58:01 roadwarrior /kernel.bak: bpf: ppp0 attached Sep 19 18:58:01 roadwarrior /kernel.bak: new masks: bio 4008c040, tty 40031092, net 40071092 Sep 19 18:58:01 roadwarrior /kernel.bak: bpf: lo0 attached Sep 19 18:58:01 roadwarrior /kernel.bak: Linux-ELF exec handler installed Sep 19 18:58:01 roadwarrior /kernel.bak: Considering FFS root f/s. Sep 19 18:58:01 roadwarrior /kernel.bak: changing root device to wd0s1a Sep 19 18:58:01 roadwarrior /kernel.bak: wd0s1: type 0xa5, start 63, end = 2040191, size 2040129 : OK Sep 19 18:58:01 roadwarrior /kernel.bak: wd0s2: type 0xa5, start 2040192, end = 7789823, size 5749632 : OK Sep 19 18:58:01 roadwarrior /kernel.bak: wd0s3: type 0xa5, start 7999488, end = 8007551, size 8064 : OK Sep 19 18:58:01 roadwarrior /kernel.bak: wd0s4: type 0xa0, start 7789824, end = 7999487, size 209664 : OK Sep 19 18:58:01 roadwarrior /kernel.bak: Card inserted, slot 0 Sep 19 18:58:01 roadwarrior /kernel.bak: start_init: trying /sbin/init Sep 19 18:58:00 roadwarrior pccardd[64]: Using I/O addr 0x300, size 32 Sep 19 18:58:00 roadwarrior pccardd[64]: Setting config reg at offs 0xfd0 to 0x41, Reset time = 50 ms Sep 19 18:58:05 roadwarrior pccardd[64]: Assigning I/O window 0, start 0x300, size 0x20 flags 0x5 Sep 19 18:58:05 roadwarrior /kernel.bak: ed0: address 00:e0:98:01:a0:6c, type NE2000 (16 bit) Sep 19 18:58:05 roadwarrior /kernel.bak: bpf: ed0 attached Sep 19 18:58:05 roadwarrior pccardd[64]: Assign ed0, io 0x300-0x31f, mem 0x0, 0 bytes, irq 11, flags 0 Sep 19 18:58:08 roadwarrior pccardd[64]: pccardd started Sep 19 18:58:09 roadwarrior /kernel.bak: bpf: tun0 attached and here's a non-verbose output of the aug 24th kernel. (for some reason the beginning of the boot sequence is not captured in verbose mode..) Sep 19 17:53:19 roadwarrior /kernel.bak: Copyright (c) 1992-1999 The FreeBSD Project. Sep 19 17:53:19 roadwarrior /kernel.bak: Copyright (c) 1982, 1986, 1989, 1991, 1993 Sep 19 17:53:19 roadwarrior /kernel.bak: The Regents of the University of California. All rights reserved. Sep 19 17:53:19 roadwarrior /kernel.bak: FreeBSD 4.0-CURRENT #13: Tue Aug 24 11:52:30 PDT 1999 Sep 19 17:53:19 roadwarrior /kernel.bak: techie@roadwarrior.stanford.edu:/c1/4/src/sys/compile/ROADWARRIOR Sep 19 17:53:19 roadwarrior /kernel.bak: Timecounter "i8254" frequency 1193182 Hz Sep 19 17:53:19 roadwarrior /kernel.bak: CPU: Pentium/P55C (233.86-MHz 586-class CPU) Sep 19 17:53:20 roadwarrior /kernel.bak: Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Sep 19 17:53:20 roadwarrior /kernel.bak: Features=0x8001bf Sep 19 17:53:20 roadwarrior /kernel.bak: real memory = 100663296 (98304K bytes) Sep 19 17:53:20 roadwarrior /kernel.bak: avail memory = 94351360 (92140K bytes) Sep 19 17:53:20 roadwarrior /kernel.bak: Preloaded elf kernel "kernel.bak" at 0xc0311000. Sep 19 17:53:20 roadwarrior /kernel.bak: Intel Pentium detected, installing workaround for F00F bug Sep 19 17:53:20 roadwarrior /kernel.bak: npx0: on motherboard Sep 19 17:53:20 roadwarrior /kernel.bak: npx0: INT 16 interface Sep 19 17:53:20 roadwarrior /kernel.bak: apm0: on motherboard Sep 19 17:53:20 roadwarrior /kernel.bak: apm: found APM BIOS v1.2, connected at v1.2 Sep 19 17:53:20 roadwarrior /kernel.bak: pcib0: on motherboard Sep 19 17:53:20 roadwarrior /kernel.bak: pci0: on pcib0 Sep 19 17:53:20 roadwarrior /kernel.bak: isab0: at device 1.0 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: devclass_alloc_unit: npx0 already exists, using next available unit number Sep 19 17:53:20 roadwarrior /kernel.bak: isa0: on isab0 Sep 19 17:53:20 roadwarrior /kernel.bak: ide_pci0: at device 1.1 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: uhci0: irq 0 at device 1.2 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: uhci0: could not map ports Sep 19 17:53:20 roadwarrior /kernel.bak: device_probe_and_attach: uhci0 attach returned 6 Sep 19 17:53:20 roadwarrior /kernel.bak: chip1: at device 1.3 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: vga-pci0: at device 2.0 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: pcic0: irq 10 at device 3.0 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: pcic1: irq 10 at device 3.1 on pci0 Sep 19 17:53:20 roadwarrior /kernel.bak: Probing for PnP devices: Sep 19 17:53:20 roadwarrior /kernel.bak: CSN 1 Vendor ID: ESS0003 [0x03007316] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Sep 19 17:53:20 roadwarrior /kernel.bak: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Sep 19 17:53:20 roadwarrior /kernel.bak: fdc0: FIFO enabled, 8 bytes threshold Sep 19 17:53:20 roadwarrior /kernel.bak: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Sep 19 17:53:20 roadwarrior /kernel.bak: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 Sep 19 17:53:20 roadwarrior /kernel.bak: wdc0: unit 0 (wd0): Sep 19 17:53:20 roadwarrior /kernel.bak: wd0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S Sep 19 17:53:20 roadwarrior /kernel.bak: wdc1 at port 0x170-0x177 irq 15 on isa0 Sep 19 17:53:20 roadwarrior /kernel.bak: wdc1: unit 0 (atapi): , removable, accel, dma, iordy Sep 19 17:53:21 roadwarrior /kernel.bak: wcd0: drive speed 2416KB/sec, 128KB cache Sep 19 17:53:21 roadwarrior /kernel.bak: wcd0: supported read types: CD-DA Sep 19 17:53:21 roadwarrior /kernel.bak: wcd0: Audio: play, 16 volume levels Sep 19 17:53:21 roadwarrior /kernel.bak: wcd0: Mechanism: ejectable tray Sep 19 17:53:21 roadwarrior /kernel.bak: wcd0: Medium: no/blank disc inside, unlocked Sep 19 17:53:21 roadwarrior /kernel.bak: atkbdc0: at port 0x60-0x6f on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: atkbd0: irq 1 on atkbdc0 Sep 19 17:53:21 roadwarrior /kernel.bak: psm0: irq 12 on atkbdc0 Sep 19 17:53:21 roadwarrior /kernel.bak: psm0: model Generic PS/2 mouse, device ID 0 Sep 19 17:53:21 roadwarrior /kernel.bak: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: sc0: on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: sc0: VGA <16 virtual consoles, flags=0x200> Sep 19 17:53:21 roadwarrior /kernel.bak: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: sio0: type 16550A Sep 19 17:53:21 roadwarrior /kernel.bak: sio1: configured irq 3 not in bitmap of probed irqs 0 Sep 19 17:53:21 roadwarrior /kernel.bak: sio2: not probed (disabled) Sep 19 17:53:21 roadwarrior /kernel.bak: sio3: not probed (disabled) Sep 19 17:53:21 roadwarrior /kernel.bak: ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Sep 19 17:53:21 roadwarrior /kernel.bak: plip0: on ppbus 0 Sep 19 17:53:21 roadwarrior /kernel.bak: lpt0: on ppbus 0 Sep 19 17:53:21 roadwarrior /kernel.bak: lpt0: Interrupt-driven port Sep 19 17:53:21 roadwarrior /kernel.bak: ppi0: on ppbus 0 Sep 19 17:53:21 roadwarrior /kernel.bak: pcm0 at port 0x220 irq 9 drq 1 on isa0 Sep 19 17:53:21 roadwarrior /kernel.bak: ESS1868 (rev 11) Sep 19 17:53:21 roadwarrior /kernel.bak: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) Sep 19 17:53:21 roadwarrior /kernel.bak: pcic: controller irq 10 Sep 19 17:53:21 roadwarrior /kernel.bak: Initializing PC-card drivers: ed ep Sep 19 17:53:21 roadwarrior /kernel.bak: changing root device to wd0s1a Sep 19 17:53:21 roadwarrior /kernel.bak: Card inserted, slot 0 Sep 19 17:53:23 roadwarrior pccardd[64]: Using I/O addr 0x300, size 32 Sep 19 17:53:23 roadwarrior pccardd[64]: Setting config reg at offs 0xfd0 to 0x41, Reset time = 50 ms Sep 19 17:53:28 roadwarrior pccardd[64]: Assigning I/O window 0, start 0x300, size 0x20 flags 0x5 Sep 19 17:53:28 roadwarrior pccardd[64]: Assign ed0, io 0x300-0x31f, mem 0x0, 0 bytes, irq 11, flags 0 Sep 19 17:53:28 roadwarrior /kernel.bak: ed0: address 00:e0:98:01:a0:6c, type NE2000 (16 bit) Sep 19 17:53:33 roadwarrior pccardd[64]: pccardd started -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org | techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 20:30:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ppp141-220.cpis.net [206.155.220.170]) by hub.freebsd.org (Postfix) with ESMTP id 68EB715648 for ; Sun, 19 Sep 1999 20:29:56 -0700 (PDT) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.volatile.by-tor.tacorp.net (8.9.3/8.9.3) id XAA00711; Sun, 19 Sep 1999 23:26:51 -0400 (EDT) (envelope-from by-tor) Date: Sun, 19 Sep 1999 23:26:50 -0400 (EDT) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: freebsd-current@freebsd.org Subject: -current NE2000 driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The ed* ne2k and friends driver has quit working for me with a recent -current snapshot as of sometime early this afternoon. The board is correctly probed, but seems that it is never initialized. Normal behavior: amd0: irq 11 at device 8.0 on pci0 ed1: irq 9 at device 9.0 on pci0 ed1: address 00:00:b4:53:c2:97, type NE2000 (16 bit) vga-pci0: at device 10.0 on pci0 New (broken) behavior: amd0: irq 11 at device 8.0 on pci0 ed0: irq 9 at device 9.0 on pci0 vga-pci0: at device 10.0 on pci0 Also, I still cant get the new pcm driver to work quite right with my SB16. Its an old original SB16 that is software configurable but isnt pnp, so I have to config it manually. How do I set up the second drq line in my kernel config? drq0 and drq1 dont seem to work (is this even the right place to ask? :) And as a fairly recent defector from the linux camp, I'd just like to say what you guys already know -- GREAT work, keep it up! WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 20:42:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 67CAC14D36 for ; Sun, 19 Sep 1999 20:42:26 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA18198; Sun, 19 Sep 1999 23:42:23 -0400 (EDT) Date: Sun, 19 Sep 1999 23:42:23 -0400 (EDT) From: "Matthew N. Dodd" To: Wes Morgan Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current NE2000 driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Wes Morgan wrote: > The ed* ne2k and friends driver has quit working for me with a recent > -current snapshot as of sometime early this afternoon. The board is > correctly probed, but seems that it is never initialized. I'm working on fixing this problem as we speak. If it comes down to PCI cards not working vs. PCCARD devices not working I think the choice is clear. If anyone wants to stand up and volunteer to test PCCARD patches so I can fix if_ed once and for all (and correctly) please don't hesitate to stand up as I don't have the hardware to test PCCARD changes against. Wes, thanks for reporting this. > Normal behavior: > amd0: irq 11 at device 8.0 on pci0 > ed1: irq 9 at device 9.0 on pci0 > ed1: address 00:00:b4:53:c2:97, type NE2000 (16 bit) > vga-pci0: at device 10.0 on pci0 > > New (broken) behavior: > amd0: irq 11 at device 8.0 on pci0 > ed0: irq 9 at device 9.0 on pci0 > vga-pci0: at device 10.0 on pci0 > > Also, I still cant get the new pcm driver to work quite right with my > SB16. Its an old original SB16 that is software configurable but isnt pnp, > so I have to config it manually. How do I set up the second drq line in my > kernel config? drq0 and drq1 dont seem to work (is this even the right > place to ask? :) I seem to recall using the 'flags' keybord in the kernel config file but you'll have to check LINT. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 21: 0:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 29D5F14CC5 for ; Sun, 19 Sep 1999 21:00:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-2-61.ucdavis.edu [169.237.16.189]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA59713; Sun, 19 Sep 1999 21:00:38 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA07254; Sun, 19 Sep 1999 21:00:36 -0700 (PDT) (envelope-from obrien) Date: Sun, 19 Sep 1999 21:00:35 -0700 From: "David O'Brien" To: Chris Costello Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa if_ed.c Message-ID: <19990919210035.K52195@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199909190724.AAA18534@freefall.freebsd.org> <19990919225257.A362@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19990919225257.A362@holly.calldei.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a CURRENT issue, so it's discussion belongs there. On Sun, Sep 19, 1999 at 10:52:57PM -0500, Chris Costello wrote: > This breaks PCI RealTek cards (at least). Reverting to rev 1.160 > makes it work just fine for me. Did it work before September? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 21: 4: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 6FB9B1527E for ; Sun, 19 Sep 1999 21:04:00 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id VAA01620; Sun, 19 Sep 1999 21:03:53 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37E5B21D.8796C06C@MexComUSA.net> Date: Mon, 20 Sep 1999 04:03:41 +0000 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Wes Morgan , freebsd-current@FreeBSD.ORG Subject: Re: -current NE2000 driver References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Sun, 19 Sep 1999, Wes Morgan wrote: > > The ed* ne2k and friends driver has quit working for me with a recent > > -current snapshot as of sometime early this afternoon. The board is > > correctly probed, but seems that it is never initialized. > > I'm working on fixing this problem as we speak. > > If it comes down to PCI cards not working vs. PCCARD devices not working I > think the choice is clear. > > If anyone wants to stand up and volunteer to test PCCARD patches so I can > fix if_ed once and for all (and correctly) please don't hesitate to stand > up as I don't have the hardware to test PCCARD changes against. IŽll give it a try. IŽm using a LinkSys DE660 running current but compiling kernel with if_ed.c version 1.155. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 21:45:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.win.bright.net (wey1-cs-3.win.bright.net [208.140.5.164]) by hub.freebsd.org (Postfix) with ESMTP id 43B1015132 for ; Sun, 19 Sep 1999 21:45:37 -0700 (PDT) (envelope-from garyh@mail.win.bright.net) Received: from localhost (garyh@localhost) by mail.win.bright.net (8.9.3/8.9.1) with ESMTP id XAA02830 for ; Sun, 19 Sep 1999 23:47:25 GMT (envelope-from garyh@mail.win.bright.net) Date: Sun, 19 Sep 1999 23:47:25 +0000 (GMT) From: Gary Hampton To: current@FreeBSD.ORG Subject: New pcm driver with Vibra16 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has any one had this work recently? I know there was a lot of E-Mail on this a week or two ago but I have still not been able to get any soud. If I try to cat to /dev/audio or /dev/dsp it just hangs with software that uses it it also hangs. It did work with the old pcm drivers but at least as of 9-18-99 it dosn't work with the new one. "I don't have any solution but I certainly admire the problem." -- Ashleigh Brilliant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 21:54:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.win.bright.net (wey1-cs-2.win.bright.net [208.140.5.163]) by hub.freebsd.org (Postfix) with ESMTP id 63C6B15132 for ; Sun, 19 Sep 1999 21:54:27 -0700 (PDT) (envelope-from garyh@mail.win.bright.net) Received: from localhost (garyh@localhost) by mail.win.bright.net (8.9.3/8.9.1) with ESMTP id XAA02851 for ; Sun, 19 Sep 1999 23:56:16 GMT (envelope-from garyh@mail.win.bright.net) Date: Sun, 19 Sep 1999 23:56:16 +0000 (GMT) From: Gary Hampton To: current@FreeBSD.ORG Subject: ata drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying to get the ata drivers to work on my system for a a while now but can't seem to mount my cdrom drives. This is what I get on boot up: ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported atapi: piomode=4, dmamode=2, udmamode=-1 ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK atapi: DMA transfer mode set acd0: CDROM drive at ata0 as master acd0: drive speed 1034KB/sec, 512KB cache, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected atapi: piomode=3, dmamode=1, udmamode=-1 atapi: PIO transfer mode set acd1: < 8X_CD-ROM/ A01> CDROM drive at ata0 as slave acd1: drive speed 1367KB/sec, 120KB cache acd1: supported read types: CD-DA acd1: Audio: play, 255 volume levels acd1: Mechanism: ejectable tray acd1: Medium: CD-ROM 120mm data disc loaded, unlocked Is there a trick I need to know to mount this? I have tride mounting /dev/ almost every thing with "cd" in it but no luck the only drive I can mount is /dev/cd0c my scsi cdrom. I was able to mount these drives with the default atapi drivers but my system hung whe I tride to write to the cd-rw drive. The easiest way to figure the cost of living is to take your income and add ten percent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 21:56:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from pike.sover.net (pike.sover.net [209.198.87.34]) by hub.freebsd.org (Postfix) with ESMTP id 624AE14CB7 for ; Sun, 19 Sep 1999 21:56:56 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a327.bf.sover.net [209.198.83.235]) by pike.sover.net (8.9.3/8.9.3) with ESMTP id AAA28218; Mon, 20 Sep 1999 00:56:51 -0400 (EDT) Comments: SoVerNet Verification (on pike.sover.net) nightfall.digitalspark.net from arc0a327.bf.sover.net [209.198.83.235] 209.198.83.235 Mon, 20 Sep 1999 00:56:51 -0400 (EDT) Date: Mon, 20 Sep 1999 01:00:42 +0000 (GMT) From: Adam Strohl To: Gary Hampton Cc: current@FreeBSD.ORG Subject: Re: ata drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Remake your acd device, I think you may need a patch to do it. I had the same problem, until I rm-ed the device and remade it. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Sun, 19 Sep 1999, Gary Hampton wrote: > I have been trying to get the ata drivers to work on my system for a > a while now but can't seem to mount my cdrom drives. This is what I get on > boot up: > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > atapi: piomode=4, dmamode=2, udmamode=-1 > ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK > atapi: DMA transfer mode set > acd0: CDROM drive at ata0 as master > acd0: drive speed 1034KB/sec, 512KB cache, DMA > acd0: supported read types: CD-R, CD-RW, CD-DA, packet track > acd0: supported write types: CD-R, CD-RW, test write > acd0: Audio: play, 128 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected > atapi: piomode=3, dmamode=1, udmamode=-1 > atapi: PIO transfer mode set > acd1: < 8X_CD-ROM/ A01> CDROM drive at ata0 as slave > acd1: drive speed 1367KB/sec, 120KB cache > acd1: supported read types: CD-DA > acd1: Audio: play, 255 volume levels > acd1: Mechanism: ejectable tray > acd1: Medium: CD-ROM 120mm data disc loaded, unlocked > > Is there a trick I need to know to mount this? I have tride mounting > /dev/ almost every thing with "cd" in it but no luck the only drive I can > mount is /dev/cd0c my scsi cdrom. I was able to mount these drives with > the default atapi drivers but my system hung whe I tride to write to the > cd-rw drive. > > The easiest way to figure the cost of living is to take your income and > add ten percent. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 22: 3:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.win.bright.net (wey1-cs-2.win.bright.net [208.140.5.163]) by hub.freebsd.org (Postfix) with ESMTP id 2C92714CE2 for ; Sun, 19 Sep 1999 22:03:52 -0700 (PDT) (envelope-from garyh@mail.win.bright.net) Received: from localhost (garyh@localhost) by mail.win.bright.net (8.9.3/8.9.1) with ESMTP id AAA02969; Mon, 20 Sep 1999 00:05:38 GMT (envelope-from garyh@mail.win.bright.net) Date: Mon, 20 Sep 1999 00:05:38 +0000 (GMT) From: Gary Hampton To: Adam Strohl Cc: current@FreeBSD.ORG Subject: Re: ata drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Sep 1999, Adam Strohl wrote: > Remake your acd device, I think you may need a patch to do it. I had the > same problem, until I rm-ed the device and remade it. > > - ----( Adam Strohl )------------------------------------------------ - > - UNIX Operations/Systems http://www.digitalspark.net - > - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - > - ----------------------------------------( DigitalSpark.NET )------- - No luck I still just get: mount_cd9660: Block device required trying to mount acd0a acd0c acd1a and acd1c > On Sun, 19 Sep 1999, Gary Hampton wrote: > > > I have been trying to get the ata drivers to work on my system for a > > a while now but can't seem to mount my cdrom drives. This is what I get on > > boot up: > > ata-pci0: at device 7.1 on pci0 > > ata-pci0: Busmastering DMA supported > > atapi: piomode=4, dmamode=2, udmamode=-1 > > ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK > > atapi: DMA transfer mode set > > acd0: CDROM drive at ata0 as master > > acd0: drive speed 1034KB/sec, 512KB cache, DMA > > acd0: supported read types: CD-R, CD-RW, CD-DA, packet track > > acd0: supported write types: CD-R, CD-RW, test write > > acd0: Audio: play, 128 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected > > atapi: piomode=3, dmamode=1, udmamode=-1 > > atapi: PIO transfer mode set > > acd1: < 8X_CD-ROM/ A01> CDROM drive at ata0 as slave > > acd1: drive speed 1367KB/sec, 120KB cache > > acd1: supported read types: CD-DA > > acd1: Audio: play, 255 volume levels > > acd1: Mechanism: ejectable tray > > acd1: Medium: CD-ROM 120mm data disc loaded, unlocked > > > > Is there a trick I need to know to mount this? I have tride mounting > > /dev/ almost every thing with "cd" in it but no luck the only drive I can > > mount is /dev/cd0c my scsi cdrom. I was able to mount these drives with > > the default atapi drivers but my system hung whe I tride to write to the > > cd-rw drive. > > > > The easiest way to figure the cost of living is to take your income and > > add ten percent. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 23: 8:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id 78093156C6 for ; Sun, 19 Sep 1999 23:08:22 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FIC00C9DGYWER@mta2.rcsntx.swbell.net> for current@FreeBSD.org; Mon, 20 Sep 1999 01:06:37 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id BAA00873; Mon, 20 Sep 1999 01:07:01 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 20 Sep 1999 01:07:01 -0500 From: Chris Costello Subject: Re: cvs commit: src/sys/i386/isa if_ed.c In-reply-to: <19990919210035.K52195@dragon.nuxi.com> To: David O'Brien Cc: current@FreeBSD.org Reply-To: chris@calldei.com Message-id: <19990920010700.A838@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199909190724.AAA18534@freefall.freebsd.org> <19990919225257.A362@holly.calldei.com> <19990919210035.K52195@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 19, 1999, David O'Brien wrote: > Did it work before September? Yes. And rev 1.160 works fine. -- |Chris Costello |Press any key to continue or any other key to quit `--------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 23:28: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EE84514CAC for ; Sun, 19 Sep 1999 23:27:58 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA01638; Mon, 20 Sep 1999 08:27:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909200627.IAA01638@freebsd.dk> Subject: Re: ata drivers In-Reply-To: from Gary Hampton at "Sep 19, 1999 11:56:16 pm" To: garyh@mail.win.bright.net (Gary Hampton) Date: Mon, 20 Sep 1999 08:27:55 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Gary Hampton wrote: > I have been trying to get the ata drivers to work on my system for a > a while now but can't seem to mount my cdrom drives. This is what I get on > boot up: > atapi: DMA transfer mode set > acd0: CDROM drive at ata0 as master I'll bet that your CDROM doesn't do DMA right. I was optimistic when I added the ATAPI DMA code, but it seems LOTS, and I mean LOTS of ATAPI devices doesn't work in DMA mode even if they tell you so :( You can disable DMA on atapi devices by commecnting out the code block with the ata_dmainit call in it. I have a new version of the ATA driver very close to being committed, and it might solve some of this. The real solution might be to have a positive list of ATAPI devices known to work in DMA mode. -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 23:29:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id E4139156F9 for ; Sun, 19 Sep 1999 23:29:41 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id XAA93422; Sun, 19 Sep 1999 23:29:33 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 19 Sep 1999 23:29:33 -0700 (PDT) From: Doug White To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: console code change In-Reply-To: <199909190907.SAA02241@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Kazutaka YOKOTA wrote: > Becase of the following change in /sys/dev/syscons, you need to > recompile both the kernel, the vesa module and screen savers. [insert mandatory grumble about breaking compatibility here] Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 19 23:43:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1814415660 for ; Sun, 19 Sep 1999 23:43:37 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D91AA1CA7; Mon, 20 Sep 1999 14:43:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White Cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: HEADS UP: console code change In-reply-to: Your message of "Sun, 19 Sep 1999 23:29:33 MST." Date: Mon, 20 Sep 1999 14:43:36 +0800 From: Peter Wemm Message-Id: <19990920064336.D91AA1CA7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > On Sun, 19 Sep 1999, Kazutaka YOKOTA wrote: > > > Becase of the following change in /sys/dev/syscons, you need to > > recompile both the kernel, the vesa module and screen savers. > > [insert mandatory grumble about breaking compatibility here] Well, if you forget to sync the modules, I can vouch for the panic at startup... (kernel page fault, virtual address 0x54 here) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 0:38:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 321AE156C6 for ; Mon, 20 Sep 1999 00:38:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-4-86.ucdavis.edu [169.237.17.214]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA60460 for ; Mon, 20 Sep 1999 00:38:19 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA43027 for current@freebsd.org; Mon, 20 Sep 1999 00:38:17 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 1999 00:38:17 -0700 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** network KLM names have changed. Message-ID: <19990920003817.A42954@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just changed the names of the installed network driver KLM's. The KLM's are now prefixed by "if_". (their registered DRIVER_MODULE names have been changed to match). You will probably want to clean out the old modules after your next ``build world''. Also, please don't forget to change any necessary files in /boot, such as loader.rc, for this change. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 0:51:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8BF7F15764 for ; Mon, 20 Sep 1999 00:51:56 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-4-86.ucdavis.edu [169.237.17.214]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA60526 for ; Mon, 20 Sep 1999 00:51:55 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA43140 for current@freebsd.org; Mon, 20 Sep 1999 00:51:51 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 1999 00:51:51 -0700 From: "David O'Brien" To: current@freebsd.org Subject: Re: ** HEADS UP ** network KLM names have changed. Message-ID: <19990920005151.A43116@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19990920003817.A42954@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19990920003817.A42954@dragon.nuxi.com> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just changed the names of the installed network driver KLM's. Foo. Make that KLD's. (some name changes are just hard to engrained on the brain...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 0:56:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 27DD215764; Mon, 20 Sep 1999 00:56:11 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA21172; Mon, 20 Sep 1999 09:53:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-reply-to: Your message of "Mon, 20 Sep 1999 09:24:47 +0800." <19990920012447.C1C1B1CC5@overcee.netplex.com.au> Date: Mon, 20 Sep 1999 09:53:32 +0200 Message-ID: <21170.937814012@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, noted. I changed to to fail the probe but still use the hardware. Poul-Henning In message <19990920012447.C1C1B1CC5@overcee.netplex.com.au>, Peter Wemm writes : >Poul-Henning Kamp wrote: >> >> If you have a PIIX4 based SMP system and run current, could you >> please try out this patch: >> >> http://phk.freebsd.dk/piix/ >> >> I'm very interested in hearing if there are any measurable difference >> apart from clock granularity being 3 times better. > >There is a problem with it as it tries to claim the same device as claimed >by pcisupport.c and intpm.c.. pcisupport.c is where some folks have been >hanging Tor Egge's RTC SMI trap patch from.. > >Cheers, >-Peter >-- >Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 2: 9: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B671714D01 for ; Mon, 20 Sep 1999 02:07:10 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA01306; Mon, 20 Sep 1999 10:08:15 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 20 Sep 1999 10:08:15 +0100 (BST) From: Doug Rabson To: Pat Lynch Cc: "Jordan K. Hubbard" , A.Leidinger@WJPServer.CS.Uni-SB.de, Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: newpcm and Vibra16X In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Pat Lynch wrote: > I have an extra Vibra16X if you haven't gotten one yet, I'm dying to have > my sound working again. -Pat If you don't mind shipping it to the UK, I can give you my address. Cameron is in the process of moving and I don't have his new address. I'm very keen to get all the cards covered by the old pcm driver (and the voxware driver as far as possible) supported again. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 2:56:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 40F3814C57 for ; Mon, 20 Sep 1999 02:56:23 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id FAA09310; Mon, 20 Sep 1999 05:55:46 -0400 (EDT) Date: Mon, 20 Sep 1999 05:55:44 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Doug Rabson Cc: "Jordan K. Hubbard" , A.Leidinger@WJPServer.CS.Uni-SB.de, Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: newpcm and Vibra16X In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don;t need it back...so I don't mind... Peter Wemm also had an idea, of setting up a clean installed box here allowing certain hosts into the network and giving a serial console to work from. I don;t mind doing this either. Let me know. If you want me to ship it, give me your address and I'll ship it in the morning. The machine I do use the Vibra16X in is at work, and for now I'm without music again. Too bad we can't have both oldpcm and newpcm for a while ;) but with the new pnp stuff I'm not sure whether I can use the old pcm stuff anymore anyway, but I've been away for 3 weeks traveling across the United States to visit my grandmother in AZ, US. Haven't has a chance to catch up on -current totally yet. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Mon, 20 Sep 1999, Doug Rabson wrote: > On Sun, 19 Sep 1999, Pat Lynch wrote: > > > I have an extra Vibra16X if you haven't gotten one yet, I'm dying to have > > my sound working again. -Pat > > If you don't mind shipping it to the UK, I can give you my address. > Cameron is in the process of moving and I don't have his new address. I'm > very keen to get all the cards covered by the old pcm driver (and the > voxware driver as far as possible) supported again. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 5:41:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CDD0714CEF; Mon, 20 Sep 1999 05:41:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 509B71CC5; Mon, 20 Sep 1999 20:41:19 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-reply-to: Your message of "Mon, 20 Sep 1999 09:53:32 +0200." <21170.937814012@critter.freebsd.dk> Date: Mon, 20 Sep 1999 20:41:19 +0800 From: Peter Wemm Message-Id: <19990920124119.509B71CC5@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > Ok, noted. I changed to to fail the probe but still use the hardware. If intpm is probed first (the smbus driver), your probe won't even get called. I think we need an early quirks or hooks handler in the pci probes to handle stuff like this. For example, we have hooks fixing up a handful of wierd bios misconfigurations, collecting these together via a quirks table or whatever would also give a convenient place for you to hook this sort of thing into, and without it being dependent on link or probe order. > Poul-Henning > > In message <19990920012447.C1C1B1CC5@overcee.netplex.com.au>, Peter Wemm writ es > : > >Poul-Henning Kamp wrote: > >> > >> If you have a PIIX4 based SMP system and run current, could you > >> please try out this patch: > >> > >> http://phk.freebsd.dk/piix/ > >> > >> I'm very interested in hearing if there are any measurable difference > >> apart from clock granularity being 3 times better. > > > >There is a problem with it as it tries to claim the same device as claimed > >by pcisupport.c and intpm.c.. pcisupport.c is where some folks have been > >hanging Tor Egge's RTC SMI trap patch from.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 5:59:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1434F14F1D; Mon, 20 Sep 1999 05:59:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA22738; Mon, 20 Sep 1999 14:56:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Testers please! In-reply-to: Your message of "Mon, 20 Sep 1999 20:41:19 +0800." <19990920124119.509B71CC5@overcee.netplex.com.au> Date: Mon, 20 Sep 1999 14:56:54 +0200 Message-ID: <22736.937832214@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990920124119.509B71CC5@overcee.netplex.com.au>, Peter Wemm writes : >Poul-Henning Kamp wrote: >> >> Ok, noted. I changed to to fail the probe but still use the hardware. > >If intpm is probed first (the smbus driver), your probe won't even get >called. I think we need an early quirks or hooks handler in the pci probes >to handle stuff like this. For example, we have hooks fixing up a handful >of wierd bios misconfigurations, collecting these together via a quirks >table or whatever would also give a convenient place for you to hook this >sort of thing into, and without it being dependent on link or probe order. sigh... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 8:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 661AB15340 for ; Mon, 20 Sep 1999 08:38:35 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 22276 invoked from network); 20 Sep 1999 15:38:32 -0000 Received: from d161.syd2.zeta.org.au (203.26.9.33) by gidora.zeta.org.au with SMTP; 20 Sep 1999 15:38:32 -0000 Date: Tue, 21 Sep 1999 01:38:25 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Poul-Henning Kamp Cc: Michael Reifenberger , Warner Losh , Andrzej Bialecki , "Rodney W. Grimes" , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-Reply-To: <12842.937688435@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I remember this one too. I think the problem is that we fail to > service the RTC intr for some reason. This patch was only a > workaround, and received a verbal broadside from Bruce if I > remember right. > > Maybe it should be added under a sysctl until a better solution > is know. > > --- clock.c Sat Sep 18 22:41:40 1999 > +++ clock.c.new Sun Sep 5 13:21:35 1999 > @@ -203,4 +203,6 @@ > clkintr(struct clockframe frame) > { > + while (rtcin(RTC_INTR) & RTCIR_PERIOD) > + statclock(&frame); > if (timecounter->tc_get_timecount == i8254_get_timecount) { > disable_intr(); Use a watchdog timeout like you should for any device that may hang. Don't waste time running it every clock tick. ISTR that we thought that the bug might be caused by a bug in unwanted SMI interrupt handling. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 8:55:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1AD701557B for ; Mon, 20 Sep 1999 08:55:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA23504; Mon, 20 Sep 1999 17:52:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Michael Reifenberger , Warner Losh , Andrzej Bialecki , "Rodney W. Grimes" , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-reply-to: Your message of "Tue, 21 Sep 1999 01:38:25 +1000." Date: Mon, 20 Sep 1999 17:52:16 +0200 Message-ID: <23502.937842736@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce E vans writes: >> I remember this one too. I think the problem is that we fail to >> service the RTC intr for some reason. This patch was only a >> workaround, and received a verbal broadside from Bruce if I >> remember right. >> >> Maybe it should be added under a sysctl until a better solution >> is know. >> >> --- clock.c Sat Sep 18 22:41:40 1999 >> +++ clock.c.new Sun Sep 5 13:21:35 1999 >> @@ -203,4 +203,6 @@ >> clkintr(struct clockframe frame) >> { >> + while (rtcin(RTC_INTR) & RTCIR_PERIOD) >> + statclock(&frame); >> if (timecounter->tc_get_timecount == i8254_get_timecount) { >> disable_intr(); > >Use a watchdog timeout like you should for any device that may hang. >Don't waste time running it every clock tick. > >ISTR that we thought that the bug might be caused by a bug in unwanted >SMI interrupt handling. If anybody can reproduce this reliably on a *BX chipset I have code that will block SMI interrupts we can test with... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 9:46:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles540.castles.com [208.214.165.104]) by hub.freebsd.org (Postfix) with ESMTP id D1B2814CCD for ; Mon, 20 Sep 1999 09:46:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA32335; Mon, 20 Sep 1999 09:39:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909201639.JAA32335@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-reply-to: Your message of "Mon, 20 Sep 1999 17:52:16 +0200." <23502.937842736@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Sep 1999 09:39:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Use a watchdog timeout like you should for any device that may hang. > >Don't waste time running it every clock tick. > > > >ISTR that we thought that the bug might be caused by a bug in unwanted > >SMI interrupt handling. > > If anybody can reproduce this reliably on a *BX chipset I have > code that will block SMI interrupts we can test with... I'm not sure I follow what the alleged problem is here; who is handling the "unwanted" SMIs? If it's the BIOS, the last thing you want to do is block all SMIs. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 9:53:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6AAF8150BD for ; Mon, 20 Sep 1999 09:53:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA23779; Mon, 20 Sep 1999 18:52:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-reply-to: Your message of "Mon, 20 Sep 1999 09:39:28 PDT." <199909201639.JAA32335@dingo.cdrom.com> Date: Mon, 20 Sep 1999 18:52:57 +0200 Message-ID: <23777.937846377@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909201639.JAA32335@dingo.cdrom.com>, Mike Smith writes: >> >Use a watchdog timeout like you should for any device that may hang. >> >Don't waste time running it every clock tick. >> > >> >ISTR that we thought that the bug might be caused by a bug in unwanted >> >SMI interrupt handling. >> >> If anybody can reproduce this reliably on a *BX chipset I have >> code that will block SMI interrupts we can test with... > >I'm not sure I follow what the alleged problem is here; who is handling >the "unwanted" SMIs? If it's the BIOS, the last thing you want to do >is block all SMIs. The problem is that the RTC stalls. It is suspected that it could be long SMI durations which is responsible for this. To confirm the diagnosis disabling SMI is feasible. You system will not blow up if you disable SMI, I have a system happily chugging away here with SMI disabled for a month. Doing so even idiot-proofs the soft-off button :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 9:55:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 7688915B3C for ; Mon, 20 Sep 1999 09:55:30 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA10621 for ; Mon, 20 Sep 1999 18:55:27 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: Date: Mon, 20 Sep 1999 18:52:19 +0200 To: freebsd-current@freebsd.org From: Brad Knowles Subject: Web page w/ postmark results so far... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I haven't put everything online that I've gotten so far, but I have started putting my information online. See . The tables were taken directly from Network Appliance, and then extended to include the additional entries. I'll be adding columns for information from other sources, as I get the time and complete information. Please send me e-mail if you have any comments. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 10:20:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 7051915682 for ; Mon, 20 Sep 1999 10:20:23 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id TAA17009; Mon, 20 Sep 1999 19:20:20 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id TAA02404; Mon, 20 Sep 1999 19:20:19 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id TAA28606; Mon, 20 Sep 1999 19:19:53 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 20 Sep 1999 19:19:53 +0200 (CEST) From: Michael Reifenberger To: Bruce Evans Cc: Poul-Henning Kamp , Warner Losh , Andrzej Bialecki , "Rodney W. Grimes" , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Use a watchdog timeout like you should for any device that may hang. > Don't waste time running it every clock tick. > > ISTR that we thought that the bug might be caused by a bug in unwanted > SMI interrupt handling. Upgrading the BIOS to Rev. 1010 does solve the problem for me without the patch to clock.c. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 10:28:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with SMTP id 791D01501C for ; Mon, 20 Sep 1999 10:28:30 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4) id MAA20399; Mon, 20 Sep 1999 12:28:28 -0500 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199909201728.MAA20399@freebsd.netcom.com.> Subject: ep0 etherlink III breakage To: freebsd-current@freebsd.org Date: Mon, 20 Sep 1999 12:28:27 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey per request I'm reporting some ep0 breakage in today's -current. I have an etherlink III 3c509B and the probing appears correct. Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200 (PC hangs) More later... Mark Hittinger Mindspring/Netcom/Dallas bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 10:40:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id 3554514DCC for ; Mon, 20 Sep 1999 10:40:34 -0700 (PDT) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id TAA15199 for current@FreeBSD.ORG; Mon, 20 Sep 1999 19:40:33 +0200 (CEST) Date: Mon, 20 Sep 1999 19:40:33 +0200 From: Stephan van Beerschoten To: current@FreeBSD.ORG Subject: Page fault with ethernet xl0 Message-ID: <19990920194033.A15172@supra.rotterdam.luna.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have experienced something nasty. After cvs'ing my tree 3 hours ago which would be approx 16:00 CET, I did a buildworld, installed it, compiled a new kernel. This was right after the announcement that improvements had been made to the xl device driver. I wanted to try... The Result: Pagefault while trying to ifconfig during boot. fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xccbfddf8 frame pointer = 0x10:0xccbfde1c code segment = base 0x10, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 67 (ifconfig) interrupt mask = net tty trap number = 12 panic: page fault I hope this can be of any help. Let me know if you need more info. -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services www.luna.nl PO Box 28013 3003 KA Rotterdam NL PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C 77 8D 35 29 C4 2A 2D 27 "RETURN VALUES: The panic() function call does not return" :P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 10:47:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id B7E5A1506A for ; Mon, 20 Sep 1999 10:47: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 NAA00974; Mon, 20 Sep 1999 13:49:08 -0400 From: Bill Paul Message-Id: <199909201749.NAA00974@skynet.ctr.columbia.edu> Subject: Re: Page fault with ethernet xl0 To: stephanb@luna.nl (Stephan van Beerschoten) Date: Mon, 20 Sep 1999 13:49:06 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: <19990920194033.A15172@supra.rotterdam.luna.net> from "Stephan van Beerschoten" at Sep 20, 99 07:40:33 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1013 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Stephan van Beerschoten had to walk into mine and say: > I have experienced something nasty. After cvs'ing my tree 3 hours > ago which would be approx 16:00 CET, I did a buildworld, installed > it, compiled a new kernel. Dammit. You didn't even tell me what kind of card you have. Do you really need me to ask you for this? Go back and boot the kernel in verbose mode and show me *EXACTLY* what it says. -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-current" in the body of the message From owner-freebsd-current Mon Sep 20 11:58:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1C89615BB1 for ; Mon, 20 Sep 1999 11:58:33 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-2-68.ucdavis.edu [169.237.16.196]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA63406; Mon, 20 Sep 1999 11:58:32 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA70902; Mon, 20 Sep 1999 11:58:30 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 1999 11:58:28 -0700 From: "David O'Brien" To: Mark Hittinger Cc: freebsd-current@freebsd.org Subject: Re: ep0 etherlink III breakage Message-ID: <19990920115828.A70877@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199909201728.MAA20399@freebsd.netcom.com.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909201728.MAA20399@freebsd.netcom.com.> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 20, 1999 at 12:28:27PM -0500, Mark Hittinger wrote: > Hey per request I'm reporting some ep0 breakage in today's -current. I have > an etherlink III 3c509B and the probing appears correct. > > Sequence of events boot -s > # ifconfig ep0 inet 192.168.18.200 > (PC hangs) \begin{wpaul} WHAT am I supose to do with this? I don't even understand what you are trying to tell me. You booted single user and got a hang. What is the #'ed line supose to be? Last time *_I_* booted single user I didn't see such output. Can you ``boot -sv''. How far does it get? (give the last two-three lines). What is printed out about your 3c509B? (give this verbatum) \end{wpaul} -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 12:30:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id CD3EB14BF8 for ; Mon, 20 Sep 1999 12:30:36 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com ([209.157.86.2]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id MAA00450 for ; Mon, 20 Sep 1999 12:19:43 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA83623; Mon, 20 Sep 1999 12:19:43 -0700 (PDT) (envelope-from dillon) Date: Mon, 20 Sep 1999 12:19:43 -0700 (PDT) From: Matthew Dillon Message-Id: <199909201919.MAA83623@apollo.backplane.com> To: current@freebsd.org Subject: request for review, patch to specfs to fix EOF condition alignment with buffer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a request for a review. This patch fixes a bug in specfs relating to dealing with the EOF condition of a block device. If the EOF occurs in the middle of a block, specfs was not properly calculating the truncation for the I/O. This problem was first found by Tor. Tor's example creates an oddly-sized VN partition and then dd's from it. Without the patch the dd believes that it can read 2880 sectors. With the patch it correctly reads the last (truncated) block. dd if=/dev/zero of=/tmp/floppy.img bs=512 count=2879 vnconfig -s labels -c /dev/vn0 /tmp/floppy.img dd if=/dev/vn0 of=/dev/null bs=8k Once this patch is committed, the only problem we will have is in recognizing the write-EOF case, which I will have a recommendation for after this patch goes in. A similar problem in the VN device has already been fixed and committed. -Matt Index: miscfs/specfs/spec_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v retrieving revision 1.108 diff -u -r1.108 spec_vnops.c --- spec_vnops.c 1999/09/17 06:10:26 1.108 +++ spec_vnops.c 1999/09/20 17:50:48 @@ -311,19 +311,37 @@ do { bn = btodb(uio->uio_offset) & ~(bscale - 1); on = uio->uio_offset % bsize; - n = min((unsigned)(bsize - on), uio->uio_resid); if (seqcount > 1) { nextbn = bn + bscale; error = breadn(vp, bn, (int)bsize, &nextbn, (int *)&bsize, 1, NOCRED, &bp); } else { error = bread(vp, bn, (int)bsize, NOCRED, &bp); + } + + /* + * Figure out how much of the buffer is valid relative + * to our offset into the buffer, which may be negative + * if we are beyond the EOF. + * + * The valid size of the buffer is based on + * bp->b_bcount (which may have been truncated by + * dscheck or the device) minus bp->b_resid, which + * may be indicative of an I/O error if non-zero. + */ + n = bp->b_bcount - on; + if (n < 0) { + error = EINVAL; + } else { + n -= bp->b_resid; + if (n < 0) + error = EIO; } - n = min(n, bsize - bp->b_resid); if (error) { brelse(bp); return (error); } + n = min(n, uio->uio_resid); error = uiomove((char *)bp->b_data + on, n, uio); brelse(bp); } while (error == 0 && uio->uio_resid > 0 && n != 0); @@ -403,16 +421,48 @@ do { bn = btodb(uio->uio_offset) & ~blkmask; on = uio->uio_offset % bsize; + + /* + * Calculate potential request size, determine + * if we can avoid a read-before-write. + */ n = min((unsigned)(bsize - on), uio->uio_resid); if (n == bsize) bp = getblk(vp, bn, bsize, 0, 0); else error = bread(vp, bn, bsize, NOCRED, &bp); + + /* + * n is the amount of effective space in the buffer + * that we wish to write relative to our offset into + * the buffer. We have to truncate it to the valid + * size of the buffer relative to our offset into + * the buffer (which may end up being negative if + * we are beyond the EOF). + * + * The valid size of the buffer is based on + * bp->b_bcount (which may have been truncated by + * dscheck or the device) minus bp->b_resid, which + * may be indicative of an I/O error if non-zero. + * + * XXX In a newly created buffer, b_bcount == bsize + * and, being asynchronous, we have no idea of the + * EOF. + */ + if (error == 0) { + n = min(n, bp->b_bcount - on); + if (n < 0) { + error = EINVAL; + } else { + n -= bp->b_resid; + if (n < 0) + error = EIO; + } + } if (error) { brelse(bp); return (error); } - n = min(n, bsize - bp->b_resid); error = uiomove((char *)bp->b_data + on, n, uio); if (n + on == bsize) bawrite(bp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 12:47: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 91E4B14F1D for ; Mon, 20 Sep 1999 12:47:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA24570; Mon, 20 Sep 1999 21:46:21 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: request for review, patch to specfs to fix EOF condition alignment with buffer In-reply-to: Your message of "Mon, 20 Sep 1999 12:19:43 PDT." <199909201919.MAA83623@apollo.backplane.com> Date: Mon, 20 Sep 1999 21:46:21 +0200 Message-ID: <24568.937856781@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Once this patch is committed, the only problem we will have is > in recognizing the write-EOF case, which I will have a > recommendation for after this patch goes in. ...and the lack of error code returns on write. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 13: 7:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 1363B150C7; Mon, 20 Sep 1999 13:07:13 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id NAA44068; Mon, 20 Sep 1999 13:07:13 -0700 (PDT) (envelope-from mph) Date: Mon, 20 Sep 1999 13:07:13 -0700 From: Matthew Hunt To: "David O'Brien" Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage Message-ID: <19990920130712.A44007@wopr.caltech.edu> References: <199909201728.MAA20399@freebsd.netcom.com.> <19990920115828.A70877@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990920115828.A70877@dragon.nuxi.com>; from David O'Brien on Mon, Sep 20, 1999 at 11:58:28AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote: > > Sequence of events boot -s > > # ifconfig ep0 inet 192.168.18.200 > > (PC hangs) > \begin{wpaul} Dunno, you seem too mellow. > WHAT am I supose to do with this? I don't even understand what you > are trying to tell me. You booted single user and got a hang. What > is the #'ed line supose to be? Last time *_I_* booted single user I > didn't see such output. At a guess, the "#" is the root prompt that shows up after boot -s, and he typed the ifconfig command. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 13:10: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 49BD31503C for ; Mon, 20 Sep 1999 13:09:41 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with ESMTP id AAA30192; Tue, 21 Sep 1999 00:09:28 +0400 (MSD) (envelope-from camel@avias.com) Date: Tue, 21 Sep 1999 00:06:40 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.35) UNREG / CD5BF9353B3B7091 Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <44.990921@avias.com> To: current@freebsd.org Cc: paxvel@iname.com Subject: ports/net/kicq problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ppl, i have installed latest (1.1.2) kde11-i18n based on qt-i18-1.44a library. kde itself works fine but, now i'm experiencing another problem: old binaries that were built with older qt do not run. but the worst thing is impossibility to re-build that binaries with new qt using ports (kicq is good example). configure just fails while trying to find qt library: checking for QT-1.4x... configure: error: QT-1.4x (libraries) not found. Please check your installation! could anybody fix this? Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 13:23:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 69F7515ABC for ; Mon, 20 Sep 1999 13:23:05 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id WAA38626; Mon, 20 Sep 1999 22:23:00 +0200 (CEST) Message-Id: <199909202023.WAA38626@midten.fast.no> To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: Re: request for review, patch to specfs to fix EOF condition alignment with buffer From: Tor.Egge@fast.no In-Reply-To: Your message of "Mon, 20 Sep 1999 12:19:43 -0700 (PDT)" References: <199909201919.MAA83623@apollo.backplane.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 20 Sep 1999 22:23:00 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This problem was first found by Tor. Tor's example creates > an oddly-sized VN partition and then dd's from it. Without the > patch the dd believes that it can read 2880 sectors. With the > patch it correctly reads the last (truncated) block. Actually, the problem was discussed in -stable under the topic "Interesting way to crash a 3.2-stable box" around 1999-08-28. The discussion soon changed topic to "Interesting ways to print 3000 spaces...". - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 13:36: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.145.150.20]) by hub.freebsd.org (Postfix) with ESMTP id 2C74B15B55; Mon, 20 Sep 1999 13:35:59 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by users.anet-stl.com (8.9.3/8.8.5) with SMTP id PAA04761; Mon, 20 Sep 1999 15:35:56 -0500 (CDT) Date: Mon, 20 Sep 1999 15:35:56 -0500 (CDT) From: Jason Young To: Matthew Hunt Cc: "David O'Brien" , Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage In-Reply-To: <19990920130712.A44007@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not certain what the problem is, but the ep0 changes that generated the HEADS UP messages affect _only_ PC Cards. The other sections of code are untouched. Further, I'm 99% sure the only card that could possibly have been broken by the probe change is the 3C574 PC Card (not 3C574B). Jason Young accessUS Chief Network Engineer On Mon, 20 Sep 1999, Matthew Hunt wrote: > On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote: > > > > Sequence of events boot -s > > > # ifconfig ep0 inet 192.168.18.200 > > > (PC hangs) > > > \begin{wpaul} > > Dunno, you seem too mellow. > > > WHAT am I supose to do with this? I don't even understand what you > > are trying to tell me. You booted single user and got a hang. What > > is the #'ed line supose to be? Last time *_I_* booted single user I > > didn't see such output. > > At a guess, the "#" is the root prompt that shows up after boot -s, > and he typed the ifconfig command. > > -- > Matthew Hunt * Stay close to the Vorlon. > http://www.pobox.com/~mph/ * > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 13:55:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with SMTP id 6A49214C59 for ; Mon, 20 Sep 1999 13:55:18 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4) id OAA20652; Mon, 20 Sep 1999 14:38:44 -0500 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199909201938.OAA20652@freebsd.netcom.com.> Subject: Re: ep0 etherlink III breakage To: freebsd-current@freebsd.org Date: Mon, 20 Sep 1999 14:38:43 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > WHAT am I supose to do with this? I don't even understand what you > are trying to tell me. You booted single user and got a hang. What > is the #'ed line supose to be? Last time *_I_* booted single user I > didn't see such output. Actually I don't really care what you do with this. I did say "more later" but you chopped that part out. I was only trying to give a heads up. I've been playing with it for a few minutes and here is some more info: ie0: unknown board_id: f000 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 10 on isa0 ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e isa_compat: didn't get ports for le isa_compat: didn't get ports for cs unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 ep0 XXX: driver didn't set ifq_maxlen changing root device to wd0s1a Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing this in stand alone eliminates other issues. When debugging it pays to do that. I assume that the unknown0 probe success is where we are going astray - this may be a similar buglet to the ed_probe_HP_pclanp() routine I submitted a patch for last week ( lots of return 0 instead of return ENXIO ). I'll be doing some additional debugging this evening when I have more time. Guess I made the mistake of misreading a request that came through freebsd-current a few days ago asking for any problem reports with ep0. My mistake - sorry - I shall return to lurking. Regards, Mark Hittinger Mindspring/Netcom/Dallas bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18: 0:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-66.birch.net [216.212.1.66]) by hub.freebsd.org (Postfix) with ESMTP id F071D15C2B for ; Mon, 20 Sep 1999 17:59:59 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id TAA04816 for freebsd-current@freebsd.org; Mon, 20 Sep 1999 19:59:56 -0500 (CDT) From: Jim Bryant Message-Id: <199909210059.TAA04816@argus.tfs.net> Subject: is this a f77 issue, egcs issue, or os issue? To: freebsd-current@freebsd.org Date: Mon, 20 Sep 1999 19:59:55 -0500 (CDT) Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM937875595-4621-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM937875595-4621-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Just for kicks, while waiting for my phones to be hooked up at the new address, I ran some heavy duty benchmarks to see if the systems transported fine. i think they did arrive undamaged in the move, but i ran pitest at the maximum rated precision. apparently, this is not a /usr/bin/time issue, as i ran it again the next day without it with the same IOT trap. while this was running, it was approximately 80M or so into swap. all other precisions seem to work fine up to and including MX=22 [~6 million digits]. this is a dual p2-333 system running -current from Sun Jul 25 23:51:16 CDT 1999 [yeah, i know, but i don't think that is the issue here]. 512M RAM. and am using a tyan 1696dlua motherboard. I will attach source code to this message. DO NOT change ANYTHING except the MX value in pi4.f i think the time returned by /usr/bin/time seems to be correct based on my second run. the program only attempts file i/o once the run is complete. i AM NOT going to submit the half a gig core file, generate your own! in the past day or so, i have tested EVERY MX between 14 and 22. since this is a f77 program, it could be the fortran compiler, egcs, or the OS itself causing this problem. the output file fort.4 remains untouched and still contains the results of the previous test [MX=22]. -------------------------------------------------------------- 7:34:07am wahoo(15): /usr/bin/time -l ./pitest_mx=23 PI4 COMPUTATION TEST -- DP COMPLEX FFT MP VERSION MW = 23 NW = 2097152 ND = 12582906 ITERATION 1 12 ITERATION 2 12 ITERATION 3 12 ITERATION 4 12 ITERATION 5 12 ITERATION 6 12 ITERATION 7 12 ITERATION 8 12 ITERATION 9 12 ITERATION 10 12 ITERATION 11 12 ITERATION 12 12 CPU TIME = 0.0000 SECONDS. sfe: unit not connected apparent state: unit 4 (unnamed) lately writing sequential formatted external IO time: command terminated abnormally 78538.50 real 75950.35 user 367.96 sys 447972 maximum resident set size 92 average shared memory size 66 average unshared data size 128 average unshared stack size 912519 page reclaims 144493 page faults 0 swaps 44 block input operations 8148 block output operations 0 messages sent 0 messages received 0 signals received 144724 voluntary context switches 1875620 involuntary context switches IOT trap (core dumped) 5:23:10am wahoo(16): d fort.4 5:27:16am wahoo(17): d total 528545 drwxr-xr-x 2 root wheel 512 Sep 8 05:23 . drwxr-xr-x 4 root wheel 512 Jul 21 04:16 .. -rw------- 1 root wheel 57731 Jun 11 19:32 mp.f -rw-r--r-- 1 root wheel 35244 Jun 11 19:45 mp.o -rw-r--r-- 1 root wheel 6377979 Jul 21 12:19 pi.mx=22 -rw------- 1 root wheel 2962 Jun 11 19:32 pi2.f -rw------- 1 root wheel 3656 Jun 11 19:45 pi4.f -rwxr-xr-x 1 root wheel 35164 Jun 11 19:46 pitest.mx=14 -rwxr-xr-x 1 root wheel 119285 Jun 11 19:32 pitest_mx=14 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=15 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=16 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=17 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=18 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=19 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=20 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=21 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=22 -rwxr-xr-x 1 root wheel 119293 Jun 11 19:32 pitest_mx=23 -rw------- 1 root wheel 532840448 Sep 8 05:23 pitest_mx=23.core -rw------- 1 root wheel 266240 Sep 8 05:23 time.core -rw-r--r-- 1 root wheel 812 Jun 13 11:47 time.out 5:27:36am wahoo(18): jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ --ELM937875595-4621-0_ Content-Type: application/octet-stream; type=tar; conversions=x-gzip Content-Disposition: attachment; filename=pitest.tgz Content-Description: pitest.tgz Content-Transfer-Encoding: base64 H4sIAM7X5jcAA+w8a3PayJbzOb+iK3VrDTZgJLDjpDZVKx7OcGMwg3FCdmtTJaCxdQOIkYQdT82P 3/PobrWEsJ3MTO5+GOreGKm7T58+73P6MJvArS1++ms/Tr1+Wq+Ln4RwXp3QX/jov0KcnLquEKev GvWGe+I2TmFa/VX95CdR/4vxos82TvxIiJ/+NY0e/HWyd979rZTLH4HQj/0wC4ajy3cjry+Gvbb7 ov2iDa/a4WqzTWQM70QSCn/9ICL561bGiZyL9XY1lZEIF2Ie3ARJXBHbDc0SK/9rsNqucMifhtuE YCVyLVbBchmE64qYy41cz4P1jQjXIrmVYrEM/QSeq5swWCdiE8lZEMNU4d/5wdKfLqWaSbBmjFck phJhbGM5rwkxvg1iWBneRP5KwFcABJsAposwwjnCjwG5eLuRkQZA0OIHOM9KzG7l7IsGA/9DtH7d +vMIEJv5y+UDbLu+k9GNXCdwgnALSFUNohWD2FJ+FefnYwFTcaCmaNnx74K5+LkmWnAg+UAk/+d2 LYXbqAjn9dmZmjeGbf3lTRgFye2Kjkb4M8Z4WuAFYAdnWYTLZXgfv1ELr2QihFeql8VbcfXLaCxK brkiRIvf1OHrkL+64shMUGt7QAs/kcwKAku82eBbOIPZA7cpDcr4961QQDx4Udaj8HDklGm0XjsR h6JE84+EI45pqZnZSmfSFJhaaqm5ZZisHwi8WTVMVw15lYKDy9XmFgD9WE6Ju1YrNTPjHJNBgoc9 FIMQpEvEG+DvIphVDAF+p9VVmPS7EP+Jdupz1f08UOMjuZCRXM/kGzhhGN2DfIr/0N8q4iVxl1gr YcPqjQzhSxTMxEr6IOxrYLYfJ/q05sPcJ16gVsmlXIEU+tGDWGzXM2LRy4q46oH6juRdIO8rIFtw mLNmzZIO5O7GB+2QqDv9CWhIjuNDDyxAd9wdCbCICW2CBIl5MQFayju5RCSM6AOxBp2JVpm8WchO BWz4RL3+8KLX7o1F5/K6ddEF69Nt9656lwMQqOrPFXFZ/e+ymtr+GbBqA1KHDlC9o96mqIoSHOWt cJoVMZiQfB8e4ruqi8x3K4TdW3GKMgITqqJR1qA7vX53QLuinE1AX1r8Z8h/2g7/nei/rvrbKLmH +I3h/AOWqxlXJefkkEH0OiXY+Qg8nznJZb8Pex33h/DNOQbEALmPFdGH//c6rYq4wH8GnVbRfPdY XJfOELbF0tV2mQSptTTcjUmWgnWQBP4y+E2K65T0gw5QAzBTj/2P8NjXTwN8Iiq5mlOdFtoP9XRB T6cGFD455rFng2p7FxcCUEdjWKojEZGA5ezoVb8tSk6tA+N1pLce/jjqjbuiRARBhUcSIakGnRcO TTi/HPU9AHww7LlIqOH12BsjJ8fdq7GoVkVnSK8vuhMyx/2h+NAdIa8Pjo8N2w7w9AdAfTDCjUlF HAzUs1PXLzr6xbHG7b1Fj7EHD5MxyJEojSdFh3P14bzcaPcXkHWQk6JFdb2olR/9ZTQRpSFAA1nL jXmdjh6aOAWbIQOGWnpa8gbUH5yJbVuCRFv8VFw6l2Dj6nRoWD/ovdBGyWYRqJp4T6OuGjX8gUkj 4gxQ0e01y2Z95kQey8fVzjAdioZKg49HDVK+nUn96wsHZgETwetocjvFsFooZrYk2lAmvNfExW32 otPK0diMdnofJowHQmkVASCuO5Y05LYf0rrizYmJjcKdCS/vTzkagXjqbEOCgIKBZmow7g2uu5lg AoUIXJ1UMVEiwU1w6EIuJ1j7SzEUd/5yK1NZG7eKtGkML2GkCspWYB0aIHrjF42M0B0ftIfXguC8 FSB3545bA/dwIK66gGznqnaQU4/z/phID0Y7Z4GAXM0yjIE174Hw9VgNXLDpzcyWTr10Vvec4/LT 613Uo84RwtAHvxpfDtXXLpi4Hxv/b4Lmvzv/e+U4dZ3/nb6qv/o7//uBH2ZBmv81/07/TPoXPT/5 i/x58LUK+v5IFphHci7j4GatkLwNbm4FoAffVz7kEHjmOzlLTPoHR2Zs0T0DtA80GPxGBFqG4QbR 9hMyuwti1ToB1NdhAoybhTdriATnSId4O7vFWQQFjyGRUNMHOnU78h9oQ8hTI+AuDCfBHbzv9Eb/ EL0Pne6Q6CSBpmY0ZlrehtvlHBOnSG6W/swADSIB6ARg7jGlwCwGXkaPn+4cRmIgvp9OACmLpR8B 8kgvRPY+jObigKcdYEIDUzFt4QB45X/hM+JUJAGO4VFX4RzTOuWmENgUxNom/iN5ex/o8/qRpJ14 AMz91uRdZ++n4OqakK1gfs1J/KdsWg/jjlqIp0wwqw2en8J/SpPo/3EAVgn/gZflz+CpPouae/K/ kD/D0FHRUEGq76kEHlcwcJwM/rEqMBsTzc88dyevFTD4ySTw6XLz5bObTd1pp2zuHlmZO5UZHk3f xe8MAyh4DMzgHL7BSA7g3+5kKEpVfIZRell+ZmrfBeO2AVxEDwwP6PeSRdDbgLqDQWQu7FCAyg2Q u6Pl3GxAtv/O1wvy9TTPHlzD0BkMDSb7k/hPT2bv/LeZz+L/4ux9cF3+UVk40lgVwtxsqGvyccgW Pn1Put38Yem2SQueTLILKgiFOfhOXszZp06M8hm1yisxht8PATc4NcON/PB1K82a8iUAHnQ55/pU /utybjYq15s5uohPqVrnEsRPgAXqxd7ks1mYGlrZpbNvOR21rYYLYOxhRH7c3VcnSOEXZ8CU3Zrx 3RKCSm9VdvyJtshQzSugmgH66bvpYsi6N2l3VdL+fcu9P7T6MYEwlRmCUFiUYQgk/TkQZPhBadDH 0p9D8X5PVQdWtic55drVINzE21ORuNwmEH9BABhvl+DhwFqpeDAA3wzBA/o8L1uaCHmJqU9QfpqV FeR7vmxVXMDYKVeoYsafUbSgYsxO1aL5B6sWBev/v1Ut/v78WZ/V5i8v/zxe/3FOYbBh3f+fYP3n 9PTV3/WfH/FpH/6ZH2VzwXiPe2mWcH5xCQHJ4J0YXvYG40wEOfTa7713Xc6289nFyOv0JsLNxJYq sLRLKqrMIm4htZ5KrDVRgm8VViDHsUsr95hOorn3Z8kW7D2lSQTPzn/wIVijI+A0KRaloCZrFVoZ rOfyK87Ah6Ufw6Rw/ZuMQipKxHxnfedHAeSp98FcLh9qqlIwv0Mc5mnJAKtVymNWlH+pUPbIcQ9n +hEWhCDPVceA9flDpHjTcWKNXOYIBpg/De/gXzGTUeIHak2N6y4JEjWSfozluoCqGXb5hCoc29hA W977D7HANHznFACMD8EHwloUF42wpmYWqPlcSNNLxroG80FxtwNx2Jvitglvm9yG0RudXxd1W9if sVzKzW24RnCi6ZxUT183q82mU9cABt6VJ7wVsG4kVcmpDdk1SJHyd9UVQIbV8ynt8F+QpcfVtR/X /Gjjayh9GBNXSbgR7slZ9cS8DhcLmSTiPJDLOUQ3nhCvm/XGib5AWSdRON/Svb5VtlHFQ3/2xb+R yNp4O41CrCsBlkoo4vyNsK6sCqqsKt7r/oMaXtYIudoswwcOflYhiHGRfH5Zh/drLFyxSDEgEiAM jpm3yE1V24xBE2GMVPEeQGD5NwmFhHNTuRCYD4jjzbQpz6laIEZkMo4R5Zm/8acwKUENwmpytnpb y1KEUYrjLTKNy6CAD5dqLc1AhcR6KQo0vI2xZCLBPiRi+pDQPlzJBFwAaAU0N7kVAGwpUcObpwLs RxLEsS+mQRJjLSVUxcyVP7sFXqjqttTURow2XGdMabLy56bC2OsPL0djD6zi4HLcfSMwuMsVxFOk d0pAWh50NZcpMEdqT+VOpRoy1SYiXt67A8rEmiHN50HC9fo8EYHnPsXLtEmwXsgokthvQMhHulKG EwjUy5lcLrFF5eUyVEVXeJAJSSC1LYA0bpd+VCEA8SzyE9C4GA4n6c4BLAZVdY3x0juDHABaCW++ XasC1mmzCofUTBRm09o+bQrWs+V2LuMccW0NE6WrIfAWDJgqdoORh1QhehAorDZ50JjpmXl9LA0+ phLEfqJiCrkda52ieX45ViZ3QWgrwdUI9RlqkwB4A7kANtdNVWGPpvevdqf3afpV0XTIF/XnSiKp QdxhuqohAp/ACdFNEWmEXoWJovp48znQ+D5MV5EQPaAhxHcgu3oVZnZ6r+00icDHPboU/L0SO3M4 zB+VxSUyLtGQ+BbG0wd4vDKPNrgNm2ANC5yThtUJwLcUASIk7oI4tCAB8F+3IViwtQ3KfQrUVQGo /i6oAaRxCtQAIxs0qFloWA1OQLb8iAAgh/XikTfQfBnJZBvhfb3YxHI7D6sRLAlXNlYyuUfDVSdB dTSM3uB8lIPBAUcib2AVNbQh50CGMD4BPWdDbgBrQJjLqs85niTJHgOjOE7J9QIqY/KnZ9qceHc/ whusa30bFGJohSVYQsc4SlhvCcpkV1D2yVqnUDo0gG+SjgKWUp2LP+b+FQ8V41UHGMMwLCAhh0BW LZ89km2+cLGmP18ssOWbbvm+EAOzZYBXuwQMlqOrmvl4cwrzH8wkc6+qPIwdzPF9HwWGtqmlqJdC b7N9zq5ZdM7ejwkTbSyCCBww3feBYcKIVREmuFljARh7fzB0rDq1ckXfi4kYolb4isvU3bG1VH7d gAUD71fahPe4NyDn1D+flsEtfUTDqpCCYzXU9TbY3iPh2qD4OMoeoz9bpGjBWTAhqPAVHcYjzBiy 2kAD1eoJZMRpu4tVQqHW09kbtAyXqEFOKgjOHMi5Qj0jl06E5GDAX2DkytUtpGLGfZByaepjuEOw KO6hbEZTSWUvdM3NbAysIEo1kMVEwIqIQ4rBCJSEwCi3pWGDn0ao97fhUhbaG4Lymj4KCX1SRga3 TFM/unYF2In056wqU/bTNJmjO8YOjybXMV5uqynAYQ069X7MCUigJEam1HVrm6PHxLzYi3ey4k4c h/xBxW/0bM2QX2dykzDC9kqKJpP7YEatDStsz9BEZg6ikFUIVx8OlnCdUwUQIMQ8gSJYujdGrDG/ VPYQaLMMZgGott10wRJi4wEALkmo07tmwOMBJRRC5iCTsIYcWdqnAHuxAg2DaUQrFARAD5gOeeci JXkFQzRMSHFC/yMuA6Fko9lTsoj9FBiR4MXvNlJHIuKqeJIcA8XQaKxijoooXbXsuJ14M43j7WIB lEBDkYlMeSZGptrVgipAyMmM5FMgrkmoWiBAAu6CcBtzWTlO8/cOBWemDzPXOJcRsdDu6rUMOdck 0kSh+HYSMcIbSoSn7QjeFiszptzlFALmL+w0Hbot1lJa0P7Dhqfg6pgosHPJzJbPnggp1m2AJKXe EW0PTcYFmx+LU7zLBIge1QusU+ozzIMVKnKIrTR6qeYCirqOrp+30laSEmmYyVL9VbgFOVhQjcIC dx8AaiwoEt1H/6PpAAHaWo7YCjmKSj3oeVAqmOYAmXLZNXdSCbdeFyW7e8rgxZ0zZeS31j7qAgi1 ZzlP62BpcchignazusS0AjsSoO1SsopBxYKEGkTT/VyCfarCVZ52Cm4Ndybx+phxbEq67EDM0Z1G GChwBpjmmpso4AgJVRQOWUgvU1TSfUAQpDxxONoslXv2g7AFpoYyy3n3c38iKGPVeqEjSoBqq4gO RTG2VDNxlwM0gPCsaiFpMIKDvH1OhyEW5RYyFhKkjzq+jnTJ6ta1d1DYRzfbFTvmnzFc6+umDm78 8LFDRl1hIeZoidAikqhOpeqby/svLdLUcYAhBDjE6fYG3LR/QwdRaS8a9rTdS8lavaabV8ijIwhK B01CoN36CYF6LUrAvhsw6xCelFVQjbkv7qh602AlEIU4Aag9INi5hCUwbRGFK+0sLQ0DcnwwMttT xk5v7NDGTS6AmuZCq0UwPW2c5Sl7QcUV08K3oBa+iDoQL5hiVA4Ob7AriSoSuzmMNpssuLzjCv0c MMzY6L22k0Eo3HZJlc8OgK0PG9UipTBU3Dq1t1LvnNOMu2mztFO9xwRYc0px0LChZ7vHfiNsU0qy /sMUfxb+DIt4OC6NI6WIKPHjL0BNFdNZP14JjKVgW8Zw0o7GGZjEG042fNYqzRBWNXCxqWxCQAe6 ALPH3tV7bmzlzhzVQpg2Jur6/J78sSJuIU2AoJDDBRUV5vIhf5lQwsAhN5fOWV1TnZ9bVXbWe1Vp R+whwoGI7lpbcR/vNh5YmxkzKshjZyOYGQg2gPrrmETYNkcKmXVapbpZhlMKa/FEgECXw0rdSMkl vTXLJEsncDbD0Aqc13J5qEIKKCYQ0pDgZQxR0/wlCdKffbXEYnl13RpdXo97g65uwPEg2qFfy+jW ZQzeE9agtMADOfIhZgsDoSpiGJfiqUVLiz0Gw29UpkP9ApYkya/+DLuTQ5b/AfK2joenxJ68JUhk r2UKemxB12qhyjF0QUSrcISyLEaTz66oXYxr4vfW7/ylBa++qwMv7bUrtajVrgMZ2Yi/VeFrj7rH 8JULX2DgEP5Ju+BGE5xKv6Shke9tgEsb81olx+p8Q+gqj1ZHOxcl9BW1d92aOCvvtqMxdweTXDPa 8QFzv3dQcYYd96TmnFTcnlM3UoA93SThFASlpIT9PFHr/lIT+EMr7Mj4uTswrSWq+0o1TQwmZgB/ tdqjX9PCKtVqYjWb6EnvLseXGKqlrRG9c12jmf8L3b8pPOR+/+Jho5vXugL0NNG9C6QWEOvi8p0D 0Z/nca8sNs0cIQf1xD4uvYBgudeyj3nBsoQYi5o36NRwUm0AhO4DnF6rzCv71FOstiRQrCqqN6fU w5YV+OcQZh6JQU7PMFnGMiO5ELdKKX5BEymKAbYx994NdMueOWcL+5oBD/PYwEcPL4tLJKFen847 SRc00xke4t+a0O+BG+VsI53DrDzJsDLDSCfXM+QSZx+VSmy+KyGQSu+tUwGZL6suPNODx6J5eXBc Ojt/XaubDptRd3w9GlhtM4VGDQvzaNRQoQqNWt82airFREtHFk20tJ0DnzKbbbkzPLR+j+G4abUI G/XjH2dodvt2vZLz7TbmD5iTAaQQJS/DvF3DghwAw4KdqIaDGQOCwrzXhrS0cOkXA6t9d6+JsK0A KgD+/L1ZJqrR9xP+7matie5r01Ut2Jx/AGO5Fwh8axddy7k4desXwcgdy76QXXmRHoQVNmcRqgPM /pAKmnd4xAH+1wXITnj8nxd4pi4hU3c1CHlweVA5h13rFTLs36JD6ge2LesH0zu6A6Qy11Z5tfq+ 7vfvdpJIykrWVT4hyQVS2/3lYKeNWDsyW0eMBUQ1yHdNfguR9Q9P8YejZSOX89iuYKKFwnAIqW3u PkziBuaq/W8jNWD9DbHJq7yaP9uyZLmERMvblkdBZj1NkdEwJumQ3eyOZdKXRBANtfTFhN3S/LRN I4E6Kw6MgBssT4jpi7O6eZsPjpTta9RTY9i9uOpmN3n9xCYktK+/bZMMtXDLHYq9GxdTzMguV9xV tZ4vaTCnX0tNT2wtVtVuU9LiZICywfg2WFBhBJRgRXVkHQjGNifaHCZZXhHfcXjkYUs3/SgMA6by Dv/cMksqje7wDy10vweqxEET/5SMpqLmlLNM0KajAWNH7l426DC4kA1W/DU4ajzGTlA5EJ0qBDsc jmUAtvfJSvZALT6Qt+9A7lMHIuHFaY8eqPGcA1UH6kgAsLEX4K5U7pE63d2QNhmi+MW2wMWqSyIT cttygXpty8UT8m2SFNjD+tXlds0Okwqk9kZGSDNxD5OsmVI+SzDGDohGKQmSq6yU1zmFyLxZIAqE NOdI/OtD/N4q1zJJe4GBY0xOnjAtnBGcPCICxrS0XwCO6iX+VKeXR47OpPETdNVuFJ7KJ0xJpK/i neqRVK0cWeyZVO+VoWrBt10FZ0Te44/mcofbNSkWx5QleJ8ZQ2q9svi2M8EW96P3bErwywtcZqbs 6vCOFj+BdWsP1q19WJ89C+uWxtpTWJ8VYG3hnFFVvZXyVLwP3lI9LlevnzJtLEHdjJSkum9LCt0I xCvsulCeRc5FhJ2MRWLjGrEp8gvPEpDM++d7EqKTu9+XZL2JW3+UCQzsEY+S9SlV7VNc51sl8hmy 9whBHvNEfIb9vijrjVz3GQR5xCNloLGwE0EaTxGExL3oya5nnQdfsTFGGd3SJlSXhmt549N/NECn ABgn3YGjWv5fe28CJ0lZ3o+jomKZRPEIigHLBdmZnemeruobUdJz7NJz9A7TM7uzIGBPT81uuz3d Q3fPzg6S4MEfIt4aiWdIYtSYX/AIRlGii/EjagwSNVETDzQYicYjQIzsT2D+7/M871lV3dM7e5Gf U35cdqur3vet93ju5/vUV3rV/uSJTBjG1oPqQzyoLqbDTC9DnU0vIGBv1PSCKWU+jUZFIHap1qho RK7dGLZljFTwyH+wUm/sBz+S3hpGuAo+LCzu/TbkHugZ5EYOXL89CzmkjOtsRJcykqh9ypHYJUdq mem4iqHaK/uSrWLKC7CFPJoOCC6fnw8YEiP68fQBIemrN0VhGSq0qr7ALf7tm+vSTDczLntjHw92 amluaB9K2HbjkJ9ACzCkzWPrMTrKH20PcWe2iESTXmwRwMCFNEhnIF/foAqgpgyWStlrts9hocRI 9GRQroCZB8KdmKxbmolKk8IHVCigcNwbaR+69//4WR1PnpUgdYysBDClx9hKUNhdxKHLf7oEwKDd QlMt/IBxjuGWpFnFsQzxJsyM1MkwIc2gPE9X+CqrdaYkL/LzQ7H7KhnFhKZjouYo56M5OajcKEoA o2q+RuPszihKmIrLafoAvD8of8DP6htFF4T4Wx+0uo1rdEmf60fQGTh+Htv/Dcz6YppZpT5Pvne/ SjZKE8EOZnTnVNTm/0wB7gv7bYD9jclpPjFtzBEmADZc+JhUQhcsxnDlBtlIR+MBQTVF3znGlm/M lDem6SNNEWVKulamDaO9sejTbAhTMCcBiTfi8KmLIJjLlKYptdGBSWcIiCJT2IxCjVRiKt9P8gel yPTp0tlQD19FXEI+2lDhpVlf9ERkLqOuEHbJiNjgrCavEC7Hbh+ihhRfjIeK4cbv1AakGSAEG3Yk YRI99yRpPFHnTobdOyfos3KbS2+Szqx4tIHkVEEp59fNg36sOM4Q8Z1BcqDwTXViDNO4W7rhOT6f jX+7OoZPXvPc6MqD6Z6nLNUg8GjQWnNELKcTv1nHGz8ovfGSmw76vPGDnbzxgwFv/GDQGz+4njd+ EJtaxxvPH+WCrOY1H5zQfnTVj4PKYT7YowCyOVVYJetCe08+t6aOclwJuTSDcIe1qHNeh3Nex8d5 HdNKM+rIXzn7dST7dcgVmscVHZUWYrnsZLJtw41JtIXwKc6Xzc+Ih5kmAzyxPT9szwtD+WD8yNmc Hi8xGM7wJuTdEG7Hfwro2iHcya+lxYPcyQQtEcd9o+xpOL9LU6CGxT4UWVTBSAfOnEwXrk/7xiZE YhWoUNCiTdGsRi6AL7sXVSYjWZQf3WPPOAaRcdABPGaMY1BjH8MnQWGBxTxmCoviEBBki/sBIM39 dv313ZYdwrmCnOTIwrmM8UFmX+jwwv2xYRPj9gb56TZG8HFqz7cvGZnayRZ9V764kx3tbdu2alQI TvdsbnDn1HTIOPNauHmD/UXOp0YKieRovhuNRrs8ekCR6GFl+Xd6/RFU4pHCrGzSQJTVBsEmTY1h CnHsgMkN4PGhaC6U5xMUlYK3kr4ArzgxIpczEsfXWXm5gcZzLdNSfkZRcUvgpj1wLLexkY8SvcYx sH/B39l/ANhSJ/yjGM0WpmOKW/mCcA6MajeV+gdiFD7D/ghySGUjzutqYB6+Nk9qnroLLIutyigY eYtCUVU/+xkYdAe7UVcT8e02ah38SNxM/A3Zmdvm0AzT5PC5E/MYcXqDHJCH5pBlDmR+KY/VF7gG oVmM+aYKW7TCrLFq7MFenxaIvwwRy4RbR6JVRoS/SRyCrhiqX93rhqECGT0KfuroFkk/Q2V8k3NR +JufdWrZ6mBdJK2v35YxhGTw43GEj4YYwmMabXWCdCxcouPAJqUiFSTu6zPJIb/fvqt4xTadG0T9 GHJAZ4MskP6FYZU8lLFTcKUZ1DioAiB1ZsTfGtTeGtTegulk/Q2w18XmApqN5Ep3lrYN5ATbftsY zqGQGM4hqaxKQxTMPLuNm9cJmXc97HPIF/Zp+EP9DxLrAC6hntcchPDxQ4FYUW0eQIEuuN1rIEDI QsmkcxTRoQjDEWIYW1f1KOqqh5ZOUp+TcAAhKsivoXHM0HH09JLjZDM7CYTcPWpjmWjkCI1lG6Hx R6sIDft5xNFyhe5YAlCAQX78w7iCy85TgC2whZwcdpLRVLcq0v9ztkCnrSHQDbMCKsd3UAkDYP5B +TnDjk9PxPaUND0cx39L1OlJEZ+4r95ocVoGUFbgEz6gV7AoYeUPABPpNU10jl/BE0vaRn1zpBIA XszheCelDdWmuNCZlCVT6UtMYUIk9VCtCT82RGGCZqegc1c07Rxx02540zj/Pdg46Suz2I/53nDc HGKOaa8aejJXQYEaFnb38mfCk6GOlXqmLcqG1LJ1raAR46hsyNyZCGpnJl6yINgbVc9oOLnuM7ok eJcMCp0nEC8Al6ytCiechHnikJrYD4AoVKGupHRyNvslplO9XC41EZaruqol/WogLuzVA+GRXBwS gjykGM8ucYFgLZnkwbOaUcAh1BUenovJ2pgrDMdfH60IDznOSuQlNgce7zumGa65I5A/shtNScN5 EgJHYruTWT8pzceic65tBHPmtIhtDqfLREhBlWGvVQ6y3QO1hdgiNzzPblUAX7MHAXe46MqesbPZ 5/dSpBJGt+ELSrLlRXkAAWiZUs69g155meqZ1gJVfjQIAk7+eSWEuIp+K07JcUtCZ+YszOqhcorm cjcSqm9sOwDdcI1mbPI0yRBSETNg/B5xRJw/t4RpP+PQikCgUWCYYksUkKnk47Bq7NnAmjlxNqRw YtwCAA84Pmzi2ZRGELqCHZ7lBkJZ9SzXdLbai4uhGVmDVl5XBDH3w8RFnAAXy3Vyhfnm0TeJGgPz eemMHcj9WFMB8VFEjSIIf1xQcApoBlmpnaCbaPdN+vKiPTLRRtyls+Ii9NBwR+s/4TsseCs+XE4M tAtzV8TXkdJ5UFLCJ6WbyRLGbknFgkFJIuYGcxMo9EmV8DL66xDmryZLj+wP6gYq7L5tLHxOVzIy 68y6GoXPisP3SxvzgZ+2YnhNrnN4DZLVDUcLUxFsM+C0E3JjkNUTiphCzwR+jqyTYEYQnUIYhDo7 MCVuVYLjF/VwYDRC6SIwOg3GikPrzgs8K87je41ydQpaR0JFl+yCt9Kq1yJTpaV9Tb1wLIWDqgJd JMYQ6J45Dzkd2ppdB3tqfUhUqW44+ycQhBLTQuCvMipYi4M1xza/WistimJ9iA9Ds+kDRe+XOHM0 uzyRAjEK5VccZQj1UUdQ0/PdCjVD4y6qbImEm8omYwlnONa1LJLcqCyC+z7c+JEfBr0sPzzo73Cc i9yimFX7MKBjZNY4GrgOf/fj00djvYbpOt8ujOzITed3jdj5wuTM9BHar/2xu7MOEVvllgWDBGyG bWCSsHuGYcP2MP2ul/Mw5NQ+7yhHJYLqc6pOnZr+4npYBGCDEDurkBNGbk3ERONxIacVIoM5hbhX YGJIsVz/nOIT3F4JE05tuKbuj+Z8aQsJsUMX4S2iz8VA5S0ADSqCRcHV1EkM3RToClPeksfoTDtK 1wzYKPgOHDffRwwv72Ar0qpHMMK+2fIQSrZSQ5RKUS6VfGzlQKBwniZqHD6+lw8RE42I2AMJCdZm MsNqQCt3egMPyYLPbZ+g4FH6Ua+tPRhw+UtmjEebUYBuiE08CKISsPLj+unMWcqxXbFnBLlWCvf6 QNdo6OdgcXaM52k4j/o8hQ70PkdmFE2I5TJUxCG1T23iWFgsnJAAyWIIpppZmlVYDV/8ZTtz+4ZY DPQSymC6W3rEJg8kcgEGSAD1Q8AT6gDZ+paQHpcmvj7kez0E4vyEo4ccFabFhpYH5zeIkGNoRnCa jm3Ils7S1d2jDeTaXuEg4SRb8pLITRNRW8sDsP3Zr8Af8djoztcCcTAgcwVN4JmEYAlzz0kIOvX9 iqFoqEI67kJozJWmzQc0MEMaCouYzRtDEtjlge1daZrbm74U1zIQVtAeysJIKSYlNtlRyxaSCmk2 7Iz5xxXUtnW0hsB0dNCmE7HwMKXpkMMe2N5DgUi6IC4ChYVZvo8X9h2RqxjoqsY9yWSzCE4u7whi yfJaT6T8k31AywUS6r6+XFLZByCOVJsdltYU/eC8GmfRn9XTxgjfQaJug7NmCAlIioIa/LqZNvpu o793x1qw8qIOLSVqVgSVewRJZfooLCWBwC7C3q16tb1M7QScZ0aXYzb31hPIrHya53mq5MtmZbEC plLOeFi3rQYGAJBLBo4HAdBjQz0j/F+MJego8kbtA6iCQ6Xa0YwVBe7IsUcJahabWkbg9ZzDGzzq wtBHquOugyCnh3Pxzh41QHKwWcLZ5DCg3S6iYYVCP6AKBcofTPgkKzkvvSAHOWarsCxlS0QC1ku/ Chw3wEE0QnpyMgSJG1vHDH4kN4RAq1UFFFq8QFdj1YYY7BLGJfG9F8ii3upslTeQGm2NqRvo7ttq qxuI4bj1cnFD1KUtQE3nfjbkfgyxYrMdw5Rx2VOSN2SrWym8dVC17aRFb4K9NQGrEhyZxqgz5qD8 Kn+v9lDE15avnAbi4MOUEQHo52VMBFIx5YNqcJ8FzSsR7zVDpsZ6zSiC0KlxsjA3TCfTYDRjONKo b6QE3w+45AihLQH7FZw4iD/txxaBO9oAx7oYnQtncgxHFxiLOQI1MipKoYW1qXaxFEB+sB8NEdD+ WB/2ALdiysPbJTggtogVfIEYjBSgnXEx0JFauQ7yH2Nv4QVKfNDwktJjFQVBv3myvaThmIlEhJ99 N5ocOacAkYqNQaP9TaoGA4OyhQFXqwWjkMHJy1D1FlqRhQrm3cvSLZ4szrFS4YlQ/iKQgffmqqXa /o1F8hr0vZ9R5x0dLaPs957Y+dkNqz656Ry0McDoSz9QHfaHC3/E4Y8E/JGEP1LwRxr+yMAf2a0D huQKsy5lV5+GkJ/VqK2WaWDI5MFc81m8gyBQ2l0kKzzmAomKL7l7HMx5yrzlA6TBX/W8bSYTzZK9 XKOCpuQ8cpCQgsRRq2GITQlduBAIsLdSoyMH60618/BR3QKlaWJ4RsYdnzNtNi/pRCzqoD+dfT84 12OOmV4AzGkWEwFjUXgqr7cCU2bcwe9DQRL2yVhvUK0LqAcIiw8uhzrP9wMWugDB7X6b2mxeCP3B dfDz+FFGI0aRQsggwIB1lxGT87lNd3rnTns8N7VjhIeh5ZNQyTsZdeCv+nQEzb3m6o2Lk6mfS/hQ WYQlYCmE+DHYyk4ocqPQKGEJYdfrxlTRhJh1nB12sKRG5MaMZ9XqAN8MQezTmqWtE+TB4lvQAcVJ J5AjVO2QIwksErkrFTSfOE3CQkwDIq88cGlzRuVY4EDnwX6Ny+lX8Y6Ef1B1+2DmopZXryG+cBAV M9ti2Mie12sPDAuK39nd50h/X0r6+1a86gERpaE8fdQYr3bid/cFitdQHRBeNoTXc8EAZW70wtZU DZgo4iMJPxwvWILvIKCgqHoEyC9gVeXoMLwZXyWUYO0FrRiRa/glRXWuMlAAUXdQr9WsTfq8lLSp OgdP8dQKcYSg34h6bBjPUpYFzphAJ+ub0Zix+jI2ZFSO1qp3iNeQd0uwHD4TXNSWdWJ4KJYaJdYt LDWbdE4qrXbu2eUmFh5sLrFBwEJ55X21CiMWrIcD9eoBoPUgo7It5WGxDri7rDBKQbS3F2AatteX GxUoacUE/CYPN4NNgVhVCyUs1LsgykRLYBaxadmeXmLKARkuqGbeNqiIgr4oUe6pAiWYAFKS9Ye1 6Uok1BR2X+6qJrnuSVWUaN6gXyLvqjJRYbe/hog9kRcFVMqNerMJYSQ0OKyNhwcAK3OVlpYoAC6k 7DFITzV7CHYk1VdqQrNmoSpeNyVDz/K6i/xhXgeVnyVRlqkKGH14GFpUxXgnzb8/CqofOmNzOVea C6u1k4SYAPRzw3NYr5GKMDfFwRKFKbXqUkfn126XZixo//Fxb08AB0n2UyaOMxxXmQQ8Vnk4Ej8Z 2EyzxynX2RewIEWa+gosO0SpVxZWw3frtKiVKSsYgxrD0VvZUZkrlfevlCAySdZOAoXeKBPPi+Sx rhYqtXlJHtfFCgsF7giGX3WwujoBOA8SLMitbDTfNmKNCzFhzccDVm8SAAqDRvPQAiMNGKzAth6i M4G3GiSNVIL/e1D8O2Dwlo7TEFw48VBXeROLlSZhRAtvpKyvpvkhUCtAewHnxbpN3qFJwADvjgbW CfQitwtdgK1+PnsoX2R3hy4aGbZ35cZnRor2zu0wJnAFFnZHIkzWdbXclS7iGST2mCPvODYvISBv JSAOzngogcEACe2EF1JAKYyHUhDQXoC6gSIQvpBhdzLGQxlonN3vsxMdYlGaIZ6rdiDr4tu1CERQ Fl0Ded9nIm8Xf9hhlxSZgNni51UUbhLSDpohKPwQpcV9peqCLBAKNetJnOA+KLITQzY/I7hAnNiO ht/lrUKiL95fyPS5QjDkFXWxWU4MAN6QQk5JABDyYtAeIctNkYjIwWaUoEJD348ihNegYPBg0KIP x9mMVwXnheZZyml5MGD7nNZ+EgkWg2gU1cEN3G0iwtd3l8ce6h0Omh0Otu9w0OhwMNBhH9vbmA/h +0Xed7kTR9eBQ2eHe3joKPXDmdFaDDpQh3tkH7QnUyHOL5HHw/4AHgJFy6oQ1EJ1Sg/CkoKRwb8j YG8OBwx6U0NsA4ClcBhkCHYS+7TkWf8jPWxsfSRtiCd9cEUUL0kMj0bDsw7azlBaO53adDuwesN6 uPOw49KtPvagnp3jiNsJV78tn05p+TZ80qH5bfhqBNuFv7vmKriO/iDmL/EHnYA3TbxoLE8DKtQ1 PV7f3JzSoSmY0oh/2nlsDFMUmRKC+J5zoE4gJWl4e5dBLOXVhCnvEMzZ7uXANih2VcEerjZ9JmSe SVbI8JvTeDwKiNAgp1M7pNOOyMyQ8id3c6JBDWZuOoDP4LRd5oxOhHWLhz4OONfqB9f4oc8JpSXB YYrQZfrZDf6s6EfIl9iyN/kAjHda21pDvoy+nO5Tx64dkc03pL5zKO57S28xYfNYa3pL5YwNIU0D kgOUagi+Zihh/CrBuQhyAx+DOWGNUGx3AONqqKfg9vnTTTDwQiJ0QQ487EI4yF6jAYA6Na6x15cA deKAF+VqLwq2WnVIM8VkuYalc9FlBYVhNaG6Z5FxJa78c9Nor6jVqyWeTJvjtA24dySpBNgit43N oTmn+/G0Q9JHNoSK2iRFTItyI25SKzgiGvMHyU1bQ23yX7lwNjI7NFIsQmTp1M4ZJigUdtgjU1M7 p7b2b89EIRNTLp0mlPGbIVmwgVy/QHRDGFaKDj0mU/p8JzWAz0lomd0gajrh4QN+hJVucvhQe9to xD/xpXyRA26b3BHz8QsRsjKEcEgwf4CqDqQRKCjbzli1FysoiwAArojxk8ELvqKcxwuAwk97QtIB AOkZe+W2Eenm4cbxms2LTRcGUDKQ3JKbUuBRVV+WPYuiGzZY4rpgZbG0l4AGICSlKWu/ootTNKsw 1JjQ4y1APIuqZwzz1y/1yhlu8hMyo1YltV0Z5HwRzyY43TCBkFsS+cqoRxwsLwxyHCqvpRZax/gr qk6Pf5mILomWlurNCuY/9mCRU0qG7NUjLpq66bZpz/LV4R9EmRdakXFs1T//rO0ClhvHuRao3TNt G5Hg8CVRLBfYPY2DLyBfUlT0+dSUGqKyK1Pl4VVeVVYUdyf0EawfzAem715pDAQhD8ZJo2Lbkuqd ixWU5mlMGFw/lUST/lXuCKgpYedHIhCFjZDmoOh59iAUwoDS21tgRrbrNs1p8RlbaBMuRZm4nKVj cVG9vL/mrdrn2aOMfexjOghrYZLtb6bHVEXIfKO5pR/eisfi/VDud199ee8+bKrmVdDe1/AE9j8y Khhci6xzyNQiC9q8DJeYQGVfFLUHS5Uq6xo2MjsObEBONpM5OnvdLJro9mzcRGc87w7YMxRXKlLC RUSeqtxsBqrMqJ4nwCw3sXPY7hnr12CrCzM2FH4BuGtxR1g0JmSiA+r7Wv5AOzMBPCOaGZvxvTQG DbO7fazPcNehVn+aSCY7QRUfwAYj+2RUcThkg/g3UBk0DaHpCII+1T+B0U+IoKVz17E/Al+B5ZiY DdgdOcvHo4zc/Xx7JM8am2KE4qJc0S7snLYHR0YKdr6Qn87nxvOXjAxvHVDWUnvrzin0K9s7GSPb uR0Gwr2W0hZbhC/KF3axt4dtNOrEdbdlZwyNofrSKqN/7HjuYUe9vI8O9J6e/cD6Z3vc/ZQsW8G/ 97bXzWIy4begtKM9UPoIm9k2FtFEX3a/r+DKnwIh6abyWuKJ9ECBOZcGUs8o2p6gtrRdMPo9jNer FAIsdtsAr52wZDCSqdnWZ0lEwizzbXYPnD/21Xt6QLfrlc+wf/X5A0XZ3USf/vIeumH8LHRE/ki+ KJ4ruMajbnAUkeAoTIk8dDl4/jUkyygdYA9qyrAo2i2XbvUVNCVjj0sPgvAf0Z926emCeRt1LGi8 D940dSu4HTFuD9LTLj6twRC7/HbEuD3jIFEa6xubUR3OwLM4ifhLQdME8XFHIKDMuKg+mYpihB7A NGF8QLPdzNKOzcHL08ZtsYSD8Nq0q/3EZ0loc8Zrhb44/RQR7wWScOjR7uRYMgZ0I8dqrBblkxMi x5KEJHQ7v5SqC7SGkNpRQKUUUr+QykViXXDWJOEwERam7viIsLgoRy7C+lbof7MIe1wkyZAdvClJ bkqSv+aSJBKbR6kkqYtYNKutuiASciL3iFQbAvLpmSVRa9YQclD0CHkuEnyOC1+zhtSlZCtgvSgp zPJbrrSsdZZkTdFpFkWnWV10mkXRSUgG6rZLT/plp1mXHieJwJSdZlF2mvXLTrMoO836ZadZlJ1m /bLTLMpOs8dXdhKSUyQgOXFZX65XwFiuhH75DJeJ9GeUMKW31OdrqRB4KCLbOs66BCpMe2Bnzx6V wuSEKUxCU/KL6aQmaZL60UmR28OkSAMAhcmHQUFS47SoPvEMo5JW6MueX5aI08WVUuOqVqO0jGkV 5frykvQsY90mDFtjNHdffZ6czFw2gjYxrSZSX4hw4xcW325UuEWLpCPwB/Q0PRCBWpUyIa0OXwTe dMiKrEbt0SgMs7jM2hURWmQxX5IlypggWVxqQI/AcJGzZ2B3Z9K9UZJaeEQaQaW5IoKRcLMM8Tlc dOZS88o+xt/D5WZsaRAa8clwQfkNIy80Yc0n0QswL08GGMwiMys1m8uLFIiI0Z3ry90UKbfKGhZC 4YRMngCPDn4HhlBWV20MY2H7mG0GjE/gIYZqkoWcDPtGhVAinjnZODHYDTkbO4gQpRBpQnBpiF/Y bmOctjE6FpvQhewa6T16lKou23Yn9fPgvRiNc7f498SsmP4JQhrjO0WAQ8hoXPYK7G6I5WAicBNC wWuEo6cL2/pqY3MhMEGzYWs/S4s/204OX6kbUrgQwcU+BZwLjhOHmwPjfUvzpSURdAxIZVqmI0WA SNfcUqm8v7TXw6LmSoTicU8zuP14GKwMD+4g/B6t9KvFJ05iumzUSTjJrJtKxpOZbDobd+MZzUt9 3GVl/gHg+yr60q2DVT40tZSIJKJDwjyW6/R3qBcKQUE1ir5twUZfrLTIZ8SEL3DzY8pIuQyuVPYA JizhuQviJHGs2t3yn0r6VrdQklbCAwlvWPKwoNUw4iK3YmSGwC1ujmNwgS9TxZH5Oaoxcs2yFRxg 74QioBkRi7F+aNqfGzENP+Uhmse4PQOoaDPo9txZtHumfUUU8ecC4s0CWAD8LLJYQvit/HL81HGj 8GPYDPA5QLifQrAmlmrWz8iVt1cIMMKgwIlVs4UUHEgCEAJHUCMezG5kDWJ1Yp5ggHwt4kIGe3k/ U5o1sBxonVESTky9eTOYjDcC/VA8ODbHKMJiHdMry/to+y5QqLinIe6pLgymIZrGhmTz2AMgJ9Y8 2NTArMACQDscgMnQ+wWpUKuimQoeELZBOIoibIZ9y03eFo7Pg8QJxHlnjVUr7BDBnLG/o2RCQNKY Io4NQjh5xCWLQTeNpMIiyykpAZ+C5A0RjC4rxfP+eEg5f6sfWgwJKMd2iKVrgPB0nuEkiOyywJGe wHqk+ULM7pkABblfBaBOgIAPeLwTKrhTvi5vyfDVCdcnWwPlEcvG95vcVYYKyKOBx/mxN6rRcdmb Pe+QiDoupFTxBGYAEjGdYNRIoj+0b4EC6kiIDwXRUNqBIV6SkNtiPBemuoQYeq59EOYAREGSSANq w/RUrgCRvIRTFWKn9Z+gkLkiFzDXMoADkIcmgJIBUzjh0PdNhE+jK6eRJiBsGsUsZsJm0TVmkb6n TUk8iWu57rTu6WZaOWRG2LTqGtmRTiv3dpGsDTNsTmvyCKe1/e7sVROy3rTyzemPFNWnNRMLaqA4 SymBEaLiI1Fa1LTHPOmO+d4guocv8ove6BJSI3hIfQ4JWIDxSEuDaQzlRJ3Jxf8666ciw+2o8Ibt o47PsDk+JpruIbQ5cT8v7wNFH5f3R4X4IRJ3UXwZz2vmVJ+xVJ0MbhkDcWvMELfyaB0bg2ZHjZJz ebSR5dG8JXtkt135fN58Ho1k8HMfBY+1Q7/VJL+8T/ITVq+ZPkO0M+xeBfM3Yd1jA/X/4Kof+grG T654x/W947rqB/OdaWHsM6163LYWNOCBqYtNBmXtBo2E8ue+Qm+oXZAecOl9NN1NO8J0Nx3yGLVD D0rv6LQTNKnRW11TCT+x7JpKrE/SN8nE8SUTAtFZJxMhSWPBg0g0IY9ttKUJBf3oy+dH29KEcQVz HXrMjUM+Axt6prczFQknaCZJGGtHEsbak4SxdiRh7NiQhLHOJGFsPZIw1h1JGDsuJGFdEbmpyYye OPaUnAKPE/K2rGJBNSsqYMMnmywZjQ0BE2RLJmUKkyIJmVo0Q6g4qkeXcrGUdGDRDNlZm9LC2gQc uPnO0Q1krDFCcPng9BBckcUuzHUVoY5jZjXZEylUWNlZtZzxeg0zbKBiKxuiBkDDKWoV2oSo0WpV qss8g72+1BR5z/Me+K7njx2N1cEYCw7iCIcokbjeWLhCBAdAFou35FGWAfvQAl+HOQ/BeWEm964i m+AB1LgCLb5SYPjnCjV/TyXbypfBkg+tLRg6P1kPNL1cS/XmVn7WNhP6CfKgTfkMLUdBZHmil9jl qamu+HdvCKayw2v++H8UekFMaRc+AJoADAg3JGkPD5nPJmRNDSN1sbzPW/Rs53xdpWtW4Ahop5Qb X5abADixggFBwoGC96qrMvoGJ5otIz/Rck7BHc8mg71Rn5/vB5s+u4H+FTYLGPDjokW5ucia65cI CAW0dmFgNEclKKBRhGiUZmSMyZSidhzBkeys4AQsiowkbiu4faPC45zvG91WcPRsI/MpToPlcwjQ GO64k4mjxoy7nWdcbnI6tDyLbF5NPIdiWBYFgzpPvLPuxBPpwskXd/0T7yjMFw3JU81nu4mP+1fI nNLRPpxUPvE4nfngxIunxMSL53DiO5gsAhMf1yYecyPlnJeqdcRiK+0FqIymBgrOZo7b4JtaVR1I jWV/eozOom10HiRcwcv6SbKFCg/ceq+RlxUg2bAGFAFnHACjuiQj8002GDAQUnIAOk8p7X+lbvcw MiPwNxo298YhQIbsrFdZWwoo9xQcPbwmGHHTkTCNUQvq34QE75MMC36J0C8K+iVA2YJB5agz19eZ Xwz196WPxvWPxtVHY+a/c/sQ36lj5k4dhYZGIbzXcQwJdtSVP/AAyTaHIClPCzUNNcgNkYwtxTZG TXjoNFsr+JdxDNQz4hCIp/AQhBuYePox98OMQb9tv81t921u529L+b7t2H6XP/lZ9Zum7+Ifxb/u WH5YWn2Yc3wWzW+yo5fCKVcCMgsPgkhYAcAafsQNIkZGWHAdLrdIbuwhX3MNaJjhS1xYaHotQhdg Yii6KfeWwKsRYeIQQOHY+0qN+ZVSQ+Z4NmkYSPZIEuOkD+km5zvSO4Q0ziRtyHUMChaVVkqDOOmL nFVsxlxdfBwETWV8GsN1BRTkbVBQccDW9LFRrklr5GAcH4fix/A8qIkouGoogXt6xgVjGutzfPfF go5xLuTPLz0S/DJEBgrBL/OVPxZ1Zu2cKH/MbzbZ1PvwzCa06vFDKn5EQZqtB2eWFHBmjLRxPLOF ykLL84jP+EHNugc0K6JjEHQg2pEqeBg8n02eR9sfhnWm4Zz1i+ASET2sMM4w0EEDOpMYZ+vim4l4 Fj+6WcgYoagH98Tq8SAgNYH/EmWmzHpR0i1DY2lfxqkujrsUtCFMY6nBJrwKHQ+2K9+EhZu2QXmS iD3H/qJXbxJ4DT5tm+2sHO0jGp/YRdEO9Z4onvxIaz4dh2JPJxYUi8CwTjjcFVKLYwR3xYe5kSJR XaNjtcFzM6JoFMhTGxAns4jO8BHiNx2PMt3DR13Pav0iUoVZictk3gYgibj/9gS2N7HbjPsMryqF IJ9MifAAl5ZDFMnlDLi+sUJTLMorDkksgAmqfyQ/R9mc80iktZOgN+SIhuQy6os8LBfZqINEuANI /GXy3wZqQk3k4bwXzSZEuNxRloWC+Y+EAb7SPO02xFA1X2oH+DeIDmE2K8pDDfMKUPBfo5q2NsOu nGH2kBvy0MwgoErBb1qDgceo2yGBUNOp25GLqUEkvCHWEJ3jEI/hXA2TaAiEnBcjZyykvFz1sQNj RDmaCP/n6UPhZYa6KITlx6wIKU0RqFKJJPgoqlQqae9kV6k8fnKeBK6l+LFQ8NrugWvnxIA2JNj5 gWtZOznMqiw1GUvo98szCNxpTLApb6k1olA7vk5UrkwgeVdqCqkWIFe2FXb3xdtW8xRyJZZYq2xA ltxQGdB2n9VlYVAhXsbZCpb4vy93j1DA1HoUuiblDtgrJeFTqTL1UoHzirGSRRocC6KQOlVYlR9e OlCvzDclZWmSZZkwb6HPRYg39w4uQXj2AY8mmgPhiTQCWEbkkREfdBFY/GgnbZZB3bBIfDQVT9vJ wJsVT+2wiqezx73i6dEJq0eNuHtk+oSvVLT/V0NMDf6OguoQvSyEHp+k1UkvOV6C+eBRCOZiPgIF SMOnJOwRmhUxH3J23E0Z3pDhVZXXEMlcF3D1rdVO0o/rK9JO0h/ikv6QEtDbDW79bo+kDq0h9ev8 Xxf+dZGjK9k/bAI12X+wzfaE34Z4nbjjVyD3iPSC7TOFoWkMpaAqrvliu+K4vDbu8KQqgcT1AQFJ TWlsDtDQfFGrhGhjzAndgnQLX+GipgeCVROT33hiXBQKSrgps2e9WBHlLGYIwRjFFFxAHDJEvlAi XwMPJhspF139kiuIarVydXme6xJiQ9RA6IU4F4qWKdnVylwDo2yoTDC0ZQzK3sveYQSjjrUdSgdK lSq4XvtBklKBG7xyAUqQR1tCeHsaxBxefSvdz5bLBURrVxYMczO9GjR+MQYckDLW0oQBxF4Q7RZz jCWLLYiVlIoDxZhZGUkAEgD/L4pQONYGf4S2zwtlK5Blxca4Td6AdwDsmABRuyjcrHbmNJMh2Tsy Kn8jyzhRR6gOKpDIM2CwMdTtSvwWKkH9TLpvqcokxRFGTob7Sb7WNbLy8iISCvb+S+tzxFcnZ1Bf BZmdwqEg4GoINSte0wZZ7VKjAq563qn4DrlTSAhfXPTm4bEqJXe2Kq1lofRi96JVmh8jh5Z1sbdR WtzQJqPmQGg8ApuCwBA9CeuDPfPlobIuiIvjHfTKWM0EaQUF9ICfsuxB2QOm4DWbpb3eCVgdHN86 y1Oc3jmpTfApJ/NaYrJPsxWdr5ePXx9MF0kx/neKbTvpJP7XhvLq9F87lUjGU+w/6XgsnnTcBFO+ HDeWSp9ix47fkNS1DAmPtn3KS+caq6Vaq+1zK/s8r3oiBnRiL7uLa7IyzfaIpd/K2RdV9u6L8NAm UI1I7opMSnWKtA7SMSYpudsKbx/kCIGKZBfpHGI56gbkYmLfbd5Uly8HvNPzhVwxZ+fAzDjlUXUU ewgiLBvrdmKPLjPS4MZ5Xnmn54frjGFgRicES5QblTkCIVun/RIMa5h9BW5GO5+31v90YLJTO4dn kH+u/3REuywLrKa0voJOkQ1XpOPXF0DexDhrReObMmkcVt8qoULstSpliM+Q8iLBfghzLcQIN5gA xySrStUPzM3L14iB8L7LCAjS1GAYjI4Q4JsC1Xg99SbGKTRICrQYBV6EMOw2AyKbVw1gtzQjQKtO 9XhRf2C3m2wNoaVKgzppSJg4YTwUo6X8Ww66Sxm7aNuLyMYt/ijVD2U6d2URamWVEC0aCne1muer 5XaEUZvPipx7ssBSgrFhl6iSZYKvDliLjYUvl5YwQpCthIaNrk4wEys9Xj6MfX0wuNNsjXPtqBqw 227AIKwLKYC1zIN2ANUOQ7FLNTLE+k9tY5m4OWC6L9bZ9IrodBhapcFBQwANQ8Zm44fvg9B7sym+ hSPpND7LKESDDXzCXB7eDPWB4GtNDQMEAWrU/tMUR5BqLG2bI5iPz3or6sWBE6EGWtEcgivU2XeV yNJs1xvzGNxvARZO1dPGBcWgDzARCK22ujW3DrbiSlPWvljmtWNnaq1K1WKPsc1bXe23yVCM1TDB yE21nw4yGQ3N0OzcH8AYGTiiV1JYrr2Xrd4SlMhTce+Yoc56g2irOt+FbOi+Ta5PkiIXdcw99xip YN8PxhE4nGz2wBOAFS15tsKUGvO++grEIfeDJKfAB2AIDbaLrCUob4rva4kLOP8dBkTiZaPCTjVt uabFZVVblgkU7oNyXablE/Wq7vWYXghrX58nclJdrdUXAUIRBEELczga3vwybOnyKtUmZA+yL4AK dGwiMU8APgrhFLwGDh+LHkTqCwtIQSplGD2OS0s7kLlsZY/RC/bTIBNovaq9sFwrc/wDniHCDhmw HaB/W5bAyF+O7PdWt9jlxupSC+j70r5VZcQkuCSmuyzTEV1crvGZNI6y5Z9SQfPAObeC+6lJQDCi Rj2sdhXBCjDXpFmvHoCtwtR0iw2hMo9h5Iy8k+oeoDx4etgd9o4/wjxKPIsIrJ6zwp00Ph6COTXg eatIgaLFszMsvqMXcEmN7A7YiruFxYISOPDggDov6jYy1sPUBiYIJO1Sy2orVOD+RXo7z3Y8JZ5o i4qlGqEAN2u9CbwIMCAYw6k34B9VPloCoxAfUF9QWFEibFLC8AhuLeicJXQUQLpYaqGohiI/+D/B kkI91NhcC98mHYgSI77zBMTgYadWx6/A1AGxDfX2wBRSKy3OVfaiF9Vi+3YhAn0S5Nc8+5UNcW+F 0o0WCNwScS9kwhYbR6lJpSXBqLKCBL5cLTWb+tL5VjgSdn4IV0kRHwvxnIEDT1YEQ8e34T7SOjh0 2IagC/NsnwJuindwqVQT5T4nKyDcAU/XGJ1E5NAPHMHwLC6Vmg3RooY1S25FNtdoXi61MB+AsxT/ IdRZEJv4ygJxCfBPUv2UOpieYdNaHFFUm4x+EdeHNlKcmZJhDiX/eqmKACWc7GDhSkv7wpUGBOMS NAueMXIwlOsNNsoWEBbel9idMEOi1gCCl9AcoeXNoPlqcLLsIEpMSmbQv6ZplfY2PI/e0wknBhY3 FfSMPacVgDF4uJA0aPtxItOoQMJdVYrGOEmw/UA2MRO8hAEBd49kjiXGpyqLXoTx+WXGbnENV/VF 5GHO2DBCmgVlNEs+zb5vGX0MyETYuPjX8FI2pvglxoySTEOcbQtFgRq4kOE75sHnVV9ivwI1axC6 rPTw6zh9flmWBi7OjKjHi4ZdGhtFcvASr0gVgFHAHKAXnC17Ga1pQIkVMw8wb425Rzm8He+sSeyc nVR2NpepqjDIMhiTUcGqVRR5omgzEFlaJki8qbGtXSlDs9sbBKZG2U1Nz+KTx7tgXBY4OORlLs+1 qkEia88t76WjDUQIoLSApliSOOOm4nI5cS7Vvy37QmLYxHMKUdjY9WKlibWJclQTAw5EP8+6EYym H9C/ylG2qCt6pG/TUy2DvYvzkUrDgrrbS6icss0Jm5htqH10Bw4ioLbNVzQiYW4oPjCsNYuhz3AW YKU0Ka2ukRujJu68FjK9AIIPcQiLyw1s/tXGYIsVmGdqgc+qSfBF/Tm2er5KvJQ2Fe2sSufGd+yc yk9fNFHEqpbTI0MXFfIXz4wUO70UaXdZRECAZMERjpBvWWMDkkIwQYLPrzQmmixrsmKtgMSImbhz fP+DdkqSMtZ0pt0pJH8mlKSSQHRVd8tUP9pSrl/PjCVnDAx74QQfVIC5ErzEi/pNl1arKCpiZqzB +ygCqtyCeBMor8xl0n4R+cJUFHTcQKowJr5iYBAIIlGLh9+UavxwMEYHeFyw/Bp+mGAA0JEqOF0r N7D0HAQXCS+reFT5/kpM7zkIlBjDyfpVGqOKdQKOiRQU+ISlImCQnAJXwwmV9BA5X81b0caCpFSu A34Km6N99N1XLpfmocWyjImCT5ehR/LbzfgbzUsP6g7pfn4oNsFoJf3PcSBxf2OiIrm3YvFgpwon xGW23NVVHrom952cl0AT9eo8m8RmHQDYLG2NQODzA70JO7g5WbJ2eqveQglMFyNhOLI+eBWyd0zl AA6JT7fW2Tg75HlYrkycvTYZHYwixRiNTkQZ62iseBX8jqFSrTRf0leMfS0KT5Qa27DkmlEslVg3 TZLDkXhwfsi4NFmBE8czNIHPEEWzfLqWHCwIu2Qk0nVhIY4SrZTqXdTaDnIIrROoHESZV/mZBYmB TT25JUVUIuOAKu0dfq7PgQynD4i2He1TexGAU+qNea+h71OJOLoYKl1YemoJn+HmVljw6mpEm19w uXeaTeA7LauMGiFAEHIEBUpWAauYpMLjXgv/ez47jzZU/o3YPQm7eWWj1aOHI2hXLIzur8LL/K1A mrB6cX1zqm0nbGcg0f5ByOPrgT9W7dDh+a/9KkykRTm+59uIafpCP7sJa21/n2P8e93B9R3h4Lqb E+iYXe7+vnjwJzekhRL88UL2nx4YEnxvrw1xO/gj/FPeFz93+Pr9xr98P6qn+hxi0yC7aPGq+l5l x8axB0g5zAsgRl4O1UdjLTFDBuEm6g+I1evTbsG1BI3w5i2emQ9WDEl4OKYGmpcw+gFAQHCngNF6 maKB5VnsgpTh4bM3cPj4+en60C3ZGL3Ud8Qvhl+hhzZ4dTou/MLxlOxeMbRSF6dhv/bXkCMrdnSY cBjanLlZ3Y7nTI4XT8XckYx2f9ijc23Gut5IS3Aa57rrfH/HL1qiMeD3wMx1/KL92hjgFIe2Z2/o i5yuPkh0zMnHko98aOeNERBGPCRt0P1tflVX968JHw/XpYPhpyggWKgFCZsvyVuhuM6U+QmqOLDu epMgH2TQRL/V0fEDxGmETEv0nTUurAWgbCzSO+VncImE6BJWlq0sVJjoDxIntwyQpEnWXBFJ1c7e LIy//p81OYdHXYk5JmuRUGJIC6svKIuKDYp/hXQnAOeBKPtmix5EvUO3vSiNoTQHpiKItiXqbfcY qEKG/YnU0F72/kKpAhouIAUxCbYlaqmr0eN6wheg8sYleZTzyIU232mJUc/UbeZgxEBlipJDNJdZ lZtrgelgiApnWaVF5CEQrEjfBePgW8/SJlkMU3OPlXyJDP22TIPg5j8t7NLCYOMyRV1aGEmgJToY 7YAuILrw5kWhCH+1J2myssKLNNk927dP90qNtGIeiP21+krNJ9ljvvjScgMszsowLDqVRSbQpbOv 4weQOxJwDFiHeK7Ytuqp2eM7d9g1GhM6hIJA2xSMrW9C2qVdM0h1uRY5ymvCGaiPR6pbcn/jOGzb HLRlnH1eb8OnFQivC/kQwGYFtkMRVCXcs2Q3Yr8zgsCjqEI90mE1INgHLKF8tkz2IiZ4hbiIaE9p LclsP99WtNVWpBoDPt3VH5MgNiDi7eh6cbuQctIKQ2Spri+nnfiVD43nZ+Npw+diIffUVQod22rH jkgOaSfHhUhFB+GfL4T/IEZA6WA3cvx6soO8whQL9R2UNtZZ0ekoJoVoYeuoYJ2lOHEpwc+xdiOB 6iBNsE5xD/MBiMiRCmNYqzpmQhf9lug/YhHRtki7uYkZiMvczE5ogNwC6c9X415fABQjccCqL8ls CvLiCXNyCRzW1Wp7UhkCA2H5zmu/7f/iXE23D5VadJzBseBJ/xmZhTXhqdJUZihCkFaGLq5fKUpA Z759fIYKMBCsTlVn0Sxk/nYtQUuEWOKPFzEVSWEBRK0TnCtRXo0AqBSa0sh4Jh2Wkn/iupHIQtW/ ST5pymTfBTAuWTrJWgJnVd1cO3OxopTSqnwSJcvHB1WCdZ2s83IUC5j9WOEeGeQ9yCQ7MlI+tyU/ uzXSOWRPFvXURKtesKvOPLudqyBfKE5PUZxdEXwT9kxxxM4VmeZe3FOcHpko2tMjxenQV9t6Cnxu g+mVunSmhUc0oLNfSMr8hFWaBjeVQTsYqsMOc2DL+mLiMHSltbqELaUSlGgBFUNTMQv+3uvL4k6k QARtVZrNEj4rqs+jGO8bjOLLZM2Iu/DKukMKHCoUk7gdXHsNoE25DK+MnOwbItBJ2zbDAw7R5Q3R WdKlZUaWzdc9ymnhYeo0U9pE9bbvUa0ZRQhy11bUDMH0y08Ur1CpSW/uZD4hxdglgXFrGHs62lkx vpGM1tAp1UBF6rlQYRMoZU9Lyf/kua/xKAWRnk5hAzXpoYO6KbbD94EYLJP05r1qhUzAPOdHgQvZ bqI/mRaqBjmhyBQFC9rwmj4XiJOM9ceYasJnXUrHOD+L3mK9sUpABcuURk1nnydmqGQNWFcLffaz E5OMVGtF3RCvUmh32ZjNpHvESMCtsCs3G3GcgXQmKb9S+MKJgHP6LvxS89DavCf+McdTskXQh0Jx mpWipkz4QSMcemhV2RsVXIGAsCK4wkclYDKE9xptltg/FiObhTEgTQ/lKxjbIlYd9x1OqcVPF/Sp BXKI6USALe67Rd48v1w2eyvzTWMpxSakG7tzN74xs2+E6m788KggFmH9xESzFmsE9GtfPITPfIr5 Ig1vqVoqizf9B07ho/p+cVXcRr0GdAfVBqskDbKM00FemNiWODZ8DeMh2VRhsgshKYefKctByzCX sKA5ih5qEPVDML0WzHyTs7at5cWlrdDKTCE/KwHy+gF3etXCgzynlHdqypPhNbzWIHTDsaMJRU94 /tHdxJ3x8yiakQ3JmxfmbB5uGmxOZNRgoA4PY0GbDKGCCEMK+JjryNVgbmp6E6hJo+bICArRK6Ef kj2kH7EM4DvBjl06IFC4VSFlaIZOLzsVeLKoCtOchxiEbEgQfgVLDoxLoI3xYDWYZIyThd+RyGjB LWweGowaCEAVqG3tj5hR8dBN2AQhQkZ7+WJiZnw6H1F5XJO5obHcjhF/A91JGabA0Z1BErwDIgzf x+M0adNib2mR0MrktFwThaZ8Mf8kFuKPqlgYUAt/Xj5tU8SHXqQwQI5JyHFiIEJXclgfS7Do7FLY uYq3FZGG283v8T2gJGhuCrEorUvYZheNGCywe7U1Bc55cJcb+DiGCI5NBlgpXUgZm2Dqa3XEvcSq 4NUKQvSy+QHnKg/mZiOzfC0srbIzWwFtBONZt1MJRpIJ7ZUSVRsDNBKIUKvxbFwgI8g/2NcQ6o3p bcdw1jKBJ7Bzs1xBwHx+lsFCiY7oZaC7pb0liJe1eMRzcN7RqCbbonJ0BDWqEM+pMCt+I9hxKTBS yzacGIc07V42khY//EDfGl7EAyBjIBELPBbV7BCGasHTmGAiSCKSCyzYDVFFZQnVwUvl+Q/IMiQV ooHHUgYeqcv3YjyOYNc4P7LrqHwMsyZy8wA0wYMiqmxbAZmREkIs6ia5pAYzxNac6spZVhFyQNQS GvqrLhUzBQ80J3/b2CntZmTQ9JX+/Y/nT5BkJLeSEM8zBk+hpyX/axaPPp1fbpCWCzK1YJemJwB2 mPAEoOWRxoFj5CGdFtHpamW/R6HjLdDhjPA6HBV2CuZ8WoeBIyaIYdeLsa2rC0w4g7/IVOWNXFdT W8dkXLwtQmbQSl4UJ+3IiwAqizQA3KpdjmticqJotDWBbRU31tbIxfCXotciW4LCFJN4XKUa6Yzr t5UbHrYBLBWKhU4CNMbkuuNo2xaAVGBbkaNvC+EpoIVtMEtH19Zwfhe1NUDjKh5dWy5v66jHhdn+ EiKCYyGo1eyxY/YF2AP704HAjQ5t5Qvbp1RbMrGBi1EL3BZPlY544k1NR6PT29o+MW0jY2NqAVBu 9RgQbS46dvmNiP+mldHlIHQBZDfCdMPBSv2bvbq1ae6JWb4ncB2Hj3zy9XWc1ffEUe17gAshe+/E ZOgyddnWi48J/RoQzHIahTYIQ+qYkiflZynnccXZP0jTmsJ4waBIlyGrk2ZohXUM5NXJAHOuW/OG ZK6YKYOgarOCcaL8Q1Bl80dD6y9Abibsb18HKMUAQwMbU7XSbKkQyha2rHDnuE+YPWjB+ampZJv5 CulhAjGhUhMMdZljIChJkLoPWrRxAnj0MUwl48KMiMx7kDfQlJbwgA3PCk+1DenSDtjxlNHT6thn 4EXVyYR8PBBA0ANgkMJiiZajXq6WD6u3IAELtQef4tZDgEv+BijWFO3nElMbQh6Xm1xQBhgg34yI Mh3kQxfVnigG3rAm2mHWRPl2IEw/xBIpSkrRrqjUeBYIW1YYl9SJ8YEtiMS5hTW0RdaO2tJvea0y 9aQ8rviyAPhssn3r6ZYb+izRI1N52CTSJrbAmIGrH/KZUO0Ktr+qW0V6KXpv5SHxr6mGBUpZflwG tzUhfPfOqeGepiR1ABWVyxfYHfnEkRAsJdub9KbIxFn6Ww87/ABPBX9E2F+7i6rUr5TSDMwfRg4u MSGK7QLWiSpr4OhdxGHqewj+kH3zBN+vbJ9ysE0YJ0dqErlSEAyihTUSBCo3ZxGkE68hBq+z9y1U 1WoRvQ1406ZKWwJxVTzCtXyRNEf7WBU6s/xlvY0zRrqXnq+PmIkenwneNlYeB7rRYU6pBJpI6Jee McAPa9a18Huzez4NIFqIk7iB2At9HEz1rnp+JC38KKBF2Wy2n/3fN2f0fTBUqXeBsmpp6KTghUHq SM/KT5JQo/xntj1Eq5o8X2laZl10JT2ZB1FkqMyH0kkkpdqJlIawkgANllny3kHIRVUuWP1N9K2Q n7KElr1VH+GFSCoISudOT/b5rsAUdukJo3YA2m7ITAAT4itoQvvK0gYAmi6eB+XHFio1WNLZq8oz 7PvouVVr0WtIozoWWdgNK0s6spxg+KdmmN/NTeVatT62JFy3BlPmcsNTc2WgK6OjQ6IPiVIWvMQH cTiLy304r4SXjFU6DCIubNSMiuPWbGGaJhQh5F8Ao8TEZMgrEJjIHAmDOymGUeNUOZkG7gNspABu Mhd7uMVY8UYA4EJYWMSFJWBYQoalAi/Dg5agM02sjRoCuwxCWGFY7EPM70N5yu+FMMIBo4iw2EUg lvTBKbw3cm5ZPazTAQD57iM5kJFXNi/q28TA58FiA02B2Un4Vfkm5nKJpd5S3YS+xyUUxNm0e5ST n9tGwSVsDMKPnU3ozyJ2UpdU6eDASozrW2octpRIkqdpDomODAmLVNGQE7v5sbK4W5Czi+08w8dr tAnDbAmrMUY+MmELRWPaijp5ntgdcS3CAYediOyU7yD0akzQxtZgws3NRNuIm5ktkF4DYpfMn4Qj iGc5cAIRtBwPIKeezXYwSF1dE7N9jrXu9GAWKX4VcVUBos5lCsJd58qTUHEpbsQPXq6qMXqNrU3D Aaa56WR/lu+EG9F/dXSCyplCjRu5ekywCBwtG9HeZZ6MehFYjsFD2uTOIgiKahklcCgnGzY0t+Jy niUr4gHCJmIazXtzy3sZJy8R7gBXKYCi+08xx7Isei2UvqEFNFZJW4Vg3Uni2yjN7sXKr41e4dpr UoeQAV5r1cELClG4jPyjouCBH4yjBRF31M8d+/RdRFvZR0L3vEOLSlwlOAAmm/YDGgwdXyTl/h2n T8epq+/FDDN01BNpk9AQNDHE8RWNbUsHya7CN4b5jSSMSJYIkszqEsUj9Mvh8DlOmV3xu06Krd8Q bURUYZSxGeupzHN3w0pdeVlh38qNi5xwoVQGxyj70ZIoLiSvtEpNAGURPnxZThu+h594zu0XVFI4 ganPW5hPiptdhjjU5vAINAiDVKPTXpntVjbc6VxxTOCe03xjAvaBSlWJsO3MTAYkAsdTNdV9q1Rt UQaj5s7kEW3yKIrodi4FQ5VHEamGDs0ZQYlLOqgWDkr4VPd7PF+Uyc9Nj9diQAJB2l5JARjZe6v1 OUrsXESWOkLSntxtqJjyXG2bY2ao5WM91uqmomxRizB9WprpFnTxblknr5uuYm5icnzE3jkzPTkT HqBlXKbWFwaSBruyxuHbhVsZprik4g4wiEgEZ1halqrOw7gEhURM+zY4DMIxr0eK9JiuUbl9qbQe nK8eI/aBn1Xt0PcKFAXypTU9sd2hS7a/PWBuPBBCfCx635ms5MmQC96uL0KNP65jp5QgTxhTv5tS BOCDs/TBCU7SBl1FD91f4n2HBEroQzM747dXqbeWIEqQB7Gf/Ep0OiBCG/z7bGuznZJDPw8E9bEt gffGR2aRqTESt2tkCnzxloVQ3Q4mPCI+N1yJWDaFN4bphptIpmNMEZ8emcoJ5xFaEdLmPTfkXjzk XiLkXjLkXirkXpruWRBcw+FfxZWOOslEnKPgFqMcxoDoCZxUvpA8FTx0IdhncSoIc2tOLVNiL1en LAZx4PGoRUDFqWQ8mcmms3E3nkmk3FQiHs/E3XQ2GXMzmYSTTTupbDybjaeTTiyZcWPZdCKbSLAX 47F0xkklYik3k3JjmWyW/ScTiycybjKecB0nHUuls1bGdRKZWCaVdOJuhr2TSiXSsSzrKpGKZZNJ aNKNO2n2TjKbiGUcN5PIOOzlBPSfcGJuOuawx5OswVgymcym2Iuum01ksslENh6LZ5xsyrIu3Skg Y+YFAKQ0IjiOmj6auss6kq6Rwq781M7CxEhhOjduT41cPJOfGoF/dYKk6GC8CiFjAIdQwxUKBSyU eVfEfVYalRZA8RLjUcEdOigP+zbplsVYnoUWr+qZ51KaiK3UcPssgZ1DEBBLgIqIoF25QjGP4EMU 7hMC44eEg5sUpY0mEHupjI0dAjT9Ia6WEeIqwA2RastP5KGTImZDUHFhdQWzMkQ+Wiv7PJzg9W28 0my7LyRsF360ME7XsMT4nsBIXiLUDR4vjFR4sVKri3y0iFqyCqKk0NxL8YVGzvgBWu2jVq6lBWEQ 0WdU0mAQ0NFCfbkhgtV4bJry25xvz07kZvstRA/v59jTXBAh4GQOyuf5nSXtEaUtWA/KsUHgEglW ysFf0OohAN0NPEJVlZtpZAppwbZn0E/Bp0JHfvYOlhYpjclr8k9Vg0TrCUQRepa0x7QAgRS3lbyl Q077hwX6jg6AFRqeDMdHxtpRwIqOPCVgrGT5nzr/QtmJZeW4070izxyIAORZQlRRCUSI2aB4S8yn ljhh+XE+5+sqOLrMpMcKgrgy8teoV2FA4NvlkrYy+Jbr1eXFmsU3Fa9tIONfYU6Kev/c2QAWz2qp tj+sLSObFfYLR/8OCCC6dCTkYT5dfCCWGgjOkSahcZUgHHOLbx5YqxIa88SyYJQmXxtcZEjxVMFg RF141iz4bNDuKtI4BLu12n0EW9sZ4WTz5+aKMXFwwta+hsgu1eS2eU9I6RZUbmZEaQu1s0UXwPRg VxGtxbcFYwUVNDRQUiNGWdWXWpXFylWBLBhhRG0hEC4Cd+kZewiOht8goWZBwIZDuFQVNkMpAGOR FjVEYcrqZL6CeE6/3k+mq6TWuZpAtIrDtywv6gPVJ92fiSg6qElrND3BZgMsE8M7KQ9XlQizCOwe jlFpuVVflJlf4j0iyn5cLCKSwAUIdhH0VEtEnvE1IaFewNDC8/pYlJdHclZDkBYserW+zNN/Ka2Y lluwDzipMoOMPm2+Mh/8HEt+DprC2fS1pJkWY9bIiV1B2l0Tfn7aoASVSzZqDmkDWWXqa0R2UrVZ x9Y590PsTnR40t40nufKtdUsLXgiRRZBN5p1+ZHz0baaoIlnhmmzikZj9oCC0fRLPU1h5uK42w2M 8gfvv5pK/qTm2JR46eLaSd4KtigcQd0OQoGuLyR24fvkcIfqmqlVyvWmnYiq/NKh7dMgpLFbxmv2 bESFrwztLNpOlNQm9Rr8B+62f4935wa7c/XuhodsN5ZUbe8qsv6Y0L5D3RLz42JSSWKH8fLQKhi9 mPIANwo7i5HiiCFob58uJOULwyNDkB9iU34IDfKgvSuqT9N2NkJ2p/07uyaKbMYMry/8LkaZ0N4t 7sjb+ak8ez4yjDcSw7YT0afEthf8MwIOv4P2UEQ4r3GMceMd/ozo0olm5Ou5JZDpJkplO5+n7wGx 34zcmyhG+Ksq9Xdwwp4csgdspnul+TPDbCXWe62YsxOZ1PCsO5BCFXZ7w/MGi8OwN6LJKH7Cglse 2Fsu25cOLDcbA3OV2gD75Mts2cb0KtMgpvctwzBd+9J5CDlcyucj8Xj8Mq1FtkkjGDQKrnWYtE5K 2XRuckQIKRAUBxH7ufHxXGfo/Y7nioACS5R7J1Ssij+whHtgz7ezWNZkPyNSDhTVmFuq9FtMhyvN eVUMK1+uoRkNSqUUh/J5Lp+QfIQiK2ZjSF4pPP1iAZrskTJRWmCWjCyJIaEcS1h6Va+2l/0DItDB IJyJ6dIdxKnz9Doo7LpP5MAY/TXBMwwbShqdtY8P9GSJnqCqYWhXkHFYblSW9IwoSjupi/ipJQ4G 3S5UW2oOagakyTKgiGl5dj6QfZV01zGNk3KzKMmPu0TMhpSBOQixrsny4nF3I5+gMss3/BFD3J0j 8OCMdlCajQgQ6CbPtgoN5pFKBDpEUJ90tM+Lr/d5AUX4UbdCiY18wqN7heLa5yXh83a2swjiOyVZ GYLpRT1G9mev1lIKJ4pyxhiHkpqKRwgdlXnAIClT/Hgd1XF6ALLKwWJpbUS8WYdCo1OlSpjJekUX 6b6r++1+JFYyQTykpguEjTBRHd1qVE0mG4PthsoRwf6W5rku3lpdqpN5YQCMPnX0eEvEf0umLLP1 2wf1HQAdAezvmGhM2I1MmhWyP3WwtAQsRoSaKC3TEpqT8SKm1qiHgIsSLg6GIfJ4nUaFNDkCYsV8 XQi3ohzH0AmyeyTEEQnoXGKWqBJMykPDnCVsGQo6GKYHdslkFRFggXF4BPMsDpPsTtwgjAMM6yLr I30cqAIiM6jhUXMyRFVfSfb7TGHn9u35oXxuHIJSLCiVg5lZK5BGtMD2RwWh8/AEwWCiJ7e0V1cX QiMMLB58oZOITk426hEnGYvCzWPYB9T/SiTa1f+y48kU1v9KO8lkPOXE2WMJ9r/N+l8n4nrua047 5TXf+GH6lMf99J13N7916+mff/iSR555cP8Lyl+bfeiOO7/9qrsuvqp2z/DTfxX96TmRr/z2c149 nd/2+ge+sZLb89vP/8Lpd/3zxZ98xwvuedOnLnnzKfmrP/3Nx7/4vLfcmnn31Q+fPpx5/Jc/+7Sz dtyW/JPpJ+Vef9pjIh/41fClV//ZW/ZP/MHU7c+a/PLbHjjtH3dc+7Nbz3rO4q4/vLjwha8cqt9/ fU/kptfd9tzP3Xfr657wN/sffnLuyxe++H+u+cSLbvv0g//1xy/+5Qc/+MUvPmn1ax/69s+vWju3 fvflb/nSiw7/zS/vs8555ffuf/rhN7389q2//O7Du97+J7uyn3/njic+fepr9q23/uz33nXTGc/d 9sh/PPMpD1zw7QdOu+ucF77h/gs+ef+p9z58xRd+8Tmv/pXRwcEbtn/wqnuf+91Dn7Be9fkz3vj2 pz7ri/fs+9uDz3/7b719yy1bvnzGjqedOXfTa66fu/KNT7vujfn/Tr79H847WH3Tb9zz0XNHXnvh Fz+emf2dO2Lb/u/T7v3KZeM3XPyHnx9yX711zyOTT3ncth+41Rtf9ITfeo97SfY5/3TX/zzjuvp/ fe+B0d95/8Envi/a84Yn3tPz9md85q+f+4a7v739lis/8eOBn73nR39578K7vv+Bt7TO78unPvef N+ZvrFlfXPj3lbk3Oo+//Jbbv/WWG9956DPX3fHFPzp467/+yQ+ir7vjrqsPP/85d039zt8+Zf6N 7/Ueemb9od+b+q3t933tHPd3fv7SN//+1qW7P1v/+a6vH76r8ODP//SUOx/8UPK035wau/fiU85a +9aHv/G5az75prVvvn3yd9+99uXP3nn+2n1fOHMt93/Oe+jjf3X6WvqVD3/uob2fvOfQbZe9efmh tU9HDg9c+r0L9zQO3XHNZ17ymWsitx546P2v/dg/rF3wpT++fu3iz68tP/KC3xg4XL/9ytoXrynl em5au+OeQ/c9WL/gkee8gf566MfOW9//kS1LT3c//Wen/cdjHr5s5CWv/eq7ex/7npe+/wY7e82u 0w+WR17+uF2n/svw6bf+1H3lMy+9/4qzTl176ytfvxb519ccvmLil2c89MTPTbz1qf0P1n/zlh++ 4UvXPPWCa5/5yD1jZ86d8Y2+wb9iw5p9zw2T5zzy5KW5v44/8rh//9hZj3z2eQ8899ofnLX2nx/7 waHvPnft8Tc9cMXU5NT0Q0/87n2HfvNlztpZczc9eNfbD3ztn7c+8qqZG9yb1r5+z6FfPFh/4SOX vkH+9UNXVf+98penPfaJ113ygdOf9OXB/7z59A//3zMfc8P3fvbS4Sf84Xf/dEtsm/eC5Jbf/0Jy y2civ3fnDR/+waHsqY882frov124eNsjd9+39vH7Dv3dw69cGx29/ENrzS89u/oXa2ulw095xjdf OnLaCxM/qL57bTRy+ClWcm43+7wfl9bia49PRm4+/S8e98MLM//WemjloY+XDt20d+tp37+s7/aP /eKKP10a77v6GfZ3Hlg6+5Sv3Lz2sdLADw999t5Xrt3+ih9f9fAVz3n+265Y25GfvWftHde/7Ozv r/75vRf/8Y6XnX3P6k8++f53rP7j+2677lwvs5b+xWt/N37mYw8++zH9z3zFAwv7T/2HL/z0hqU/ u7n21/tP+/zTEhef+tlTv/WKLdUPnf6Z77qP/dhlp//5R//u02eP/MUD11zxq2t++NDKA9dc/6aX PjLwNz9+8O7rlh+6+8trr3v2Y+756rUHv/Dmtf84/XlX3HPhtX994+lL7/vAN79z5mNmrr7+2a/4 zH3fGN1+yk9eHn/sHa9LfeiNa5mVf/naQzf1vu+HD1wTfe8T3nbX2m0Pr938zcf37viXn9Sura+k Xn1L4kD5ab935dlv+VU1dfabr7w/e5533aueeuH2fO59+Wef8fwv7q0867rc0v/87Jwf9b3y53f+ +113v/7VT/ujz5+b+dXhn1y7J3fhWW95oH/ilne969BPn7z9F1vvP+N094GPHzr7iRef3zqjYY9e f/GLzu2/9i1v+NTKp275P2cf/p17Kxe86LyLXzF0+jl33HPwD85o/lX+q5dW7+y5beWnr/771ff8 5XnPW73+3HcUHviNw2e+9b4HX3Hay/qTQ1/99q53bflc4syX3LX9i5nzHnPgeRNffcEF9eXXv+xv Z298c8/IRa+/Zd9/2Icn//C+U1/wjBffdtoFf3LD333L+cJ5f/DBZ/38ul89+dszr39dYv78O578 jM9/87cviB/u/dLP7zn34Wbukfhr7nef/ZIdZz/2VOurD375TReeeffz/vlLXzn1OVfef2nktMu3 3V278Rfn3p05JfdPN/78Mb965WWHr3nTzyd+9JyXf+Wp73jm4Y9d8v+Nf+hLH/9g5L6x/MR7/vt1 6cPvf8rzb9235e4b6pf8cs9b6r/7puvv/NE7v/VH573j7z/+rW98auTTb//m9VfHn1C788rXXP2q N15XG7v7cvcfH3nrnf/1iQvf+JP3vfbNH/23r5/zxPq/tWLvGD68t/HOvU8/93M31b70o6e8//2/ fFXPc1/74cd9/yV/cMW1p732az/6yQ//e/Hsz1942aeyE1P/bZ9TuPfeJ33k5u9/5+P2gy9zK1e+ 8iP/dM3HDj10182H++78wK6P/usnfnb/ocLapR+55tzCnis+eE71A+dkXhGf+saNr3jGLQ9WH/bs U3buuP1rp/9X69QLznqM8dddL3wgddd7p5bOvOGSf3lD/r0f/dZpL/7ab072P+NLH33KV57/uZ99 7AlP//LKx5Nvu/QDP/3hR3dOFWbu+Wj9ttpDH7z0Vd/Pfuf2y/d9eib9tjff8bd33Fwae+SBT933 3MTNP77mWckzVn9wiG3jGz71rIeuftLvb7/5g4/8849Pf+j2Py/dWPuLtY987+L62de/72l/evHf ZG/98Fev+/oH/+EzZ9X/aKxncCxyYPfgPbezPx7nPfuC4uDjbn5n/ZaZJ/791DeefNunrn3fyz/5 HftDr3/vu5e/vmev+uP66trjX3HBg6lTJk82z9cvXf5bcuLxYy37wbWO/OfE02km/6Uc13VicdeF Owlns/7rCbnaxToNT3YR7iSjnUS4k4h2Cgt3AputGYjkBu7EA3cSgTvJwJ1U4E7abhPgFI0BgpQM b+Ib0M1EHRcCI6tiS7rpqJuiSE9xxcBX0VwVIeZOKpEBUJ2D6A9kWjfaJdCP2KxcpWK8XfZUCZBC 9kJ0KEaEcmAS7TEnlkiqx5Zr/EEM5tBbc/TW5GNsB5f3G8/FY2mASd2LMI7VUmVRC4yP8V8WSlBc y7jfXCktmXcoFJyiHFU+TMgjwlkY/oz0wGM51dBfwHdZOeDNmwOq7K1BecXQHw/Uq8tMO28g0lnL O8gmnqne5X0yC8DJxJM2oVe2e/BkH7+Tfhn03wXfyLHnAN3Rf6b/J9JOMp2EOylnU/8/IdevF/2P hdJ/9jHRhKPTf7gTz/jpP3tTo/9OOtUN/c+6XdH/UMK+YfrvpjfpP0xX0t2k/50vRf+TJ4D+24ru a/Q/4TqC/qcT8TTQ/5gbO8H0H/CDOz23Sf9N+g9kWNH/jAN0TtH/RNZJpIL0PxOg/5kA/c8E6H8m QP8zAfqfCdB/804G73TNEeKZqBs3OAK746Q7cgQX4oiOFUdwY6ljyhGS8XhbjhDvmiM4j2KOkOyG I8SzmxqBcSn6n3pU0P9Uytmk/yfw2jD9R3Ff0H8nFc+gQiDofzbjZjP/e+m/k4hHHYP+s00aZZ/o twi5Gv1PuG5XFqGu6H8CQt2OHf13YvHsiaH/zqOZ/juJZHyT/uuXov/pk0f/E3Ee/xFzUskE0n8n vkn/T8S1YfoPJFbS/7ibBnFV0n8nm0rF3CD9zwbofzZA/7MB+p8N0P9sgP5nA/Q/G6D/5p0s3umW IyTYwUgZNqJE3I1mAz4CV/cRMCZ47GxEGSeVPoYcwY0lkyfGRhR/NNuIEvFs7NeZIyj6n3k00P9E DHDuGP2PnWj7/yb9PzL6j+Re0P8URG7aiv7Hs3HXCbH//6+l/07McU2LELsTi8ZdP/1PpRT9d1KM Rxwr+u+kXP2xo6b/CczHOhH0P/Uopv8OUJxN+g/0P3uy4r+dRIqd6RRbCicJ64Hx305i0/97Iq4N 038gn4L+O3Enltbt/+lMKuEG7f+MJfjov+9OPHAnEbiTDNxJBe6kA3cygTtZ/x2UPGLdRg0lYy6T /zO6RpB2Y1HHCWgEjuII8Xh3PgI3k1yfI0TS2XQ3UUPsLDndcISMm3CPAUdY30bknDSNwF2fIyST 2UT214cj6PT/ZMX/EP0H+R/ICMr/yXRqk/6fiGuT/q9P/0M1AjeezETZK4r+szuJaNxH/51oUtMI 4m46ljh2PoJYKn4MNYIMO38nRCNw3EexRuDGM+nMryH9Z7LLSZL/3ZSbIvk/nkymHYfk/834/xNy 5TkGGYE3QTo9lolHhKQVQvFEAE9AW+Y4nkuVFk/ij0YBTW58yp5M2WzfTFx0Vb+dSkz021buolzE zSZiu/sBUwZgB4e2TybcWHq33ZOIupkdvf2WgHyVSGZu1IlMjYyP5Ioj9n6vUfOq/QifBsBNUMqI dQa0BnLRseSSLIoAoHQwJKrhaFQKTmT7k2l3PyKisXd5yZqVfZDMb/GSvKxdbAOS+zE3HEAx6yUA 0iLgJfZBhAEAwAUIAaCKWC9hEW0HeunPJDM2QgA2+zlAFq/MvbVp4FH4K3OvtvYtRjeAW9AeqnY9 9g1SlmTf7AA6Cc1977BvYZ/y/wr7DlPfHCeTdqIZg31n06mom/az77Tm4k8mY5mu1Ld4N0kfqUQ8 0Q37TsXD/D4+9u0wJu+Eq28Ql5boln1DXPc67NtNnAz27QKS77rs20kkM7H11LeNHLQ99WUEzyDE OcIeJDo459XK+xZLjf0EBmJZT1poLZ0/MLBSBqBFwCQpz7MfooxgDCwtzw1w3KmBCpSGZTRigNqJ srFG915lWaOVxRMoYCj+7548/Q98/ql0PJZOxTByHfS/Tf5/Qq6xCnDWjfMRV/ERJsBlkmnNDZRy s2xtg24gxwnwESfAR5wAH3ECfMQJ8BEnwEecAB9xAnzECfAR8w6NmVhlIh6LJjSzn5tMpdIQCKzx DSflRhNK7WOkK5k4dqHBdjx+7EKD49lkOhuu9iVj8Viqa7Vvfb5xXEODnXZ8g31FOr4u33BTyUzm 1zE0TNH/+Emj/wiymUqn2VPE5Bn9T23S/xNybZjwxxXhh1oMmGrFCb/jJjNuNhZi/3Mtzm/40Uwl opmUJoMnsslsNJs1ZHCgt8qFkkgn04ljZ0KLO+6xM6E5qazrtDGhOel092G2qUcpLYWvyK5vQks5 MYgG+bWjpZvX5rV5bV6b1+a1eW1em9fmtXltXpvX5rV5bV6b1+a1eW1em9fmtXltXpvX5rV5bV6b 1+a1eW1em9fmdaKv/x9Zeed4AOABAA== --ELM937875595-4621-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18: 8:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-66.birch.net [216.212.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 550D314DB6; Mon, 20 Sep 1999 18:07:36 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id UAA04840; Mon, 20 Sep 1999 20:07:31 -0500 (CDT) From: Jim Bryant Message-Id: <199909210107.UAA04840@argus.tfs.net> Subject: Re: Testers please! In-Reply-To: <17979.937771312@critter.freebsd.dk> from Poul-Henning Kamp at "Sep 19, 99 10:01:52 pm" To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Mon, 20 Sep 1999 20:07:31 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. just cvsupped, added your changes, and am building world and a new kernel. i'll get back to ya. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18: 9:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id D168A15BF1 for ; Mon, 20 Sep 1999 18:09:24 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id DAA29534; Tue, 21 Sep 1999 03:09:20 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id A7C25D226; Tue, 21 Sep 1999 03:09:19 +0200 (CEST) Message-ID: <19990921030919.A14737@enst.fr> Date: Tue, 21 Sep 1999 03:09:19 +0200 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: DANGER: login and friends with libscrypt/libdescrypt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just been bitten by the following, so I figured I might as well warn others. From a quick glance it doesn't seem to have been mentioned, or not clearly enough, in this list. - libscrypt/libdescrypt major number has been bumped a few days ago. - /usr/bin/login and friends are now linked against libscrypt instead of libcrypt. The bottom line is, if: - you don't have crypto sources on your machine - you were using a symbolic link from libcrypt* to libscrypt*/libdescrypt* - you used that to link to an old libdes binary then ***test*** your compiled login binary before you reinstall everything. Thanksfully I kept an older -current on another machine from which I could find a working copy of login, which saved me from totally ruining my night. But I'll be sure to install complete crypto sources first thing tomorrow morning on my machines. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18:12:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from pike.sover.net (pike.sover.net [209.198.87.34]) by hub.freebsd.org (Postfix) with ESMTP id 6A00714F44 for ; Mon, 20 Sep 1999 18:12:25 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a252.bf.sover.net [209.198.85.252]) by pike.sover.net (8.9.3/8.9.3) with ESMTP id VAA28770 for ; Mon, 20 Sep 1999 21:12:21 -0400 (EDT) Comments: SoVerNet Verification (on pike.sover.net) nightfall.digitalspark.net from arc0a252.bf.sover.net [209.198.85.252] 209.198.85.252 Mon, 20 Sep 1999 21:12:21 -0400 (EDT) Date: Mon, 20 Sep 1999 21:16:13 +0000 (GMT) From: Adam Strohl To: freebsd-current@FreeBSD.ORG Subject: Wierd su/vnc issue In-Reply-To: <199909210059.TAA04816@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG adams@nightfall(21:13:30)$ su Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k As soon as I hit enter I get more: load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k (hit enter 3 times). I can't do anything here, I have to telnet back into my machine log in as myself, and then su, it looks like some wierd tty issue. Also, vncviewer does the same thing: vncviewer: VNC server supports protocol version 3.3 (viewer 3.3) Password: load: 0.13 cmd: vncviewer 422 [ttyin] 0.00u 0.00s 0% 840k This has been going on for the last few days, I just rebuilt my entire world about 30 seconds ago, still there. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18:24:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id B84BD152BE for ; Mon, 20 Sep 1999 18:24:44 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id DAA00704; Tue, 21 Sep 1999 03:24:38 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id B0723D226; Tue, 21 Sep 1999 03:24:37 +0200 (CEST) Message-ID: <19990921032437.A15533@enst.fr> Date: Tue, 21 Sep 1999 03:24:37 +0200 From: Pierre Beyssac To: Adam Strohl , freebsd-current@FreeBSD.ORG Subject: Re: Wierd su/vnc issue References: <199909210059.TAA04816@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Adam Strohl on Mon, Sep 20, 1999 at 09:16:13PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 20, 1999 at 09:16:13PM +0000, Adam Strohl wrote: > adams@nightfall(21:13:30)$ su > Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > As soon as I hit enter I get more: > load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k I saw that, too. That might be a strange side effect of the libcrypt->libscrypt change (note how it happens with programs which ask for a passwd). I just get SIGSEVs right now when I try su but I've had the same as you at least once before that. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 18:51:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id 1C72115391 for ; Mon, 20 Sep 1999 18:51:46 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a252.bf.sover.net [209.198.85.252]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id VAA16653; Mon, 20 Sep 1999 21:51:27 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a252.bf.sover.net [209.198.85.252] 209.198.85.252 Mon, 20 Sep 1999 21:51:27 -0400 (EDT) Date: Mon, 20 Sep 1999 21:55:19 +0000 (GMT) From: Adam Strohl To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: Wierd su/vnc issue In-Reply-To: <19990921032437.A15533@enst.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, is there a work around, telneting out does the same thing, using the -l option used to allow me to log into remote hosts, not anymore, same with loopback telneting and suing. I can hear Jordan already: "TAKE IT LIKE A MAN!" ;'D - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Tue, 21 Sep 1999, Pierre Beyssac wrote: > On Mon, Sep 20, 1999 at 09:16:13PM +0000, Adam Strohl wrote: > > adams@nightfall(21:13:30)$ su > > Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > > > As soon as I hit enter I get more: > > load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > I saw that, too. That might be a strange side effect of the > libcrypt->libscrypt change (note how it happens with programs which > ask for a passwd). I just get SIGSEVs right now when I try su but > I've had the same as you at least once before that. > -- > Pierre Beyssac pb@enst.fr > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 20: 5:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E2FAE14C97 for ; Mon, 20 Sep 1999 20:05:49 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 348691CC5; Tue, 21 Sep 1999 11:05:48 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-reply-to: Your message of "Mon, 20 Sep 1999 18:52:57 +0200." <23777.937846377@critter.freebsd.dk> Date: Tue, 21 Sep 1999 11:05:48 +0800 From: Peter Wemm Message-Id: <19990921030548.348691CC5@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <199909201639.JAA32335@dingo.cdrom.com>, Mike Smith writes: > >> >Use a watchdog timeout like you should for any device that may hang. > >> >Don't waste time running it every clock tick. > >> > > >> >ISTR that we thought that the bug might be caused by a bug in unwanted > >> >SMI interrupt handling. > >> > >> If anybody can reproduce this reliably on a *BX chipset I have > >> code that will block SMI interrupts we can test with... > > > >I'm not sure I follow what the alleged problem is here; who is handling > >the "unwanted" SMIs? If it's the BIOS, the last thing you want to do > >is block all SMIs. > > The problem is that the RTC stalls. It is suspected that it could > be long SMI durations which is responsible for this. To confirm > the diagnosis disabling SMI is feasible. > > You system will not blow up if you disable SMI, I have a system > happily chugging away here with SMI disabled for a month. > > Doing so even idiot-proofs the soft-off button :-) Tor Egge's patches are more finely grained than that. They disable the SMI traps when the OS tries to access ports 0x70/0x71 only and leaves the rest of the SMI's alone (including soft off buttons) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 23:29:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 8A9CD1514D for ; Mon, 20 Sep 1999 23:29:40 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA70984; Tue, 21 Sep 1999 08:29:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909210629.IAA70984@gratis.grondar.za> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt Date: Tue, 21 Sep 1999 08:29:26 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - /usr/bin/login and friends are now linked against libscrypt > instead of libcrypt. This is a link bug. The Makefile says "-lcrypt". JDP? i M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 20 23:39:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from bantha.org (adsl-117.ntrnet.net [208.241.154.117]) by hub.freebsd.org (Postfix) with ESMTP id D90F214BC2 for ; Mon, 20 Sep 1999 23:39:15 -0700 (PDT) (envelope-from krinsky@bantha.org) Received: by bantha.org (Postfix, from userid 100) id 2552E66B8B; Tue, 21 Sep 1999 02:38:30 -0400 (EDT) Date: Tue, 21 Sep 1999 02:38:30 -0400 From: David Krinsky To: Gary Hampton Cc: Adam Strohl , current@FreeBSD.ORG Subject: Re: ata drivers Message-ID: <19990921023830.B68476@bantha.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Gary Hampton on Mon, Sep 20, 1999 at 12:05:38AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 20, 1999 at 12:05:38AM +0000, Gary Hampton (garyh@mail.win.bright.net) wrote: > On Mon, 20 Sep 1999, Adam Strohl wrote: > > > Remake your acd device, I think you may need a patch to do it. I had the > > same problem, until I rm-ed the device and remade it. > > > > - ----( Adam Strohl )------------------------------------------------ - > > - UNIX Operations/Systems http://www.digitalspark.net - > > - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - > > - ----------------------------------------( DigitalSpark.NET )------- - > No luck I still just get: > mount_cd9660: Block device required > trying to mount acd0a acd0c acd1a and acd1c What's the major number on acd0c? It should be 31; IIRC older MAKEDEV scripts set it to 19. Dave. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 0:40:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.win.bright.net (wey1-cs-1.win.bright.net [208.140.5.162]) by hub.freebsd.org (Postfix) with ESMTP id 93D6F150C6 for ; Tue, 21 Sep 1999 00:40:27 -0700 (PDT) (envelope-from garyh@mail.win.bright.net) Received: from localhost (garyh@localhost) by mail.win.bright.net (8.9.3/8.9.1) with ESMTP id CAA05306; Tue, 21 Sep 1999 02:41:39 GMT (envelope-from garyh@mail.win.bright.net) Date: Tue, 21 Sep 1999 02:41:39 +0000 (GMT) From: Gary Hampton To: David Krinsky Cc: Adam Strohl , current@FreeBSD.ORG Subject: Re: ata drivers In-Reply-To: <19990921023830.B68476@bantha.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Sep 1999, David Krinsky wrote: > On Mon, Sep 20, 1999 at 12:05:38AM +0000, Gary Hampton (garyh@mail.win.bright.net) wrote: > > On Mon, 20 Sep 1999, Adam Strohl wrote: > > > > > Remake your acd device, I think you may need a patch to do it. I had the > > > same problem, until I rm-ed the device and remade it. > > > > > > - ----( Adam Strohl )------------------------------------------------ - > > > - UNIX Operations/Systems http://www.digitalspark.net - > > > - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - > > > - ----------------------------------------( DigitalSpark.NET )------- - > > No luck I still just get: > > mount_cd9660: Block device required > > trying to mount acd0a acd0c acd1a and acd1c > > What's the major number on acd0c? It should be 31; IIRC older > MAKEDEV scripts set it to 19. > > Dave. Thanks thats what was wrong at least I can mount the drive now I will try to write to it when I have more time. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 1:42:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 344A5153F8 for ; Tue, 21 Sep 1999 01:42:16 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id JAA38129; Tue, 21 Sep 1999 09:42:14 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA02679; Tue, 21 Sep 1999 09:48:00 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199909210848.JAA02679@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt In-reply-to: Your message of "Tue, 21 Sep 1999 03:09:19 +0200." <19990921030919.A14737@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Sep 1999 09:48:00 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just been bitten by the following, so I figured I might as > well warn others. From a quick glance it doesn't seem to have been > mentioned, or not clearly enough, in this list. Too late.... drat ! But xdm saves the day ! [.....] > -- > Pierre Beyssac pb@enst.fr -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 1:44:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 0848415401 for ; Tue, 21 Sep 1999 01:44:14 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id KAA28556; Tue, 21 Sep 1999 10:44:11 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 15749D226; Tue, 21 Sep 1999 10:44:11 +0200 (CEST) Message-ID: <19990921104411.C4814@enst.fr> Date: Tue, 21 Sep 1999 10:44:11 +0200 From: Pierre Beyssac To: Adam Strohl Cc: freebsd-current@FreeBSD.ORG Subject: Re: Wierd su/vnc issue References: <19990921032437.A15533@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Adam Strohl on Mon, Sep 20, 1999 at 09:55:19PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 20, 1999 at 09:55:19PM +0000, Adam Strohl wrote: > Well, is there a work around, telneting out does the same thing, using > the -l option used to allow me to log into remote hosts, not The workaround I found was to boot single then "su - mylogin". -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 1:54:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 63A5B152F7 for ; Tue, 21 Sep 1999 01:54:53 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id KAA29142; Tue, 21 Sep 1999 10:54:49 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 1BB98D226; Tue, 21 Sep 1999 10:54:49 +0200 (CEST) Message-ID: <19990921105449.A21254@enst.fr> Date: Tue, 21 Sep 1999 10:54:49 +0200 From: Pierre Beyssac To: Mark Murray Cc: freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt References: <199909210629.IAA70984@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199909210629.IAA70984@gratis.grondar.za>; from Mark Murray on Tue, Sep 21, 1999 at 08:29:26AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 08:29:26AM +0200, Mark Murray wrote: > > - /usr/bin/login and friends are now linked against libscrypt > > instead of libcrypt. > > This is a link bug. The Makefile says "-lcrypt". JDP? Then there's the problem that libcrypto.so.3 won't magically be a link to a working libdescrypt.so.3 if the latter doesn't exist, especially if you don't have crypto sources. Then, the fact that login SIGSEV's in strcmp from inside PAM doesn't look very normal to me either. I suppose there's an error check missing somewhere when the libscrypt is called while you use DES passwords. (gdb) where #0 0x280d0cf4 in strcmp () from /usr/lib/libc.so.3 #1 0x28115365 in pam_sm_authenticate () from /usr/lib/pam_unix.so #2 0x280754b9 in pam_getenvlist () from /usr/lib/libpam.so.1 #3 0x2807577d in _pam_dispatch () from /usr/lib/libpam.so.1 #4 0x28074b37 in pam_authenticate () from /usr/lib/libpam.so.1 #5 0x804a88a in setlogin () #6 0x8049c3a in setlogin () #7 0x804986d in setlogin () -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 5:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ED68E14F86 for ; Tue, 21 Sep 1999 05:56:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA28597 for ; Tue, 21 Sep 1999 14:55:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: "md" driver, some info From: Poul-Henning Kamp Date: Tue, 21 Sep 1999 14:55:50 +0200 Message-ID: <28595.937918550@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The "md" driver I committed today is mostly a proof-of-concept thing which came out of a chat with Peter Wemm. It acts like a disk in all aspects, although it will be hard to boot from it :-) It will do very simple compression, in that a sector (512bytes) which is filled with the same character throughout, will not be allocated as a full sector, instead just the byte value is saved. In practice this means that making a 10M filesystem doesn't take 10M of ram, until you fill data into it. The driver will also free the sectors after you delete a file from the filesystem (ufs only). # disklabel -r -w md0 auto # newfs md0c # vmstat -m | grep " MD s" MD sectors 635 318K 318K 21136K 635 0 0 512 # mount /dev/md0c /mnt # cp /kernel /mnt # vmstat -m | grep " MD s" MD sectors 4178 2089K 2089K 21136K 4178 0 0 512 # rm /mnt/kernel # vmstat -m | grep " MD s" MD sectors 636 318K 2120K 21136K 4240 0 0 512 # umount /mnt # dd if=/dev/zero of=/dev/rmd0 # vmstat -m | grep " MD s" MD sectors 0 0K 2120K 21136K 4240 0 0 512 # Currently the size is arbitrarily set at 20000 sectors, just shy of 10MB. The driver can be nice-ified in various ways, suggestions and patches are welcome. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 7:20:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.fw-bc.sony.com (mail2.fw-bc.sony.com [198.83.177.13]) by hub.freebsd.org (Postfix) with ESMTP id 0BD9E15173 for ; Tue, 21 Sep 1999 07:20:41 -0700 (PDT) (envelope-from Internet.MailSystem@us-ti-xims-1.am.sony.com) Received: from mail1.bc.in.sel.sony.com (mail1.bc.in.sel.sony.com [43.144.65.11]) by mail2.fw-bc.sony.com (8.8.8/8.8.8) with ESMTP id OAA14103 for ; Tue, 21 Sep 1999 14:20:40 GMT Received: by mail1.bc.in.sel.sony.com id JAA26822; Tue, 21 Sep 1999 09:51:24 -0400 (EDT) Received: by us-ti-xims-1.am.sony.com with Internet Mail Service (5.5.2448.0) id ; Tue, 21 Sep 1999 09:51:23 -0400 Message-ID: <294F1168BAD0D21195680090271775CB451ECE@us-ti-xmsg-2.am.sony.com> From: Internet MailSystem To: current@FreeBSD.ORG Subject: request for review, patch to specfs to fix EOF condition alignmen t with buffer Date: Tue, 21 Sep 1999 09:51:22 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-2022-jp" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a request for a review. This patch fixes a bug in specfs relating to dealing with the EOF condition of a block device. If the EOF occurs in the middle of a block, specfs was not properly calculating the truncation for the I/O. This problem was first found by Tor. Tor's example creates an oddly-sized VN partition and then dd's from it. Without the patch the dd believes that it can read 2880 sectors. With the patch it correctly reads the last (truncated) block. dd if=/dev/zero of=/tmp/floppy.img bs=512 count=2879 vnconfig -s labels -c /dev/vn0 /tmp/floppy.img dd if=/dev/vn0 of=/dev/null bs=8k Once this patch is committed, the only problem we will have is in recognizing the write-EOF case, which I will have a recommendation for after this patch goes in. A similar problem in the VN device has already been fixed and committed. -Matt Index: miscfs/specfs/spec_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v retrieving revision 1.108 diff -u -r1.108 spec_vnops.c --- spec_vnops.c 1999/09/17 06:10:26 1.108 +++ spec_vnops.c 1999/09/20 17:50:48 @@ -311,19 +311,37 @@ do { bn = btodb(uio->uio_offset) & ~(bscale - 1); on = uio->uio_offset % bsize; - n = min((unsigned)(bsize - on), uio->uio_resid); if (seqcount > 1) { nextbn = bn + bscale; error = breadn(vp, bn, (int)bsize, &nextbn, (int *)&bsize, 1, NOCRED, &bp); } else { error = bread(vp, bn, (int)bsize, NOCRED, &bp); + } + + /* + * Figure out how much of the buffer is valid relative + * to our offset into the buffer, which may be negative + * if we are beyond the EOF. + * + * The valid size of the buffer is based on + * bp->b_bcount (which may have been truncated by + * dscheck or the device) minus bp->b_resid, which + * may be indicative of an I/O error if non-zero. + */ + n = bp->b_bcount - on; + if (n < 0) { + error = EINVAL; + } else { + n -= bp->b_resid; + if (n < 0) + error = EIO; } - n = min(n, bsize - bp->b_resid); if (error) { brelse(bp); return (error); } + n = min(n, uio->uio_resid); error = uiomove((char *)bp->b_data + on, n, uio); brelse(bp); } while (error == 0 && uio->uio_resid > 0 && n != 0); @@ -403,16 +421,48 @@ do { bn = btodb(uio->uio_offset) & ~blkmask; on = uio->uio_offset % bsize; + + /* + * Calculate potential request size, determine + * if we can avoid a read-before-write. + */ n = min((unsigned)(bsize - on), uio->uio_resid); if (n == bsize) bp = getblk(vp, bn, bsize, 0, 0); else error = bread(vp, bn, bsize, NOCRED, &bp); + + /* + * n is the amount of effective space in the buffer + * that we wish to write relative to our offset into + * the buffer. We have to truncate it to the valid + * size of the buffer relative to our offset into + * the buffer (which may end up being negative if + * we are beyond the EOF). + * + * The valid size of the buffer is based on + * bp->b_bcount (which may have been truncated by + * dscheck or the device) minus bp->b_resid, which + * may be indicative of an I/O error if non-zero. + * + * XXX In a newly created buffer, b_bcount == bsize + * and, being asynchronous, we have no idea of the + * EOF. + */ + if (error == 0) { + n = min(n, bp->b_bcount - on); + if (n < 0) { + error = EINVAL; + } else { + n -= bp->b_resid; + if (n < 0) + error = EIO; + } + } if (error) { brelse(bp); return (error); } - n = min(n, bsize - bp->b_resid); error = uiomove((char *)bp->b_data + on, n, uio); if (n + on == bsize) bawrite(bp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 7:41:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 715DE15520 for ; Tue, 21 Sep 1999 07:41:14 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8F37E1CC4; Tue, 21 Sep 1999 22:41:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: Pierre Beyssac , freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt In-reply-to: Your message of "Tue, 21 Sep 1999 08:29:26 +0200." <199909210629.IAA70984@gratis.grondar.za> Date: Tue, 21 Sep 1999 22:41:13 +0800 From: Peter Wemm Message-Id: <19990921144113.8F37E1CC4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > - /usr/bin/login and friends are now linked against libscrypt > > instead of libcrypt. > > This is a link bug. The Makefile says "-lcrypt". JDP? Umm... Previously there was: .if ${OBJFORMAT} == elf SONAME= ${LCRYPTBASE}.so.${SHLIB_MAJOR} .endif This appears to have been lost. # objdump --all-headers /usr/lib/libscrypt.so.2 ... Dynamic Section: SONAME libcrypt.so.2 ^^^^^^^^^^^^^ INIT 0x354 Since somebody has deleted the SONAME override, the various libXcrypt files have their own soname and the symlink redirection doesn't work as the program gets compiled specifically to use the SONAME of the link-time targets. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 8:45:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B4A8D150BC; Tue, 21 Sep 1999 08:45:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA06329; Tue, 21 Sep 1999 08:45:16 -0700 (PDT) (envelope-from dillon) Date: Tue, 21 Sep 1999 08:45:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199909211545.IAA06329@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: "md" driver, some info References: <28595.937918550@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The "md" driver I committed today is mostly a proof-of-concept thing :which came out of a chat with Peter Wemm. : :It acts like a disk in all aspects, although it will be hard to boot :from it :-) : :It will do very simple compression, in that a sector (512bytes) :which is filled with the same character throughout, will not be :allocated as a full sector, instead just the byte value is saved. : :In practice this means that making a 10M filesystem doesn't take :10M of ram, until you fill data into it. The driver will also free :the sectors after you delete a file from the filesystem (ufs only). : :# disklabel -r -w md0 auto :# newfs md0c :# vmstat -m | grep " MD s" : MD sectors 635 318K 318K 21136K 635 0 0 512 :# mount /dev/md0c /mnt :# cp /kernel /mnt :# vmstat -m | grep " MD s" : MD sectors 4178 2089K 2089K 21136K 4178 0 0 512 :# rm /mnt/kernel :# vmstat -m | grep " MD s" : MD sectors 636 318K 2120K 21136K 4240 0 0 512 :# umount /mnt :# dd if=/dev/zero of=/dev/rmd0 :# vmstat -m | grep " MD s" : MD sectors 0 0K 2120K 21136K 4240 0 0 512 :# That's very interesting. You can do the same thing with the VN device, using swap-backing, except it does not do any compression. test3:/root# vnconfig -s labels -c -S 32g vn0 test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/od0b 1048448 0 1048448 0% Interleaved /dev/da1b 1048448 0 1048448 0% Interleaved /dev/da2b 1048448 0 1048448 0% Interleaved Total 3145344 0 3145344 0% test3:/root# disklabel -r -w vn0 auto test3:/root# newfs /dev/rvn0c Warning: Block size restricts cylinders per group to 8. /dev/rvn0c: 67108864 sectors in 2048 cylinders of 1 tracks, 32768 sectors 32768.0MB in 256 cyl groups (8 c/g, 128.00MB/g, 8128 i/g) super-block backups (for fsck -b #) at: 32, 262176, 524320, 786464, 1048608, 1310752, 1572896, 1835040, 2097184, 2359328, 2621472, 2883616, 3145760, 3407904, 3670048, 3932192, 4194336, 4456480, 4718624, 4980768, 5242912, 5505056, 5767200, 6029344, 6291488, ... 62128160, 62390304, 62652448, 62914592, 63176736, 63438880, 63701024, 63963168, 64225312, 64487456, 64749600, 65011744, 65273888, 65536032, 65798176, 66060320, 66322464, 66584608, 66846752 test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/od0b 1048448 88092 960356 8% Interleaved /dev/da1b 1048448 88064 960384 8% Interleaved /dev/da2b 1048448 88064 960384 8% Interleaved Total 3145344 264220 2881124 8% test3:/root# mount /dev/vn0c /mnt test3:/root# cp /kernel /mnt test3:/root# test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/od0b 1048448 88764 959684 8% Interleaved /dev/da1b 1048448 88704 959744 8% Interleaved /dev/da2b 1048448 88704 959744 8% Interleaved Total 3145344 266172 2879172 8% test3:/root# rm /mnt/kernel test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/od0b 1048448 88092 960356 8% Interleaved /dev/da1b 1048448 88064 960384 8% Interleaved /dev/da2b 1048448 88064 960384 8% Interleaved Total 3145344 264220 2881124 8% test3:/root# umount /mnt test3:/root# vnconfig -u vn0 test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/od0b 1048448 0 1048448 0% Interleaved /dev/da1b 1048448 0 1048448 0% Interleaved /dev/da2b 1048448 0 1048448 0% Interleaved Total 3145344 0 3145344 0% However, for general use it is recommended that one use the 'reserve' flag for swap-backed VN filesystems to pre-reserve all necessary swap in order to maintain performance. And enabling softupdates on it once you've newfs'd is also a good idea. Just for kicks: test3:/root# vnconfig -s labels -c -S 4t vn0 test3:/root# disklabel -r -w vn0 auto test3:/root# disklabel vn0 ... bytes/sector: 4096 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1073741824 0 unused 0 0 # (Cyl. 0 - 4194303) test3:/root# pstat -s Device 1K-blocks Used Avail Capacity Type Total 3145344 8 3145336 0% test3:/root# newfs /dev/rvn0c preposterous size 0 <--------------------------- I find that totally amusing. I think I'm going to fix newfs, it really should be able to handle a 4 terrabyte filesystem. :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 9:20:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from web119.yahoomail.com (web119.yahoomail.com [205.180.60.120]) by hub.freebsd.org (Postfix) with SMTP id 7562114E47 for ; Tue, 21 Sep 1999 09:20:41 -0700 (PDT) (envelope-from padequoi@yahoo.com) Message-ID: <19990921162043.17972.rocketmail@web119.yahoomail.com> Received: from [208.153.11.101] by web119.yahoomail.com; Tue, 21 Sep 1999 09:20:43 PDT Date: Tue, 21 Sep 1999 09:20:43 -0700 (PDT) From: gramond lamoureux Subject: mount: ufs filesystem not available To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all the suggestions, Here are some followup comments to some suggestions * '...get a copy of mount...' I was not able to mount anything so I could not copy from the floppy. * '... why not start with 3.3 ...' I just got the hang of cvsup so I wanted to try upgrade and make world * '... use picobsd ...' I'm not familiar enough but after reading it sound really interesting. Specially since a have a small 486 with 8 meg, network cards but no drive. sounds like it could be a good router Finally, I solve my problem this way, probably not recommended but it worked. I started with my 2.2.6 install disk. Created the mount points and rebooted. This allowed to get access to /usr so I could get ee to work and copy etc to a floppy. (ok I should do backups more often) but for me backup only work when I don't need them. Once I got my /etc. I restart the install of 2.2.6 and then copied the files back. Ho yea, made the mistake and copied passwd, then I could no longer logon. So did it over and now it works. I would like to start with 3.3 but I could not find the install disk for that. So I'll try again the upgrade. But I'm better prepared this time. Thanks Gramond __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 10:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 86DE3153A3 for ; Tue, 21 Sep 1999 10:11:49 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id TAA26981 for ; Tue, 21 Sep 1999 19:11:48 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id E84ECD226; Tue, 21 Sep 1999 19:11:47 +0200 (CEST) Message-ID: <19990921191147.A63436@enst.fr> Date: Tue, 21 Sep 1999 19:11:47 +0200 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: top and w breakage Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like top and w are broken (whereas ps works) with a -current from this night. top displays weird stuff: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND -1067947544 375545 185 50663 3078M 0K ? 64 ??? 134561792.00% 657040 0 root -22 49209 0K 0K ? 82 0:00 0.00% 1455.13% <> w works except that the "WHAT" column is apparently always "-". I have reinstalled libkvm and a kernel in sync with the rest of the system... Have I missed something? -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 10:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id BC9431543C for ; Tue, 21 Sep 1999 10:55:10 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA73513; Tue, 21 Sep 1999 19:51:19 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909211751.TAA73513@gratis.grondar.za> To: Peter Wemm Cc: Pierre Beyssac , freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt Date: Tue, 21 Sep 1999 19:51:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This appears to have been lost. Hmm. I might be the culprit. Fixing now... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 11: 0: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 6D8A6153A3 for ; Tue, 21 Sep 1999 11:00:03 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id UAA29272; Tue, 21 Sep 1999 20:00:00 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 7A75ED226; Tue, 21 Sep 1999 20:00:00 +0200 (CEST) Message-ID: <19990921200000.A59287@enst.fr> Date: Tue, 21 Sep 1999 20:00:00 +0200 From: Pierre Beyssac To: Mark Murray , Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt References: <199909211751.TAA73513@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199909211751.TAA73513@gratis.grondar.za>; from Mark Murray on Tue, Sep 21, 1999 at 07:51:18PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 07:51:18PM +0200, Mark Murray wrote: > > This appears to have been lost. > Hmm. I might be the culprit. Fixing now... Uh, this seems to have been fixed by Peter a moment ago. Now the only thing that I'd like to know is: where do I get the current CVS sources for libdescrypt, so that this doesn't prevent me from logging-in next time? peter 1999/09/21 07:44:28 PDT Modified files: lib/libcrypt Makefile Log: Somebody deleted the SONAME override causing the symlink to be expanded at link time and the target name compiled into the binaries. ie: everything used libscrypt or libdescrypt explicitly. Revision Changes Path 1.21 +5 -1 src/lib/libcrypt/Makefile peter 1999/09/21 07:47:37 PDT Modified files: secure/lib/libcrypt Makefile Log: Restore SONAME setting, otherwise libdescrypt.so.3 doesn't end up with a special SONAME of libcrypt.so.3 and the runtime symlink doesn't work. Revision Changes Path 1.19 +5 -1 src/secure/lib/libcrypt/Makefile -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 11:12:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id B0FDD15164 for ; Tue, 21 Sep 1999 11:12:09 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id UAA73763; Tue, 21 Sep 1999 20:09:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909211809.UAA73763@gratis.grondar.za> To: Pierre Beyssac Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt Date: Tue, 21 Sep 1999 20:09:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now the only thing that I'd like to know is: where do I get the > current CVS sources for libdescrypt, so that this doesn't prevent > me from logging-in next time? Usual places? It is in Internat as well. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 11:23: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 3E03A1544C for ; Tue, 21 Sep 1999 11:22:57 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id UAA00186; Tue, 21 Sep 1999 20:22:56 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 833A4D226; Tue, 21 Sep 1999 20:22:55 +0200 (CEST) Message-ID: <19990921202255.B59287@enst.fr> Date: Tue, 21 Sep 1999 20:22:55 +0200 From: Pierre Beyssac To: Mark Murray Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt References: <199909211809.UAA73763@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199909211809.UAA73763@gratis.grondar.za>; from Mark Murray on Tue, Sep 21, 1999 at 08:09:02PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 08:09:02PM +0200, Mark Murray wrote: > Usual places? It is in Internat as well. Yes, my question was more or less _where_ are the usual places :-) because internat.freebsd.org is apparently down at the moment. I finally got it from: ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur/ -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 11:30:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 9E91414E45 for ; Tue, 21 Sep 1999 11:30:33 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.19.16.06.p6) with ESMTP id <0FIF00BN9A1INI@mta1.rcsntx.swbell.net> for freebsd-current@FreeBSD.ORG; Tue, 21 Sep 1999 13:29:43 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id NAA06003; Tue, 21 Sep 1999 13:30:02 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 21 Sep 1999 13:30:02 -0500 From: Chris Costello Subject: Re: top and w breakage In-reply-to: <19990921191147.A63436@enst.fr> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19990921133002.C5457@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19990921191147.A63436@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999, Pierre Beyssac wrote: > I have reinstalled libkvm and a kernel in sync with the rest of > the system... Have I missed something? You haven't given a lot of information. Was this the result of a full buildworld, installworld and then new kernel? Or did you just update src/lib/libkvm and src/sys? -- |Chris Costello |You forgot to do your backup 16 days ago. Tomorrow you'll |need that version. `---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 11:40:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 71C551503A for ; Tue, 21 Sep 1999 11:40:13 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id UAA00841; Tue, 21 Sep 1999 20:40:09 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 72687D226; Tue, 21 Sep 1999 20:40:07 +0200 (CEST) Message-ID: <19990921204007.A65110@enst.fr> Date: Tue, 21 Sep 1999 20:40:07 +0200 From: Pierre Beyssac To: chris@calldei.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: top and w breakage References: <19990921191147.A63436@enst.fr> <19990921133002.C5457@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990921133002.C5457@holly.calldei.com>; from Chris Costello on Tue, Sep 21, 1999 at 01:30:02PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 01:30:02PM -0500, Chris Costello wrote: > You haven't given a lot of information. Was this the result > of a full buildworld, installworld and then new kernel? Sorry I was unclear, yes: a full buildworld+installworld+new kernel (the same installworld that broke login and friends for me). This includes kernel modules of course. Something more (probably unrelated): when I exit top with ^C, I have a SIGSEGV there: (gdb) where #0 0x2808a19d in tputs () from /usr/lib/libncurses.so.5 #1 0x804c16b in free () #2 0x804d1f8 in clear () #3 0xbfbfdfd4 in ?? () #4 0x80493c5 in free () Am I cursed (pun intended) or what :-) ? -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 12: 0:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 39CEB15A4F for ; Tue, 21 Sep 1999 12:00:16 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id UAA01197; Tue, 21 Sep 1999 20:59:42 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199909211859.UAA01197@zibbi.mikom.csir.co.za> Subject: Re: DANGER: login and friends with libscrypt/libdescrypt In-Reply-To: <19990921202255.B59287@enst.fr> from Pierre Beyssac at "Sep 21, 1999 08:22:55 pm" To: beyssac@enst.fr (Pierre Beyssac) Date: Tue, 21 Sep 1999 20:59:42 +0200 (SAT) Cc: mark@grondar.za, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Sep 21, 1999 at 08:09:02PM +0200, Mark Murray wrote: > > Usual places? It is in Internat as well. > > Yes, my question was more or less _where_ are the usual places :-) > because internat.freebsd.org is apparently down at the moment. Can you explain a bit more what "apparently down" mean please? It seems up to me. I'm logged in on it at the moment and did an ftp from freefall just to make sure. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 12:29:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id F298715413 for ; Tue, 21 Sep 1999 12:29:25 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id VAA02158; Tue, 21 Sep 1999 21:29:23 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id C6389D226; Tue, 21 Sep 1999 21:29:22 +0200 (CEST) Message-ID: <19990921212922.A65874@enst.fr> Date: Tue, 21 Sep 1999 21:29:22 +0200 From: Pierre Beyssac To: John Hay Cc: mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: DANGER: login and friends with libscrypt/libdescrypt References: <19990921202255.B59287@enst.fr> <199909211859.UAA01197@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199909211859.UAA01197@zibbi.mikom.csir.co.za>; from John Hay on Tue, Sep 21, 1999 at 08:59:42PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 08:59:42PM +0200, John Hay wrote: > Can you explain a bit more what "apparently down" mean please? I didn't manage to connect on it by ftp when I sent the previous message. Apparently I haven't waited long enough: connectivity between France and this machine is just dreadfully slow. That's why I tried ping which makes checking easier than FTP, but I didn't know ping is filtered for this machine. > It seems up to me. I'm logged in on it at the moment and did an It's up for me too now, but it's extremely sloooooow. I get FTP timeouts 3 times out of 4. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 12:44:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.145.150.20]) by hub.freebsd.org (Postfix) with ESMTP id 8D35A15C3C for ; Tue, 21 Sep 1999 12:44:16 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by users.anet-stl.com (8.9.3/8.8.5) with SMTP id OAA71007; Tue, 21 Sep 1999 14:43:55 -0500 (CDT) Date: Tue, 21 Sep 1999 14:43:55 -0500 (CDT) From: Jason Young Reply-To: Jason Young To: Mark Hittinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage In-Reply-To: <199909201938.OAA20652@freebsd.netcom.com.> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ie0: unknown board_id: f000 > 1 3C5x9 board(s) on ISA found at 0x300 > ep0 at port 0x300-0x30f irq 10 on isa0 > ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e > isa_compat: didn't get ports for le > isa_compat: didn't get ports for cs > unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > ep0 XXX: driver didn't set ifq_maxlen > changing root device to wd0s1a > > Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing > this in stand alone eliminates other issues. When debugging it pays to do > that. I think that the PNP code is finding your 3C509 and doing things with it, like, moving its resources around. That's your unknown0 device. Try disabling PNP in your kernel or PNP on your card with the DOS utility. > Guess I made the mistake of misreading a request that came through > freebsd-current a few days ago asking for any problem reports with ep0. > My mistake - sorry - I shall return to lurking. I think David was joking with you, hence the \begin{wpaul} statement. Bill Paul is of course our resident Ethernet driver guy, and he is not known for his patience with people who do not supply enough information. :) Jason Young accessUS Chief Network Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 12:54:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CF09115F3B for ; Tue, 21 Sep 1999 12:53:17 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA21135 for current@freebsd.org; Tue, 21 Sep 1999 21:53:16 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909211953.VAA21135@freebsd.dk> Subject: UPDATE10: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Tue, 21 Sep 1999 21:53:16 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ten'th update to the new ATA/ATAPI driver: It been awhile since the last major update, as a benefit there are some cool things in this one (and new bugs probably :) )... The ATA driver has grown "real" timeout support for all devices. This means that it should be possible to get in contact with (especially) lost ATAPI devices. It also means that the ATA driver is now usable on notebooks as it will DTRT on resume. An experimental hack at utilizing the Promise66's at UDMA66 is in there, but I cant test it. If someone feels like sending me one, give me a ping. The ATAPI DMA enableling scheme has been changed, also better DMA support for the Aladdin chipset has been implemented for ATAPI devices. Note that the Aladdin apparently only can do DMA reads on ATAPI devices, and the Promise cant do ATAPI DMA at all. I have seen problems on some ATAPI devices that should be able to run in DMA mode, so if you encounter problems with hanging atapi devices during the probe, or during access, disable DMA in atapi-all.c, and let me know. It might be nessesary to do this via a "white list" for known good devices... The ATAPI CDROM driver can now use eject/close without hanging and the bug that caused reading beyond the end of a CD has been fixed. Media change is also handled proberly. DVD drives are identified and are usable as CDROM devices at least, I dont have the HW to test this further, see above :). The ATAPI tape driver has gotten some support for using the DSC method for not blocking the IDE channel during read/write when the device has full buffers. It knows about the OnStream DI-30 device, support is not completed yet, but it can function as a primitive backup medium, without filemarks, and without bad media handeling. This is because the OnStream device doesn't handle this (like everybody else) in HW. It also now supports getting/setting the record position on devices that supports it. Some rather major cleanups and rearrangements as well (cvs -b diff is your freind). I'm closing in on declaring this for beta code, most of the infrastruture is in place by now. As usual USE AT YOUR OWN RISK!!, this is still alpha level code. This driver can hose your disk real bad if anything goes wrong, but now you have been warned :) But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 14: 1: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [195.133.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 0F9AA16028 for ; Tue, 21 Sep 1999 13:56:05 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id AAA42042 for current@freebsd.org; Wed, 22 Sep 1999 00:56:04 +0400 (MSD) (envelope-from ache) Date: Wed, 22 Sep 1999 00:56:03 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Repository copy request Message-ID: <19990922005603.A42010@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody who control CVS tree please copy /usr/src/contrib/groff/troff/hyphen.us-ru to /usr/src/contrib/groff/tmac/locale/hyphen.us-ru and /usr/src/usr.sbin/lpr/filters.ru/koi2alt.c to /usr/src/usr.sbin/lpr/filters.ru/koi2alt/koi2alt.c Thanx in advance. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 15:51:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from fasterix.frmug.org (d092.paris-89.cybercable.fr [212.198.89.92]) by hub.freebsd.org (Postfix) with ESMTP id 7244915715 for ; Tue, 21 Sep 1999 15:51:28 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.3/8.9.3/pb-19990315) id AAA63819; Wed, 22 Sep 1999 00:51:20 +0200 (CEST) Message-ID: <19990922005119.A63739@fasterix.frmug.fr.net> Date: Wed, 22 Sep 1999 00:51:19 +0200 From: Pierre Beyssac To: Pierre Beyssac , chris@calldei.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: top and w breakage References: <19990921191147.A63436@enst.fr> <19990921133002.C5457@holly.calldei.com> <19990921204007.A65110@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19990921204007.A65110@enst.fr>; from Pierre Beyssac on Tue, Sep 21, 1999 at 08:40:07PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 08:40:07PM +0200, Pierre Beyssac wrote: > Sorry I was unclear, yes: a full buildworld+installworld+new kernel > (the same installworld that broke login and friends for me). This > includes kernel modules of course. > Something more (probably unrelated): when I exit top with ^C, I > have a SIGSEGV there: Following up: top seems to work ok for me now (-current from tonight), as well as 'w'. I certainly have made something wrong somewhere. Sorry for the false alarm... -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 17:25:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id DD8A914BD8; Tue, 21 Sep 1999 17:25:09 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA25595; Tue, 21 Sep 1999 20:25:08 -0400 (EDT) (envelope-from luoqi) Date: Tue, 21 Sep 1999 20:25:08 -0400 (EDT) From: Luoqi Chen Message-Id: <199909220025.UAA25595@lor.watermarkgroup.com> To: current@FreeBSD.ORG, phk@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Testers please! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > This reminds me about the usage of TSC counter on SMP. First even though we don't use TSC for time keeping on SMP, the TSC frequency from calibration is still valid (at least for BSP), and we can show it in the cpu identification message. Second, the listed reason for not using TSC on SMP is the inability to synchronize TSCs on all cpus. My question is, is it really necessary? TSC is initialized to 0 at hardware reset, which should happen to all CPUs at the same time (invalid assumption?), in another words, all TSCs should be automatically synchronized. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 18:24:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 54FB515094 for ; Tue, 21 Sep 1999 18:24:45 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall (arc0a326.bf.sover.net [209.198.83.234]) by megadodo.segNET.COM (8.9.1a/8.8.5) with SMTP id VAA17627 for ; Tue, 21 Sep 1999 21:24:43 -0400 (EDT) Message-ID: <001301bf04b2$f0a813e0$0100a8c0@digitalspark.net> From: "Adam Strohl" To: References: <199909220025.UAA25595@lor.watermarkgroup.com> Subject: libcrypt issue upgraded to "Fiasco" status ;'D Date: Tue, 21 Sep 1999 21:28:33 -0700 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 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rebuilt world and kernel about 20 minutes ago, now XDM cores, along with login, I've had to fall back to single user mode, whoever is workin' on this let me know if you commit some fixes, I'll be awake for a few hours and I'd love to test them (read as "love to have my box working again" ;'D). -- Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 19:41:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2BB0014A0F for ; Tue, 21 Sep 1999 19:40:24 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 421791CA7; Wed, 22 Sep 1999 10:40:22 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Young Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage In-reply-to: Your message of "Tue, 21 Sep 1999 14:43:55 EST." Date: Wed, 22 Sep 1999 10:40:22 +0800 From: Peter Wemm Message-Id: <19990922024022.421791CA7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Young wrote: > > > ie0: unknown board_id: f000 > > 1 3C5x9 board(s) on ISA found at 0x300 > > ep0 at port 0x300-0x30f irq 10 on isa0 > > ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e > > isa_compat: didn't get ports for le > > isa_compat: didn't get ports for cs > > unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep0 XXX: driver didn't set ifq_maxlen > > changing root device to wd0s1a > > > > Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing > > this in stand alone eliminates other issues. When debugging it pays to do > > that. > > I think that the PNP code is finding your 3C509 and doing things with it, > like, moving its resources around. That's your unknown0 device. Try > disabling PNP in your kernel or PNP on your card with the DOS utility. No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc and just have "device ep0" *only*. If the pnp code finds it, let it use pnp to configure it. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 20:13:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 58ECF14EF0; Tue, 21 Sep 1999 20:13:39 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id XAA14018; Tue, 21 Sep 1999 23:13:42 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 21 Sep 1999 23:13:36 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Luoqi Chen Cc: current@FreeBSD.org, phk@FreeBSD.org, smp@FreeBSD.org Subject: Re: Testers please! In-Reply-To: <199909220025.UAA25595@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Sep 1999, Luoqi Chen wrote: > This reminds me about the usage of TSC counter on SMP. First even though > we don't use TSC for time keeping on SMP, the TSC frequency from calibration > is still valid (at least for BSP), and we can show it in the cpu identification > message. Second, the listed reason for not using TSC on SMP is the inability > to synchronize TSCs on all cpus. My question is, is it really necessary? > TSC is initialized to 0 at hardware reset, which should happen to all CPUs > at the same time (invalid assumption?), in another words, all TSCs should be > automatically synchronized. ISTRT something I did long ago was kill the TSC reset FreeBSD did, so there should be no reason that they won't be all at the same place. I am willing to bet half my farm that the biggest problem was that we did that, and barring that we could have always done SMP using the TSC. One question comes to mind: is there a way that the TSCs could become desynchronized somehow? Even though all CPUs run at the same frequency, isn't there a strong possibility for slight frequency deviation since we use crystal oscillation instead of a more accurate atomic breakdown for regulation, or am I just smoking crack? > > -lq > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 21: 0:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 3F8BF15B4C; Tue, 21 Sep 1999 21:00:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA10049; Tue, 21 Sep 1999 20:53:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909220353.UAA10049@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Brian F. Feldman" Cc: Luoqi Chen , current@FreeBSD.org, phk@FreeBSD.org, smp@FreeBSD.org Subject: Re: Testers please! In-reply-to: Your message of "Tue, 21 Sep 1999 23:13:36 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Sep 1999 20:53:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One question comes to mind: is there a way that the TSCs could become > desynchronized somehow? Even though all CPUs run at the same frequency, > isn't there a strong possibility for slight frequency deviation since > we use crystal oscillation instead of a more accurate atomic breakdown > for regulation, or am I just smoking crack? They should all be using the same clock source, so that's not an issue. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 21 22:56:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ECB9C14D83; Tue, 21 Sep 1999 22:56:21 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA32779; Wed, 22 Sep 1999 07:55:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Testers please! In-reply-to: Your message of "Tue, 21 Sep 1999 20:25:08 EDT." <199909220025.UAA25595@lor.watermarkgroup.com> Date: Wed, 22 Sep 1999 07:55:36 +0200 Message-ID: <32777.937979736@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909220025.UAA25595@lor.watermarkgroup.com>, Luoqi Chen writes: >Second, the listed reason for not using TSC on SMP is the inability >to synchronize TSCs on all cpus. My question is, is it really necessary? Strictly speaking no, it isn't necessary, but unless they are in sync the timekeeping code gets very complex. See Dave "ntp" Mills code to hold them in sync. >TSC is initialized to 0 at hardware reset, which should happen to all CPUs >at the same time (invalid assumption?), in another words, all TSCs should be >automatically synchronized. They are not. The PLL is local to each cpu and every single clock-stop/start event has then inching away from each other because the on-chip VCO is very temperature dependent. Furthermore Linux people have found sufficiently many cases where the counters are not in sync after the BIOS is done. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 2:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8873C150FD for ; Wed, 22 Sep 1999 02:55:36 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 31700 invoked from network); 22 Sep 1999 09:55:33 -0000 Received: from d135.syd2.zeta.org.au (203.26.9.7) by gidora.zeta.org.au with SMTP; 22 Sep 1999 09:55:33 -0000 Date: Wed, 22 Sep 1999 19:55:26 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: request for review, patch to specfs to fix EOF condition alignment with buffer In-Reply-To: <199909201919.MAA83623@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a request for a review. This patch fixes a bug in specfs > relating to dealing with the EOF condition of a block device. > > If the EOF occurs in the middle of a block, specfs was not > properly calculating the truncation for the I/O. I didn't have time to review this properly when you first asked. It is a bit over-commented, and returns wrong error codes for EOF. > Index: miscfs/specfs/spec_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v > retrieving revision 1.108 > diff -u -r1.108 spec_vnops.c > --- spec_vnops.c 1999/09/17 06:10:26 1.108 > +++ spec_vnops.c 1999/09/20 17:50:48 > @@ -311,19 +311,37 @@ > do { > bn = btodb(uio->uio_offset) & ~(bscale - 1); > on = uio->uio_offset % bsize; > - n = min((unsigned)(bsize - on), uio->uio_resid); > if (seqcount > 1) { > nextbn = bn + bscale; > error = breadn(vp, bn, (int)bsize, &nextbn, > (int *)&bsize, 1, NOCRED, &bp); > } else { > error = bread(vp, bn, (int)bsize, NOCRED, &bp); > + } > + > + /* > + * Figure out how much of the buffer is valid relative > + * to our offset into the buffer, which may be negative > + * if we are beyond the EOF. > + * > + * The valid size of the buffer is based on > + * bp->b_bcount (which may have been truncated by > + * dscheck or the device) minus bp->b_resid, which > + * may be indicative of an I/O error if non-zero. > + */ The short read must have been caused by EOF unless error != 0. Note that filesystems depend on this, i.e., the following handling in VOP_STRATEGY(): Case 1: do some i/o (possibly null), then hit an i/o error: Return the amount not done in b_resid, and set B_ERROR to indicate that i/o was truncated because of an error. Case 2: do some i/o (possibly null), then hit EOF: Return the amount not done in b_resid, and don't touch B_ERROR. Some drivers change b_bcount, but this is dubious, especially for writes where the data beyond b_bcount is still valid and something may be using it. ffs handles these cases as follows: Case 1: Throw away the partial block. Depend on VOP_STRATEGY() setting B_ERROR so that bread()/bwrite()/etc. return nonzero in this case. Case 2: Assume that this case can't happen for metadata (a reasonable assumption, since filesystems don't use blocks beyond EOF), and don't check for it. Similarly for VOP_WRITE(). Handle it in VOP_READ(), although I think it can't happen there either. specfs (for bdevs) currently handle these cases like ffs. Short counts are only handled for Case 2. physio() handles the cases like VOP_STRATEGY(). It passes the distinction bewtween EOF and error to its caller by returning nonzero only if there was an error. (Distinguishing the cases is especially important for write-once devices.) Control eventually reaches the level dofileread(), etc., where the distinction is screwed up :-( (`error' is only reset to 0 for nonzero short counts if it is ERESTART, EINTR or EWOULDBLOCK). > + n = bp->b_bcount - on; > + if (n < 0) { > + error = EINVAL; `error' shouldn't be changed here if it is already nonzero. EINVAL is a wrong value to return for EOF here (but neccessary to give bug for bug compatibility here). See the comment in my version. > + } else { > + n -= bp->b_resid; > + if (n < 0) > + error = EIO; EIO is a wronger value to return for EOF. Here are my fixes (relative to the old version) for spec_read(). They are over-commented to temporarily document the buggy EOF return code. --- diff -c2 spec_vnops.c~ spec_vnops.c *** spec_vnops.c~ Sat Sep 11 15:54:39 1999 --- spec_vnops.c Wed Sep 22 19:47:52 1999 *************** *** 309,313 **** bn = btodb(uio->uio_offset) & ~(bscale - 1); on = uio->uio_offset % bsize; - n = min((unsigned)(bsize - on), uio->uio_resid); if (vp->v_lastr + bscale == bn) { nextbn = bn + bscale; --- 311,314 ---- *************** *** 317,325 **** error = bread(vp, bn, (int)bsize, NOCRED, &bp); vp->v_lastr = bn; - n = min(n, bsize - bp->b_resid); if (error) { brelse(bp); return (error); } error = uiomove((char *)bp->b_data + on, n, uio); brelse(bp); --- 318,343 ---- error = bread(vp, bn, (int)bsize, NOCRED, &bp); vp->v_lastr = bn; if (error) { brelse(bp); return (error); } + + /* + * The amount of valid data in the buffer is + * bp->b_bcount - bp->b_resid. If this is smaller + * than `on', return EINVAL to give bug for bug + * compatibility with physio() and with ourself + * (most strategy routines erroneously return EINVAL + * for i/o completely beyond EOF). POSIX and POLA + * specify returning 0 for reads from all offsets + * beyond EOF. + */ + n = bp->b_bcount - bp->b_resid - on; + if (n < 0) { + brelse(bp); + return (EINVAL); + } + + n = imin(n, uio->uio_resid); error = uiomove((char *)bp->b_data + on, n, uio); brelse(bp); --- I was also concerned about what happens when buffers with a short b_bcount or a nonzero b_resid are left in the cache. It seems that nothing fatal happens, but they just get in the way. I observed the following farcial handling for rereading block 4 on /dev/vn0a where /dev/vn0a has size 6: spec_read(): call bread() bread(): call getblk() getblk(): call gbincore() gb_incore(): returns the buffer successfully getblk(): The buffer has the wrong size, so it is thrown away. Do a VOP_WRITE() as part of throwing it away, although the buffer is not dirty! :-( Return an empty buffer. bread(): do a VOP_STRATEGY() to read the buffer again. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 5:21:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from pa.scotland.net (pa1.scotland.net [194.247.64.132]) by hub.freebsd.org (Postfix) with ESMTP id D910814D8F for ; Wed, 22 Sep 1999 05:21:50 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.237.140] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 2.12 #4) id 11TlP8-0003wM-00 for current@freebsd.org; Wed, 22 Sep 1999 13:21:47 +0100 Received: (qmail 11857 invoked by uid 1002); 22 Sep 1999 06:56:56 -0000 Date: Wed, 22 Sep 1999 07:56:55 +0100 From: Timo Geusch To: Peter Wemm Cc: current@freebsd.org Subject: Re: ep0 etherlink III breakage Message-ID: <19990922075655.A11837@tabby.timog.prestel.co.uk> References: <19990922024022.421791CA7@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990922024022.421791CA7@overcee.netplex.com.au>; from Peter Wemm on Wed, Sep 22, 1999 at 10:40:22AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 22, 1999 at 10:40:22AM +0800, Peter Wemm wrote: > No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc > and just have "device ep0" *only*. If the pnp code finds it, let it use > pnp to configure it. Does it do that by now? About two or three months ago it didn't and I started writing the necessary code. Now I'm just learning how to remotely debug the kernel... Cheers, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 7:39:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 5552A15240; Wed, 22 Sep 1999 07:39:28 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA05687; Wed, 22 Sep 1999 10:39:27 -0400 (EDT) (envelope-from luoqi) Date: Wed, 22 Sep 1999 10:39:27 -0400 (EDT) From: Luoqi Chen Message-Id: <199909221439.KAA05687@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, phk@critter.freebsd.dk Subject: Re: Testers please! Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >TSC is initialized to 0 at hardware reset, which should happen to all CPUs > >at the same time (invalid assumption?), in another words, all TSCs should be > >automatically synchronized. > > They are not. The PLL is local to each cpu and every single > clock-stop/start event has then inching away from each other because > the on-chip VCO is very temperature dependent. Furthermore Linux The internal clock is phase-locked to an external clock source, which should be the same bus clock and identical for all cpus. The multipliers for the internal clocks should also be identical (in almost all cases unless you design your own mother board). The highest multiplier as of today is 6x (600MHz cpu on a 100MHz bus), it might increase over time, but I expect it to be still around 10. If the PLL's accuracy is 1%, the difference between two cpus could at most be 10% (or 3% = 1% * sqrt(10), assuming a Gaussian distribution of the drift) of the internal clock cycle, that is 10% (3%) of the time you might get two different readings (differ by 1) if you read TSCs of two cpus simultaneously, that's still much more accurate than the i8254 timer. > people have found sufficiently many cases where the counters are > not in sync after the BIOS is done. > I would really like to know how they managed to read the TSCs simultaneously, or they resorted to some kind of statistical means (which I tried without much success, maybe I will try later with some kernel hooks). The multiplier is set at hard reset, so BIOS couldn't change that (some mother boards may be soft configurable, but the change has to take effect after next reset). Bus clock is external, BIOS couldn't change that either. So the internal clock is not affected by BIOS. Now it would be really hard or me to believe that TSC is not a simple counter that increments at each internal clock edge. I am very skeptical about the Linux people's findings. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 7:44: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from munin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id 0AFFA14D78 for ; Wed, 22 Sep 1999 07:44:01 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id JAA17701 for ; Wed, 22 Sep 1999 09:44:00 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <37E8EB30.639283DC@odin-corporation.com> Date: Wed, 22 Sep 1999 09:44:00 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: current@freebsd.org Subject: How to dump the stack trace for other CPU Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How does one go about dumping the stack trace for the other cpu while in ddb or gdb? This is on current. Thanks, Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 8: 8: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3F53915442; Wed, 22 Sep 1999 08:07:55 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA34338; Wed, 22 Sep 1999 17:07:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Testers please! In-reply-to: Your message of "Wed, 22 Sep 1999 10:39:27 EDT." <199909221439.KAA05687@lor.watermarkgroup.com> Date: Wed, 22 Sep 1999 17:07:10 +0200 Message-ID: <34336.938012830@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909221439.KAA05687@lor.watermarkgroup.com>, Luoqi Chen writes: >> people have found sufficiently many cases where the counters are >> not in sync after the BIOS is done. >> >I would really like to know how they managed to read the TSCs simultaneously, >or they resorted to some kind of statistical means (which I tried without >much success, maybe I will try later with some kernel hooks). The differences were pretty significant in offset, I havn't heard any numbers from them on skew, and I don't know of anybody who have tried to measure it. The trouble with N counters for N>1 is that you need to add code to synchronize AND syntonize them, you need code to make sure time is monotonic no matter what and yada yada yada. By the time you're done the i8254 doesn't look so bad after all... The ACPI counter is a good sized step in the right direction, they should have made it PCI clock driven, to get better resolution but I suspect the fact that they didn't is a sign that the PCI clock will be power munged at some point. For "general purpose" time a clock which is about the resolution of the IO busses is sufficient, the ACPI is a little low on frequency, but hey, it's miles better than the i8254, and the APM/ACPI will not fuck with it's frequency. For high resolution timing of "in-cpu" events, the TSC is still the way to go, and nothing (except SMP complexity) prevents it from being used for that, and it is probably pointless to convert the data to nanoseconds until the difference has been found in the end anyway. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 8:25:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-206.birch.net [216.212.1.206]) by hub.freebsd.org (Postfix) with ESMTP id E7CDA14D29; Wed, 22 Sep 1999 08:25:30 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id KAA28026; Wed, 22 Sep 1999 10:25:28 -0500 (CDT) From: Jim Bryant Message-Id: <199909221525.KAA28026@argus.tfs.net> Subject: Re: Testers please! In-Reply-To: from "Brian F. Feldman" at "Sep 21, 99 11:13:36 pm" To: green@FreeBSD.ORG (Brian F. Feldman) Date: Wed, 22 Sep 1999 10:25:27 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Tue, 21 Sep 1999, Luoqi Chen wrote: > > > This reminds me about the usage of TSC counter on SMP. First even though > > we don't use TSC for time keeping on SMP, the TSC frequency from calibration > > is still valid (at least for BSP), and we can show it in the cpu identification > > message. Second, the listed reason for not using TSC on SMP is the inability > > to synchronize TSCs on all cpus. My question is, is it really necessary? > > TSC is initialized to 0 at hardware reset, which should happen to all CPUs > > at the same time (invalid assumption?), in another words, all TSCs should be > > automatically synchronized. > > ISTRT something I did long ago was kill the TSC reset FreeBSD did, so > there should be no reason that they won't be all at the same place. I > am willing to bet half my farm that the biggest problem was that we > did that, and barring that we could have always done SMP using the TSC. > > One question comes to mind: is there a way that the TSCs could become > desynchronized somehow? Even though all CPUs run at the same frequency, > isn't there a strong possibility for slight frequency deviation since > we use crystal oscillation instead of a more accurate atomic breakdown > for regulation, or am I just smoking crack? time for rehab, dude. since there is only a single master clock oscillator, there really should be no frequency difference between CPUs. There is the a phase difference caused by differences in conductor lengths between the master clock and the CPUs, but this difference is fixed by the length of the conductor and the laws of physics. Granted, all crystals have drift over time and temperature, but this drift should be identical for all CPUs on the same clock bus. Ideally, motherboards should be designed to have equal length clock lines to each CPU, thus eliminating this phase difference, especially with multiple selectable clock speeds which would change the wavelength, and thus the phase difference if the lines are of differing lengths. the current price of accurate TCXOs is low enough to be economical in PCs, and these seriously reduce the drift compared to the cheezy TTL clocks currently used. speaking of atomic breakdown... they could start making cheaper cesium-beam tubes given the current level of the nuclear waste issue if they felt like it, provided some kind of untamperable enclosure can be built [30 year half life, biologically behaves like potassium and goes straight for the muscle, 200 day biological half-time]. let's not bury nuclear waste, let's put it to use IN PCs! even then, such a clock would only act as a reference filter to correct a running oscillator. Cesium beam tubes are essentially extremely accurate narrow bandwidth filters, and not oscillators. with russia having made two seperate threats of aggression to destroy the entire planet with nuclear weapons in the past twelve months [MAD is still a policy, they launch, everybody launches], GPS/GOES is not a good idea for clock synchronization. an EMP pulse would take the sats out, but then many computers would be zapped at the same time anyhow, thus making this a moot point for anything that is plugged in at the time or has cables attached at the time. [this is not intended to be a political statement, nor am i bashing common russians, this is just a reality check]. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 9: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id B169614F64 for ; Wed, 22 Sep 1999 09:00:28 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.9.3/8.9.3) id MAA49804; Wed, 22 Sep 1999 12:00:27 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14312.64794.754661.861916@trooper.velocet.ca> Date: Wed, 22 Sep 1999 12:00:26 -0400 (EDT) To: freebsd-current@freebsd.org Subject: make release failing? X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting 100's of these messages and then a failure of 'make release': /usr/local/bin/jade:/usr/doc/ru_RU.KOI8-R/books/faq/book.sgml:9161:12:E: unexpected element name: QUESTION /usr/local/bin/jade:/usr/doc/ru_RU.KOI8-R/books/faq/book.sgml:9162:75:E: unexpected element name: ANSWER I tried blowing my source tree away and then cvsup'ing RELENG_3_3_0_RELEASE, but I still get this error. Any ideas? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 9:53:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 00FAE14BC5; Wed, 22 Sep 1999 09:53:15 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA66241; Wed, 22 Sep 1999 09:52:40 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909221652.JAA66241@gndrsh.dnsmgr.net> Subject: Re: Testers please! In-Reply-To: <199909221525.KAA28026@argus.tfs.net> from Jim Bryant at "Sep 22, 1999 10:25:27 am" To: jbryant@tfs.net Date: Wed, 22 Sep 1999 09:52:40 -0700 (PDT) Cc: green@FreeBSD.ORG (Brian F. Feldman), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > One question comes to mind: is there a way that the TSCs could become > > desynchronized somehow? Even though all CPUs run at the same frequency, > > isn't there a strong possibility for slight frequency deviation since > > we use crystal oscillation instead of a more accurate atomic breakdown > > for regulation, or am I just smoking crack? > > time for rehab, dude. > > since there is only a single master clock oscillator, there really > should be no frequency difference between CPUs. There is the a phase > difference caused by differences in conductor lengths between the > master clock and the CPUs, but this difference is fixed by the length > of the conductor and the laws of physics. Granted, all crystals have > drift over time and temperature, but this drift should be identical > for all CPUs on the same clock bus. Ideally, motherboards should be > designed to have equal length clock lines to each CPU, thus > eliminating this phase difference, especially with multiple selectable > clock speeds which would change the wavelength, and thus the phase > difference if the lines are of differing lengths. And I would suspect if some one was to go look at the layout requirements in Intel's design data for SMP boards you would find it is a requirement that all CPU's in an SMP system have a very minimal phase skew in the clock driven to the chip. How else are you going to run in sync with the shared processor bus. I suspect that the allowed margin on the phase of the clock pin is specified in pico seconds, and probably near 50 or so, given the 100Mhz nature of this signal. 73 to KC5VDJ, KD7CAX -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 9:57:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BF74914E06 for ; Wed, 22 Sep 1999 09:57:48 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA38698; Wed, 22 Sep 1999 09:57:39 -0700 (PDT) Date: Wed, 22 Sep 1999 09:57:42 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Bruce Evans Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: request for review, patch to specfs to fix EOF condition alignment with buffer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Sep 1999, Bruce Evans wrote: > > This is a request for a review. This patch fixes a bug in specfs > > It is a bit over-commented, and returns wrong error codes for EOF. This is certainly not over commented in my opinion. I wish more people would comment as much as Matt does. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 11: 6:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4F7C314CB9 for ; Wed, 22 Sep 1999 11:06:49 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-3-24.ucdavis.edu [169.237.17.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA77718; Wed, 22 Sep 1999 11:06:47 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA46153; Wed, 22 Sep 1999 11:06:45 -0700 (PDT) (envelope-from obrien) Date: Wed, 22 Sep 1999 11:06:43 -0700 From: "David O'Brien" To: Jason Young Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: ep0 etherlink III breakage Message-ID: <19990922110642.A45531@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199909201938.OAA20652@freebsd.netcom.com.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think David was joking with you, hence the \begin{wpaul} statement. Bill > Paul is of course our resident Ethernet driver guy, and he is not known > for his patience with people who do not supply enough information. :) Only 1/2 joking. This seems to be my month for content free bug reports. I would also expect a computer professional (especially one running -CURRENT) to understand what a bug report is and what should be contained in one. Gezz, am I the only one that has had to do system administration before? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 11:10:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6203B157EC for ; Wed, 22 Sep 1999 11:10:29 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (IDENT:root@iras-3-24.ucdavis.edu [169.237.17.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA77739; Wed, 22 Sep 1999 11:10:27 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA46176; Wed, 22 Sep 1999 11:10:26 -0700 (PDT) (envelope-from obrien) Date: Wed, 22 Sep 1999 11:10:24 -0700 From: "David O'Brien" To: Mark Hittinger Cc: freebsd-current@freebsd.org Subject: Re: ep0 etherlink III breakage Message-ID: <19990922111024.B45531@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199909201938.OAA20652@freebsd.netcom.com.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909201938.OAA20652@freebsd.netcom.com.> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually I don't really care what you do with this. I did say "more later" > but you chopped that part out. I was only trying to give a heads up. Then way waste people's time with content-free messages? Just to lower the signal-to-noise ratio? We all could have waited for this email. > Guess I made the mistake of misreading a request that came through > freebsd-current a few days ago asking for any problem reports with ep0. Yes report problems. That means giving enough details that someone can figure out what is going on. I guess I'm the only one that has ever been in a position where I had to fix others' problems from their description of the problem. > Mindspring/Netcom/Dallas > bugs@freebsd.netcom.com I guess what really thru me off was this email address -- I assumed you were a system administrator. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 11:10:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 84286157B5; Wed, 22 Sep 1999 11:10:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA34760; Wed, 22 Sep 1999 20:09:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: jbryant@tfs.net Cc: green@FreeBSD.ORG (Brian F. Feldman), freebsd-current@FreeBSD.ORG Subject: Re: Testers please! In-reply-to: Your message of "Wed, 22 Sep 1999 10:25:27 CDT." <199909221525.KAA28026@argus.tfs.net> Date: Wed, 22 Sep 1999 20:09:08 +0200 Message-ID: <34758.938023748@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909221525.KAA28026@argus.tfs.net>, Jim Bryant writes: >since there is only a single master clock oscillator, there really >should be no frequency difference between CPUs. As long it runs constantly: yes. As soon as you have clock-stop events you will have different resync times for the on-chip PLLs. >Ideally, motherboards should be >designed to have equal length clock lines to each CPU, They are, but that doesn't mean that the PLL'ed core frequencies are in lockstep when the clocks change. >the current price of accurate TCXOs is low enough to be economical in >PCs, and these seriously reduce the drift compared to the cheezy TTL >clocks currently used. There are no cheesy TTL clocks used. There are random encapsulated rock with pretty high-quality drive circuitry and PLL generation of all sorts of other frequencies. >speaking of atomic breakdown... they could start making cheaper >cesium-beam tubes given the current level of the nuclear waste issue The actual amount of Cs in the Cesium unit has no cost impact. There are man components of a Cs unit which carry significantly higher pricetags than the few grammes of Cs. A un-optimally constructed Cs is worse than a low-cost Rb unit. >Cesium beam tubes are essentially extremely accurate >narrow bandwidth filters, and not oscillators. It is neither. >with russia having made two seperate threats of aggression to destroy >the entire planet with nuclear weapons in the past twelve months [...] Lets not get too far from the topic, OK ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 11:51:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 71D8714FF0 for ; Wed, 22 Sep 1999 11:51:22 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-c1s3-43.mfi.net [209.26.94.136]) by pawn.primelocation.net (Postfix) with ESMTP id A8A9EF80F for ; Wed, 22 Sep 1999 14:51:20 -0400 (EDT) Date: Wed, 22 Sep 1999 14:51:20 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: current@freebsd.org Subject: aha driver disabled? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsupping yesterday (last cvsup was at the beginning of the month), I found that my AHA-1542CP was no longer being seen/probed. I've traced it down to the following: RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v Working file: src/sys/i386/isa/isa_compat.h head: 1.12 description: ---------------------------- revision 1.12 date: 1999/09/07 08:42:47; author: dfr; state: Exp; lines: +1 -6 Change isa_get/set_flags() to device_get/set_flags(). - * $FreeBSD: src/sys/i386/isa/isa_compat.h,v 1.11 1999/09/03 19:15:13 peter Exp $ + * $FreeBSD: src/sys/i386/isa/isa_compat.h,v 1.12 1999/09/07 08:42:47 dfr Exp $ */ #include "vt.h" @@ -99,7 +99,6 @@ extern struct isa_driver vtdriver; extern struct isa_driver advdriver; -extern struct isa_driver ahadriver; extern struct isa_driver wdcdriver; extern struct isa_driver msedriver; extern struct isa_driver ardriver; @@ -311,10 +310,6 @@ #if NADV > 0 { INTR_TYPE_CAM, &advdriver }, #endif -#endif - -#if NAHA > 0 - { INTR_TYPE_CAM, &ahadriver }, #endif If I reverse the above, the card seems to work fine again. I'm just wondering if this was intentional and/or if the driver will be reenabled again [soon]. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 12:23:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B167F158E6 for ; Wed, 22 Sep 1999 12:23:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA03428; Wed, 22 Sep 1999 13:23:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA34735; Wed, 22 Sep 1999 13:23:31 -0600 (MDT) Message-Id: <199909221923.NAA34735@harmony.village.org> To: "Chris D. Faulhaber" Subject: Re: aha driver disabled? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Sep 1999 14:51:20 EDT." References: Date: Wed, 22 Sep 1999 13:23:31 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Chris D. Faulhaber" writes: : If I reverse the above, the card seems to work fine again. I'm just : wondering if this was intentional and/or if the driver will be reenabled : again [soon]. Doug Rabson sent me patches to make aha work with the new pnp code. However, on the two cards I tried it on i hit errors. I haven't had the time to follow up on those errors so I haven't committed them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 14:42:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 58E7014E9A for ; Wed, 22 Sep 1999 14:42:01 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id RAA00289 for ; Wed, 22 Sep 1999 17:41:16 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Wed, 22 Sep 1999 17:41:16 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: sb0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some reason, after cvsupping about 5 minutes ago, and rebuilding a kernel, the sb0 device no longer works. it gives me this error: dscheck(#wd/0x20002): b_blkno 32256 is not on a sector boundary (ssize 1) Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 23: 6:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix13.ix.netcom.com (dfw-ix13.ix.netcom.com [206.214.98.13]) by hub.freebsd.org (Postfix) with ESMTP id 072F814F80 for ; Wed, 22 Sep 1999 23:06:16 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from smap@localhost) by dfw-ix13.ix.netcom.com (8.8.4/8.8.4) id BAA07156 for ; Thu, 23 Sep 1999 01:06:05 -0500 (CDT) Received: from sil-wa16-22.ix.netcom.com(207.93.148.150) by dfw-ix13.ix.netcom.com via smap (V1.3) id rma007060; Thu Sep 23 01:05:17 1999 Message-ID: <37E9C266.2F76@ix.netcom.com> Date: Wed, 22 Sep 1999 23:02:15 -0700 From: "Thomas D. Dean" Reply-To: tomdean@ix.netcom.com Organization: Home X-Mailer: Mozilla 3.04 (WinNT; I) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: bounced mail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may be off subject. I am seeing bounced mail from -current since this evening. The message is: <<< 550 service unavailable; [207.93.148.150] blocked using \ dul.maps.vix.com I tried disconnecting from my ISP and redialing to change the IP. Same results. My ISP, netcom (now mindspring) has no idea. Is FreeBSD blocking? I am running -current as of 25 August. I made no config changes. uptime is 28 days. I did a cvsup today and attempted a make world. This failed, in libdes, trying to install des.h from /usr/src/crypto, which does not exist. The make world should not have effected the system. sendmail is dated 8/25. The config files have not changed. any ideas? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 23: 9:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 5DE1514EC4 for ; Wed, 22 Sep 1999 23:09:15 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FII007A0136C7@mta4.rcsntx.swbell.net> for freebsd-current@FreeBSD.ORG; Thu, 23 Sep 1999 01:09:10 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id BAA15273; Thu, 23 Sep 1999 01:09:19 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Thu, 23 Sep 1999 01:09:18 -0500 From: Chris Costello Subject: Re: bounced mail In-reply-to: <37E9C266.2F76@ix.netcom.com> To: "Thomas D. Dean" Cc: freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19990923010918.O5457@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.6i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <37E9C266.2F76@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 22, 1999, Thomas D. Dean wrote: > <<< 550 service unavailable; [207.93.148.150] blocked using \ > dul.maps.vix.com It's rather obvious that your IP address, which is a dial-up, is blocked via the MAPS Dialup Users List (DUL). Please configure your MTA to use Netcom's SMTP relay as your smart-relay. And this is, indeed, an off-topic thread. -- |Chris Costello |Avoid temporary variables and strange women. `-------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 22 23:53:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix4.ix.netcom.com (dfw-ix4.ix.netcom.com [206.214.98.4]) by hub.freebsd.org (Postfix) with ESMTP id 8313815516 for ; Wed, 22 Sep 1999 23:53:10 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from smap@localhost) by dfw-ix4.ix.netcom.com (8.8.4/8.8.4) id BAA03493 for ; Thu, 23 Sep 1999 01:53:07 -0500 (CDT) Received: from smx-ca16-22.ix.netcom.com(207.93.148.150) by dfw-ix4.ix.netcom.com via smap (V1.3) id rma003463; Thu Sep 23 01:52:57 1999 Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id XAA14481; Wed, 22 Sep 1999 23:52:54 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Wed, 22 Sep 1999 23:52:54 -0700 (PDT) Message-Id: <199909230652.XAA14481@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Make World Broken? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup this evening. make world failed. /usr/src/crypto does not exist. tomdean ========= make world output ========== cd /usr/src/gnu/lib/libdialog; /usr/obj/usr/src/tmp/usr/bin/make beforeinstall install -C -o root -g wheel -m 444 /usr/src/gnu/lib/libdialog/dialog.h /usr/obj/usr/src/tmp/usr/include cd /usr/src/gnu/lib/libgmp; /usr/obj/usr/src/tmp/usr/bin/make beforeinstall install -C -o root -g wheel -m 444 /usr/src/gnu/lib/libgmp/../../../contrib/libgmp/gmp.h /usr/obj/usr/src/tmp/usr/include cd /usr/src/gnu/usr.bin/cc/cc1plus; /usr/obj/usr/src/tmp/usr/bin/make beforeinstall install -C -o root -g wheel -m 444 /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/egcs/gcc/cp/inc/exception /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/egcs/gcc/cp/inc/new /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/egcs/gcc/cp/inc/new.h /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/egcs/gcc/cp/inc/typeinfo /usr/obj/usr/src/tmp/usr/include/g++ cd /usr/src/secure/lib/libdes; /usr/obj/usr/src/tmp/usr/bin/make beforeinstall install -C -o root -g wheel -m 444 /usr/src/secure/lib/libdes/../../../crypto/libdes/des.h /usr/obj/usr/src/tmp/usr/include install: /usr/src/secure/lib/libdes/../../../crypto/libdes/des.h: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 2:16:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A939014E00 for ; Thu, 23 Sep 1999 02:16:14 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11U4z0-0000lU-00; Thu, 23 Sep 1999 11:16:06 +0200 From: Sheldon Hearn To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make World Broken? In-reply-to: Your message of "Wed, 22 Sep 1999 23:52:54 MST." <199909230652.XAA14481@ix.netcom.com> Date: Thu, 23 Sep 1999 11:16:06 +0200 Message-ID: <2943.938078166@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Sep 1999 23:52:54 MST, Thomas Dean wrote: > cvsup this evening. make world failed. /usr/src/crypto does not exist. Nope, no problem (well, apart from a few momentarily pending repo-copies which are resolved now). A lot of stuff moved from secure to crypto, so mebbe check which collections cvsup pulls down? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 2:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 409B915A19 for ; Thu, 23 Sep 1999 02:25:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id CAA23816; Thu, 23 Sep 1999 02:25:26 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 02:25:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199909230925.CAA23816@apollo.backplane.com> To: current@freebsd.org Subject: CCD update committed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a bunch of fixes and enhancements to CCD. I do not believe I've messed anything up but CCD is rather messy so I'm doing a little head's up anyway. * CCD panic when underlying storage has a sector size larger then 1K fixed. * CCD lockup when dd'ing from the raw ccd device using a block size that causes the CCD partition's EOF to occur in the middle of an I/O fixed. * CCD complains to dmesg (but does not yet cause a configuration failure) if you try to use a mirror with an interleave of 0. * MIRRORing code enhanced: - When reading, CCD will issue the read from either side of the mirror. CCD now implements a zone selector to try to optimize which disk is selected based on seek proximity. - If a read error occurs, CCD will automatically try to recover by reading from the other side of the mirror. If this also fails, the read error is propogated back. Note that CCD's mirroring has never been and still does not use any formal recovery mechanisms. You cannot replace a disk in the mirror and expect to get something coherent out of it. You can turn off a disk in the mirror by unmounting the CCD and reconfiguring it without the mirror disks as a non-mirror CCD, but that's about it. Replacing a bad disk effectively requires backing up the good one, replacing the disk, and then regenerating (to be safe) both disks from the backup. The parity stuff never worked and probably never will. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4: 1:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.199.mpoweredpc.net [142.177.203.199]) by hub.freebsd.org (Postfix) with ESMTP id F0246154E9 for ; Thu, 23 Sep 1999 04:01:45 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id IAA09686 for ; Thu, 23 Sep 1999 08:00:50 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 23 Sep 1999 08:00:50 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: gcc optimizer in -current system ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just curious, but what is the max setting that can be used to compile the kernel? looking through the man page, I can do something like: -O3 -march=pentium and, if I'm reading the man page right: -mcpu=cpu type Assume the defaults for the machine type CPU TYPE when scheduling instructions. The choices for CPU TYPE are: i386, i486, i586 (pentium), pentium, i686 (pentiumpro), and pentiumpro. While picking a spe- cific CPU TYPE will schedule things appropriately for that particular chip, the compiler will not generate any code that does not run on the i386 without the -march=cpu type option being used. -march=cpu type Generate instructions for the machine type CPU TYPE. The choices for CPU TYPE are: i386, i486, pentium, and pentiumpro. Specifying -march=cpu type implies -mcpu=cpu type. it will generate code that wouldn't run on an i386, but is totally optimized for a pentium? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:13:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D7A8614DA7 for ; Thu, 23 Sep 1999 04:13:21 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11U6nY-0001MR-00; Thu, 23 Sep 1999 13:12:24 +0200 From: Sheldon Hearn To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-reply-to: Your message of "Thu, 23 Sep 1999 08:00:50 -0300." Date: Thu, 23 Sep 1999 13:12:24 +0200 Message-ID: <5234.938085144@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999 08:00:50 -0300, The Hermit Hacker wrote: > just curious, but what is the max setting that can be used to compile the > kernel? -O Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:25:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.199.mpoweredpc.net [142.177.203.199]) by hub.freebsd.org (Postfix) with ESMTP id 495F814D91 for ; Thu, 23 Sep 1999 04:25:06 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id IAA00444; Thu, 23 Sep 1999 08:23:09 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 23 Sep 1999 08:23:09 -0300 (ADT) From: The Hermit Hacker To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <5234.938085144@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Sheldon Hearn wrote: > > > On Thu, 23 Sep 1999 08:00:50 -0300, The Hermit Hacker wrote: > > > just curious, but what is the max setting that can be used to compile the > > kernel? > > -O well, I just did -O3 -mpentium, and it both compiled cleanly, and appears to be running okay, so is -O the max that makes a difference, or...? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A9ABB15025 for ; Thu, 23 Sep 1999 04:25:54 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11U6za-0001SD-00; Thu, 23 Sep 1999 13:24:50 +0200 From: Sheldon Hearn To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-reply-to: Your message of "Thu, 23 Sep 1999 08:23:09 -0300." Date: Thu, 23 Sep 1999 13:24:50 +0200 Message-ID: <5592.938085890@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999 08:23:09 -0300, The Hermit Hacker wrote: > well, I just did -O3 -mpentium, and it both compiled cleanly, and appears > to be running okay, so is -O the max that makes a difference, or...? Or... Try build world with that kernel running. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:44: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 93EFA15025 for ; Thu, 23 Sep 1999 04:44:04 -0700 (PDT) (envelope-from bsd@picard.mandrakesoft.de) Received: from picard.mandrakesoft.de (root@picard.mandrakesoft.de [151.189.96.131]) by relay.pair.com (8.8.7/8.8.5) with ESMTP id HAA03721; Thu, 23 Sep 1999 07:19:36 -0400 (EDT) From: bsd@picard.mandrakesoft.de Received: from localhost (bsd@localhost) by picard.mandrakesoft.de (8.9.3/8.9.3) with ESMTP id NAA02711; Thu, 23 Sep 1999 13:21:49 +0200 Date: Thu, 23 Sep 1999 13:21:49 +0200 (CEST) To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, The Hermit Hacker wrote: > just curious, but what is the max setting that can be used to compile the > kernel? Works rather nicely here with -O6 -mpentiumpro -march=pentiumpro -pipe -s -fexpensive-optimizations -ffast-math LLaP bero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id D83E515025 for ; Thu, 23 Sep 1999 04:45:59 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id NAA04452; Thu, 23 Sep 1999 13:44:05 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id NAA10452; Thu, 23 Sep 1999 13:44:05 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:Y+DX+3nBCp5WKhnhu2fW+vaX57OSW3yH@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/8.9.1/wjp-SVR4/1998063000) with ESMTP id NAA04911; Thu, 23 Sep 1999 13:44:00 +0200 (CEST) Message-Id: <199909231144.NAA04911@wurzelausix.cs.uni-sb.de> Date: Thu, 23 Sep 1999 13:43:56 +0200 (CEST) From: Alexander Leidinger Subject: Re: gcc optimizer in -current system ... To: sheldonh@uunet.co.za Cc: scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <5592.938085890@axl.noc.iafrica.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 Sep, Sheldon Hearn wrote: >> well, I just did -O3 -mpentium, and it both compiled cleanly, and appears >> to be running okay, so is -O the max that makes a difference, or...? > > Or... > > Try build world with that kernel running. :-) Just to let you know: -Os works for me (since egcs hit the repository). Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 4:51:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7B4D215025 for ; Thu, 23 Sep 1999 04:51:10 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11U7OT-0001Wf-00; Thu, 23 Sep 1999 13:50:33 +0200 From: Sheldon Hearn To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-reply-to: Your message of "Thu, 23 Sep 1999 13:24:50 +0200." <5592.938085890@axl.noc.iafrica.com> Date: Thu, 23 Sep 1999 13:50:33 +0200 Message-ID: <5868.938087433@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999 13:24:50 +0200, Sheldon Hearn wrote: > > well, I just did -O3 -mpentium, and it both compiled cleanly, and appears > > Try build world with that kernel running. :-) I should have mentioned that I'm speaking from fairly stale experience. I got bitten by this last year and haven't tried since. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 5: 9:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.199.mpoweredpc.net [142.177.203.199]) by hub.freebsd.org (Postfix) with ESMTP id 9880614E91 for ; Thu, 23 Sep 1999 05:09:34 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id JAA27334; Thu, 23 Sep 1999 09:07:56 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 23 Sep 1999 09:07:56 -0300 (ADT) From: The Hermit Hacker To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <5592.938085890@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Sheldon Hearn wrote: > > > On Thu, 23 Sep 1999 08:23:09 -0300, The Hermit Hacker wrote: > > > well, I just did -O3 -mpentium, and it both compiled cleanly, and appears > > to be running okay, so is -O the max that makes a difference, or...? > > Or... > > Try build world with that kernel running. :-) currently being run, with /etc/make.conf containing the same optimizations *shrug* Up to building libm right now... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 5:16:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 5CCD414EC4 for ; Thu, 23 Sep 1999 05:16:10 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id OAA85963; Thu, 23 Sep 1999 14:15:33 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909231215.OAA85963@gratis.grondar.za> To: tomdean@ix.netcom.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: bounced mail Date: Thu, 23 Sep 1999 14:15:31 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The message is: > > <<< 550 service unavailable; [207.93.148.150] blocked using \ > dul.maps.vix.com DUL == "Dial-up list", and it is a listing of IP addresses that is designed to stop "direct injection" spam. If you use your ISP's mailer as a "smarthost", you will avoid this problem. Thos of us in the anti-spam community think thsat this is a Good Thing. > I tried disconnecting from my ISP and redialing to change the IP. Same > results. > > My ISP, netcom (now mindspring) has no idea. Is FreeBSD blocking? Yes, using a three-way co-operation - FreeBSD, MAPS/DUL and your ISP. > in libdes, trying to install des.h from /usr/src/crypto, which > does not exist. The make world should not have effected the system. Please cvsup crypto. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 7:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (Postfix) with ESMTP id 8865215D9B for ; Thu, 23 Sep 1999 07:59:09 -0700 (PDT) (envelope-from lh@aus.org) Received: from PHOENIX.ZER0.NET (lh@ZER0.NET [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id KAA04913; Thu, 23 Sep 1999 10:57:07 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5868.938087433@axl.noc.iafrica.com> Date: Thu, 23 Sep 1999 10:57:07 -0400 (EDT) From: Luke To: Sheldon Hearn Subject: Re: gcc optimizer in -current system ... Cc: freebsd-current@FreeBSD.ORG, The Hermit Hacker Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> > well, I just did -O3 -mpentium, and it both compiled cleanly, and >> > appears >> >> Try build world with that kernel running. :-) > > I should have mentioned that I'm speaking from fairly stale experience. > I got bitten by this last year and haven't tried since. I have -03 -mpentium -fomit-frame-pointer and the only inexpicable problem I have is I cant compile groff with more than -O for some reason. Other than that make world and make release have worked many times. I wonder does anyone think [or have stats] on whether O3-6 and things like - -ffast-math actually make any difference? Luke -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBN+o/w/VVg78E7PJuEQKUUQCfchhb9H521psWgwpe36w0gyojVkAAoK5w Fghbeaf0nxhgNrBjHDae4Bgg =s/Ik -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 8:24: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 439C014E2C for ; Thu, 23 Sep 1999 08:23:54 -0700 (PDT) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from libr.scitec.kobe-u.ac.jp (aksh0613.ppp.infoweb.ne.jp [202.219.220.173]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id AAA17962; Fri, 24 Sep 1999 00:21:10 +0900 (JST) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id AAA00842; Fri, 24 Sep 1999 00:18:32 +0900 (JST) From: takawata@shidahara1.planet.sci.kobe-u.ac.jp Message-Id: <199909231518.AAA00842@libr.scitec.kobe-u.ac.jp> To: current@freebsd.org Cc: Mitsuru IWASAKI Subject: Experimental ACPI driver. In-reply-to: Your message of "Thu, 23 Sep 1999 21:14:23 JST." <199909231211.VAA05339@tasogare.imasy.or.jp> Date: Fri, 24 Sep 1999 00:18:31 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We wrote experimental ACPI driver for 4.0-CURRENT. Now it can 1. Detect signature in so-called BIOS area. 2. Map ACPI reclaim memory and ACPI NVS memory. 3. Detect tables in ACPI memory areas (RSDT FACS DSDT FACP). 4. Catch Powerbutton event and report by dmesg. 5. use character device (temporaly CDEV_MAJOR 210) interface open,close, mmap (not complete). The attached file contains 3 file i386/acpi.c include/pc/acpi.h diff . So extract it under ${SRC_BASE}/sys/i386/ then apply 'diff' in the same directory. And add controller acpi0 to your configuration then config(8). If your system supports ACPI, you will get following dmesg ================= ACPI: Found ACPI BIOS data at 0xc00f6fe0 (, RSDT@3ff3000) acpi0: on motherboard acpi0: ADDR RANGE 3ff3000 d000 (mapped 0xc582f000) acpi0: ADDR RANGE 3ff0000 3000 (mapped 0xc583c000) acpi0: RSDT have 2 entries acpi0: RSDT entry0 FACP acpi0: FACP found acpi0: DSDT found Size=8166 bytes acpi0: FACS Found Size=64 bytes acpi0: RSDT entry1 BOOT acpi0: at 0xb2 irq 9 (snip) ACPI: pm1_status intr CALLED <-When you push Power button. ========= If you have question please ask me or iwasaki@jp.FreeBSD.org . Thanks. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A begin 644 acpi_driver.tar.gz M'XL("*@^ZC<``V%C<&E?9')I=F5R+G1A<@#L.VU[VDB2\Q5^19]GDP5;!@D[ M=F+'GF"0'=W9X$4X+SCPD/W`F'+\2L$G8XU#_H3?<:.A,'9T?-PX M/(!R`\`4^>C@!R9_;\+P-P\C,V#LA\B\-[^8D5D$!V#?7U+_^I\-\\_VYP&K MC_VI4[>B:3T,K'KX&-;=@]='=[,6..` M-1HG!XE/?V]K+8E@`/3@X.3AI''/#=.[;_YLV1=,3V\/&&O7M7 M9C^RRXDY8O*#_)J9\\B?FI%KF9/)([/=T!Q,G)!%8X>YKUX?,7\6N5/W-\=F M@3^/7,\):X"@S,I[/S9;MQI3'V9.X$X=+S(GK!VX"R!/)D[`3&OF MRN4]1.-[80F4%;L9;?7B[HH0_.@" MX35\CT63UFP4=PJZE=`+P`].E,8)+,5$],J1@J+'QS&)GD:D/_/0"1"7.ZI9 MI9(O9%!*J[/`B^GK(P2#)>399F`OMQE3TQK;SFP)8B^%P#E8&@0K8A0#*VSP MOX83!)X/@`D<5><`#BTOFFP#Z/I6'F#7`UUS/2'-$Y:*\Y_;S;50IZ79SM9M MG.\L<.DR<&D*V0&380I?G8"I79WQI0XKRPWF_#`SYV\4Z17,.3SX5$;IR\>I6=EP)0F)'&*YB4=$8. M9%A]>_07YZ.^6V9LE[5\VV%#/P!+8TY<;\2^N-&8#-^%UM51/1]`N6Y;#&B+ MG"G:/;9;+^.LN)XUF4/O'2[6'9!67/46.9F9@3FMC<_7Z@/?RJG&`0@;_;Z)?G!D>&WVJ;]IPI-#=[$5\7!H:0HL"P. MCJ0&9PTW`S8+7"\:5G:`.J3[A%V8-KOU;ODDV.!.,&OL6/?A?/I?WD[U%+I] M+9/3\S7#Q3GP@'4PM?2$Z27F$$E2@_P806C/F!NRJ^ON1?.:MINQ/[%#UM/; M[+;?8Z$[\LQH'CAQOSHOP%"5"C2:MAVP,X;$&O`:.F9@C2NRQ'9B##L2>RTQ MY4AB=@D(Y_T+HR"N85#)X.R M#-%GK,(!B#6JVJU6YH!A%@5&5"7)WS;;[5Z_^P$?,;4@-($,M;UB+1#5W(". MKXT(<"1#2,RZAS;@Q<7'*3S>@CQ^<_SAZM!5:-S;$WPA:NBY=\:LQ<_N+\EP M7^-"_`0!:,-D/G$:.E=2['0P-^)\EU#4@"\CN51/D`"N),D$YVD)]4D8.^O< M75^?PNCR@XDZ^?8,YLJ`N7HK/RA8(:<"3\C^FBH^5S@D:^#[$;@X`S]TD#3. M.R">^/X]B=>'B0S8O>=_234I1+Z6U;U+8$1]!FSHSSW[A'.POP3/V7XAOWZ` M5FEK[3N-EPK^V\Y@)[Y$;&&3BHUF.W5#8G/,WC#Y]8ER?"(?KUGN=6ANO.6C M$UG.&.]C,M['PGBSW=(P\*\`:,HZ-U^0FP@.T#[RP((]*E+)@]F`S-^20RQD`8>OH$CTT$*O@Z M;N#LP?-(4@ZXU8-MNVHCVK6*-(;C.0`S',OH73AV;1-,FZG49A/3W_@[,]KIE7[ MQ^R\`.N-&X7S8,ZTCTV]^1\:./=?S-"\=]^)C:[F!R/JVYQ,&/4-P=2%3K!P M;(AA=K&IYX#3%07N8(XA)7G!\]#!F"?TYX'E4,W`]4RPB^#53$.)1T?@X.#3 MGT>(9>J#?7(M$W%(S`2_=>8$4S="HPJASL*UH1"-S8B\VZ$_F?A?,-""@-IV M>2R+;CGTFSK1"9:5V@II(?.',4T6!FQ3T#9@)S*!5L1J#OP%-@DQ(1+X>7[D M6HX$$.!C3@`?HDF')?:6:8)!K8GI3F&;1AR-=4)@P(Q$8D*`3WL.Q'T?6ACG M4F"R?6M.F;9XTNJ)PSF%G2QPS4F8"CX)9[-LQ`K0?Z_I3.]>]C\V>RJ#\FVO M^T%KJVUV\1D:5=:\Z[_O]EBSTV:M;J??TR[N^MV>SO[^]Z8.\'_]*S:1EG4^ M,_73;4_5=08=M)O;:PW0`-Y>L]/75%UB6J=U?=?6T-<'+*S3[;-K[4;K`UB_ M*^%PB&B])^M>LANUUWH/K\T+[5KK?R:"+K5^!X>[1`+9+<2A6NONNMECMW>] MVZY.V)"MMJ:WKIO:C=JN,2`"!F;J![739_K[YO5UEDWXM\3EA0H4-B^N"14- M`URVM9[:ZB,[::D%,@/BKB6FWZHM#0OJ)Q4X:?8^2P*MKO[M#H"@$;&UFS?- M*^"MLD$J,"&MNYYZ@_2"'/2["[VO]>_Z*KOJ=MLZH@+TNMK[H+54_91==W42 MV)VN2C!(OTG#`Q:0%C1#^>).UTAN6J>O]GIWMWVMVZDBHO?=CR`8(+8)O=LD MXVZ'>`89=7N?$2_*@Z9`8A_?JU#?0Y&2U)HH"QVDU^HCM@PDC`KR[&>891WU MZEJ[4CLM%5N[B.BCIJM5F#%-1P"-C_RQ^9EXO"/V<:Z`-E[,J*Y$,\JT2]9L M?]"0>`$,>J!K0F/81>:?4EU`]\ M^Y'7&UC,Z6,OH8(^.J5?H0LJ=B)C\8-WKCQ`<@O]:`L3J1P*V)\/AUEYV(8_ MTL1YB#"B)RB^!&SF\ MEHJBFJB/D="+:`@C?\;!L91@!OV-44-15`.]D1]%C[PE?A.-,_!?>0.61"5* M)AX5R\F@`3BLH\=X8/XF&CUS2@Q0:FTGQFY"%"+08S'&;_X#*U.1QY3.IX(K M+,4XT&()'%@4U<.).2+4M1L1/E>T6R#\%@K+B*K, MT<`NE,LQVFKEDNEP(GF@7>*J6:P,RSP_2GM M1"4Z?,L,(W3O6F<.1%N;_@*"6\8N-Z#8\\/S.()( M^`6PN,->I@.Y'D4?_S!-/+ES13[.W9DFPY M.Z58GC`T/?9998FB?>I<14I+:Q3AP6(Z(:5$Q&7,DL,_F*(ESE-O.$\:>';+ M)WU]($[=4I.0.31AZ31'H_?V2)\S2ZO\E`.[K:HNS--G*LW"Q(/=#)XJA1P& M_(>!*WG"D,K\+"*S[60%0A.2UBZR0D3Z2K%;)HXIR6+LX-DSZS4[5RI[\8#_ M*D#!S+&9_/#BH8KGE^5DS%RBU@F1N"<-DUTHZ5SG'X2-1T!RKLB?)UT:9.ZM M"7/Q%-V<9G&0DR$]G:,,!QM#D>U5AUO9Y]N9L/DF-- MQ/HGBG(5:0_Q[1?:+;'60:UI_N,%OU2[2:X;0[3M=X]OE>MB1:Z+'+DNEN6Z MV$:N,[/`YD.?Q;)<%_ERG>7*=;8L5Q!.>;-/BBYID2CG!IWC)C_`,.5737:M M^\&0WT@11[V,`L%U(4,UG9=RV0+1A`1OG0`&L7/%#'#\=('D)R:S$Z9JG0_- MZWQ+7>"7E]-X-Q,$[X86D"0`1Z`;5%WACGQN((S;BK5_CD4I)\P5H3']3>_X MI`U5ACWWSY?#YI7XN)QKB4N(A=\JX9=*2C$AAAA.($6B5BX8$?G5]4R)1'WV MS[$+U`4Q5H&";MHDXX1I#2X##L.KN`8G6_E7X6D!!9XUG1'H_GER-P:8:>OM M_H[$#JLTK[1NDAUD22^Q:U5,_N\%>U0)L7'),!V6U-D+FPT>(R>DZS5VK&JT M-C+Q\/"4OA(_EA8SR_H6RJ.\">[L<[=@,T95,[DU5^,&;@R0# M]FC,NCH=(^%]HBJ57`^B6.^1<%BP[$-)B_"^%=1W/NAXYF;6L+&^+'4D:EGJ M2$`J=4YH9G)%=J90^W1V62!C/I20,>WK2\'J[8UB-*^O#;6#QS#&A=;72_*# M?-Q0T#G%*UM,5A0%2HJ,KTHVW9,-2J*`+J7`PC,C\\DU7+\VE`@H-PV5BC(NQD.UQW=(]NU1.N/4%K`6:J+:Y">7144R9.9D0"`EAY'A. MP`]G*4RB&0/%BNF!P2O_+-)N,C4TN6F/P>8>SY`WS_IPEQ_TZ:50*'H.$LY: MX$8'*4]"#$7\%-%6P,Q3X,]0TNTXZ26JDG!#;/P/1%:@JMQ@P\K`^9_LW\Z# M&:9L5:ZV\M.+,IMNVG)5RL]:BMGTTY9K4?[V!2BG2TQ^8HEEN/XSUQB._L^8 MDM,X^$-LX$R*$Y4O3G+E&%#_M(P']IC3.&`K/4N$0E>$-G[#>I)/$?[3IT_+ M:KJ-?A2,O6D%/(NMK&H\K?`;=J%L]G)+A5>>J_#/W7R4;U=X)55XY6F%_QZ; MBI)1>.5/5?AMC>.W*[Q2J/#;[@#?H/#;LY55#:'PML]"?^I$8SQXC7S&[S[3 M+2NN,;5:C49LJ]?-SQ7\MJ!*3)[L5[$^+_IT;>CH#A\K-GT]B;EU7I)8$H[. M3%1Y\EY7#T*ML3NQD7\J@'`O[G2CV6X;K??:=;O">TH8:8OS-"97X[2VZ"*" M$$H3>ZY5V5FB:R<_%8#'S^O9MI(`2Z)]WYGB[3-O]//Q+TO9=/Y-RWK\PRIJ MYY/6Y4(O#7YS`K^2()'BSU&2FJJ(NCUK]IB%2\;8/X?:I-]R=94DL;Q.>;RR M\G&)&;$7,U9Y^R(\E_!+H?Z[)).9S9WRCVCRJ1!?XB03B&DEVPDM'BRE_)RF M20PY7_)F%)G6^,_/5>!9OD1IG+0QO@L#K0Z$KWZ`$%AT@U]/G[J(DI<$6JT+ M7#NGE@]2@#\(UB.C78BJP_7J]4`+4WKQR9?HZHY/<>5D4U-XL64D=/85Z>QZ M.I\F,GA.TF1=$V@I!"(C\D2J0EP6P8/TV?@QQ"^UQ2<+(J>3NW#$#L7#^F`M MF=)+DBE\PXJS*97U=$I`Z10"*R82\6%^81#X]XX7$Y:;G2\D&0VRD*FX5I*> M&0H6)H[']AD>M74O#1C2>-_N55D]7MWIIR"G^0DQ(G.,7X"\L&-EI6R$*&,_ MU*;D"SGQ&0ILLIP`GB];STVNIWV?HQPKAS9`0'SXPNU?HI")'4MJJCQ%)0Q@ M%G!ERN..2]6\=Z&DD*M'D-0++B172I<&WW*SN:,U':MZW3;W;?,B&_&:$,8G22+;!@XH8DW0(UI3M;@^;EPZAK6 M%`T2F"6>YR_%-@\3I6A*<`@C-HE<4/IG'7P'\">[^(DW>`W06Q(VC/]58,>X M-)JMOO9!37;>%'-V!\Q=_N3"H04P8PZQXW.66/=&O8G-0O!K#NL6),_N=;U;C1]%9Z?!F[;-C%2!NBGPC M=:#PA+S=V+?G']$/YJ,1NL4%"<=O2#;F7_8IPK(1S$#Q:U7*@:600@!2.1>*N[_Q83N]`%RY]#O8`?EK]D)Q M$E`1*'_CY"=7"[.\P>ORQ^ZI)UV5Q'4>[E=7(&;E\=QI5FK6Q`S#9#CQ#A!X M.;'=`XO7,VZZ[;MKE;PL";_:G(=2ECIIN:^4O2=*ADY.[Q/_=WM7]]LT#,2? MV5]A'I!:&(RTI9HTX($OB0<$`MXF%"6-RZ(E34G3;M/$_X[O_)GDDJY?DX#X M81^]Q#[[SO;9=_)Q6PV7Q:.81-G8(M6P[J6I?@J M&!+MUA4;OFMGPWD>]$W\4KN&,8M4E(\'UM%K:24]?:K#5!*,4Q&_7KYDIWVQ M)<2SL"=Y84]8K-9ER0I&FB2TW]9V+%L6!^R9?/6,\$A#M)`U^007;C_05R,L MQ^?7TZF^W6>OQ6B<-D:R;!9ZN<.AKQR2734)2D.A.O1*N:&MG53UZ:LQP\U. M,NC(6[[L=!+&@/%DP>F'U!"H[J>3!U'[+GMC\;I#7]Z3C6Q+>_+=9+EY'L,_(4LS^781:4,EVTFV.G-W ME.PV*2_W+EEOOY+U=IJEY-O;R+)N?.PLR[]@EAY"EKO.TK9*MI/LCK-4NR4A M816JUZ)$Y+`D^*G^2HMCG0(+%_CL,9NC0-45%.:$56K$5-?]5HF)KVZ52S_) M`)$FC8[9!///A'+A*=,VUM*&C2JO-`2YKFX[;BJ!_$.V,`,^5K&Y7 M[HC2>);AC75?WS7#BX1G77,+MICZ","K_+#(YKV5^'%QHR(NP%7U1#':EY># M':Q80U&P#Q:>X@!MK,-_'XU>2/PO;SST1IYX;#@(^@^^Z*0NBTNC@'0N:U[0DP4S/GI M#\)1LEBFQ*<93\_'U.,Y)Z+;F$3S^Z`[1D^\8 M'EON!YA[K=T84:!.D(I)<;LB/L50'[K3<41W6Y"*,!%4<@P%5;2D&:LTEO.@ MR/)&HGY1`_:4X\G8#T`8_PZK?,K3 MD.<.@M,D6,"F"![C=H%]B*]YI+_TH2JT'K33=V1GCK6W=>GH?$-"<#IU4Y-. M;32Q^,\7VSI/:#U$(\(DIWECF]5F0HAJ^6Z.O[#<5MD92%*M%[!*7HP`*"[G MOPB:8?0%P8][(TZ3PW9RX$]FK6^WD0>M5+](\P:BOJ"C29Y+5YZW\^B;VS?T^"C?/>5][A?@G@J\QD.^HE&=A"+V7RZA=/Z=Q MDFB3U@1!PP[(%PM!%W8S\SZ]>?@0*Q`57CP31>4WUQ9&T5?_*KCD_HI/SNK1 MWS]]P,H$EF`;"&,`P.<)+MZU9\T`KW]4R^E\]'R-/!3*?@M0'\:[8OA/@[EB M-OFC2L"[#E`L0S4A:O\9_>P>T)G.NLNCKG2E*UWI2E>Z\D^5/Y<\L[(`>``` ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 8:58: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.loeth.dk (mail.kolind-heise.dk [194.192.218.25]) by hub.freebsd.org (Postfix) with SMTP id CA80B15025 for ; Thu, 23 Sep 1999 08:57:50 -0700 (PDT) (envelope-from jan@osterskov.dk) Received: from SMP_XEON.OSTERSKOV.DK ([172.29.26.51]) by mail.loeth.dk (8.9.2/8.9.2) with SMTP id PAA17044 for ; Thu, 23 Sep 1999 15:56:28 +0200 (CEST) From: freebsd@osterskov.dk To: current@FreeBSD.ORG Subject: Problem with Compaq SMART-2SL array controller Date: Thu, 23 Sep 1999 17:43:17 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99092318013400.00254@SMP_XEON.OSTERSKOV.DK> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After doing a cvsup yesterday evening i can't seem to boot on my raid cotroller using the same kernel config. Is -current probing hardware i a different way now or ?? Is there anyone with an answer to this ?? Kernel Config: #Compaq SMART Array 2-SL Controller controller ida0 device id0 controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device wcd0 #IDE CD-ROM The bootmessage that i got when it was Working : ida0: irq 18 at device 0.0 on pci2 ida0: drives=1 firm_rev=3.08 WARNING: "id" is usurping "id"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj WARNING: "id" is usurping "wd"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj id0: on ida0 id0: 17355MB (35544960 sectors), blocksize=512 ~ wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): , removable, intr, dma, iordis ~ changing root device to id0s2a The bootmessage that i have now : "Not Working" ida0: irq 18 at device 0.0 on pci2 ida0: drives=1 firm_rev=3.08 WARNING: "id" is usurping "id"'s cdevsw[] WARNING: "id" is usurping "id"'s bmaj id0: on ida0 id0: 17355MB (35544960 sectors), blocksize=512 ~ wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 ~ WARNING: "wd" is usurping "id"'s cdevsw[] WARNING: "wd" is usurping "wd"'s bmaj ~ wdc0: unit 0 (atapi): , removable, intr, dma, iordis ~ ~ changing root device to wd0s2a changing root device to wd0a rootdev=0xC1499000 error=6 panic cannot mount rootdev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 8:59:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 79CCA15E54; Thu, 23 Sep 1999 08:59:41 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA03643; Thu, 23 Sep 1999 11:58:53 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA06516; Thu, 23 Sep 1999 11:58:23 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id LAA79568; Thu, 23 Sep 1999 11:58:23 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199909231558.LAA79568@bb01f39.unx.sas.com> Subject: ccd build failure To: freebsd-current@freebsd.org Date: Thu, 23 Sep 1999 11:58:23 -0400 (EDT) Cc: dillon@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm current as of 11:30am EST. If a fix has been made for the following I probably won't see it until the cvsup servers run their hourly updates... didn't know if you'd seen this or not. Thanks, John cc -nostdinc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ccd -I/usr/obj/usr/src/sys/modules/ccd/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdstart': /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:892: structure has no member named `sc_pick' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:895: structure has no member named `sc_blk' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:896: structure has no member named `sc_blk' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:898: structure has no member named `sc_pick' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:900: structure has no member named `sc_blk' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdiodone': /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_blk' /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_pick' *** Error code 1 Stop in /usr/src/sys/modules/ccd. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id AA91715F18 for ; Thu, 23 Sep 1999 09:06:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA02428; Thu, 23 Sep 1999 18:04:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: freebsd@osterskov.dk Cc: current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Thu, 23 Sep 1999 17:43:17 +0200." <99092318013400.00254@SMP_XEON.OSTERSKOV.DK> Date: Thu, 23 Sep 1999 18:04:35 +0200 Message-ID: <2426.938102675@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know who is maintaining the id driver, but it looks to me like it isn't able to co-exist with the wd driver (because it "steals" the wd drivers cdevsw entry) Poul-Henning In message <99092318013400.00254@SMP_XEON.OSTERSKOV.DK>, freebsd@osterskov.dk w rites: >After doing a cvsup yesterday evening i can't seem to boot on my >raid cotroller using the same kernel config. > >Is -current probing hardware i a different way now or ?? > >Is there anyone with an answer to this ?? > >Kernel Config: > >#Compaq SMART Array 2-SL Controller >controller ida0 >device id0 > >controller wdc0 at isa? port IO_WD1 irq 14 >disk wd0 at wdc0 drive 0 >disk wd1 at wdc0 drive 1 > >controller wdc1 at isa? port IO_WD2 irq 15 >disk wd2 at wdc1 drive 0 >disk wd3 at wdc1 drive 1 > >device wcd0 #IDE CD-ROM > > >The bootmessage that i got when it was Working : > >ida0: irq 18 at device 0.0 on pci2 >ida0: drives=1 firm_rev=3.08 >WARNING: "id" is usurping "id"'s cdevsw[] >WARNING: "id" is usurping "id"'s bmaj >WARNING: "id" is usurping "wd"'s cdevsw[] >WARNING: "id" is usurping "id"'s bmaj >id0: on ida0 >id0: 17355MB (35544960 sectors), blocksize=512 >~ >wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 >wdc0: unit 0 (atapi): , removable, intr, dma, iordis >~ >changing root device to id0s2a > > >The bootmessage that i have now : "Not Working" > >ida0: irq 18 at device 0.0 on pci2 >ida0: drives=1 firm_rev=3.08 >WARNING: "id" is usurping "id"'s cdevsw[] >WARNING: "id" is usurping "id"'s bmaj >id0: on ida0 >id0: 17355MB (35544960 sectors), blocksize=512 >~ >wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 >~ >WARNING: "wd" is usurping "id"'s cdevsw[] >WARNING: "wd" is usurping "wd"'s bmaj >~ >wdc0: unit 0 (atapi): , removable, intr, dma, iordis >~ >~ >changing root device to wd0s2a >changing root device to wd0a >rootdev=0xC1499000 error=6 panic cannot mount rootdev > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9: 7:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id BA9D8160A4; Thu, 23 Sep 1999 09:07:09 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA02444; Thu, 23 Sep 1999 18:06:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 11:58:23 EDT." <199909231558.LAA79568@bb01f39.unx.sas.com> Date: Thu, 23 Sep 1999 18:06:16 +0200 Message-ID: <2442.938102776@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Insert semi-nasty message about how people should really be testing their changes before they commit, how it is a blatant disregard for basic human rigths not to do so etc etc etc] Poul-Henning In message <199909231558.LAA79568@bb01f39.unx.sas.com>, "John W. DeBoskey" writ es: >Hi, > > I'm current as of 11:30am EST. If a fix has been made for the >following I probably won't see it until the cvsup servers run >their hourly updates... didn't know if you'd seen this or >not. > >Thanks, >John > >cc -nostdinc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ccd -I/usr/obj/usr/src/sys/modules/ccd/@ -I/usr/obj/usr/src/ >tmp/usr/include -c /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdstart': >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:892: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:895: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:896: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:898: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:900: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdiodone': >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_pick' >*** Error code 1 > >Stop in /usr/src/sys/modules/ccd. >*** Error code 1 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9: 7:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id 2E8F0160BB; Thu, 23 Sep 1999 09:06:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA02444; Thu, 23 Sep 1999 18:06:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 11:58:23 EDT." <199909231558.LAA79568@bb01f39.unx.sas.com> Date: Thu, 23 Sep 1999 18:06:16 +0200 Message-ID: <2442.938102776@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Insert semi-nasty message about how people should really be testing their changes before they commit, how it is a blatant disregard for basic human rigths not to do so etc etc etc] Poul-Henning In message <199909231558.LAA79568@bb01f39.unx.sas.com>, "John W. DeBoskey" writ es: >Hi, > > I'm current as of 11:30am EST. If a fix has been made for the >following I probably won't see it until the cvsup servers run >their hourly updates... didn't know if you'd seen this or >not. > >Thanks, >John > >cc -nostdinc -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/ccd -I/usr/obj/usr/src/sys/modules/ccd/@ -I/usr/obj/usr/src/ >tmp/usr/include -c /usr/src/sys/modules/ccd/../../dev/ccd/ccd.c >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdstart': >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:892: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:895: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:896: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:898: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:900: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c: In function `ccdiodone': >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1161: structure has no member named `sc_pick' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_blk' >/usr/src/sys/modules/ccd/../../dev/ccd/ccd.c:1162: structure has no member named `sc_pick' >*** Error code 1 > >Stop in /usr/src/sys/modules/ccd. >*** Error code 1 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:18:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 8B4B114F5A for ; Thu, 23 Sep 1999 09:18:54 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id LAA62118; Thu, 23 Sep 1999 11:17:52 -0500 (CDT) (envelope-from dan) Date: Thu, 23 Sep 1999 11:17:52 -0500 From: Dan Nelson To: bsd@picard.mandrakesoft.de Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Message-ID: <19990923111752.B57930@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Sep 23), bsd@picard.mandrakesoft.de said: > On Thu, 23 Sep 1999, The Hermit Hacker wrote: > > just curious, but what is the max setting that can be used to > > compile the kernel? > > Works rather nicely here with > > -O6 -mpentiumpro -march=pentiumpro -pipe -s -fexpensive-optimizations > -ffast-math -O6 is too much; -O3 is the highest level tested for by egcs. -fexpensive-optimizations is redundant because -O2 turns it on. See /usr/src/contrib/egcs/gcc/toplev.c, starting at line ~4250, to see what the different -O levels actually do. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D571A15E65 for ; Thu, 23 Sep 1999 09:19:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA27815; Thu, 23 Sep 1999 09:19:18 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 09:19:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199909231619.JAA27815@apollo.backplane.com> To: Poul-Henning Kamp Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure References: <2442.938102776@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :[Insert semi-nasty message about how people should really be testing :their changes before they commit, how it is a blatant disregard for :basic human rigths not to do so etc etc etc] : :Poul-Henning I just forgot to commit a header file. Sorry about that. I test all of my code, unlike you Poul. Insert nasty message about how people shouldn't post idiotic comments. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:27:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id 7260E14F65 for ; Thu, 23 Sep 1999 09:27:21 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA02537; Thu, 23 Sep 1999 18:25:47 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 09:19:18 PDT." <199909231619.JAA27815@apollo.backplane.com> Date: Thu, 23 Sep 1999 18:25:46 +0200 Message-ID: <2535.938103946@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909231619.JAA27815@apollo.backplane.com>, Matthew Dillon writes: >: >:[Insert semi-nasty message about how people should really be testing >:their changes before they commit, how it is a blatant disregard for >:basic human rigths not to do so etc etc etc] >: >:Poul-Henning > > I just forgot to commit a header file. Sorry about that. I test all > of my code, unlike you Poul. > > Insert nasty message about how people shouldn't post idiotic comments. Who complained recently when I *had* included and committed a header file ? :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:28:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 44E7B14D7F for ; Thu, 23 Sep 1999 09:28:48 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA89468; Thu, 23 Sep 1999 12:28:04 -0400 (EDT) (envelope-from wollman) Date: Thu, 23 Sep 1999 12:28:04 -0400 (EDT) From: Garrett Wollman Message-Id: <199909231628.MAA89468@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: Poul-Henning Kamp , "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-Reply-To: <199909231619.JAA27815@apollo.backplane.com> References: <2442.938102776@critter.freebsd.dk> <199909231619.JAA27815@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Insert nasty message about how people shouldn't post idiotic comments. Totally uncalled-for in our mailing-lists. (And before you hit that `R' key: it doesn't matter how much you think you were provoked.) -GAWEollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:33:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 69FA414D7F for ; Thu, 23 Sep 1999 09:33:45 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id MAA02320 for ; Thu, 23 Sep 1999 12:36:50 -0400 (EDT) Date: Thu, 23 Sep 1999 12:36:50 -0400 (EDT) From: Ben Rosengart To: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-Reply-To: <199909231628.MAA89468@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mutual respect is the glue that holds FreeBSD together, IMHO. As such, it should not be discarded lightly. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:44:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id E166714F72 for ; Thu, 23 Sep 1999 09:44:55 -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.9.3/8.8.8) with ESMTP id JAA86441; Thu, 23 Sep 1999 09:43:08 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199909231643.JAA86441@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Poul-Henning Kamp , "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 09:19:18 PDT." <199909231619.JAA27815@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Sep 1999 09:43:08 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stay nice 8) Never give the opposition an opportunity to get the best of you for most likely they will fully exploit your weakness . After all isn't that was opposition is all about? -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:45:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D43C714E6E for ; Thu, 23 Sep 1999 09:45:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA28110; Thu, 23 Sep 1999 09:44:42 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 09:44:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199909231644.JAA28110@apollo.backplane.com> To: Ben Rosengart Cc: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Mutual respect is the glue that holds FreeBSD together, IMHO. As such, :it should not be discarded lightly. : :-- : Ben Rosengart Mutual respect doesn't exist when one of the parties refuses to listen to *anyone's* advise, ever. I am getting wholely sick and tired of having to clean up after Poul's commit bugs. I've spent at least a hundred hours and probably more in the last month fixing things that he's broken, like BOOTP and VN. I would much rather spend my time on other more interesting things. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:47:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A75B51607D for ; Thu, 23 Sep 1999 09:47:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA28158; Thu, 23 Sep 1999 09:47:12 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 09:47:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199909231647.JAA28158@apollo.backplane.com> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure References: <199909231558.LAA79568@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Hi, : : I'm current as of 11:30am EST. If a fix has been made for the :following I probably won't see it until the cvsup servers run :their hourly updates... didn't know if you'd seen this or :not. : :Thanks, :John The missing header file changes have been committed. They should show up for cvsup in the next hour or two, depending which cvsup server you use. The file is sys/sys/ccdvar.h. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:55:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from drago.cert.org.tw (drago.cert.org.tw [140.117.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 0C72014EE9; Thu, 23 Sep 1999 09:55:38 -0700 (PDT) (envelope-from foxfair@drago.cert.org.tw) Received: from foxfair (foxfair.cc.nsysu.edu.tw [140.117.100.101]) by drago.cert.org.tw (8.9.3/8.9.3) with SMTP id AAA00760; Fri, 24 Sep 1999 00:51:37 +0800 (CST) (envelope-from foxfair@drago.cert.org.tw) Date: Fri, 24 Sep 1999 00:54:18 +0800 From: Foxfair Hu To: phk@FreeBSD.org, dillon@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Re: ccd build failure In-Reply-To: References: <199909231628.MAA89468@khavrinen.lcs.mit.edu> Message-Id: <37EA5B3A3AC.772CFOXFAIR@drago.cert.org.tw> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.25.04 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG phk, dillon, other FreeBSD folks, We are all in a Open Source project named "Free"BSD. So could we agree with all, play it totally "free" and "open" ? Not just sharing your own knowledge freely, but also sitting you mind with thousands of others' open. It is more helpful to the FreeBSD project. Only my 2c. On Thu, 23 Sep 1999 12:36:50 -0400 (EDT) Ben Rosengart wrote: > Mutual respect is the glue that holds FreeBSD together, IMHO. As such, > it should not be discarded lightly. > > -- > Ben Rosengart > > UNIX Systems Engineer, Skunk Group > StarMedia Network, Inc. > Cheers, -Foxfair. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:57:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0D34B15E24 for ; Thu, 23 Sep 1999 09:57:42 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA28373; Thu, 23 Sep 1999 09:57:24 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 09:57:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199909231657.JAA28373@apollo.backplane.com> To: Sheldon Hearn Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... References: <5234.938085144@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, 23 Sep 1999 08:00:50 -0300, The Hermit Hacker wrote: : :> just curious, but what is the max setting that can be used to compile the :> kernel? : :-O : :Ciao, :Sheldon. I've found -Os to produce quite excellent code. It's an option specific to the new EGCS compiler (known as 'GCC' in current :-)). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 9:58:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 9E44414E6E for ; Thu, 23 Sep 1999 09:58:42 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id TAA18702; Thu, 23 Sep 1999 19:58:12 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 0CC17EA; Thu, 23 Sep 1999 19:58:20 +0300 (EEST) Date: Thu, 23 Sep 1999 19:58:19 +0300 From: Vallo Kallaste To: Matthew Dillon Cc: Poul-Henning Kamp , "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Message-ID: <19990923195819.A35231@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <2442.938102776@critter.freebsd.dk> <199909231619.JAA27815@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199909231619.JAA27815@apollo.backplane.com>; from Matthew Dillon on Thu, Sep 23, 1999 at 09:19:18AM -0700 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 23, 1999 at 09:19:18AM -0700, Matthew Dillon wrote: > : > :[Insert semi-nasty message about how people should really be testing > :their changes before they commit, how it is a blatant disregard for > :basic human rigths not to do so etc etc etc] > : > :Poul-Henning > > I just forgot to commit a header file. Sorry about that. I test all > of my code, unlike you Poul. > > Insert nasty message about how people shouldn't post idiotic comments. It's very unfortunate to see you both often opposite. Two hard millstones doesn't do good flour. It's a very old proverb. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 10: 9:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 5EB231507A for ; Thu, 23 Sep 1999 10:09:23 -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 MAA19247; Thu, 23 Sep 1999 12:07:59 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id MAA12386; Thu, 23 Sep 1999 12:07:58 -0500 (CDT) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id MAA21789; Thu, 23 Sep 1999 12:07:58 -0500 (CDT) Date: Thu, 23 Sep 1999 12:07:58 -0500 (CDT) From: Jonathan Lemon Message-Id: <199909231707.MAA21789@free.pcs> To: freebsd@osterskov.dk, current@freebsd.org Subject: Re: Problem with Compaq SMART-2SL array controller X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >After doing a cvsup yesterday evening i can't seem to boot on my >raid cotroller using the same kernel config. > >Is -current probing hardware i a different way now or ?? It appears so. The IDA driver needs to stomp on the WD driver's vectors in order to boot off of the RAID controller. It seems that something changed so that wd is getting probed after the ida driver now, and removing the vectors. For now, you could remove the IDE devices from the config file, until this gets fixed. Ideally, the boot blocks/loader should be taught to boot from something other than wd() or da(). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 10:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182]) by hub.freebsd.org (Postfix) with ESMTP id 05D2414F50 for ; Thu, 23 Sep 1999 10:16:48 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id KAA38700; Thu, 23 Sep 1999 10:16:01 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37EA6051.BB36356E@gorean.org> Date: Thu, 23 Sep 1999 10:16:01 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make World Broken? References: <199909230652.XAA14481@ix.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > > cvsup this evening. make world failed. /usr/src/crypto does not exist. I got bitten by this too. The solution is to add the crypto distribution to your cvsup file. I'm not sure how I feel about this though. I kind of liked having DES in its own dist since I don't need kerberos. Doug -- "Let 'er work." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 10:48:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id AA05F154BB for ; Thu, 23 Sep 1999 10:48:15 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA10192; Thu, 23 Sep 1999 13:47:55 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16701; Thu, 23 Sep 1999 13:47:25 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id NAA80231; Thu, 23 Sep 1999 13:47:25 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199909231747.NAA80231@bb01f39.unx.sas.com> Subject: Re: ccd build failure In-Reply-To: <199909231647.JAA28158@apollo.backplane.com> from Matthew Dillon at "Sep 23, 1999 9:47:12 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 23 Sep 1999 13:47:25 -0400 (EDT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Many thanks... personal opinions aside, I appreciate the work that ALL of you do. Again, many thanks, John > > : > :Hi, > : > : I'm current as of 11:30am EST. If a fix has been made for the > :following I probably won't see it until the cvsup servers run > :their hourly updates... didn't know if you'd seen this or > :not. > : > :Thanks, > :John > > The missing header file changes have been committed. They should show > up for cvsup in the next hour or two, depending which cvsup server you > use. The file is sys/sys/ccdvar.h. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 10:51:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 2913515FA3 for ; Thu, 23 Sep 1999 10:51:07 -0700 (PDT) (envelope-from bsd@picard.mandrakesoft.de) Received: from picard.mandrakesoft.de (root@picard.mandrakesoft.de [151.189.96.131]) by relay.pair.com (8.8.7/8.8.5) with ESMTP id NAA09953; Thu, 23 Sep 1999 13:03:13 -0400 (EDT) From: bsd@picard.mandrakesoft.de Received: from localhost (bsd@localhost) by picard.mandrakesoft.de (8.9.3/8.9.3) with ESMTP id TAA03475; Thu, 23 Sep 1999 19:05:25 +0200 Date: Thu, 23 Sep 1999 19:05:25 +0200 (CEST) To: Dan Nelson Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <19990923111752.B57930@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Dan Nelson wrote: > > Works rather nicely here with > > > > -O6 -mpentiumpro -march=pentiumpro -pipe -s -fexpensive-optimizations > > -ffast-math > > -O6 is too much; -O3 is the highest level tested for by egcs. But specifying something too high (-O99) doesn't hurt - I'm using -O6 for gcc 2.95.1 (which, by the way, compiles almost everything in 3.3-RELEASE and 4.0-CURRENT, the only thing still troubling me with it is the kernel). LLaP bero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11: 3:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2399514D3A for ; Thu, 23 Sep 1999 11:03:48 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA28917; Thu, 23 Sep 1999 11:03:14 -0700 (PDT) (envelope-from dillon) Date: Thu, 23 Sep 1999 11:03:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199909231803.LAA28917@apollo.backplane.com> To: bsd@picard.mandrakesoft.de Cc: Dan Nelson , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> -O6 is too much; -O3 is the highest level tested for by egcs. : :But specifying something too high (-O99) doesn't hurt - I'm using -O6 for :gcc 2.95.1 (which, by the way, compiles almost everything in 3.3-RELEASE :and 4.0-CURRENT, the only thing still troubling me with it is the kernel). : :LLaP :bero I tend not to like the higher optimization levels because they cause the compiler to attempt to turn static functions into inlines and, in my opinion, it doesn't do a very good job of selecting which functions to convert. The result is that I see bloated binaries with no performance gain to show for it. EGCS's -Os is my favorite. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11: 6:26 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 30EE114D3A; Thu, 23 Sep 1999 11:06:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2227E1CD735; Thu, 23 Sep 1999 11:06:25 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Thu, 23 Sep 1999 11:06:25 -0700 (PDT) From: Kris Kennaway To: Sheldon Hearn Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <5592.938085890@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Sheldon Hearn wrote: > On Thu, 23 Sep 1999 08:23:09 -0300, The Hermit Hacker wrote: > > > well, I just did -O3 -mpentium, and it both compiled cleanly, and appears > > to be running okay, so is -O the max that makes a difference, or...? > > Or... > > Try build world with that kernel running. :-) My kernel is compiled -O2 -mpentium -march=pentium (one of these two is redundant) and works perfectly. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:10:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id A444A14ED4 for ; Thu, 23 Sep 1999 11:10:32 -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.9.3/8.9.3) with SMTP id MAA08401; Thu, 23 Sep 1999 12:09:46 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA21805; Thu, 23 Sep 1999 12:09:45 -0600 Date: Thu, 23 Sep 1999 12:09:45 -0600 Message-Id: <199909231809.MAA21805@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-Reply-To: <199909231619.JAA27815@apollo.backplane.com> References: <2442.938102776@critter.freebsd.dk> <199909231619.JAA27815@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :[Insert semi-nasty message about how people should really be testing > :their changes before they commit, how it is a blatant disregard for > :basic human rigths not to do so etc etc etc] > ... > Insert nasty message about how people shouldn't post idiotic comments. Play nice boys! Remeber the first rule of committers. *grin* Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:16:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8D9FD15484 for ; Thu, 23 Sep 1999 11:16:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA02222; Thu, 23 Sep 1999 11:15:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Poul-Henning Kamp , "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 09:19:18 PDT." <199909231619.JAA27815@apollo.backplane.com> Date: Thu, 23 Sep 1999 11:15:35 -0700 Message-ID: <2218.938110535@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just forgot to commit a header file. Sorry about that. I test all > of my code, unlike you Poul. > > Insert nasty message about how people shouldn't post idiotic comments. Ummm. I don't see this going in positive directions at all and I'd appreciate it highly if everyone involved would just count to 10 and stay away from their mail clients for awhile. The only point in even sending email is to COMMUNICATE with other people and I don't see any communication happening here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:29:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CC81E15083 for ; Thu, 23 Sep 1999 11:29:37 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA02294; Thu, 23 Sep 1999 11:29:32 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Ben Rosengart , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 09:44:42 PDT." <199909231644.JAA28110@apollo.backplane.com> Date: Thu, 23 Sep 1999 11:29:32 -0700 Message-ID: <2290.938111372@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mutual respect doesn't exist when one of the parties refuses to listen > to *anyone's* advise, ever. > > I am getting wholely sick and tired of having to clean up after Poul's > commit bugs. I've spent at least a hundred hours and probably more in > the last month fixing things that he's broken, like BOOTP and VN. I > would much rather spend my time on other more interesting things. I don't think that either of you are communicating at this point and you going after Poul-Henning like this is only going to bring us rapidly back to a point of crisis. This is NOT the kind of conflict resolution which I strongly encouraged you to employ should you again find yourself at loggerheads with another member of the project, and from where I'm sitting it looks like the kind of "but Johnny hit me FIRST!" sniping you'd expect from the back seat of a family car on a long vacation trip, not communications between two grown adults. It takes two to tango, as my spanish teacher used to say, and I see two people very much involved in heading towards the rocks here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:47:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 0413F14CA0 for ; Thu, 23 Sep 1999 11:47:11 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA01040; Thu, 23 Sep 1999 14:46:13 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id LAA05404; Thu, 23 Sep 1999 11:46:30 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id LAA04038; Thu, 23 Sep 1999 11:46:39 -0700 (PDT) Message-Id: <199909231846.LAA04038@mina.sr.hp.com> To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Reply-To: Darryl Okahata Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: multipart/mixed; boundary="Multipart_Thu_Sep_23_11:46:38_1999-1" Content-Transfer-Encoding: 7bit Date: Thu, 23 Sep 1999 11:46:38 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Thu_Sep_23_11:46:38_1999-1 Content-Type: text/plain; charset=US-ASCII In the interests of peace and harmony (;-), I'd like to submit the attached perl script, which lists the status of cvs-controlled files. In particular, it's very useful for determining which files have been modified but not committed, like: i386/linux/linux_file.c Locally Modified kern/imgact_elf.c Locally Modified CVS is severely lacking in many areas (it is all we have, though), and one thing it is missing is an easy way of showing concise file status. As a result, it's easy to forget about locally-modified files. This perl script will list all files, in the current directory and below, that do not have a status of "Up-to-date", such as those which have been locally modified or which need updating. To use this script, just cd to some directory that contains cvs- controlled files and run the script. A list of non-up-to-date files in the current directory and below will be listed. Note that this script isn't particularly fast, as it has to execute a cvs command in each and every directory (due to cvs deficiencies). As examples, the script takes around 3 minutes to run under /usr/src/sys, and around 30 minutes for /usr/src (checked out via "cvs checkout src"). [ My (local, mirrored via cvsup) repository is accessed via pserver over 128K ISDN, and so there's a good chance that many people will see better performance. ] -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. --Multipart_Thu_Sep_23_11:46:38_1999-1 Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename="cvsinfo" Content-Transfer-Encoding: quoted-printable #! /usr/bin/perl #########################################################################= ###### # # File: cvsinfo # RCS: $Header: $ # Description: = # Author: Darryl Okahata # Created: Wed Jul 15 14:52:01 1998 # Modified: Thu Sep 23 11:35:35 1999 (Darryl Okahata) darrylo@sr.hp.c= om # Language: CPerl # Package: N/A # # (C) Copyright 1998, Hewlett-Packard, all rights reserved. # #########################################################################= ###### $listfile =3D ".changed-files"; #########################################################################= ###### require 'getopts.pl'; &Getopts('ac'); $all_status =3D 1 if ($opt_a); $update_changed_file =3D 1 if ($opt_c); require "pwd.pl"; &initpwd; $top_dir =3D $ENV{'PWD'}; #########################################################################= ###### open(DIRS, "find . -type d | sort |") || die "$!"; while ($dir =3D ) { chdir($top_dir); # make sure we're in a known location chop($dir); $dir =3D~ s|^\./||; $dir =3D '.' if ($dir eq ''); # print "$dir\n"; next if (!-d "$dir/CVS"); &process_dir($dir); } close(DIRS); if ($update_changed_file) { unlink($listfile); open(OUT, ">$listfile") || die "$listfile: $!"; if ($#update_files >=3D 0) { foreach $file (sort @update_files) { print OUT "$file\n"; } } close(OUT); } exit 0; #########################################################################= ###### sub process_dir { local($dir) =3D @_; local($file, $status, $cmd); # print "$dir\n"; chdir($dir); $cmd =3D "cvs status -l"; open(IN, "$cmd 2>&1 |") || die "$!"; while () { if (/^File:\s+([^\s]+)\s+Status:\s+(.+)$/i){ $file =3D $1; $status =3D $2; if ($all_status || $status ne 'Up-to-date') { if ($status eq 'Needs Patch') { $status =3D 'Needs Updating'; } printf("%-50s %s\n", ($dir eq '.') ? $file : "$dir/$file", $status); if ($status =3D~ /Locally Modified/) { push(@update_files, $file); } } } elsif (/\[status\s+aborted\]/) { die "$_\n"; } # print; } close(IN); } --Multipart_Thu_Sep_23_11:46:38_1999-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:49:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 0255514CA0 for ; Thu, 23 Sep 1999 11:49:10 -0700 (PDT) (envelope-from bsd@picard.mandrakesoft.de) Received: from picard.mandrakesoft.de (root@picard.mandrakesoft.de [151.189.96.131]) by relay.pair.com (8.8.7/8.8.5) with ESMTP id OAA17271; Thu, 23 Sep 1999 14:09:08 -0400 (EDT) From: bsd@picard.mandrakesoft.de Received: from localhost (bsd@localhost) by picard.mandrakesoft.de (8.9.3/8.9.3) with ESMTP id UAA03679; Thu, 23 Sep 1999 20:11:21 +0200 Date: Thu, 23 Sep 1999 20:11:20 +0200 (CEST) To: Matthew Dillon Cc: Dan Nelson , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <199909231803.LAA28917@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Matthew Dillon wrote: > I tend not to like the higher optimization levels because they cause > the compiler to attempt to turn static functions into inlines and, > in my opinion, it doesn't do a very good job of selecting which functions > to convert. The result is that I see bloated binaries with no > performance gain to show for it. > > EGCS's -Os is my favorite. Have you tried specifying -O6 and -Os (With -Os following -O6 because we want it to override the values set by -O6)? I haven't tried it for a while, but at least in an older egcs snapshot (somewhere between 1.1.2 and gcc 2.95), it worked (optimize as much as possible, but value size over speed). LLaP bero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:57:29 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id D45B615068; Thu, 23 Sep 1999 11:57:27 -0700 (PDT) From: "Jonathan M. Bresler" To: tomdean@ix.netcom.com Cc: freebsd-current@freebsd.org In-reply-to: <37E9C266.2F76@ix.netcom.com> (tomdean@ix.netcom.com) Subject: Re: bounced mail Message-Id: <19990923185727.D45B615068@hub.freebsd.org> Date: Thu, 23 Sep 1999 11:57:27 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am seeing bounced mail from -current since this evening. > > The message is: > > <<< 550 service unavailable; [207.93.148.150] blocked using \ > dul.maps.vix.com > > I tried disconnecting from my ISP and redialing to change the IP. Same > results. > > My ISP, netcom (now mindspring) has no idea. Is FreeBSD blocking? you must relay your mail through your service provider. currently you are trying to send mail directly to FreeBSD.org. hub.FreeBSD.org does not talk to dial up IP addresses. this is an anti-spam measure. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 11:58:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 541FC15068 for ; Thu, 23 Sep 1999 11:58:29 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA25120; Thu, 23 Sep 1999 13:57:47 -0500 (CDT) (envelope-from dan) Date: Thu, 23 Sep 1999 13:57:47 -0500 From: Dan Nelson To: bsd@picard.mandrakesoft.de Cc: Matthew Dillon , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Message-ID: <19990923135747.A24995@dan.emsphone.com> References: <199909231803.LAA28917@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Sep 23), bsd@picard.mandrakesoft.de said: > On Thu, 23 Sep 1999, Matthew Dillon wrote: > > I tend not to like the higher optimization levels because they > > cause the compiler to attempt to turn static functions into inlines > > and, in my opinion, it doesn't do a very good job of selecting > > which functions to convert. The result is that I see bloated > > binaries with no performance gain to show for it. > > > > EGCS's -Os is my favorite. > > Have you tried specifying -O6 and -Os (With -Os following -O6 because > we want it to override the values set by -O6)? I haven't tried it for > a while, but at least in an older egcs snapshot (somewhere between > 1.1.2 and gcc 2.95), it worked (optimize as much as possible, but > value size over speed). Order doesn't matter, since -Os is more like an optimization flag then a level (should really have been called -foptimize-size IMHO). It doesn't disable/enable anything else apart from forcing the minimum O level to 2. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:17:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 5BFD415058 for ; Thu, 23 Sep 1999 12:17:00 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com (localhost [127.0.0.1]) by gw.nectar.com (Postfix) with ESMTP id C9E4ABD08; Thu, 23 Sep 1999 14:18:47 -0500 (CDT) 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-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Darryl Okahata Cc: freebsd-current@FreeBSD.ORG In-reply-to: <199909231846.LAA04038@mina.sr.hp.com> References: <199909231846.LAA04038@mina.sr.hp.com> Subject: pcl-cvs (was Re: ccd build failure) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Sep 1999 14:18:47 -0500 Message-Id: <19990923191847.C9E4ABD08@gw.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the script! I thought I'd point out pcl-cvs for emacs, which can be found at src/contrib/cvs/tools/pcl-cvs or it can be easily installed using XEmacs 21's package management. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 23 September 1999 at 11:46, Darryl Okahata wrote: > In the interests of peace and harmony (;-), I'd like to submit the > attached perl script, which lists the status of cvs-controlled files. [snip] > CVS is severely lacking in many areas (it is all we have, though), and > one thing it is missing is an easy way of showing concise file status. [snip] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:23:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 69CD914D84 for ; Thu, 23 Sep 1999 12:23:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA07919; Thu, 23 Sep 1999 13:22:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA42769; Thu, 23 Sep 1999 13:23:11 -0600 (MDT) Message-Id: <199909231923.NAA42769@harmony.village.org> To: Matthew Dillon Subject: Re: ccd build failure Cc: Ben Rosengart , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Sep 1999 09:44:42 PDT." <199909231644.JAA28110@apollo.backplane.com> References: <199909231644.JAA28110@apollo.backplane.com> Date: Thu, 23 Sep 1999 13:23:11 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909231644.JAA28110@apollo.backplane.com> Matthew Dillon writes: : Mutual respect doesn't exist when one of the parties refuses to listen : to *anyone's* advise, ever. I think that this overstates things too much. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:26:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DC9E614BEA for ; Thu, 23 Sep 1999 12:26:29 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA07942; Thu, 23 Sep 1999 13:26:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA42815; Thu, 23 Sep 1999 13:26:35 -0600 (MDT) Message-Id: <199909231926.NAA42815@harmony.village.org> To: Jonathan Lemon Subject: Re: Problem with Compaq SMART-2SL array controller Cc: freebsd@osterskov.dk, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Sep 1999 12:07:58 CDT." <199909231707.MAA21789@free.pcs> References: <199909231707.MAA21789@free.pcs> Date: Thu, 23 Sep 1999 13:26:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909231707.MAA21789@free.pcs> Jonathan Lemon writes: : It appears so. The IDA driver needs to stomp on the WD driver's : vectors in order to boot off of the RAID controller. It seems that : something changed so that wd is getting probed after the ida driver : now, and removing the vectors. Is this so that it could mount root? In 3.x the only way to do this is to have a special disk label type. I've hacked things to get fla bootable on -stable using this method. The sysinstall program hasn't been updated, however. : For now, you could remove the IDE devices from the config file, : until this gets fixed. Ideally, the boot blocks/loader should be : taught to boot from something other than wd() or da(). phk's fla driver mount / correctly when it is the boot device. However, the boot loader does have some interesting limitations in this area last time I checked. Likely it was due to using the -stable version for most of my testing. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:29:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id E58D714BEA for ; Thu, 23 Sep 1999 12:29:16 -0700 (PDT) (envelope-from tobez@plab.ku.dk) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by plab.ku.dk (8.9.1/8.9.1) with ESMTP id VAA09341; Thu, 23 Sep 1999 21:27:22 +0200 (CEST) Received: (from tobez@localhost) by lion.plab.ku.dk (8.9.3/8.9.3) id VAA40674; Thu, 23 Sep 1999 21:23:52 +0200 (CEST) (envelope-from tobez) Date: Thu, 23 Sep 1999 21:23:52 +0200 From: Anton Berezin To: Darryl Okahata Cc: Matthew Dillon , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Message-ID: <19990923212352.A40492@lion.plab.ku.dk> References: <199909231846.LAA04038@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199909231846.LAA04038@mina.sr.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 23, 1999 at 11:46:38AM -0700, Darryl Okahata wrote: > I'd like to submit the attached perl script, which lists the status of > cvs-controlled files. In particular, it's very useful for determining > which files have been modified but not committed With the following patch this scripts becomes even more useful (properly handles situations when the file is missing): --- /home/tobez/cvsinfo Thu Sep 23 21:19:53 1999 +++ cvsinfo Thu Sep 23 21:19:22 1999 @@ -69,7 +69,7 @@ $cmd = "cvs status -l"; open(IN, "$cmd 2>&1 |") || die "$!"; while () { - if (/^File:\s+([^\s]+)\s+Status:\s+(.+)$/i){ + if (/^File:\s+(?:no file\s+)?([^\s]+)\s+Status:\s+(.+)$/i){ $file = $1; $status = $2; if ($all_status || $status ne 'Up-to-date') { Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:30:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 8DE1D15EE9 for ; Thu, 23 Sep 1999 12:29:30 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA01658 for freebsd-current@FreeBSD.ORG; Thu, 23 Sep 1999 21:28:15 +0200 (CEST) (envelope-from olli) Date: Thu, 23 Sep 1999 21:28:15 +0200 (CEST) From: Oliver Fromme Message-Id: <199909231928.VAA01658@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bsd@picard.mandrakesoft.de wrote in list.freebsd-current: > On Thu, 23 Sep 1999, The Hermit Hacker wrote: > > just curious, but what is the max setting that can be used to compile the > > kernel? > > Works rather nicely here with > > -O6 -mpentiumpro -march=pentiumpro -pipe -s -fexpensive-optimizations > -ffast-math -ffast-math shouldn't have any effect, because the kernel does not contain floating-point code. -ffexp-opt is already included in -O3 (which is the maximum -O value supported by the compiler), so it is redundant, too. The gcc optimizer is traditionally buggy. I wouldn't trust a system compiled with anything more than -O (especially on production servers). The higher optimization levels don't provide much of a speed improvement anyway, sometimes they make the code even slower. YMMV. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:42:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4953414D48 for ; Thu, 23 Sep 1999 12:42:27 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA01843 for freebsd-current@freebsd.org; Thu, 23 Sep 1999 21:42:11 +0200 (CEST) (envelope-from olli) Date: Thu, 23 Sep 1999 21:42:11 +0200 (CEST) From: Oliver Fromme Message-Id: <199909231942.VAA01843@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: Re: ccd build failure Organization: Administration Heim 3 Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darryl Okahata wrote in list.freebsd-current: > In the interests of peace and harmony (;-), I'd like to submit the > attached perl script, which lists the status of cvs-controlled files. > In particular, it's very useful for determining which files have been > modified but not committed, like: > [...] Uhm... Maybe I misunderstand what your 100-line perl script does, but I use the following 3-line shell script instead: #!/bin/sh - cvs status | grep '^File:' | grep -v 'Status: Up-to-date$' true Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:48: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 220BA14CD0 for ; Thu, 23 Sep 1999 12:48:02 -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 OAA19932; Thu, 23 Sep 1999 14:47:00 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id OAA10690; Thu, 23 Sep 1999 14:46:59 -0500 (CDT) Message-ID: <19990923144658.29434@right.PCS> Date: Thu, 23 Sep 1999 14:46:58 -0500 From: Jonathan Lemon To: Warner Losh Cc: freebsd@osterskov.dk, current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller References: <199909231707.MAA21789@free.pcs> <199909231926.NAA42815@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199909231926.NAA42815@harmony.village.org>; from Warner Losh on Sep 09, 1999 at 01:26:35PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 09, 1999 at 01:26:35PM -0600, Warner Losh wrote: > In message <199909231707.MAA21789@free.pcs> Jonathan Lemon writes: > : It appears so. The IDA driver needs to stomp on the WD driver's > : vectors in order to boot off of the RAID controller. It seems that > : something changed so that wd is getting probed after the ida driver > : now, and removing the vectors. > > Is this so that it could mount root? In 3.x the only way to do this > is to have a special disk label type. I've hacked things to get fla > bootable on -stable using this method. The sysinstall program hasn't > been updated, however. Yes. The IDA driver will be happy with it's own device nodes (/dev/ida....), but last time I checked, the boot/loader would only understand root devices of wd() or da(). I understand that Soren's ad() driver has the same problem. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 12:54:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4414614EDD for ; Thu, 23 Sep 1999 12:54:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA08100; Thu, 23 Sep 1999 13:54:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA43042; Thu, 23 Sep 1999 13:54:17 -0600 (MDT) Message-Id: <199909231954.NAA43042@harmony.village.org> To: Jonathan Lemon Subject: Re: Problem with Compaq SMART-2SL array controller Cc: freebsd@osterskov.dk, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Sep 1999 14:46:58 CDT." <19990923144658.29434@right.PCS> References: <19990923144658.29434@right.PCS> <199909231707.MAA21789@free.pcs> <199909231926.NAA42815@harmony.village.org> Date: Thu, 23 Sep 1999 13:54:17 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990923144658.29434@right.PCS> Jonathan Lemon writes: : Yes. The IDA driver will be happy with it's own device nodes : (/dev/ida....), but last time I checked, the boot/loader would : only understand root devices of wd() or da(). I understand that : Soren's ad() driver has the same problem. That's not entirely true. I've hacked the 3.x boot loader to grok fla devices on boot. In 4.x I didn't need to hack anything. It just worked, but I might have had to specify the BIOS device number hwen booting... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 13:12:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id A419614CD0 for ; Thu, 23 Sep 1999 13:04:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA88130; Thu, 23 Sep 1999 21:57:04 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909231957.VAA88130@gratis.grondar.za> To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Date: Thu, 23 Sep 1999 21:57:03 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am getting wholely sick and tired of having to clean up after Poul's > commit bugs. I've spent at least a hundred hours and probably more in > the last month fixing things that he's broken, like BOOTP and VN. I > would much rather spend my time on other more interesting things. Matt - you don't "have" to fix _anyone's_ bugs; like everyone here, you are a volunteer, and you do it for the love of the job. If it really is so painful, then perhaps you should reconsider your motives. I think both of you are very valuable assets to the FreeBSD project, but this public Jihad is a bit much. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 14:28: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 91F4E14F02 for ; Thu, 23 Sep 1999 14:28:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA00514; Thu, 23 Sep 1999 23:24:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Jonathan Lemon , freebsd@osterskov.dk, current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Thu, 23 Sep 1999 13:26:35 MDT." <199909231926.NAA42815@harmony.village.org> Date: Thu, 23 Sep 1999 23:24:55 +0200 Message-ID: <512.938121895@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909231926.NAA42815@harmony.village.org>, Warner Losh writes: >phk's fla driver mount / correctly when it is the boot device. >However, the boot loader does have some interesting limitations in >this area last time I checked. Likely it was due to using the -stable >version for most of my testing. I actually have a design and most of an implementation for a better handling of root device/method selection, the boot blocks already pass a environment string in with the name (at least in current). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 14:40:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id F122814C7F for ; Thu, 23 Sep 1999 14:40:06 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA16137; Thu, 23 Sep 1999 23:24:25 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03420; Thu, 23 Sep 1999 22:59:44 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909232059.WAA03420@yedi.iaf.nl> Subject: Re: ccd build failure In-Reply-To: <2218.938110535@localhost> from "Jordan K. Hubbard" at "Sep 23, 1999 11:15:35 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 23 Sep 1999 22:59:44 +0200 (CEST) Cc: dillon@apollo.backplane.com, phk@critter.freebsd.dk, jwd@unx.sas.com, freebsd-current@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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jordan K. Hubbard wrote ... > > I just forgot to commit a header file. Sorry about that. I test all > > of my code, unlike you Poul. > > > > Insert nasty message about how people shouldn't post idiotic comments. > > Ummm. I don't see this going in positive directions at all and I'd > appreciate it highly if everyone involved would just count to 10 and > stay away from their mail clients for awhile. The only point in even > sending email is to COMMUNICATE with other people and I don't see any > communication happening here. To add to that: if people absolutely must have to fight some issue at the brass knuckles level, why not do it in private email? Having it on an archived mailing list that 1000s of people read (well, are subscribed to) IMO gives the project a bad name (let alone the people doing the fighting). But maybe I'm weird in this respect Wilko (who shuts up now) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 14:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.fwi.com (mail.fwi.com [209.84.160.144]) by hub.freebsd.org (Postfix) with ESMTP id 9233614F34 for ; Thu, 23 Sep 1999 14:48:47 -0700 (PDT) (envelope-from croyle@gelemna.ft-wayne.in.us) Received: from gelemna.ft-wayne.in.us (fw5-40.fwi.com [209.84.173.236]) by mail.fwi.com (8.8.5/8.8.5) with ESMTP id QAA01750; Thu, 23 Sep 1999 16:48:20 -0500 (EST) Received: (from croyle@localhost) by gelemna.ft-wayne.in.us (8.9.3/8.9.3) id QAA21569; Thu, 23 Sep 1999 16:47:43 -0500 (EST) (envelope-from croyle) To: Mark Murray Cc: current@freebsd.org Subject: On hub.freebsd.org refusing to talk to dialups References: <199909231215.OAA85963@gratis.grondar.za> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Don Croyle Date: 23 Sep 1999 16:47:42 -0500 Organization: Minimal at best In-Reply-To: Mark Murray's message of "Thu, 23 Sep 1999 14:15:31 +0200" Message-ID: <86u2olfgg1.fsf@emerson.gelemna.ft-wayne.in.us> Lines: 33 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray writes: [hub.freebsd.org now blocking IP adresses on the DUL] > If you use your ISP's mailer as a "smarthost", you will avoid this > problem. > > Thos of us in the anti-spam community think thsat this is a Good > Thing. That's one way to cut down on support mail from new users, I suppose. This is yet another feel-good measure that will end up doing at least as much harm as good. At a minimum the default freebsd.mc needs something like the attached patch. Something prominent in the FAQ and support for defining SMART_HOST in sysinstall is probably called for as well. --- freebsd.mc.orig Sun Feb 28 14:52:06 1999 +++ freebsd.mc Thu Sep 23 16:31:33 1999 @@ -53,6 +53,8 @@ FEATURE(virtusertable, `hash -o /etc/mail/virtusertable')dnl dnl Uncomment to activate Realtime Blackhole List (recommended!) dnl FEATURE(rbl)dnl +dnl Dialup users should uncomment and define this appropriately +dnl define(`SMART_HOST', `your.isp.mail.server')dnl FEATURE(local_lmtp)dnl define(`LOCAL_MAILER_FLAGS', LOCAL_MAILER_FLAGS`'P)dnl define(`confCW_FILE', `-o /etc/mail/sendmail.cw')dnl -- I've always wanted to be a dilettante, but I've never quite been ready to make the commitment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 14:52:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 88FDA14FB2 for ; Thu, 23 Sep 1999 14:52:48 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA04947 for ; Thu, 23 Sep 1999 14:51:32 -0700 (PDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id OAA19201; Thu, 23 Sep 1999 14:51:06 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id OAA06536; Thu, 23 Sep 1999 14:51:15 -0700 (PDT) Message-Id: <199909232151.OAA06536@mina.sr.hp.com> To: freebsd-current@FreeBSD.ORG Cc: Anton Berezin Subject: Re: ccd build failure Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 23 Sep 1999 21:42:11 +0200." <199909231942.VAA01843@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: multipart/mixed; boundary="Multipart_Thu_Sep_23_14:51:14_1999-1" Content-Transfer-Encoding: 7bit Date: Thu, 23 Sep 1999 14:51:15 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Thu_Sep_23_14:51:14_1999-1 Content-Type: text/plain; charset=US-ASCII Oliver Fromme wrote: > Uhm... Maybe I misunderstand what your 100-line perl script > does, but I use the following 3-line shell script instead: > > #!/bin/sh - > cvs status | grep '^File:' | grep -v 'Status: Up-to-date$' > true This works (and is faster), but it doesn't give you concise, nicely-formatted pathnames. Personally, I prefer status like: i386/linux/linux_file.c Locally Modified kern/imgact_elf.c Locally Modified instead of: cvs server: Examining aaa ... cvs server: Examining bbb ... cvs server: Examining ccc ... cvs server: Examining ddd ... cvs server: Examining eee ... File: linux_file.c Status: Locally Modified cvs server: Examining fff ... cvs server: Examining ggg ... File imgact_elf.c Status: Locally Modified I think the script's output is easier to read. [ Hmmm, but you do incidentally bring up a point: it's better to parse the output of "cvs status -R", instead of the ugly way used by the script. I've attached a newer, faster version. Instead of taking around 3 minutes to list the status below /usr/src/sys, this new version takes around 1 minute. I've also applied Anton's fix. ] -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. --Multipart_Thu_Sep_23_14:51:14_1999-1 Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename="cvsinfo" Content-Transfer-Encoding: quoted-printable #! /usr/bin/perl #########################################################################= ###### # # File: cvsinfo # RCS: $Header: $ # Description: List CVS files in the current directory and below that ar= e # not up-to-date. These files are typically those which have # been modified or need updating. # # This is a new, rewritten, version, thanks to feedback from # Anton Berezin and # Oliver Fromme . # # Usage: # # cvsinfo [-a] [-l] # # Options: # # -a Show status of all files, and not just those which # are not up-to-date. # # -l Show status of files in the current directory only. # Do not recurse into subdirectories. # # Author: Darryl Okahata # Created: Thu Sep 23 14:32:34 1999 # Modified: Thu Sep 23 14:45:03 1999 (Darryl Okahata) darrylo@sr.hp.c= om # Language: CPerl # Package: N/A # Status: Experimental # # (C) Copyright 1999, Hewlett-Packard, all rights reserved. # #########################################################################= ###### #########################################################################= ###### require 'getopts.pl'; &Getopts('al'); $all_status =3D 1 if ($opt_a); # Explicitly specify options, just in case the user has overridden them i= n # ~/.cvsrc. if ($opt_l) { $recursive =3D "-l"; } else { $recursive =3D "-R"; } $dir =3D "."; open(IN, "cvs status $recursive 2>&1 |") || die "$!"; while() { if (/^cvs\s+server:\s+Examining\s+([^\s].*)$/) { $dir =3D $1; } elsif (/^File:\s+(?:no\s+file\s+)?([^\s]+)\s+Status:\s+(.+)$/i){ $file =3D $1; $status =3D $2; if ($all_status || $status ne 'Up-to-date') { if ($status eq 'Needs Patch') { $status =3D 'Needs Updating'; } printf("%-50s %s\n", ($dir eq '.') ? $file : "$dir/$file", $status); if ($status =3D~ /Locally Modified/) { push(@update_files, $file); } } } elsif (/\[status\s+aborted\]/) { die "$_\n"; } } --Multipart_Thu_Sep_23_14:51:14_1999-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 15:49: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id A042B14EB4; Thu, 23 Sep 1999 15:49:03 -0700 (PDT) From: "Jonathan M. Bresler" To: croyle@gelemna.ft-wayne.in.us Cc: mark@grondar.za, current@freebsd.org In-reply-to: <86u2olfgg1.fsf@emerson.gelemna.ft-wayne.in.us> (message from Don Croyle on 23 Sep 1999 16:47:42 -0500) Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-Id: <19990923224903.A042B14EB4@hub.freebsd.org> Date: Thu, 23 Sep 1999 15:49:03 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don, excellent idea. i have expanded upon it and added it to freebsd.mc. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 15:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 37EED14DB1 for ; Thu, 23 Sep 1999 15:57:34 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA12496; Thu, 23 Sep 1999 17:54:00 -0500 (CDT) Date: Thu, 23 Sep 1999 17:54:00 -0500 From: "Matthew D. Fuller" To: Darryl Okahata Cc: freebsd-current@FreeBSD.ORG, Anton Berezin Subject: Re: ccd build failure Message-ID: <19990923175400.M10357@futuresouth.com> References: <199909231942.VAA01843@dorifer.heim3.tu-clausthal.de> <199909232151.OAA06536@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199909232151.OAA06536@mina.sr.hp.com>; from Darryl Okahata on Thu, Sep 23, 1999 at 02:51:15PM -0700 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 23, 1999 at 02:51:15PM -0700, a little birdie told me that Darryl Okahata remarked > Oliver Fromme wrote: > > > Uhm... Maybe I misunderstand what your 100-line perl script > > does, but I use the following 3-line shell script instead: > > > > #!/bin/sh - > > cvs status | grep '^File:' | grep -v 'Status: Up-to-date$' > > true > > This works (and is faster), but it doesn't give you concise, > nicely-formatted pathnames. Personally, I prefer status like: OK: #!/bin/sh (cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2> /dev/null -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 16:10:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 4FDBA14FFA for ; Thu, 23 Sep 1999 16:10:13 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id TAA03636; Thu, 23 Sep 1999 19:07:53 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id QAA25896; Thu, 23 Sep 1999 16:08:10 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id QAA07032; Thu, 23 Sep 1999 16:08:17 -0700 (PDT) Message-Id: <199909232308.QAA07032@mina.sr.hp.com> To: "Matthew D. Fuller" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 23 Sep 1999 17:54:00 CDT." <19990923175400.M10357@futuresouth.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 23 Sep 1999 16:08:17 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" wrote: > OK: > #!/bin/sh > (cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2> /dev/null This doesn't give path information -- it's worse than before, in that the (verbose) path information is thrown away. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 16:16:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 640A714E97 for ; Thu, 23 Sep 1999 16:16:33 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id DAA41873; Fri, 24 Sep 1999 03:12:03 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id DAA05642; Fri, 24 Sep 1999 03:15:45 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199909232315.DAA05642@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Matthew D. Fuller" Cc: Darryl Okahata , freebsd-current@FreeBSD.ORG, Anton Berezin From: Dmitrij Tejblum Subject: Re: ccd build failure In-reply-to: Your message of "Thu, 23 Sep 1999 17:54:00 CDT." <19990923175400.M10357@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Sep 1999 03:15:44 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" wrote: > OK: > #!/bin/sh > (cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2> /dev/null Excuse me, I apparently completely missed the idea, but what is wrong with cvs -qn up ? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 21:13:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 83E8015B60 for ; Thu, 23 Sep 1999 21:13:17 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id VAA13436; Thu, 23 Sep 1999 21:12:19 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 23 Sep 1999 21:12:19 -0700 Date: Thu, 23 Sep 1999 21:12:19 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: dfr@nlsystems.com Cc: freebsd-current@freebsd.org Subject: freebsd-uthread.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dfr@nlsystems.com,freebsd-current@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In three places in your code you do the following or something similar: ptr = (CORE_ADDR) cached_pthread.nxt; struct pthread has no member nxt in either -current or -stable and your patch did not add it to pthread_private.h What did you mean for this to be? Thanks. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 21:29:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 76A5615058 for ; Thu, 23 Sep 1999 21:29:25 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id QAA32588; Fri, 24 Sep 1999 16:28:21 +1200 (NZST) Date: Fri, 24 Sep 1999 16:28:20 +1200 From: Joe Abley To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-ID: <19990924162820.A27798@patho.gen.nz> References: <199909231215.OAA85963@gratis.grondar.za> <86u2olfgg1.fsf@emerson.gelemna.ft-wayne.in.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <86u2olfgg1.fsf@emerson.gelemna.ft-wayne.in.us>; from Don Croyle on Thu, Sep 23, 1999 at 04:47:42PM -0500 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray writes: > [hub.freebsd.org now blocking IP adresses on the DUL] > > If you use your ISP's mailer as a "smarthost", you will avoid this > problem. > > Thos of us in the anti-spam community think thsat this is a Good > Thing. One of us, at least, evidently. How much mail does the use of the MAPS DUL reject? How much of that do you think is worth rejecting? Serious questions; just interested. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 22:30: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from out1.mx.skynet.be (out1.mx.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id DAF1D14D7E for ; Thu, 23 Sep 1999 22:29:55 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out1.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id HAA09184; Fri, 24 Sep 1999 07:29:41 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id HAA16596; Fri, 24 Sep 1999 07:29:38 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19990924162820.A27798@patho.gen.nz> References: <199909231215.OAA85963@gratis.grondar.za> <86u2olfgg1.fsf@emerson.gelemna.ft-wayne.in.us> <19990924162820.A27798@patho.gen.nz> Date: Fri, 24 Sep 1999 07:05:20 +0200 To: Joe Abley , Mark Murray From: Brad Knowles Subject: Re: On hub.freebsd.org refusing to talk to dialups Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:28 PM +1200 1999/9/24, Joe Abley wrote: > How much mail does the use of the MAPS DUL reject? I don't know about the stats from hub.freebsd.org, but from my experience it rejects a relatively small amount. > How much of that do you think is worth rejecting? Again, from my experience, most of it. Damn few dial-up users around the world are clueful enough to be able to run their own mail server properly, and to be able to prevent it from being used as an open relay. IME, the *vast* majority of people with dial-up accounts that attempt to directly contact remote servers are in fact junkmailers that are attempting to secretly send out their effluent while by-passing the mail servers provided by their ISP, so that they hopefully don't get detected. A classic example of this would be someone using a throwaway AOL account to send out as many junkmail messages as they can in several hours through a number of open relays, knowing that they will be detected and the "free" account will be terminated in a few hours. This is becoming pretty standard practice, and is generally recommended. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 22:37:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 6CC4214CD0 for ; Thu, 23 Sep 1999 22:37:03 -0700 (PDT) (envelope-from john@nlc.net.au) Received: (qmail 19631 invoked from network); 24 Sep 1999 15:36:57 +1000 Received: from nhj.nlc.net.au (HELO saruman) (203.24.133.1) by nhj.nlc.net.au with SMTP; 24 Sep 1999 15:36:57 +1000 Message-ID: <011701bf064e$d0f7f4f0$6cb611cb@scitec.com.au> From: "John Saunders" To: "FreeBSD current" Subject: Automating filesystem check at boot time Date: Fri, 24 Sep 1999 15:36:56 +1000 Organization: NORTHLINK COMMUNICATIONS 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 5.00.2314.1300 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I administer a number of remote FreeBSD boxes and starting with 3.x they have been unreliable at rebooting. We all know FreeBSD wants to keep running forever, however it seems to be at the expense of reboot stability. I have found the following problems occuring. 1) After a power failure the filesystem is inconsistent such that a manual fsck is required. Actually this can also occur following a crash or failed shutdown. However I must admit that FreeBSD does this less than Linux, but it still does it. 2) After running "shutdown -r now" FreeBSD will kill off all processes but complain that is unable to kill everything. It then says Syncing disks...done. Then hangs until the reset button is pressed. I think that amd is causing this. The time this happened was following a reboot to clear an amd problem when the NFS server was isolated from from the network for some time. My previous hacks at Linux has led me to the following patch to /etc/rc which I have been using for a while on FreeBSD to solve point 1. It has saved me a lot of driving on 2 occasions. The program "waitkey" is one I wrote that sleeps for the specicifed and returns TRUE (0), unless a key is pressed in which case it returns the ASCII code for the key. +++ rc Wed Aug 18 13:59:59 1999 @@ -69,6 +69,12 @@ ;; 8) echo "Automatic file system check failed... help!" + if waitkey 30; then + exit 1 + fi + fsck -y + reboot + echo "reboot failed... help!" exit 1 ;; 12) Anyway I am proposing a method where FreeBSD can be configured though an rc.conf knob to be more friendly in an unattended situation. I propose as a first step that a knob called "unattended_operation" be added with a default value of "NO". Enabling this knob can be used to allow code like the above to be executed. It can also be used to force the sysctl variable "debug.debugger_on_panic" to 0 in the rc file. I can also contribute the waitkey.c program. It may even be useful for other stuff with some changes to the command syntax. Does anybody have any strong opinions on this, either way? I have this running on my machine at present so I'm not too fussed either way, just thought it might be useful for other people as well. I can supply code and patches, but I would like somebody with commit privs to look over the code, make suggestions and eventually commit the work. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 23 23:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 8AEDA15082 for ; Thu, 23 Sep 1999 23:15:08 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id XAA01586; Thu, 23 Sep 1999 23:13:02 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909240613.XAA01586@gndrsh.dnsmgr.net> Subject: Re: Automating filesystem check at boot time In-Reply-To: <011701bf064e$d0f7f4f0$6cb611cb@scitec.com.au> from John Saunders at "Sep 24, 1999 03:36:56 pm" To: john@nlc.net.au (John Saunders) Date: Thu, 23 Sep 1999 23:13:02 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG (FreeBSD current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > I administer a number of remote FreeBSD boxes and starting with 3.x > they have been unreliable at rebooting. We all know FreeBSD wants to > keep running forever, however it seems to be at the expense of > reboot stability. I have found the following problems occuring. > > 1) After a power failure the filesystem is inconsistent such that > a manual fsck is required. Actually this can also occur following > a crash or failed shutdown. However I must admit that FreeBSD does > this less than Linux, but it still does it. Unattended remotly administered systems shall have an ups, power failure is not an acceptable operation in 99% of these types of systems. There is no good reason to have to hack thems up to deal with this situation. Get a good ups, and install one of the ups monitor daemons from ports to properly shut down before total battery failure. > 2) After running "shutdown -r now" FreeBSD will kill off all processes > but complain that is unable to kill everything. It then says Syncing > disks...done. Then hangs until the reset button is pressed. I think > that amd is causing this. The time this happened was following a > reboot to clear an amd problem when the NFS server was isolated from > from the network for some time. You need to find and fix what ever it is that is not dieing when being told to die. Your work around is a bandaid that only hides the real problem, which is probably a bug some place in something. amd and NFS are good first conidates. Just what process does it complain that it is unable to kill, or does it just say could not kill? > My previous hacks at Linux has led me to the following patch to /etc/rc > which I have been using for a while on FreeBSD to solve point 1. It has > saved me a lot of driving on 2 occasions. The program "waitkey" is one > I wrote that sleeps for the specicifed and returns TRUE (0), unless a > key is pressed in which case it returns the ASCII code for the key. Not a bad hack, but I will never ever run a fsck -y without at least a log file some place, and then only as a last resort after imaging the disk and doing everything else I can to try and recoverer it if it has anything important at all on it. > > +++ rc Wed Aug 18 13:59:59 1999 > @@ -69,6 +69,12 @@ > ;; > 8) > echo "Automatic file system check failed... help!" > + if waitkey 30; then > + exit 1 > + fi > + fsck -y fsck -y >tosomeplace writable. Hard to figure out at this stage, but if you run a seperate /tmp like we do you can always change this to: newfs /dev/rawtmpdev mount -u /tmp fsck -u >&/tmp/fsck-y.OUT So you have some clue as to what got destroyed during the fsck. > + reboot > + echo "reboot failed... help!" Have you actually ever seen this echo execute?? > exit 1 > ;; > 12) > > Anyway I am proposing a method where FreeBSD can be configured though an > rc.conf knob to be more friendly in an unattended situation. I propose > as a first step that a knob called "unattended_operation" be added with > a default value of "NO". Enabling this knob can be used to allow code > like the above to be executed. It can also be used to force the sysctl > variable "debug.debugger_on_panic" to 0 in the rc file. You might want to get input from Julian and friends at Whistle, they are experts at unattended operations... > > I can also contribute the waitkey.c program. It may even be useful for > other stuff with some changes to the command syntax. This can actually be done from /bin/sh using a background processes, just run a read from the console in background, sleep for X, check for child status, if child alive no keypress occured, kill child. > > Does anybody have any strong opinions on this, either way? I have this > running on my machine at present so I'm not too fussed either way, just > thought it might be useful for other people as well. I can supply code > and patches, but I would like somebody with commit privs to look over > the code, make suggestions and eventually commit the work. I'll strongly object to any automated running of a fsck -y, it is far to dangerious for way to many folks. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 0: 4:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 934FE14F9C for ; Fri, 24 Sep 1999 00:04:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA10985; Fri, 24 Sep 1999 16:04:39 +0900 (JST) Message-ID: <37EAED6F.2460BC8C@newsguy.com> Date: Fri, 24 Sep 1999 12:18:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jonathan Lemon Cc: freebsd@osterskov.dk, current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller References: <199909231707.MAA21789@free.pcs> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > For now, you could remove the IDE devices from the config file, > until this gets fixed. Ideally, the boot blocks/loader should be > taught to boot from something other than wd() or da(). Alas, the loader uses BIOS to read the disk. Anything the BIOS can read, so can the loader. The way it _passes_ the information, though, is limited by the kernel. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Thus, over the years my wife and I have physically diverged. While I have zoomed toward a crusty middle-age, she has instead clung doggedly to the sweet bloom of youth. Naturally I think this unfair. Yet, if it was the other way around, I confess I wouldn't be happy either." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 0:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 81BEB14F9C for ; Fri, 24 Sep 1999 00:10:21 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA10963; Fri, 24 Sep 1999 16:04:30 +0900 (JST) Message-ID: <37EAEB1A.3B0E4263@newsguy.com> Date: Fri, 24 Sep 1999 12:08:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: bsd@picard.mandrakesoft.de Cc: Dan Nelson , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bsd@picard.mandrakesoft.de wrote: > > But specifying something too high (-O99) doesn't hurt - I'm using -O6 for > gcc 2.95.1 (which, by the way, compiles almost everything in 3.3-RELEASE > and 4.0-CURRENT, the only thing still troubling me with it is the kernel). The point is that it _does_ hurt. Anything above -O3 is _likely_ to have bugs. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Thus, over the years my wife and I have physically diverged. While I have zoomed toward a crusty middle-age, she has instead clung doggedly to the sweet bloom of youth. Naturally I think this unfair. Yet, if it was the other way around, I confess I wouldn't be happy either." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 0:39:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 80BCE15554 for ; Fri, 24 Sep 1999 00:39:42 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA90307; Fri, 24 Sep 1999 09:38:24 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909240738.JAA90307@gratis.grondar.za> To: Joe Abley Cc: current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups Date: Fri, 24 Sep 1999 09:38:23 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How much mail does the use of the MAPS DUL reject? Virtually none. The idea is that dial-up users use their own ISP's smarthosts, in which case the ISP can nail them if they are spammers, and I don't get their spam if they go for the "direct-to-MX" or "direct injection" spamming method. Some mail may get temporarily blocked until the sender added his IPS's smathost to his mailing configs. > How much of that do you think is worth rejecting? I wish to reject no legitimate mail. I would fight use of the DUL _hard_ if there was no (smarthost) alternative. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 0:57:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id E11BA14E0E for ; Fri, 24 Sep 1999 00:57:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA02115; Fri, 24 Sep 1999 00:50:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909240750.AAA02115@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd@osterskov.dk Cc: current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Thu, 23 Sep 1999 17:43:17 +0200." <99092318013400.00254@SMP_XEON.OSTERSKOV.DK> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Sep 1999 00:50:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After doing a cvsup yesterday evening i can't seem to boot on my > raid cotroller using the same kernel config. > > Is -current probing hardware i a different way now or ?? This is a consequence of a defect in the way that the ida driver works, and new code which resorts the disk drivers (so that the 'wd' driver throws out the 'ida' driver). The correct fix for this is nontrivial and a little while off; you might want to go back to your old kernel for a while if the issue hasn't already been resolved. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 1: 2:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 367DD15186 for ; Fri, 24 Sep 1999 01:02:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA02144; Fri, 24 Sep 1999 00:54:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909240754.AAA02144@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jonathan Lemon Cc: freebsd@osterskov.dk, current@freebsd.org Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Thu, 23 Sep 1999 12:07:58 CDT." <199909231707.MAA21789@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Sep 1999 00:54:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For now, you could remove the IDE devices from the config file, > until this gets fixed. Ideally, the boot blocks/loader should be > taught to boot from something other than wd() or da(). The loader groks this already; there's some missing glue in the kernel that Poul has already worked out. I'm not sure if he's going to write it or whether it'll need some other enterprising soul at this point. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 1: 8: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 0F08614D71 for ; Fri, 24 Sep 1999 01:07:52 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA05283; Fri, 24 Sep 1999 11:06:53 +0300 (EEST) (envelope-from will) To: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... References: <199909231928.VAA01658@dorifer.heim3.tu-clausthal.de.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 24 Sep 1999 11:06:53 +0300 In-Reply-To: Oliver Fromme's message of "23 Sep 1999 22:33:13 +0300" Message-ID: <86zoycvile.fsf@not.demophon.com> Lines: 32 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: > The gcc optimizer is traditionally buggy. I wouldn't trust a > system compiled with anything more than -O (especially on > production servers). The higher optimization levels don't > provide much of a speed improvement anyway, sometimes they make > the code even slower. YMMV. This is a somewhat religious issue. There is no absolutely safe optimization level, and recommendations needn't remain constant, especially as the compiler changes. There are known problems that break code when compiling with -O. I know at least one case that breaks with -O or -O2 but works with -O3 (this applies to both pre-egcs and egcs compilers). When things will break is very unpredictable. In my experience, -O2 rarely causes additional breakage compared to -O in correct code. In egcs >= 1.1 and gcc >= 2.95, -O2 includes new optimizations that can improve performance quite significantly. Sometimes breakage can also be caused by incorrect code that is only exposed by the optimization. You really shouldn't generalize too much. All you can correctly state is that software package X seems to work well with gcc/egcs version Y at optimization level Z. You can also state that some gcc/egcs version has known bugs at some optimization level (however, all reasonably current versions have known bugs at *all* optimization levels). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 1:28:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4ACA415D74 for ; Fri, 24 Sep 1999 01:28:26 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA02942 for ; Fri, 24 Sep 1999 10:28:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: test/review of tty changes From: Poul-Henning Kamp Date: Fri, 24 Sep 1999 10:28:25 +0200 Message-ID: <2940.938161705@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://phk.freebsd.dk/tty This patch clears the way for removing a number of fields in struct cdevsw: d_stop moved to struct tty. d_reset unused. d_devtotty linkage now provided by dev_t->si_tty. Once this patch is in, these fields will be removed from struct cdevsw together with d_params and d_maxio. The changes in this patch consist of: initialize dev->si_tty in *_open() initialize tty->t_stop remove devtotty functions rename ttpoll to ttypoll a few adjustments to these changes in the generic code a bump of __FreeBSD_version Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 1:50: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 97F7515925 for ; Fri, 24 Sep 1999 01:50:01 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA05341; Fri, 24 Sep 1999 11:49:29 +0300 (EEST) (envelope-from will) To: "Daniel C. Sobral" Cc: freebsd-current@freebsd.org Subject: Re: gcc optimizer in -current system ... References: <37EAEB1A.3B0E4263@newsguy.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 24 Sep 1999 11:49:28 +0300 In-Reply-To: "Daniel C. Sobral"'s message of "24 Sep 1999 10:10:40 +0300" Message-ID: <86yadwvgmf.fsf@not.demophon.com> Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > bsd@picard.mandrakesoft.de wrote: > > > > But specifying something too high (-O99) doesn't hurt - I'm using -O6 for > > gcc 2.95.1 (which, by the way, compiles almost everything in 3.3-RELEASE > > and 4.0-CURRENT, the only thing still troubling me with it is the kernel). > > The point is that it _does_ hurt. Anything above -O3 is _likely_ to > have bugs. That only applies to pgcc, which shouldn't be used as anything other than an experimental compiler, anyhow. Whether real future gcc versions will enable new optimizations at levels > 3 is, to my knowledge, an open question. I don't like the thought myself, because -O3 already includes an often undesirable optimization (automatic inlining). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 2:14: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id EA94D14E00 for ; Fri, 24 Sep 1999 02:13:54 -0700 (PDT) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id LAA04225 for current@freebsd.org; Fri, 24 Sep 1999 11:13:47 +0200 (CEST) Date: Fri, 24 Sep 1999 11:13:43 +0200 From: Stephan van Beerschoten To: Develop-list FreeBSD Subject: Re: gcc optimizer in -current system ... Message-ID: <19990924111343.B4169@supra.rotterdam.luna.net> References: <37EAEB1A.3B0E4263@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37EAEB1A.3B0E4263@newsguy.com>; from Daniel C. Sobral on Fri, Sep 24, 1999 at 12:08:10PM +0900 Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 24, 1999 at 12:08:10PM +0900, Daniel C. Sobral wrote: > The point is that it _does_ hurt. Anything above -O3 is _likely_ to > have bugs. I am forced to agree about the fact that optimisation is traditionally buggy :) I tried to optimize my system with -O3 and -pipe. So I build myself a new kernel and a new world, I booted the kernel (I forgot to install the world)... It booted, windowmaker came up, I executed a linux-compatible binary (elf) and my system ended up with a boot. Thank god I didn't do a installworld :) Right now I'm recompiling everything using only -O and -pipe. Maybe its the linux-libs that had to be recompiled, but I don't have the time to sort this out because this machine has to be kind online without the fear of too much downtime. (I know .. -current .. living on the edge) :) I'll try to sort it out this weekend. -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services www.luna.nl PO Box 28013 3003 KA Rotterdam NL PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C 77 8D 35 29 C4 2A 2D 27 "RETURN VALUES: The panic() function call does not return" :P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 3: 2:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2509614FF4 for ; Fri, 24 Sep 1999 03:02:27 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id DAA02083; Fri, 24 Sep 1999 03:00:56 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241000.DAA02083@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909240738.JAA90307@gratis.grondar.za> from Mark Murray at "Sep 24, 1999 09:38:23 am" To: mark@grondar.za (Mark Murray) Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT) Cc: jabley@patho.gen.nz (Joe Abley), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How much mail does the use of the MAPS DUL reject? I think they meant to ask ``how much SPAM mail does ...'' > > Virtually none. The idea is that dial-up users use their own ISP's > smarthosts, in which case the ISP can nail them if they are spammers, > and I don't get their spam if they go for the "direct-to-MX" or > "direct injection" spamming method. Some mail may get temporarily > blocked until the sender added his IPS's smathost to his mailing > configs. It will actually block a very high amount of spam when initially turned on at a site that is known in the spam world to have open relays. Many of the drive by shooters use any dial up account that can get (often AOL freebees) to do this with. The DUL has all of aol's dial up IP space in it, so it immediately kills the drive by shooters. Another thing that ISP coulds start doing (we are in process with this now, but on a monitoring only basis, instead of a deny we just log them) is to block all outbound from AS tcp 25 setup packets. This prevents your customers from being something that could get you on the RBL or the DUL MAP for bad behavior, it also inforces the use of your smart host relay, as it/they is/are the only way to get a tcp port 25 setup completed. So far we have not had to terminated anyone's account for bad habbits, and we have helped several folks correct thier configurations for a much smoother operation. This is especially true for clients that have migrated over from another ISP. They often have old DNS and SMTP servers configured and the logging allows us to quickly track them down, blast them an email and save us a tech support call down the road when there old ISP changes something. If it's the DNS thats wrong they often go ``wowww!! Things are much faster now'' :-). [We monitor all port 53 traffic that is not to/from our DNS servers] > > > How much of that do you think is worth rejecting? > > I wish to reject no legitimate mail. I would fight use of the DUL > _hard_ if there was no (smarthost) alternative. Do you know about the RBL? How do you feel about it? We are using it via DNS and BGP on a test basis right now. I have had legitimate important mail blocked at Freebsd.org due to the source being on the RBL, but that is a price I am willing to pay. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 3:11:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 926DF15172 for ; Fri, 24 Sep 1999 03:10:59 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA26101; Fri, 24 Sep 1999 08:21:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 24 Sep 1999 08:21:04 +0100 (BST) From: Doug Rabson To: Kip Macy Cc: freebsd-current@freebsd.org Subject: Re: freebsd-uthread.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Kip Macy wrote: > > In three places in your code you do the following or something similar: > ptr = (CORE_ADDR) cached_pthread.nxt; > > struct pthread has no member nxt in either -current or -stable > and your patch did not add it to pthread_private.h > What did you mean for this to be? This field changed after I generated the patch. Here is the latest diff against -current (not sure if it will work in -stable): Index: Makefile =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/binutils/gdb/Makefile,v retrieving revision 1.43 diff -u -r1.43 Makefile --- Makefile 1999/08/27 23:34:48 1.43 +++ Makefile 1999/09/05 21:59:39 @@ -8,20 +8,20 @@ XSRCS= annotate.c ax-general.c ax-gdb.c bcache.c blockframe.c \ breakpoint.c buildsym.c c-exp.y c-lang.c c-typeprint.c \ c-valprint.c ch-exp.c ch-lang.c ch-typeprint.c ch-valprint.c \ - coffread.c command.c complaints.c copying.c corefile.c \ - corelow.c core-regset.c cp-valprint.c dcache.c dbxread.c demangle.c \ - dwarfread.c dwarf2read.c elfread.c environ.c eval.c exec.c \ - expprint.c f-exp.y f-lang.c f-typeprint.c f-valprint.c \ - findvar.c fork-child.c gdbarch.c gdbtypes.c infcmd.c inflow.c \ - infptrace.c infrun.c inftarg.c language.c jv-exp.y jv-lang.c \ - jv-valprint.c jv-typeprint.c nlmread.c m2-lang.c m2-exp.y \ - m2-typeprint.c m2-valprint.c main.c maint.c mdebugread.c \ - mem-break.c minsyms.c objfiles.c parse.c printcmd.c remote.c \ - remote-utils.c scm-exp.c scm-lang.c scm-valprint.c solib.c \ - source.c stabsread.c stack.c symfile.c symmisc.c symtab.c \ - target.c thread.c top.c tracepoint.c typeprint.c utils.c \ - valarith.c valops.c valprint.c values.c version.c serial.c \ - ser-unix.c ser-tcp.c callback.c + coffread.c command.c complaints.c copying.c core-regset.c \ + corefile.c corelow.c cp-valprint.c dcache.c dbxread.c \ + demangle.c dwarfread.c dwarf2read.c elfread.c environ.c eval.c \ + exec.c expprint.c f-exp.y f-lang.c f-typeprint.c f-valprint.c \ + findvar.c fork-child.c freebsd-uthread.c gdbarch.c gdbtypes.c \ + infcmd.c inflow.c infptrace.c infrun.c inftarg.c language.c \ + jv-exp.y jv-lang.c jv-valprint.c jv-typeprint.c nlmread.c \ + m2-lang.c m2-exp.y m2-typeprint.c m2-valprint.c main.c maint.c \ + mdebugread.c mem-break.c minsyms.c objfiles.c parse.c \ + printcmd.c remote.c remote-utils.c scm-exp.c scm-lang.c \ + scm-valprint.c solib.c source.c stabsread.c stack.c symfile.c \ + symmisc.c symtab.c target.c thread.c top.c tracepoint.c \ + typeprint.c utils.c valarith.c valops.c valprint.c values.c \ + version.c serial.c ser-unix.c ser-tcp.c callback.c SRCS= init.c ${XSRCS} .if exists(${.CURDIR}/Makefile.${MACHINE_ARCH}) @@ -34,6 +34,8 @@ CFLAGS+= -I${SRCDIR}/bfd CFLAGS+= -I${GDBDIR}/gdb CFLAGS+= -I${GDBDIR}/gdb/config +CFLAGS+= -I${.CURDIR}/../../../../lib/libc_r/uthread #pthread_private.h +CFLAGS+= -I${.CURDIR}/../../../../lib/libc/include #spinlock.h LDADD+= -L${RELTOP}/libbfd -lbfd LDADD+= -L${RELTOP}/libopcodes -lopcodes LDADD+= -lreadline Index: freebsd-uthread.c =================================================================== RCS file: freebsd-uthread.c diff -N freebsd-uthread.c --- /dev/null Fri Sep 24 08:17:20 1999 +++ freebsd-uthread.c Wed Aug 18 06:28:01 1999 @@ -0,0 +1,1005 @@ +/* Low level interface for debugging FreeBSD user threads for GDB, the GNU debugger. + Copyright 1996, 1999 Free Software Foundation, Inc. + +This file is part of GDB. + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. + +This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ + +/* This module implements a sort of half target that sits between the + machine-independent parts of GDB and the ptrace interface (infptrace.c) to + provide access to the FreeBSD user-mode thread implementation. + + FreeBSD threads are true user-mode threads, which are invoked via + the pthread_* interfaces. These are mostly implemented in + user-space, with all thread context kept in various structures that + live in the user's heap. For the most part, the kernel has no + knowlege of these threads. + + Based largely on hpux-thread.c + + */ + + +#include "defs.h" +#define PTHREAD_KERNEL +#include +#include "pthread_private.h" +#include "gdbthread.h" +#include "target.h" +#include "inferior.h" +#include +#include +#include +#include "gdbcore.h" + +extern int child_suppress_run; +extern struct target_ops child_ops; /* target vector for inftarg.c */ + +extern void _initialize_freebsd_uthread PARAMS ((void)); + +static int main_pid = -1; /* Real process ID */ + +/* Set to true while we are part-way through attaching */ +static int freebsd_uthread_attaching; + +static int freebsd_uthread_active = 0; +static CORE_ADDR P_thread_list; +static CORE_ADDR P_thread_run; + +static struct cleanup * save_inferior_pid PARAMS ((void)); + +static void restore_inferior_pid PARAMS ((int pid)); + +static void freebsd_uthread_resume PARAMS ((int pid, int step, + enum target_signal signo)); + +static void init_freebsd_uthread_ops PARAMS ((void)); + +static struct target_ops freebsd_uthread_ops; +static struct target_thread_vector freebsd_uthread_vec; + +/* + +LOCAL FUNCTION + + save_inferior_pid - Save inferior_pid on the cleanup list + restore_inferior_pid - Restore inferior_pid from the cleanup list + +SYNOPSIS + + struct cleanup *save_inferior_pid () + void restore_inferior_pid (int pid) + +DESCRIPTION + + These two functions act in unison to restore inferior_pid in + case of an error. + +NOTES + + inferior_pid is a global variable that needs to be changed by many of + these routines before calling functions in procfs.c. In order to + guarantee that inferior_pid gets restored (in case of errors), you + need to call save_inferior_pid before changing it. At the end of the + function, you should invoke do_cleanups to restore it. + + */ + +static struct cleanup * +save_inferior_pid () +{ + return make_cleanup ((make_cleanup_func) restore_inferior_pid, + (void *) inferior_pid); +} + +static void +restore_inferior_pid (pid) + int pid; +{ + inferior_pid = pid; +} + +static int find_active_thread PARAMS ((void)); + +static int cached_thread; +static struct pthread cached_pthread; +static CORE_ADDR cached_pthread_addr; + +#define THREADID_TID(id) ((id) >> 17) +#define THREADID_PID(id) ((id) & ((1 << 17) - 1)) + +LIST_HEAD(idmaplist, idmap); + +struct idmap { + LIST_ENTRY(idmap) link; + u_int64_t uniqueid; + int tid; +}; + +#define MAPHASH_SIZE 257 +#define TID_MIN 1 +#define TID_MAX 16383 + +static int tid_to_hash[TID_MAX + 1]; /* set to map_hash index */ +static struct idmaplist map_hash[MAPHASH_SIZE]; +static int next_free_tid = TID_MIN; /* first available tid */ +static int last_free_tid = TID_MIN; /* first unavailable */ + +#define UNIQUEID_HASH(id) (id % MAPHASH_SIZE) +#define TID_ADD1(tid) (((tid) + 1) == TID_MAX + 1 \ + ? TID_MIN : (tid) + 1) +#define IS_TID_FREE(tid) (tid_to_hash[tid] == -1) + +static int +get_new_tid(h) + int h; +{ + int tid = next_free_tid; + + tid_to_hash[tid] = h; + next_free_tid = TID_ADD1(next_free_tid); + if (next_free_tid == last_free_tid) + { + int i; + + for (i = last_free_tid; TID_ADD1(i) != last_free_tid; i = TID_ADD1(i)) + if (IS_TID_FREE(i)) + break; + if (TID_ADD1(i) == last_free_tid) + { + error("too many threads"); + return 0; + } + next_free_tid = i; + for (i = TID_ADD1(i); IS_TID_FREE(i); i = TID_ADD1(i)) + ; + last_free_tid = i; + } + + return tid; +} + +static int +find_pid(thread) + struct pthread *thread; +{ + int h = UNIQUEID_HASH(thread->uniqueid); + struct idmap *im; + + LIST_FOREACH(im, &map_hash[h], link) + if (im->uniqueid == thread->uniqueid) + return (im->tid << 17) + main_pid; + + im = xmalloc(sizeof(struct idmap)); + im->uniqueid = thread->uniqueid; + im->tid = get_new_tid(h); + LIST_INSERT_HEAD(&map_hash[h], im, link); + + return (im->tid << 17) + main_pid; +} + +static void +free_pid(pid) + int pid; +{ + int tid = THREADID_TID(pid); + int h = tid_to_hash[tid]; + struct idmap *im; + + if (!tid) return; + + LIST_FOREACH(im, &map_hash[h], link) + if (im->tid == tid) + break; + + if (!im) return; + + LIST_REMOVE(im, link); + tid_to_hash[tid] = -1; + free(im); +} + +static int +find_active_thread () +{ + static struct pthread pthread; + CORE_ADDR ptr; + + if (main_pid == -1) + return -1; + + read_memory ((CORE_ADDR)P_thread_run, + (char *)&ptr, + sizeof ptr); + + read_memory (ptr, (char *)&pthread, sizeof pthread); + + return find_pid(&pthread); +} + +static CORE_ADDR find_pthread_addr PARAMS ((int thread)); +static struct pthread * find_pthread PARAMS ((int thread)); + +static CORE_ADDR +find_pthread_addr (thread) + int thread; +{ + CORE_ADDR ptr; + + if (thread == cached_thread) + return cached_pthread_addr; + + read_memory ((CORE_ADDR)P_thread_list, + (char *)&ptr, + sizeof ptr); + + while (ptr != 0) + { + read_memory (ptr, (char*)&cached_pthread, sizeof cached_pthread); + + if (find_pid(&cached_pthread) == thread) + { + cached_thread = thread; + cached_pthread_addr = ptr; + return ptr; + } + ptr = (CORE_ADDR) cached_pthread.tle.tqe_next; + } + +#if 0 + error ("Can't find pthread %d,%d", + THREADID_TID(thread), THREADID_PID(thread)); +#endif + return NULL; +} + +static struct pthread * +find_pthread (thread) + int thread; +{ + CORE_ADDR ptr; + + if (thread == cached_thread) + return &cached_pthread; + + read_memory ((CORE_ADDR)P_thread_list, + (char *)&ptr, + sizeof ptr); + + while (ptr != 0) + { + read_memory (ptr, (char*)&cached_pthread, sizeof cached_pthread); + + if (find_pid(&cached_pthread) == thread) + { + cached_thread = thread; + cached_pthread_addr = ptr; + return &cached_pthread; + } + ptr = (CORE_ADDR) cached_pthread.tle.tqe_next; + + } + + error ("Can't find pthread %d,%d", + THREADID_TID(thread), THREADID_PID(thread)); + return NULL; +} + + +/* Most target vector functions from here on actually just pass through to + inftarg.c, as they don't need to do anything specific for threads. */ + +/* ARGSUSED */ +static void +freebsd_uthread_open (arg, from_tty) + char *arg; + int from_tty; +{ + child_ops.to_open (arg, from_tty); +} + +/* Attach to process PID, then initialize for debugging it + and wait for the trace-trap that results from attaching. */ + +static void +freebsd_uthread_attach (args, from_tty) + char *args; + int from_tty; +{ + child_ops.to_attach (args, from_tty); + push_target (&freebsd_uthread_ops); + freebsd_uthread_attaching = 1; +} + +/* After an attach, see if the target is threaded */ + +static void +freebsd_uthread_post_attach (pid) + int pid; +{ + if (freebsd_uthread_active) + { + main_pid = pid; + + bind_target_thread_vector (&freebsd_uthread_vec); + + inferior_pid = find_active_thread (); + + add_thread (inferior_pid); + } + else + { + unpush_target (&freebsd_uthread_ops); + push_target (&child_ops); + } + + freebsd_uthread_attaching = 0; +} + +/* Take a program previously attached to and detaches it. + The program resumes execution and will no longer stop + on signals, etc. We'd better not have left any breakpoints + in the program or it'll die when it hits one. For this + to work, it may be necessary for the process to have been + previously attached. It *might* work if the program was + started via the normal ptrace (PTRACE_TRACEME). */ + +static void +freebsd_uthread_detach (args, from_tty) + char *args; + int from_tty; +{ + child_ops.to_detach (args, from_tty); +} + +/* Resume execution of process PID. If STEP is nozero, then + just single step it. If SIGNAL is nonzero, restart it with that + signal activated. We may have to convert pid from a thread-id to an LWP id + for procfs. */ + +static void +freebsd_uthread_resume (pid, step, signo) + int pid; + int step; + enum target_signal signo; +{ + struct cleanup *old_chain; + + if (freebsd_uthread_attaching) + { + child_ops.to_resume (pid, step, signo); + return; + } + + old_chain = save_inferior_pid (); + + pid = inferior_pid = main_pid; + + child_ops.to_resume (pid, step, signo); + + cached_thread = 0; + + do_cleanups (old_chain); +} + +/* Wait for any threads to stop. We may have to convert PID from a thread id + to a LWP id, and vice versa on the way out. */ + +static int +freebsd_uthread_wait (pid, ourstatus) + int pid; + struct target_waitstatus *ourstatus; +{ + int rtnval; + struct cleanup *old_chain; + + if (freebsd_uthread_attaching) + { + return child_ops.to_wait (pid, ourstatus); + } + + old_chain = save_inferior_pid (); + + inferior_pid = main_pid; + + if (pid != -1) + pid = main_pid; + + rtnval = child_ops.to_wait (pid, ourstatus); + + if (rtnval >= 0) + { + rtnval = find_active_thread (); + if (!in_thread_list (rtnval)) + add_thread (rtnval); + } + + do_cleanups (old_chain); + + return rtnval; +} + +#ifdef __i386__ + +static char sigmap[NUM_REGS] = /* map reg to sigcontext */ +{ + 16, /* eax */ + 15, /* ecx */ + 14, /* edx */ + 13, /* ebx */ + 2, /* esp */ + 3, /* ebp */ + 12, /* esi */ + 11, /* edi */ + 5, /* eip */ + 6, /* eflags */ + 9, /* cs */ + 10, /* ss */ + 8, /* ds */ + 7, /* es */ + 18, /* fs */ + 17, /* gs */ +}; + +static char jmpmap[NUM_REGS] = /* map reg to jmp_buf */ +{ + 6, /* eax */ + -1, /* ecx */ + -1, /* edx */ + 1, /* ebx */ + 2, /* esp */ + 3, /* ebp */ + 4, /* esi */ + 5, /* edi */ + 0, /* eip */ + -1, /* eflags */ + -1, /* cs */ + -1, /* ss */ + -1, /* ds */ + -1, /* es */ + -1, /* fs */ + -1, /* gs */ +}; + +#endif + +#ifdef __alpha__ + +static char sigmap[NUM_REGS] = /* map reg to sigcontext */ +{ + 4, 5, 6, 7, 8, 9, 10, 11, /* v0 - t6 */ + 12, 13, 14, 15, 16, 17, 18, 19, /* t7 - fp */ + 20, 21, 22, 23, 24, 25, 26, 27, /* a0 - t9 */ + 28, 29, 30, 31, 32, 33, 34, 35, /* t10 - zero */ + 37, 38, 39, 40, 41, 42, 43, 44, /* f0 - f7 */ + 45, 46, 47, 48, 49, 50, 51, 52, /* f8 - f15 */ + 53, 54, 55, 56, 57, 58, 59, 60, /* f16 - f23 */ + 61, 62, 63, 64, 65, 66, 67, 68, /* f24 - f31 */ + 2, -1, /* pc, vfp */ +}; + +/* alpha jmp_buf is the same layout as sigcontext */ +#define jmpmap sigmap + +#endif + +static void +freebsd_uthread_fetch_registers (regno) + int regno; +{ + struct pthread *thread; + struct cleanup *old_chain; + int i; + int active; + int first_regno, last_regno; + u_int32_t *regbase; + char *regmap; + + if (freebsd_uthread_attaching) + { + child_ops.to_fetch_registers (regno); + return; + } + + thread = find_pthread (inferior_pid); + + old_chain = save_inferior_pid (); + + active = (inferior_pid == find_active_thread()); + + inferior_pid = main_pid; + + if (active) + { + child_ops.to_fetch_registers (regno); + + do_cleanups (old_chain); + + return; + } + + if (regno == -1) + { + first_regno = 0; + last_regno = NUM_REGS - 1; + } + else + { + first_regno = regno; + last_regno = regno; + } + + if (thread->sig_saved) + { + regbase = (u_int32_t*) &thread->saved_sigcontext; + regmap = sigmap; + } + else + { + regbase = (u_int32_t*) &thread->saved_jmp_buf[0]; + regmap = jmpmap; + } + + for (regno = first_regno; regno <= last_regno; regno++) + { + if (regmap[regno] == -1) + child_ops.to_fetch_registers (regno); + else + supply_register (regno, (char*) ®base[regmap[regno]]); + } + + do_cleanups (old_chain); +} + +static void +freebsd_uthread_store_registers (regno) + int regno; +{ + struct pthread *thread; + CORE_ADDR ptr; + struct cleanup *old_chain; + int i; + int first_regno, last_regno; + u_int32_t *regbase; + char *regmap; + + if (freebsd_uthread_attaching) + { + child_ops.to_store_registers (regno); + return; + } + + thread = find_pthread (inferior_pid); + + old_chain = save_inferior_pid (); + + inferior_pid = main_pid; + + if (thread->state == PS_RUNNING) + { + child_ops.to_store_registers (regno); + + do_cleanups (old_chain); + + return; + } + + if (regno == -1) + { + first_regno = 0; + last_regno = NUM_REGS - 1; + } + else + { + first_regno = regno; + last_regno = regno; + } + + if (thread->sig_saved) + { + regbase = (u_int32_t*) &thread->saved_sigcontext; + regmap = sigmap; + } + else + { + regbase = (u_int32_t*) &thread->saved_jmp_buf[0]; + regmap = jmpmap; + } + + ptr = find_pthread_addr (inferior_pid); + for (regno = first_regno; regno <= last_regno; regno++) + { + if (regmap[regno] == -1) + child_ops.to_store_registers (regno); + else + { + u_int32_t *reg = ®base[regmap[regno]]; + int off; + + /* Hang onto cached value */ + memcpy(reg, registers + REGISTER_BYTE (regno), + REGISTER_RAW_SIZE (regno)); + + /* And push out to inferior */ + off = (char *) reg - (char *) thread; + write_memory (ptr + off, + registers + REGISTER_BYTE (regno), + REGISTER_RAW_SIZE (regno)); + } + } + + do_cleanups (old_chain); +} + +/* Get ready to modify the registers array. On machines which store + individual registers, this doesn't need to do anything. On machines + which store all the registers in one fell swoop, this makes sure + that registers contains all the registers from the program being + debugged. */ + +static void +freebsd_uthread_prepare_to_store () +{ + struct cleanup *old_chain; + + if (freebsd_uthread_attaching) + { + child_ops.to_prepare_to_store (); + return; + } + + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + child_ops.to_prepare_to_store (); + + do_cleanups (old_chain); +} + +static int +freebsd_uthread_xfer_memory (memaddr, myaddr, len, dowrite, target) + CORE_ADDR memaddr; + char *myaddr; + int len; + int dowrite; + struct target_ops *target; /* ignored */ +{ + int retval; + struct cleanup *old_chain; + + if (freebsd_uthread_attaching) + { + return child_ops.to_xfer_memory (memaddr, myaddr, len, dowrite, target); + } + + old_chain = save_inferior_pid (); + + inferior_pid = main_pid; + + retval = child_ops.to_xfer_memory (memaddr, myaddr, len, dowrite, target); + + do_cleanups (old_chain); + + return retval; +} + +/* Print status information about what we're accessing. */ + +static void +freebsd_uthread_files_info (ignore) + struct target_ops *ignore; +{ + child_ops.to_files_info (ignore); +} + +static void +freebsd_uthread_kill_inferior () +{ + inferior_pid = main_pid; + child_ops.to_kill (); +} + +static void +freebsd_uthread_notice_signals (pid) + int pid; +{ + struct cleanup *old_chain; + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + child_ops.to_notice_signals (pid); + + do_cleanups (old_chain); +} + +/* Fork an inferior process, and start debugging it with /proc. */ + +static void +freebsd_uthread_create_inferior (exec_file, allargs, env) + char *exec_file; + char *allargs; + char **env; +{ + child_ops.to_create_inferior (exec_file, allargs, env); + + if (inferior_pid && freebsd_uthread_active) + { + main_pid = inferior_pid; + + push_target (&freebsd_uthread_ops); + bind_target_thread_vector (&freebsd_uthread_vec); + + inferior_pid = find_active_thread (); + + add_thread (inferior_pid); + } +} + +/* This routine is called to find out if the inferior is using threads. + We check for the _thread_run and _thread_list globals. */ + +void +freebsd_uthread_new_objfile (objfile) + struct objfile *objfile; +{ + struct minimal_symbol *ms; + + if (!objfile) + { + freebsd_uthread_active = 0; + return; + } + + ms = lookup_minimal_symbol ("_thread_run", NULL, objfile); + + if (!ms) + return; + + P_thread_run = SYMBOL_VALUE_ADDRESS (ms); + + ms = lookup_minimal_symbol ("_thread_list", NULL, objfile); + + if (!ms) + return; + + P_thread_list = SYMBOL_VALUE_ADDRESS (ms); + + freebsd_uthread_active = 1; +} + +int +freebsd_uthread_has_exited (pid, wait_status, exit_status) + int pid; + int wait_status; + int * exit_status; +{ + int t = child_ops.to_has_exited (pid, wait_status, exit_status); + if (t) + main_pid = -1; + return t; +} + +/* Clean up after the inferior dies. */ + +static void +freebsd_uthread_mourn_inferior () +{ + inferior_pid = main_pid; /* don't bother to restore inferior_pid */ + child_ops.to_mourn_inferior (); + unpush_target (&freebsd_uthread_ops); +} + +/* Mark our target-struct as eligible for stray "run" and "attach" commands. */ + +static int +freebsd_uthread_can_run () +{ + return child_suppress_run; +} + +static int +freebsd_uthread_thread_alive (pid) + int pid; +{ + struct cleanup *old_chain; + struct pthread *thread; + int ret = 0; + + if (freebsd_uthread_attaching) + return 1; + + /* + * We can get called from child_ops.to_wait() which passes the underlying + * pid (without a thread number). + */ + if (THREADID_TID(pid) == 0) + return 1; + + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + if (find_pthread_addr (pid) != 0) + { + thread = find_pthread (pid); + ret = (thread->state != PS_DEAD); + } + + do_cleanups (old_chain); + + if (!ret) + free_pid(pid); + + return ret; +} + +static void +freebsd_uthread_stop () +{ + struct cleanup *old_chain; + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + child_ops.to_stop (); + + do_cleanups (old_chain); +} + +static int +freebsd_uthread_find_new_threads () +{ + CORE_ADDR ptr; + struct pthread pthread; + struct cleanup *old_chain; + + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + read_memory ((CORE_ADDR)P_thread_list, + (char *)&ptr, + sizeof ptr); + + while (ptr != 0) + { + read_memory (ptr, (char*)&pthread, sizeof pthread); + + if (pthread.state != PS_DEAD && + !in_thread_list (find_pid(&pthread))) + add_thread (find_pid(&pthread)); + ptr = (CORE_ADDR) pthread.tle.tqe_next; + } + + do_cleanups (old_chain); + + return 0; +} + +/* MUST MATCH enum pthread_state */ +static const char *statenames[] = { + "RUNNING", + "SIGTHREAD", + "MUTEX_WAIT", + "COND_WAIT", + "FDLR_WAIT", + "FDLW_WAIT", + "FDR_WAIT", + "FDW_WAIT", + "FILE_WAIT", + "SELECT_WAIT", + "SLEEP_WAIT", + "WAIT_WAIT", + "SIGSUSPEND", + "SIGWAIT", + "SPINBLOCK", + "JOIN", + "SUSPENDED", + "DEAD", + "DEADLOCK", +}; + +static int +freebsd_uthread_get_thread_info (ref, selection, info) + gdb_threadref *ref; + int selection; + struct gdb_ext_thread_info *info; +{ + int pid = *ref; + struct pthread *thread = find_pthread (pid); + struct cleanup *old_chain; + + old_chain = save_inferior_pid (); + inferior_pid = main_pid; + + memset(&info->threadid, 0, OPAQUETHREADBYTES); + + memcpy(&info->threadid, ref, sizeof *ref); + info->active = thread->state == PS_RUNNING; + strcpy(info->display, statenames[thread->state]); + if (thread->name) + read_memory ((CORE_ADDR) thread->name, info->shortname, 32); + else + strcpy(info->shortname, ""); + + do_cleanups (old_chain); +} + +char * +freebsd_uthread_pid_to_str (pid) + int pid; +{ + static char buf[30]; + + if (STREQ (current_target.to_shortname, "freebsd-uthreads")) + sprintf (buf, "process %d, thread %d\0", + THREADID_PID(pid), THREADID_TID(pid)); + else + sprintf (buf, "process %d\0", pid); + + return buf; +} + + +static void +init_freebsd_uthread_ops () +{ + freebsd_uthread_ops.to_shortname = "freebsd-uthreads"; + freebsd_uthread_ops.to_longname = "FreeBSD uthreads"; + freebsd_uthread_ops.to_doc = "FreeBSD user threads support."; + freebsd_uthread_ops.to_open = freebsd_uthread_open; + freebsd_uthread_ops.to_attach = freebsd_uthread_attach; + freebsd_uthread_ops.to_post_attach = freebsd_uthread_post_attach; + freebsd_uthread_ops.to_detach = freebsd_uthread_detach; + freebsd_uthread_ops.to_resume = freebsd_uthread_resume; + freebsd_uthread_ops.to_wait = freebsd_uthread_wait; + freebsd_uthread_ops.to_fetch_registers = freebsd_uthread_fetch_registers; + freebsd_uthread_ops.to_store_registers = freebsd_uthread_store_registers; + freebsd_uthread_ops.to_prepare_to_store = freebsd_uthread_prepare_to_store; + freebsd_uthread_ops.to_xfer_memory = freebsd_uthread_xfer_memory; + freebsd_uthread_ops.to_files_info = freebsd_uthread_files_info; + freebsd_uthread_ops.to_insert_breakpoint = memory_insert_breakpoint; + freebsd_uthread_ops.to_remove_breakpoint = memory_remove_breakpoint; + freebsd_uthread_ops.to_terminal_init = terminal_init_inferior; + freebsd_uthread_ops.to_terminal_inferior = terminal_inferior; + freebsd_uthread_ops.to_terminal_ours_for_output = terminal_ours_for_output; + freebsd_uthread_ops.to_terminal_ours = terminal_ours; + freebsd_uthread_ops.to_terminal_info = child_terminal_info; + freebsd_uthread_ops.to_kill = freebsd_uthread_kill_inferior; + freebsd_uthread_ops.to_create_inferior = freebsd_uthread_create_inferior; + freebsd_uthread_ops.to_has_exited = freebsd_uthread_has_exited; + freebsd_uthread_ops.to_mourn_inferior = freebsd_uthread_mourn_inferior; + freebsd_uthread_ops.to_can_run = freebsd_uthread_can_run; + freebsd_uthread_ops.to_notice_signals = freebsd_uthread_notice_signals; + freebsd_uthread_ops.to_thread_alive = freebsd_uthread_thread_alive; + freebsd_uthread_ops.to_stop = freebsd_uthread_stop; + freebsd_uthread_ops.to_stratum = process_stratum; + freebsd_uthread_ops.to_has_all_memory = 1; + freebsd_uthread_ops.to_has_memory = 1; + freebsd_uthread_ops.to_has_stack = 1; + freebsd_uthread_ops.to_has_registers = 1; + freebsd_uthread_ops.to_has_execution = 1; + freebsd_uthread_ops.to_has_thread_control = 0; + freebsd_uthread_ops.to_magic = OPS_MAGIC; + + freebsd_uthread_vec.find_new_threads = freebsd_uthread_find_new_threads; + freebsd_uthread_vec.get_thread_info = freebsd_uthread_get_thread_info; +} + +void +_initialize_freebsd_uthread () +{ + init_freebsd_uthread_ops (); + add_target (&freebsd_uthread_ops); + + child_suppress_run = 1; +} Index: alpha/tm.h =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/binutils/gdb/alpha/tm.h,v retrieving revision 1.2 diff -u -r1.2 tm.h --- tm.h 1999/06/21 15:00:14 1.2 +++ tm.h 1999/07/20 13:45:50 @@ -34,4 +34,11 @@ #undef START_INFERIOR_TRAPS_EXPECTED #define START_INFERIOR_TRAPS_EXPECTED 2 +struct objfile; +void freebsd_uthread_new_objfile PARAMS ((struct objfile *objfile)); +#define target_new_objfile(OBJFILE) freebsd_uthread_new_objfile (OBJFILE) + +extern char *freebsd_uthread_pid_to_str PARAMS ((int pid)); +#define target_pid_to_str(PID) freebsd_uthread_pid_to_str (PID) + #endif /* TM_FREEBSDALPHA_H */ Index: i386/freebsd-nat.c =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/binutils/gdb/i386/freebsd-nat.c,v retrieving revision 1.21 diff -u -r1.21 freebsd-nat.c --- freebsd-nat.c 1999/05/02 11:32:10 1.21 +++ freebsd-nat.c 1999/08/18 05:28:34 @@ -345,20 +345,9 @@ uaddr = (char *)&U_FPSTATE(u) - (char *)&u; if (inferior_pid != 0 && core_bfd == NULL) { - int *ip; - - rounded_addr = uaddr & -sizeof (int); - rounded_size = (((uaddr + sizeof (struct fpstate)) - uaddr) + - sizeof (int) - 1) / sizeof (int); - skip = uaddr - rounded_addr; - - ip = (int *)buf; - for (i = 0; i < rounded_size; i++) - { - *ip++ = ptrace (PT_READ_U, inferior_pid, (caddr_t)rounded_addr, 0); - rounded_addr += sizeof (int); - } - fpstatep = (struct fpstate *)(buf + skip); + int pid = inferior_pid & ((1 << 17) - 1); /* XXX extract pid from tid */ + ptrace(PT_GETFPREGS, pid, &buf[0], sizeof(struct fpreg)); + fpstatep = (struct fpstate *)&buf[0]; } else fpstatep = &pcb_savefpu; Index: i386/tm.h =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/binutils/gdb/i386/tm.h,v retrieving revision 1.12 diff -u -r1.12 tm.h --- tm.h 1999/06/13 19:41:50 1.12 +++ tm.h 1999/07/20 13:45:50 @@ -55,4 +55,11 @@ #define SIGTRAMP_START(pc) 0xbfbfdfd8 #define SIGTRAMP_END(pc) 0xbfbfdff0 +struct objfile; +void freebsd_uthread_new_objfile PARAMS ((struct objfile *objfile)); +#define target_new_objfile(OBJFILE) freebsd_uthread_new_objfile (OBJFILE) + +extern char *freebsd_uthread_pid_to_str PARAMS ((int pid)); +#define target_pid_to_str(PID) freebsd_uthread_pid_to_str (PID) + #endif /* ifndef TM_FBSD_H */ -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 3:15: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 0A90F1528F for ; Fri, 24 Sep 1999 03:15:00 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id MAA91015; Fri, 24 Sep 1999 12:14:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909241014.MAA91015@gratis.grondar.za> To: "Rodney W. Grimes" Cc: jabley@patho.gen.nz (Joe Abley), current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups Date: Fri, 24 Sep 1999 12:14:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do you know about the RBL? How do you feel about it? We are using > it via DNS and BGP on a test basis right now. I have had legitimate > important mail blocked at Freebsd.org due to the source being on the > RBL, but that is a price I am willing to pay. The RBL is great! There is a teensy bit of colateral damage, but not so much that I worry about it. Here in ZA, our USP traffic provider (Teleglobe) uses RBL, thus absolving us of the responsibility. Since we started getting this "cleanfeed", spam has dropped dramatically. What I particularly enjoy about the RBL is its strong sense of the need to listen to its client base, and to adapt as necessary. Paul Vixie has a high degree of respect, as a consequence. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 3:28:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 460F61513F for ; Fri, 24 Sep 1999 03:27:36 -0700 (PDT) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.3/8.9.3) id SAA52285 for current@freebsd.org; Fri, 24 Sep 1999 18:27:08 +0800 (WST) (envelope-from mike) From: Michael Kennett Message-Id: <199909241027.SAA52285@laurasia.com.au> Subject: RBL, DUL + other acronymns [was Re: On hub.freebsd.org refusing to talk to dialups] In-Reply-To: <199909241014.MAA91015@gratis.grondar.za> from Mark Murray at "Sep 24, 1999 12:14:37 pm" To: current@freebsd.org Date: Fri, 24 Sep 1999 18:27:08 +0800 (WST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those who don't know the acronymns RBL, DUL, etc... (like me a few minutes ago :-), they are: RBL Realtime Blackhole List TSI Transport Security Initiative DUL Dial-up User List RSS Relay Spam Stopper. More information can be found at the site: http://maps.vix.com/. Regards, Mike Kennett. [trim of old thread] > > Do you know about the RBL? How do you feel about it? We are using > > it via DNS and BGP on a test basis right now. I have had legitimate > > important mail blocked at Freebsd.org due to the source being on the > > RBL, but that is a price I am willing to pay. > > The RBL is great! There is a teensy bit of colateral damage, but not > so much that I worry about it. Here in ZA, our USP traffic provider > (Teleglobe) uses RBL, thus absolving us of the responsibility. Since > we started getting this "cleanfeed", spam has dropped dramatically. > > What I particularly enjoy about the RBL is its strong sense of the > need to listen to its client base, and to adapt as necessary. Paul > Vixie has a high degree of respect, as a consequence. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 6:32:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from thequest.net (tnt006.thequest.net [205.198.52.133]) by hub.freebsd.org (Postfix) with ESMTP id D7F80151A3 for ; Fri, 24 Sep 1999 06:32:06 -0700 (PDT) (envelope-from znh@thequest.net) Received: by thequest.net (Postfix, from userid 1005) id 4468D20CA; Fri, 24 Sep 1999 13:29:59 +0000 (GMT) Date: Fri, 24 Sep 1999 08:29:59 -0500 From: "Zach N. Heilig" To: Luke Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG, The Hermit Hacker Subject: Re: gcc optimizer in -current system ... Message-ID: <19990924082958.A14943@murkwood.znh.org> References: <5868.938087433@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Luke on Thu, Sep 23, 1999 at 10:57:07AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 23, 1999 at 10:57:07AM -0400, Luke wrote: > I have -03 -mpentium -fomit-frame-pointer and the only inexpicable > problem I have is I cant compile groff with more than -O for some reason. > Other than that make world and make release have worked many times. > I wonder does anyone think [or have stats] on whether O3-6 and things like > - -ffast-math actually make any difference? Only a couple of the options make much speed difference for me, and those that do significantly slow the code down instead of speeding it up. I did some tests earlier this year, since I had an application that (I thought) bumped up against the performance limits of a MediaGX 200 MHz at times (the cpu seemed generally fast enough, it seems there are some significant wait-states added at unpredictable times when using on-chip multi-media hardware -- it'll have drop outs simply dumping raw stereo, 16-bit, 44100 samples/sec to the on-processor audio card -- adding a sound card fixed these problems). The application for the tests is mpg123. test mp3 playing time: 373 seconds. compilation options (for mpg123, all versions use the i386+486 objects): If anyone wants a specific set of options, I can re-run this whole deal (I put together some scripts to automate almost all of this, I ran these tests on an amd5x86-133, amd k6-300, and mediagx-200). These are (some of) the MediaGX-200 results: 1) No Optimization 225.08 real 224.30 user 0.23 sys 225.23 real 224.55 user 0.21 sys 225.06 real 224.34 user 0.16 sys 225.21 real 224.39 user 0.21 sys 225.17 real 224.40 user 0.13 sys 2) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns -fschedule-insns2 141.92 real 141.43 user 0.10 sys 142.17 real 141.71 user 0.11 sys 142.05 real 141.53 user 0.14 sys 142.01 real 141.42 user 0.18 sys 142.11 real 141.53 user 0.14 sys 3) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns 141.75 real 141.24 user 0.10 sys 141.52 real 141.06 user 0.09 sys 141.04 real 140.62 user 0.08 sys 142.04 real 141.48 user 0.14 sys 141.82 real 141.27 user 0.16 sys 4) -O3 -mcpu=i486 -march=i486 -funroll-loops 135.56 real 135.09 user 0.13 sys 134.88 real 134.39 user 0.11 sys 135.18 real 134.69 user 0.11 sys 135.66 real 135.24 user 0.10 sys 134.79 real 134.42 user 0.07 sys 5) -O3 134.50 real 133.93 user 0.21 sys 134.82 real 134.35 user 0.13 sys 135.04 real 134.60 user 0.10 sys 135.00 real 134.56 user 0.14 sys 135.14 real 134.61 user 0.14 sys 6) -O3 -mcpu=i486 -march=i486 -funroll-all-loops 134.08 real 133.64 user 0.12 sys 134.45 real 133.99 user 0.12 sys 134.81 real 134.35 user 0.12 sys 134.70 real 134.15 user 0.14 sys 134.41 real 133.94 user 0.12 sys 7) -O3 -mcpu=i486 -march=i486 -ffast-math 133.38 real 132.89 user 0.13 sys 133.03 real 132.49 user 0.14 sys 133.35 real 132.86 user 0.12 sys 133.42 real 132.94 user 0.15 sys 133.47 real 133.03 user 0.10 sys 8) -O3 -mcpu=i486 -march=i486 -mwide-multiply 133.19 real 132.70 user 0.08 sys 132.90 real 132.44 user 0.12 sys 133.43 real 132.98 user 0.13 sys 133.31 real 132.87 user 0.11 sys 133.83 real 133.33 user 0.10 sys 9) -O3 -mcpu=i486 -march=i486 -fthread-jumps 132.79 real 132.28 user 0.17 sys 133.15 real 132.65 user 0.11 sys 133.47 real 132.94 user 0.17 sys 133.07 real 132.61 user 0.10 sys 133.41 real 132.93 user 0.13 sys 10) -O3 -mcpu=i486 -march=i486 133.48 real 133.00 user 0.10 sys 133.36 real 132.94 user 0.14 sys 133.25 real 132.81 user 0.09 sys 133.60 real 133.08 user 0.15 sys 133.34 real 132.89 user 0.11 sys 11) -O3 -mcpu=i586 -march=i486 132.06 real 131.52 user 0.11 sys 131.90 real 131.37 user 0.16 sys 132.20 real 131.65 user 0.20 sys 132.04 real 131.61 user 0.11 sys 132.66 real 132.15 user 0.13 sys 12) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -frerun-loop-opt 130.86 real 130.41 user 0.14 sys 130.18 real 129.72 user 0.16 sys 130.75 real 130.28 user 0.16 sys 130.78 real 130.32 user 0.11 sys 130.60 real 130.13 user 0.14 sys 13) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fmove-all-movables -freduce-all-givs 131.49 real 131.00 user 0.14 sys 130.97 real 130.49 user 0.17 sys 130.55 real 130.05 user 0.10 sys 130.61 real 130.18 user 0.10 sys 130.87 real 130.36 user 0.20 sys 14) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fcse-follow-jumps -fcse-skip-blocks -fgcse 130.51 real 129.94 user 0.14 sys 130.55 real 130.04 user 0.11 sys 131.18 real 130.62 user 0.22 sys 130.83 real 130.42 user 0.11 sys 130.50 real 130.06 user 0.10 sys 15) -O3 -mcpu=i586 -march=i486 -fomit-frame-pointer -fexpensive-optimizations 130.89 real 130.42 user 0.14 sys 130.56 real 130.16 user 0.08 sys 130.39 real 129.99 user 0.08 sys 130.17 real 129.66 user 0.10 sys 130.46 real 129.98 user 0.15 sys 16) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fcse-follow-jumps -fcse-skip-blocks 300.23 real 299.20 user 0.24 sys 300.35 real 299.33 user 0.22 sys 300.76 real 299.69 user 0.26 sys 299.89 real 298.96 user 0.20 sys 300.48 real 299.61 user 0.17 sys 17) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fcse-follow-jumps 131.19 real 130.71 user 0.11 sys 131.15 real 130.74 user 0.07 sys 131.14 real 130.65 user 0.14 sys 130.85 real 130.29 user 0.14 sys 131.22 real 130.73 user 0.15 sys 18) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer 131.20 real 130.81 user 0.08 sys 131.18 real 130.65 user 0.17 sys 130.34 real 129.85 user 0.10 sys 130.54 real 130.08 user 0.13 sys 131.12 real 130.59 user 0.17 sys 19) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fstrict-aliasing 130.10 real 129.62 user 0.10 sys 130.16 real 129.64 user 0.13 sys 130.31 real 129.85 user 0.17 sys 130.43 real 130.06 user 0.09 sys 130.21 real 129.71 user 0.08 sys 20) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fexpensive-optimizations 130.59 real 130.11 user 0.13 sys 129.89 real 129.46 user 0.12 sys 129.85 real 129.41 user 0.12 sys 130.81 real 130.29 user 0.16 sys 130.34 real 129.85 user 0.15 sys 21) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fcse-skip-blocks 130.53 real 130.04 user 0.13 sys 130.48 real 130.07 user 0.12 sys 130.05 real 129.56 user 0.10 sys 130.67 real 130.17 user 0.19 sys 130.83 real 130.43 user 0.10 sys 22) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -funroll-all-loops 130.61 real 130.11 user 0.17 sys 130.11 real 129.64 user 0.09 sys 130.83 real 130.39 user 0.09 sys 130.24 real 129.78 user 0.13 sys 130.30 real 129.78 user 0.12 sys 23) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -malign-double 130.36 real 129.90 user 0.15 sys 130.72 real 130.25 user 0.15 sys 130.71 real 130.23 user 0.11 sys 130.50 real 130.05 user 0.09 sys 130.31 real 129.93 user 0.10 sys 24) -O3 -mcpu=i586 -march=i586 -fomit-frame-pointer -malign-double 130.35 real 129.93 user 0.10 sys 130.19 real 129.73 user 0.10 sys 130.23 real 129.79 user 0.10 sys 129.67 real 129.16 user 0.14 sys 130.42 real 129.93 user 0.12 sys -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 7: 2:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id B42AD14D1C for ; Fri, 24 Sep 1999 07:02:29 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id HAA04384; Fri, 24 Sep 1999 07:02:14 -0700 (PDT) Date: Fri, 24 Sep 1999 07:02:14 -0700 (PDT) From: David Wolfskill Message-Id: <199909241402.HAA04384@pau-amma.whistle.com> To: current@FreeBSD.ORG, freebsd@gndrsh.dnsmgr.net Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241000.DAA02083@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Rodney W. Grimes" >Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT) >Another thing that ISP coulds start doing (we are in process with >this now, but on a monitoring only basis, instead of a deny we >just log them) is to block all outbound from AS tcp 25 setup packets. Not quite sure I follow this. >This prevents your customers from being something that could get you >on the RBL or the DUL MAP for bad behavior, it also inforces the use >of your smart host relay, as it/they is/are the only way to get a >tcp port 25 setup completed. About the only positive thing I have to say about the DUL is that Vix stated that entries are placed on it at the request of the custodians of the netblock in question. >Do you know about the RBL? How do you feel about it? We are using >it via DNS and BGP on a test basis right now. I have had legitimate >important mail blocked at Freebsd.org due to the source being on the >RBL, but that is a price I am willing to pay. I'm far more comfortable with the use of the RBL than the DUL. Indeed, my externally-visible home SMTP server uses the RBL (but not the DUL). Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 7:23:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 4159814FAF for ; Fri, 24 Sep 1999 07:23:22 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 81C457C31; Fri, 24 Sep 1999 09:22:06 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14315.35085.935406.940824@celery.zuhause.org> Date: Fri, 24 Sep 1999 09:22:05 -0500 (CDT) To: current@FreeBSD.ORG Subject: Why do FreeBSD mailing lists ignore MX preference? In-Reply-To: <199909241014.MAA91015@gratis.grondar.za> References: <199909241014.MAA91015@gratis.grondar.za> X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is not -current related, but then, neither is the thread on hub.freebsd.org refusing DUL origin messages. I have a DSL line with static IP, and all my FreeBSD mailing lists are sent to bruce@zuhause.mn.org. There are two DNS MX records for zuhause.mn.org, one at preference 100 with my IP address, and a second at preference 150 for the mn.org main mail server. Even though my IP has a lower preference value, none of my FreeBSD mailing list mail come directly to my machine, it all passes through the minuet.skypoint.net. I get plenty of mail sent to zuhause.mn.org from other locations which talk directly to my machine, so why don't the FreeBSD mailing lists? As you can see, hub.freebsd.org has the correct information its DNS tables, so it can't be out of date information. nslookup - hub.freebsd.org Default Server: hub.FreeBSD.ORG Address: 204.216.27.18 > set querytype=mx > zuhause.mn.org Server: hub.FreeBSD.ORG Address: 204.216.27.18 Non-authoritative answer: zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 Authoritative answers can be found from: mn.org nameserver = minuet.skypoint.net mn.org nameserver = ns2.skypoint.net mn.org nameserver = zeus.cs.uh.edu minuet.skypoint.net internet address = 199.86.32.2 ns2.skypoint.net internet address = 199.86.32.4 > zuhause.org Server: hub.FreeBSD.ORG Address: 204.216.27.18 zuhause.org preference = 10, mail exchanger = mail.zuhause.org zuhause.org nameserver = ns1.uswest.net zuhause.org nameserver = ns2.dnvr.uswest.net zuhause.org nameserver = ns3.mn.uswest.net mail.zuhause.org internet address = 205.215.217.178 ns1.uswest.net internet address = 204.147.80.5 ns2.dnvr.uswest.net internet address = 206.196.128.1 ns3.mn.uswest.net internet address = 204.147.80.1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 7:36:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 2F81414D09 for ; Fri, 24 Sep 1999 07:36:26 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA04690 for ; Fri, 24 Sep 1999 07:36:08 -0700 Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda04688; Fri Sep 24 07:36:04 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id HAA63605 for ; Fri, 24 Sep 1999 07:36:03 -0700 (PDT) Message-Id: <199909241436.HAA63605@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdZ63596; Fri Sep 24 07:35:06 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.3-RELEASE X-Sender: cy To: freebsd-current@freebsd.org Subject: Re: FreeBSD-specific denial of service Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Sep 1999 07:35:06 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is from BUGTRAQ. There's a fix for -stable, though there is none for -current. Is -current vulnerable? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" ------- Forwarded Message Replied: Fri, 24 Sep 1999 07:32:41 -0700 Replied: Adrian Penisoara Replied: "Charles M. Hannum" Replied: BUGTRAQ@SECURITYFOCUS.COM Replied: freebsd-security@FreeBSD.ORG Return-Path: Cy.Schubert@uumail.gov.bc.ca Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA19965 for ; Fri, 24 Sep 1999 07:07:39 -0700 (PDT) Resent-Message-Id: <199909241407.HAA19965@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdL19958; Fri Sep 24 07:06:39 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA19950 for ; Fri, 24 Sep 1999 07:06:39 -0700 (PDT) Received: from point.osg.gov.bc.ca(142.32.102.44) via SMTP by passer.osg.gov.bc.ca, id smtpdW19948; Fri Sep 24 07:06:27 1999 Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA04613 for ; Fri, 24 Sep 1999 07:06:27 -0700 Received: from hub.FreeBSD.ORG(204.216.27.18) via SMTP by point.osg.gov.bc.ca, id smtpda04611; Fri Sep 24 07:06:14 1999 Received: by hub.freebsd.org (Postfix, from userid 538) id 47FB414D1C; Fri, 24 Sep 1999 07:04:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 309E61CD621; Fri, 24 Sep 1999 07:04:18 -0700 (PDT) (envelope-from owner-freebsd-security) Received: by hub.freebsd.org (bulk_mailer v1.12); Fri, 24 Sep 1999 07:04:18 -0700 Delivered-To: freebsd-security@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id C4621150E5 for ; Fri, 24 Sep 1999 07:04:02 -0700 (PDT) (envelope-from ady@freebsd.ady.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id RAA36387; Fri, 24 Sep 1999 17:02:25 +0300 (EEST) (envelope-from ady@freebsd.ady.ro) Date: Fri, 24 Sep 1999 17:02:25 +0300 (EEST) From: Adrian Penisoara X-Sender: ady@ady.warpnet.ro To: "Charles M. Hannum" Cc: BUGTRAQ@SECURITYFOCUS.COM, freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD-specific denial of service In-Reply-To: <199909211950.PAA09009@bill-the-cat.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Resent-To: cy Resent-Date: Fri, 24 Sep 1999 07:06:39 -0700 Resent-From: Cy Schubert X-UIDL: e11831742cf1648327586c6ab307b72c Hi, On Tue, 21 Sep 1999, Charles M. Hannum wrote: > [Resending once, since it's been 10.5 days...] > > Here's an interesting denial-of-service attack against FreeBSD >=3.0 > systems. It abuses a flaw in the `new' FreeBSD vfs_cache.c; it has no > way to purge entries unless the `vnode' (e.g. the file) they point to > is removed from memory -- which generally doesn't happen unless a > certain magic number of `vnodes' is in use, and never happens when the > `vnode' (i.e. file) is open. Thus it's possible to chew up an > arbitrary amount of wired kernel memory relatively simply. > Seems to be fixed in CVS version 1.38.2.3 of vfs_cache.c for RELENG_3 branch (meaning 3.3-STABLE) -- could you please check again ? Commit log: Limit aliases to a vnode in the namecache to a sysctl tunable 'vfs.cache.maxaliases'. This protects against a DoS via thousands of hardlinks to a file wiring down all kernel memory. Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 7:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 6512314D78 for ; Fri, 24 Sep 1999 07:46:55 -0700 (PDT) (envelope-from jesper@wheel.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 75BB03E1E; Fri, 24 Sep 1999 16:45:46 +0200 (CEST) Date: Fri, 24 Sep 1999 16:45:46 +0200 From: Jesper Skriver To: Bruce Albrecht Cc: current@FreeBSD.ORG Subject: Re: Why do FreeBSD mailing lists ignore MX preference? Message-ID: <19990924164546.B91653@skriver.dk> References: <199909241014.MAA91015@gratis.grondar.za> <14315.35085.935406.940824@celery.zuhause.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <14315.35085.935406.940824@celery.zuhause.org>; from Bruce Albrecht on Fri, Sep 24, 1999 at 09:22:05AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 24, 1999 at 09:22:05AM -0500, Bruce Albrecht wrote: > I know this is not -current related, but then, neither is the thread > on hub.freebsd.org refusing DUL origin messages. > > I have a DSL line with static IP, and all my FreeBSD mailing lists are > sent to bruce@zuhause.mn.org. There are two DNS MX records for > zuhause.mn.org, one at preference 100 with my IP address, and a second > at preference 150 for the mn.org main mail server. Even though my IP > has a lower preference value, none of my FreeBSD mailing list mail come > directly to my machine, it all passes through the minuet.skypoint.net. > I get plenty of mail sent to zuhause.mn.org from other locations which > talk directly to my machine, so why don't the FreeBSD mailing lists? It's not allowed to use ip addresses in MX records, only hostnames, and postfix doesn't accept the ip address, sendmail does. jesper@freesbee$ host -t mx zuhause.mn.org zuhause.mn.org mail is handled (pri=100) by 205.215.217.178 zuhause.mn.org mail is handled (pri=150) by minuet.skypoint.net So change it to zuhause.mn.org. IN A 205.215.217.178 IN MX 100 zuhause.mn.org. IN MX 150 minuet.skypoint.net. /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 8:23:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id BD92A14CF5 for ; Fri, 24 Sep 1999 08:23:31 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com (localhost [127.0.0.1]) by gw.nectar.com (Postfix) with ESMTP id F0C2BBE08; Fri, 24 Sep 1999 10:24:37 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: mlist/freebsd/current 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-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG In-reply-to: <199909241000.DAA02083@gndrsh.dnsmgr.net> References: <199909241000.DAA02083@gndrsh.dnsmgr.net> Subject: Filtering port 25 (was Re: On hub.freebsd.org refusing to talk to dialups) Mime-Version: 1.0 Content-Type: text/plain Date: Fri, 24 Sep 1999 10:24:37 -0500 Message-Id: <19990924152438.F0C2BBE08@gw.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This thread is off topic, but ... ] On 24 September 1999 at 3:00, "Rodney W. Grimes" wrote: > Another thing that ISP coulds start doing (we are in process with > this now, but on a monitoring only basis, instead of a deny we > just log them) is to block all outbound from AS tcp 25 setup packets. Monitoring this is not a bad idea. However, if you are suggesting that an ISP should /filter/ TCP port 25 packets, I have to disagree strongly. Vehemently, even :-) An ISP is in the business of delivering IP traffic. An ISP that fails to deliver ALL packets that are well formed (according to the relevant IETF standards and have a legitimate source address) is not doing what they are being payed to do. > This prevents your customers from being something that could get you > on the RBL or the DUL MAP for bad behavior, it also inforces the use > of your smart host relay, as it/they is/are the only way to get a > tcp port 25 setup completed. Evil! How does the ISP know I'm not running some other protocol (which is none of its business) on port 25? How does it know that I don't have a policy reason for accessing some other mail server than its own? Don't throw out the baby with the water! end-of-rant :-) Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 8:45:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id D74A4150FE for ; Fri, 24 Sep 1999 08:45:36 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id LAA08557; Fri, 24 Sep 1999 11:43:22 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id IAA23358; Fri, 24 Sep 1999 08:43:30 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id IAA26573; Fri, 24 Sep 1999 08:43:37 -0700 (PDT) Message-Id: <199909241543.IAA26573@mina.sr.hp.com> To: "Zach N. Heilig" Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Reply-To: Darryl Okahata In-reply-to: Your message of "Fri, 24 Sep 1999 08:29:59 CDT." <19990924082958.A14943@murkwood.znh.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 24 Sep 1999 08:43:37 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Zach N. Heilig" wrote: > The application for the tests is mpg123. > test mp3 playing time: 373 seconds. [ ... ] > 1) No Optimization > 225.08 real 224.30 user 0.23 sys [ ... ] > 2) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns > -fschedule-insns2 > 141.92 real 141.43 user 0.10 sys What do these timings represent? As you say the mp3 playing time is 373 seconds, but the "real" times vary, the timings don't appear to be the playing/processing of the mp3 file. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 8:52: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 178E2154D6 for ; Fri, 24 Sep 1999 08:51:49 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id RAA91996; Fri, 24 Sep 1999 17:50:43 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909241550.RAA91996@gratis.grondar.za> To: David Wolfskill Cc: current@FreeBSD.ORG, freebsd@gndrsh.dnsmgr.net Subject: Re: On hub.freebsd.org refusing to talk to dialups Date: Fri, 24 Sep 1999 17:50:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > About the only positive thing I have to say about the DUL is that Vix > stated that entries are placed on it at the request of the custodians of > the netblock in question. This is a very positive thing about the DUL; ISP co-operation. This implies that said ISP's are also prepared to provide an alternative method of mail delivery. I have some experience (from anti-spam mailing lists) of ISP's who are quite prepared to open port 25 for customers who ask. This is very good; SMTP has no authentication at all, and it is this "free-for-all" feature that spammers abuse. However - with a view to keeping the "open internet culture" going, it is delightful that said ISP's will allow outgoing SMTP provided the user "pre-agrees" that they will not abuse the privelige. This reduces the ISP's effort, keeping costs down, and is instrumental in huge spam "trappage". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 8:54:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0F2F2154D6 for ; Fri, 24 Sep 1999 08:54:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA11517; Fri, 24 Sep 1999 09:53:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA48117; Fri, 24 Sep 1999 09:53:54 -0600 (MDT) Message-Id: <199909241553.JAA48117@harmony.village.org> To: "Matthew D. Fuller" Subject: Re: ccd build failure Cc: Darryl Okahata , freebsd-current@FreeBSD.ORG, Anton Berezin In-reply-to: Your message of "Thu, 23 Sep 1999 17:54:00 CDT." <19990923175400.M10357@futuresouth.com> References: <19990923175400.M10357@futuresouth.com> <199909231942.VAA01843@dorifer.heim3.tu-clausthal.de> <199909232151.OAA06536@mina.sr.hp.com> Date: Fri, 24 Sep 1999 09:53:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990923175400.M10357@futuresouth.com> "Matthew D. Fuller" writes: : OK: : #!/bin/sh : (cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2> /dev/null ^^ -q Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 9: 2:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5B9D815589 for ; Fri, 24 Sep 1999 09:00:49 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA16730; Fri, 24 Sep 1999 09:00:41 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA70710; Fri, 24 Sep 1999 09:00:40 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 24 Sep 1999 09:00:40 -0700 (PDT) Message-Id: <199909241600.JAA70710@vashon.polstra.com> To: mark@grondar.za Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241014.MAA91015@gratis.grondar.za> References: <199909241014.MAA91015@gratis.grondar.za> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199909241014.MAA91015@gratis.grondar.za>, Mark Murray wrote: > > The RBL is great! There is a teensy bit of colateral damage, but not > so much that I worry about it. Here in ZA, our USP traffic provider > (Teleglobe) uses RBL, thus absolving us of the responsibility. Since > we started getting this "cleanfeed", spam has dropped dramatically. Strange. I use the RBL on my mail server here, but it really doesn't accomplish much. In the past 8 days it has blocked only 3 distinct spam e-mails, and that's typical. Yet I still receive an average of 5-10 spam mails in my mailbox every day. (*Must* *stop* *fist* *of* *death*!) A few random manual checks seem to indicate that the DUL would do much better for me. These days the RBL is more of a preventative measure than a blocking measure. It has already forced most open relays to tighten up. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 9: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A365614D21 for ; Fri, 24 Sep 1999 09:08:57 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA93368; Fri, 24 Sep 1999 12:08:19 -0400 (EDT) (envelope-from wollman) Date: Fri, 24 Sep 1999 12:08:19 -0400 (EDT) From: Garrett Wollman Message-Id: <199909241608.MAA93368@khavrinen.lcs.mit.edu> To: "Daniel C. Sobral" Cc: bsd@picard.mandrakesoft.de, freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... In-Reply-To: <37EAEB1A.3B0E4263@newsguy.com> References: <37EAEB1A.3B0E4263@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The point is that it _does_ hurt. Anything above -O3 is _likely_ to > have bugs. And more to the point: the FreeBSD Project will not support those who compile their kernel or world with anything other than the default optimization settings and compilers. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 9:11:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id DB58B1558C for ; Fri, 24 Sep 1999 09:11:36 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id SAA92080; Fri, 24 Sep 1999 18:11:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909241611.SAA92080@gratis.grondar.za> To: John Polstra Cc: current@freebsd.org Subject: Re: On hub.freebsd.org refusing to talk to dialups Date: Fri, 24 Sep 1999 18:11:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These days the RBL is more of a preventative measure than a blocking > measure. It has already forced most open relays to tighten up. I'll go with that. The DUL stops _huge_ amounts of "drive-by" spam, though... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 9:23:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D431B14D43 for ; Fri, 24 Sep 1999 09:23:12 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA02805; Fri, 24 Sep 1999 09:22:04 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241622.JAA02805@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241402.HAA04384@pau-amma.whistle.com> from David Wolfskill at "Sep 24, 1999 07:02:14 am" To: dhw@whistle.com (David Wolfskill) Date: Fri, 24 Sep 1999 09:22:03 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From: "Rodney W. Grimes" > >Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT) > > >Another thing that ISP coulds start doing (we are in process with > >this now, but on a monitoring only basis, instead of a deny we > >just log them) is to block all outbound from AS tcp 25 setup packets. > > Not quite sure I follow this. ipfw add 10250 allow tcp from ${smtpsmarthost} to any 25 setup out via lnc1 ipfw add 10259 allow log tcp from any to any 25 setup out via lnc1 This is placed on all AS border routers, anyone attempting to do direct port 25 outbound from our AS trips 10259 and gets to talk to me about what it is they are doing. The comptete rules set is a fair bit more complicated than the above as we are also a transit AS and I have to allow the port 25 setup traffic from them to work correctly, so I can't just go make 10259 a deny at this time. > > >This prevents your customers from being something that could get you > >on the RBL or the DUL MAP for bad behavior, it also inforces the use > >of your smart host relay, as it/they is/are the only way to get a > >tcp port 25 setup completed. > > About the only positive thing I have to say about the DUL is that Vix > stated that entries are placed on it at the request of the custodians of > the netblock in question. If that is the case then this is ideal. Everyone should be using the DUL, as the maintainer of that IP space has specifically stated that they do not want or allow smtp setup connections from that IP space. Thus by using the DUL you are simply helping a costodian implement the policy they have already layed down. > > >Do you know about the RBL? How do you feel about it? We are using > >it via DNS and BGP on a test basis right now. I have had legitimate > >important mail blocked at Freebsd.org due to the source being on the > >RBL, but that is a price I am willing to pay. > > I'm far more comfortable with the use of the RBL than the DUL. Given what you stated above I don't see how you could favor the RBL over the DUL, the DUL is stated administrative policy, the RBL is a reactive to bad behavior and in opposition to stated administrative policy for almost every entry in it. > Indeed, my externally-visible home SMTP server uses the RBL (but not the > DUL). You should probably run both.... I know I am going to go see what it takes to intergrate DUL into our current scheme of things. And submit our IP dial up blocks for inclusion in the list. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 9:39: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B6ADB14CBB for ; Fri, 24 Sep 1999 09:38:36 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA02838; Fri, 24 Sep 1999 09:37:14 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241637.JAA02838@gndrsh.dnsmgr.net> Subject: Re: Filtering port 25 (was Re: On hub.freebsd.org refusing to talk to dialups) In-Reply-To: <19990924152438.F0C2BBE08@gw.nectar.com> from Jacques Vidrine at "Sep 24, 1999 10:24:37 am" To: n@nectar.com (Jacques Vidrine) Date: Fri, 24 Sep 1999 09:37:14 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [This thread is off topic, but ... ] > On 24 September 1999 at 3:00, "Rodney W. Grimes" wrote: > > Another thing that ISP coulds start doing (we are in process with > > this now, but on a monitoring only basis, instead of a deny we > > just log them) is to block all outbound from AS tcp 25 setup packets. > > Monitoring this is not a bad idea. However, if you are suggesting > that an ISP should /filter/ TCP port 25 packets, I have to disagree > strongly. Vehemently, even :-) Perhaps you should try being in the business and having to deal with the calls that happen when some luser signs up with you for the purpose of spamming and admin's around the world start to flood your abuse@domain address with the spammers junk. Perhaps you should have to make the calls to get your IP space unblocked from certain entities due to the actions of 1 bad luser. If we have an AUP that states that all outbound smtp port 25 connections shall be via our smarthost relay hosts we darn well have a right not only to monitor that this is being done, we further more have a right to inforce it if we so decide to. > An ISP is in the business of delivering IP traffic. An ISP that fails > to deliver ALL packets that are well formed (according to the relevant > IETF standards and have a legitimate source address) is not doing what > they are being payed to do. If you want us to be a transpart IP transport you are asking us to waive our AUP. We can, but your contract is going to have to be specially written, and will have serous damage clauses attached to it that will basically allow us to terminate your contract without notice, yet collect the balance due on your contract. > > > This prevents your customers from being something that could get you > > on the RBL or the DUL MAP for bad behavior, it also inforces the use > > of your smart host relay, as it/they is/are the only way to get a > > tcp port 25 setup completed. > > Evil! How does the ISP know I'm not running some other protocol > (which is none of its business) on port 25? How does it know that I > don't have a policy reason for accessing some other mail server than > its own? We don't, but your violating IETF standards by doing anything other than smtp on port 25 of tcp. Violating IETF standards is not a good thing to do, and violating an ISP's AUP is also not a good thing to do. The only real reason to run something other than smtp on port 25 is to circumvent firewalls, which can lead to legal prosecussion. ISP's are _not_ common carriers, or at least the courts haven't made up thier minds on this one. > > Don't throw out the baby with the water! If the baby is causing us problems we darn well throw him right out! And we will collect a big chunk of money from them in the process. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:17:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id DBD1F14C96 for ; Fri, 24 Sep 1999 10:17:19 -0700 (PDT) (envelope-from gary@eyelab.psy.msu.edu) Received: from DEVEL-EYELAB (dhcp202.baker.ssc.msu.edu [35.8.194.202]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id NAA24987; Fri, 24 Sep 1999 13:15:06 -0400 (EDT) (envelope-from gary@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> X-Sender: gary@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 24 Sep 1999 13:10:56 -0700 To: "Rodney W. Grimes" From: Gary Schrock Subject: Re: On hub.freebsd.org refusing to talk to dialups Cc: current@FreeBSD.ORG In-Reply-To: <199909241000.DAA02083@gndrsh.dnsmgr.net> References: <199909240738.JAA90307@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:00 AM 9/24/1999 -0700, you wrote: >Another thing that ISP coulds start doing (we are in process with >this now, but on a monitoring only basis, instead of a deny we >just log them) is to block all outbound from AS tcp 25 setup packets. Hmm, maybe I'm interpreting this wrong (I hope so), but I interpret this as saying that basically you'd only be able to mail things through your local isp's mailhost. It means that if you use several different mail servers, all mail would still have to go through the local isp's. Personally, I would immediately unsubscribe to any isp that decided this was acceptable behavior on their part. I use the mail server at work for all my outgoing mail. Why? Because the machine is lightly loaded and I don't have to worry about my mail getting lost in the depths of my isp's mail server for a couple hours because their loads tend to run high. (Hell, I don't generally even use the email account provided by the local isp because of load issues, my work account is so much more reliable). Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:36: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 250EC14C2A for ; Fri, 24 Sep 1999 10:36:04 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA03460; Fri, 24 Sep 1999 10:35:52 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241735.KAA03460@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> from Gary Schrock at "Sep 24, 1999 01:10:56 pm" To: gary@eyelab.psy.msu.edu (Gary Schrock) Date: Fri, 24 Sep 1999 10:35:52 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 03:00 AM 9/24/1999 -0700, you wrote: > >Another thing that ISP coulds start doing (we are in process with > >this now, but on a monitoring only basis, instead of a deny we > >just log them) is to block all outbound from AS tcp 25 setup packets. > > Hmm, maybe I'm interpreting this wrong (I hope so), but I interpret this as > saying that basically you'd only be able to mail things through your local > isp's mailhost. It means that if you use several different mail servers, > all mail would still have to go through the local isp's. Personally, I Yep, thats exactly what I am saying. > would immediately unsubscribe to any isp that decided this was acceptable > behavior on their part. I use the mail server at work for all my outgoing > mail. Why? Because the machine is lightly loaded and I don't have to > worry about my mail getting lost in the depths of my isp's mail server for > a couple hours because their loads tend to run high. (Hell, I don't > generally even use the email account provided by the local isp because of > load issues, my work account is so much more reliable). Our outbound smarthost smtp server is carefully monitor, has never lost a single mail message, and screaming fast at getting email out. After all we also run commercial opt-in bulk emailing for large clients and we do know how to get 100's of thosands of messages out in a real fast way. Probably mork work has been put into our smarthost than any company has bothered to put into thier smtp relay. Your work also has a serious security concern if it allows this you to directly attatch to it's port 25. Can you say firewall circumvention... I thought so. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:38:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CCD7915081 for ; Fri, 24 Sep 1999 10:37:45 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA93926; Fri, 24 Sep 1999 13:37:37 -0400 (EDT) (envelope-from wollman) Date: Fri, 24 Sep 1999 13:37:37 -0400 (EDT) From: Garrett Wollman Message-Id: <199909241737.NAA93926@khavrinen.lcs.mit.edu> To: "Rodney W. Grimes" Cc: gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241735.KAA03460@gndrsh.dnsmgr.net> References: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> <199909241735.KAA03460@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Your work also has a serious security concern if it allows this you to > directly attatch to it's port 25. Can you say firewall circumvention... What firewall? If Gary's employer is at all like the shop I help run, there are none. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:43:57 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 72E4514CE5; Fri, 24 Sep 1999 10:43:55 -0700 (PDT) From: "Jonathan M. Bresler" To: jabley@patho.gen.nz Cc: mark@grondar.za, current@FreeBSD.ORG In-reply-to: <19990924162820.A27798@patho.gen.nz> (message from Joe Abley on Fri, 24 Sep 1999 16:28:20 +1200) Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-Id: <19990924174355.72E4514CE5@hub.freebsd.org> Date: Fri, 24 Sep 1999 10:43:55 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One of us, at least, evidently. > > How much mail does the use of the MAPS DUL reject? varies sharply from day to day. since 8/31 dul has rejected 93 connection attempts. map has rejected 361 connection attempts. > > How much of that do you think is worth rejecting? > all of it. dialup addresses are havens for spammers....these are throw away accounts that are covered by the cost of the spamming. only if the spammer is sued successfully does teh account become a problem to the spammer. legitimate dialup users should use the mail relay provided by their ISP. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:46:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 2BF3E14CD5 for ; Fri, 24 Sep 1999 10:46:16 -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.9.3/8.9.3) with SMTP id LAA20615; Fri, 24 Sep 1999 11:45:31 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA27853; Fri, 24 Sep 1999 11:45:25 -0600 Date: Fri, 24 Sep 1999 11:45:25 -0600 Message-Id: <199909241745.LAA27853@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Rodney W. Grimes" Cc: gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241735.KAA03460@gndrsh.dnsmgr.net> References: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> <199909241735.KAA03460@gndrsh.dnsmgr.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > would immediately unsubscribe to any isp that decided this was acceptable > > behavior on their part. I agree. > Your work also has a serious security concern if it allows this you to > directly attatch to it's port 25. No it doesn't, but you do bring up another good point why not to use the ISP's mail server. Security. I don't want email to bounce on your box and potentially give the ISP's postmaster information they shouldn't be having. (Including email about us switching ISP's because we hate their email policy. :) Yes, our ISP *could* sniff packets are read our email if they wanted, but it would be a breach of contract for them to do so. Basically, I think not allowing ISP's to allow the Dialup lines to forward email as a good thing, but for them to limit was businesses do with their IP traffic is simply too big brother'ish, no matter what their contract states. I'm as much at risk (or more) from spammers that abuse my mail host as they are, so it behooves me to setup my mail machine (and network) to 'Do The Right Thing'. Rather than ISP's blocking email, they should instead be working with their customers to provide them with expertise on how to setup a working/usable mail server. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 10:50:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id F165214D2F for ; Fri, 24 Sep 1999 10:50:16 -0700 (PDT) (envelope-from gary@eyelab.psy.msu.edu) Received: from DEVEL-EYELAB (dhcp202.baker.ssc.msu.edu [35.8.194.202]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id NAA25617; Fri, 24 Sep 1999 13:49:47 -0400 (EDT) (envelope-from gary@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990924133513.00a86350@eyelab.msu.edu> X-Sender: gary@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 24 Sep 1999 13:45:37 -0700 To: "Rodney W. Grimes" From: Gary Schrock Subject: Re: On hub.freebsd.org refusing to talk to dialups Cc: current@FreeBSD.ORG In-Reply-To: <199909241735.KAA03460@gndrsh.dnsmgr.net> References: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:35 AM 9/24/1999 -0700, Rodney W. Grimes wrote: >Our outbound smarthost smtp server is carefully monitor, has never lost >a single mail message, and screaming fast at getting email out. After >all we also run commercial opt-in bulk emailing for large clients and >we do know how to get 100's of thosands of messages out in a real fast >way. Probably mork work has been put into our smarthost than any company >has bothered to put into thier smtp relay. Maybe at your place this is true, but for a lot of isps this is definitely not true. If this type of thing were to become a general practice (blocking you from using any smtp server other than the local isp's), I would consider it to be a bad thing. Hell, I don't use the university's mail servers here because they're slow. (Quite honestly, one of the reasons we have our own mail server for our lab is that we got frustrated with the university's mail system). >Your work also has a serious security concern if it allows this you to >directly attatch to it's port 25. Can you say firewall circumvention... >I thought so. Heh, yeah, that's a good one. Firewall? Hell, I don't even have control over the wiring to our lab. Without running a whole bunch of new wires in the building (and I guarantee the campus network people would have a fit about that), I don't think I could even set up a firewall if I wanted to. Some of us have to work within the situation dealt to us, and that situation isn't always optimal. Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 11:41: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 06D0B15758; Fri, 24 Sep 1999 11:40:58 -0700 (PDT) From: "Jonathan M. Bresler" To: bruce@zuhause.mn.org Cc: current@FreeBSD.ORG In-reply-to: <14315.35085.935406.940824@celery.zuhause.org> (message from Bruce Albrecht on Fri, 24 Sep 1999 09:22:05 -0500 (CDT)) Subject: Re: Why do FreeBSD mailing lists ignore MX preference? Message-Id: <19990924184058.06D0B15758@hub.freebsd.org> Date: Fri, 24 Sep 1999 11:40:58 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Non-authoritative answer: > zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net > zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 postfix does not like your numeric MX record Sep 24 01:35:46 hub postfix/smtp[77991]: warning: valid_hostname: numeric hostname: 205.215.217.178 Sep 24 01:35:49 hub postfix/smtp[77991]: 76AE315266: to=, relay=minuet.skypoint.net, delay=66, status=sent (250 DAA01296 Message accepted for delivery) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 11:48:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7109D14CF8 for ; Fri, 24 Sep 1999 11:48:32 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA03621; Fri, 24 Sep 1999 11:47:46 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241847.LAA03621@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241745.LAA27853@mt.sri.com> from Nate Williams at "Sep 24, 1999 11:45:25 am" To: nate@mt.sri.com (Nate Williams) Date: Fri, 24 Sep 1999 11:47:46 -0700 (PDT) Cc: gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > would immediately unsubscribe to any isp that decided this was acceptable > > > behavior on their part. > > I agree. > > > Your work also has a serious security concern if it allows this you to > > directly attatch to it's port 25. > > No it doesn't, but you do bring up another good point why not to use the > ISP's mail server. Security. I don't want email to bounce on your box > and potentially give the ISP's postmaster information they shouldn't be > having. (Including email about us switching ISP's because we hate their > email policy. :) If your mail is sensitive use a proper transport, encrypt it. > > Yes, our ISP *could* sniff packets are read our email if they wanted, > but it would be a breach of contract for them to do so. No, it would not, I have yet to see any ISP's contract that says such a thing. Do not attempt to apply common carrier status to ISP's, that only works if they happen to be CLEC/LEC/IXC/LD's or some such, and only if they screwed up thier organizationalization to cause the ISP portion of the business to classify under the common carrier laws. > Basically, I think not allowing ISP's to allow the Dialup lines to > forward email as a good thing, but for them to limit was businesses do > with their IP traffic is simply too big brother'ish, no matter what > their contract states. If _we_ don't start to do something about it, big brother _is_ going to do something about it. Trust me on this one, being a member of the USPA I know that we are far better off implementing our own (as ISP's) set of safe gaurds that help eliminate certain undesirable behavior. 5 years ago I could get in a jump plan and not worry about a seat or a seat belt. Now the FAA has regulated us into mandator seat's and seat belts. Yes, it improved safety, but the fact that the FAA now runs around poping surprize inspections cost me more tax payer dollars for something we all knew we should have been doing all along. I don't want any more stinking laws!! Also understand that ISP's can be held legally liable under negligence law for certain in actions. There are cases on the books that demonstrate this. Unfortanate, but true non the less. > I'm as much at risk (or more) from spammers that abuse my mail host as > they are, so it behooves me to setup my mail machine (and network) to > 'Do The Right Thing'. Rather than ISP's blocking email, they should > instead be working with their customers to provide them with expertise > on how to setup a working/usable mail server. And we do, for dedicated connect customers ${smtpsmarthost} usally includes their host as well, but we prefer to have them hand the mail off to our servers since it is far better designed than 99% of what any customer can even afford to do. For the really big clients we even co-locate thier dedicated smtp smarthost in our facility for them. This saves them traffic on thier link, puts them on carrier class power and environment, and gives them a 24x7 tech winnie to fix any problems. They also have great benifits by agreeing to our standard AUP, they have RBL filtering done, etc, etc, etc. This is the _service_ part of ISP that every one else leaves out. If you want IP without service go talk to someone else. We are about service. A lot of what we implemented was actually caused by direct requests from customers. We have had no complaints about it, and I don't get email from the RBL maintainers! -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 11:50: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id DE27F15F54; Fri, 24 Sep 1999 11:50:01 -0700 (PDT) From: "Jonathan M. Bresler" To: jdp@polstra.com Cc: mark@grondar.za, current@freebsd.org In-reply-to: <199909241600.JAA70710@vashon.polstra.com> (message from John Polstra on Fri, 24 Sep 1999 09:00:40 -0700 (PDT)) Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-Id: <19990924185001.DE27F15F54@hub.freebsd.org> Date: Fri, 24 Sep 1999 11:50:01 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Strange. I use the RBL on my mail server here, but it really doesn't > accomplish much. In the past 8 days it has blocked only 3 distinct > spam e-mails, and that's typical. Yet I still receive an average of > 5-10 spam mails in my mailbox every day. (*Must* *stop* *fist* *of* > *death*!) A few random manual checks seem to indicate that the DUL > would do much better for me. insert plug for the FreeBSDcon talk "Stopping Spam--Five Years in the Trenches" by Jonathan M Bresler ;P jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12: 7:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 2FB2714CEE for ; Fri, 24 Sep 1999 12:07:35 -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.9.3/8.9.3) with SMTP id NAA21354; Fri, 24 Sep 1999 13:07:29 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA28321; Fri, 24 Sep 1999 13:07:27 -0600 Date: Fri, 24 Sep 1999 13:07:27 -0600 Message-Id: <199909241907.NAA28321@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Rodney W. Grimes" Cc: nate@mt.sri.com (Nate Williams), gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241847.LAA03621@gndrsh.dnsmgr.net> References: <199909241745.LAA27853@mt.sri.com> <199909241847.LAA03621@gndrsh.dnsmgr.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I agree. > > > > > Your work also has a serious security concern if it allows this you to > > > directly attatch to it's port 25. > > > > No it doesn't, but you do bring up another good point why not to use the > > ISP's mail server. Security. I don't want email to bounce on your box > > and potentially give the ISP's postmaster information they shouldn't be > > having. (Including email about us switching ISP's because we hate their > > email policy. :) > > If your mail is sensitive use a proper transport, encrypt it. All mail is senstive, it just that sometimes that the cost of encrypting is more expensive than the cost of setting everyone up so they can decrypt it. In short, there is no 'portable' way of encrypting/decrypting mail. > > Yes, our ISP *could* sniff packets are read our email if they wanted, > > but it would be a breach of contract for them to do so. > > No, it would not. *YES*, it would. Don't tell me what my ISP can/can not do, because you have no idea. > > Basically, I think not allowing ISP's to allow the Dialup lines to > > forward email as a good thing, but for them to limit was businesses do > > with their IP traffic is simply too big brother'ish, no matter what > > their contract states. > > If _we_ don't start to do something about it, big brother _is_ going > to do something about it. Now you're going off the deep-end. Big-brother has shown that they simply don't *care* what happens, to the point that SPAM is still legal to do in almost all cases, and people must opt-out of it. > They also have great benifits by agreeing to our standard AUP, they > have RBL filtering done, etc, etc, etc. This is the _service_ part > of ISP that every one else leaves out. As I stated before, any decent ISP will take the time to help a client setup services they desire, not do it for them. Doing it for a customer WHO WANTS TO DO IT THEMSELVES is the unix way. We're doing it, because you're too stupid/clueless to do it yourself, and we're not going to give out the 'secret' information. If the customer doesn't want to host it themselves, then by all means have the ability to do it for them, and you can charge them for it even. :) But, just because you think you are an ISP doesn't make you any more expert than people running their own businesses off it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:18:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 2315315654 for ; Fri, 24 Sep 1999 12:18:45 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn14.imasy.or.jp [202.227.24.206]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id EAA06519 for ; Sat, 25 Sep 1999 04:17:14 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199909241917.EAA06519@tasogare.imasy.or.jp> To: current@freebsd.org Subject: Re: Experimental ACPI driver. In-Reply-To: Your message of "Fri, 24 Sep 1999 00:18:31 +0900" <199909231518.AAA00842@libr.scitec.kobe-u.ac.jp> References: <199909231518.AAA00842@libr.scitec.kobe-u.ac.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 25 Sep 1999 04:20:03 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, there. > We wrote experimental ACPI driver for 4.0-CURRENT. This was just one week work so its functionallity is very very poor :-) but I think it is good idea to start with this for developping ACPI driver for FreeBSD because it is enough small to understand it. If someone already started wriring ACPI devive driver, please let us know. We'd like to merge them and would be happy in collaboration with you. > If you have question please ask me or iwasaki@jp.FreeBSD.org . BTW, I've just start leaning a week ago, my knowledge is still little on ACPI :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:29:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id E81B314EDC for ; Fri, 24 Sep 1999 12:29:32 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id PAA28391 for ; Fri, 24 Sep 1999 15:27:04 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Fri, 24 Sep 1999 15:27:04 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: rtc? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reinstalled -current today, and for some reason there is an extra device generating interrupts. When I do a systat -vm 1 I find that there is a device called rtc at irq8 generating 128 interrupts. What is it? I didn't configure it, and it wasn't there before. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:35:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2509614CE5 for ; Fri, 24 Sep 1999 12:35:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA05639; Fri, 24 Sep 1999 21:34:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: rtc? In-reply-to: Your message of "Fri, 24 Sep 1999 15:27:04 EDT." Date: Fri, 24 Sep 1999 21:34:36 +0200 Message-ID: <5637.938201676@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kenneth Culver writes: >I reinstalled -current today, and for some reason there is an extra device >generating interrupts. When I do a systat -vm 1 I find that there is a >device called rtc at irq8 generating 128 interrupts. What is it? I didn't >configure it, and it wasn't there before. It has always been there, it is the RTC clock or "softclock" which is used to tally up the user/system times for processes and a few similar statistics jobs. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:44:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id C2BCF156A4 for ; Fri, 24 Sep 1999 12:44:34 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA03816; Fri, 24 Sep 1999 12:44:10 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909241944.MAA03816@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241907.NAA28321@mt.sri.com> from Nate Williams at "Sep 24, 1999 01:07:27 pm" To: nate@mt.sri.com (Nate Williams) Date: Fri, 24 Sep 1999 12:44:09 -0700 (PDT) Cc: gary@eyelab.psy.msu.edu (Gary Schrock), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I agree. > > > > > > > Your work also has a serious security concern if it allows this you to > > > > directly attatch to it's port 25. > > > > > > No it doesn't, but you do bring up another good point why not to use the > > > ISP's mail server. Security. I don't want email to bounce on your box > > > and potentially give the ISP's postmaster information they shouldn't be > > > having. (Including email about us switching ISP's because we hate their > > > email policy. :) > > > > If your mail is sensitive use a proper transport, encrypt it. > > All mail is senstive, it just that sometimes that the cost of encrypting > is more expensive than the cost of setting everyone up so they can > decrypt it. In short, there is no 'portable' way of > encrypting/decrypting mail. > > > > Yes, our ISP *could* sniff packets are read our email if they wanted, > > > but it would be a breach of contract for them to do so. > > > > No, it would not. > > *YES*, it would. Don't tell me what my ISP can/can not do, because you > have no idea. I think you should take a chill pill, then go read that contract again... there should at least be a clause that allows them to monitor (``sniff'') for the purpose of rendering service. If not, they really blew thier contract from a legal prespective as now they can't even hook up a sniffer to trouble shoot, run tcpdump, etc. > > > > Basically, I think not allowing ISP's to allow the Dialup lines to > > > forward email as a good thing, but for them to limit was businesses do > > > with their IP traffic is simply too big brother'ish, no matter what > > > their contract states. > > > > If _we_ don't start to do something about it, big brother _is_ going > > to do something about it. > > Now you're going off the deep-end. Big-brother has shown that they > simply don't *care* what happens, to the point that SPAM is still > legal to do in almost all cases, and people must opt-out of it. You haven't been around unregulated things much have you? HAM radio and the FCC use to be a pretty open page, now it's rules up the wazoo. Skydiving use to be totally unregulated, started out as a few pages in a FAR, now its getting bigger, and if the USPA had not taken drastics steps 5 years ago to impose it's own major self regulation the FCC was ready to cram some pretty tight rules down our throats. It took untold time and money to sway the FCC into letting us correct the problem ourselves. One reason spam is still legal is we (the internet community at large) has made inroads into cutting it down, and are infact at least trying to self regulate it. Uncle sam will only keep its hands off so long, but trust me, a few more kidnappings by email occur and your going to see some deadly serious laws proposed. We already have several laws on the books, one in Washigton, and another in California. There has been a propsed senate bill. If you think this is ``don't care'' aditude you had better wake up to just how the legislative process works. They never get it right the first 10 times, and by the time they get it done it's way more than what was ever needed. > > > They also have great benifits by agreeing to our standard AUP, they > > have RBL filtering done, etc, etc, etc. This is the _service_ part > > of ISP that every one else leaves out. > > As I stated before, any decent ISP will take the time to help a client > setup services they desire, not do it for them. Doing it for a customer > WHO WANTS TO DO IT THEMSELVES is the unix way. We're doing it, because > you're too stupid/clueless to do it yourself, and we're not going to > give out the 'secret' information. Then your an exception in the general populus of clients, as we are an exception in the general populas of ISP's. Most customers actually like it when you do something for them for free that they wanted done anyway. Like I said else where, most of this has been done at customer requests. > If the customer doesn't want to host it themselves, then by all means > have the ability to do it for them, and you can charge them for it > even. :) > > But, just because you think you are an ISP doesn't make you any more > expert than people running their own businesses off it. We don't think we are an ISP, we are. Myself, well, I'm not, I just do contract work for a dozen or so companies that call themselves ISP's. If you really think I am lost and off the deep end, well... thats your right. Several of the peers to us are loving what we do for them... and our attrition rate has gone done since we implemented many of these policies. Being able to tout ``Reduced spam internet service'' on a sales litrature is a selling point to many a client... -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:48:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 322FE151D0 for ; Fri, 24 Sep 1999 12:48:23 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA17359; Fri, 24 Sep 1999 15:47:11 -0400 (EDT) (envelope-from luoqi) Date: Fri, 24 Sep 1999 15:47:11 -0400 (EDT) From: Luoqi Chen Message-Id: <199909241947.PAA17359@lor.watermarkgroup.com> To: culverk@culverk.student.umd.edu, phk@critter.freebsd.dk Subject: Re: rtc? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kenneth Culver writes: > > >I reinstalled -current today, and for some reason there is an extra device > >generating interrupts. When I do a systat -vm 1 I find that there is a > >device called rtc at irq8 generating 128 interrupts. What is it? I didn't > >configure it, and it wasn't there before. > > It has always been there, it is the RTC clock or "softclock" which is ^^^^^^^^^ You meant statclock, right? > used to tally up the user/system times for processes and a few similar > statistics jobs. > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 12:53:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 571DA14C93 for ; Fri, 24 Sep 1999 12:53:10 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 67E4C1C25; Fri, 24 Sep 1999 14:56:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 5B44A382B; Fri, 24 Sep 1999 14:56:52 -0400 (EDT) Date: Fri, 24 Sep 1999 14:56:52 -0400 (EDT) From: Bill Fumerola To: "Rodney W. Grimes" Cc: John Saunders , FreeBSD current Subject: Re: Automating filesystem check at boot time In-Reply-To: <199909240613.XAA01586@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Sep 1999, Rodney W. Grimes wrote: > You need to find and fix what ever it is that is not dieing when being > told to die. Your work around is a bandaid that only hides the real > problem, which is probably a bug some place in something. amd and NFS > are good first conidates. Just what process does it complain that it > is unable to kill, or does it just say could not kill? Vinum is usually the culprit for me, though I haven't built a world on most of these machines for a while, so this may be fixed. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13: 2:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D929914E0C for ; Fri, 24 Sep 1999 13:02:26 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA05793; Fri, 24 Sep 1999 22:00:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: culverk@culverk.student.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: rtc? In-reply-to: Your message of "Fri, 24 Sep 1999 15:47:11 EDT." <199909241947.PAA17359@lor.watermarkgroup.com> Date: Fri, 24 Sep 1999 22:00:08 +0200 Message-ID: <5791.938203208@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909241947.PAA17359@lor.watermarkgroup.com>, Luoqi Chen writes: >> Kenneth Culver writes: >> >> >I reinstalled -current today, and for some reason there is an extra device >> >generating interrupts. When I do a systat -vm 1 I find that there is a >> >device called rtc at irq8 generating 128 interrupts. What is it? I didn't >> >configure it, and it wasn't there before. >> >> It has always been there, it is the RTC clock or "softclock" which is > ^^^^^^^^^ >You meant statclock, right? Yes of course. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13: 2:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 90F61156EB for ; Fri, 24 Sep 1999 13:02:35 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk ([192.168.0.3] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.032 #1) id 11UZH1-0009FM-00; Fri, 24 Sep 1999 18:36:43 +0100 Received: (from ben) by lithium.scientia.demon.co.uk (Exim 3.032 #1) id 11UZH0-0007uy-00; Fri, 24 Sep 1999 18:36:42 +0100 Date: Fri, 24 Sep 1999 18:36:41 +0100 From: Ben Smithurst To: Bruce Albrecht Cc: current@FreeBSD.ORG Subject: Re: Why do FreeBSD mailing lists ignore MX preference? Message-ID: <19990924183641.A30415@lithium.scientia.demon.co.uk> References: <199909241014.MAA91015@gratis.grondar.za> <14315.35085.935406.940824@celery.zuhause.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <14315.35085.935406.940824@celery.zuhause.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Albrecht wrote: > Non-authoritative answer: > zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net > zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 "205.215.217.178." almost certainly does not have an address (A) record. Mail exchangers must be host names, not IP addresses. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13: 9:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-45.cpinternet.com [208.149.16.45]) by hub.freebsd.org (Postfix) with ESMTP id 4372114E0C; Fri, 24 Sep 1999 13:08:55 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id PAA23295; Fri, 24 Sep 1999 15:08:10 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 24 Sep 1999 15:08:10 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: gary@eyelab.psy.msu.edu Cc: chat@freebsd.org Subject: Re: On hub.freebsd.org refusing to talk to dialups X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14315.55666.529851.717631@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I would immediately unsubscribe to any isp that decided this was acceptable : behavior on their part. I use the mail server at work for all my outgoing : mail. Why? Because the machine is lightly loaded and I don't have to : worry about my mail getting lost in the depths of my isp's mail server for : a couple hours .... Amen. For that matter, I'd much rather have my private data on the public wire than on an independently administered server's disk -- make them at least take the trouble to run a sniffer in order to see the data! [But let's redirect this to chat.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13:14: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 6B42E14E0C for ; Fri, 24 Sep 1999 13:14:04 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA18557; Fri, 24 Sep 1999 22:13:36 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9294A8711; Fri, 24 Sep 1999 20:42:05 +0200 (CEST) Date: Fri, 24 Sep 1999 20:42:05 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Cc: Bruce Albrecht Subject: Re: Why do FreeBSD mailing lists ignore MX preference? Message-ID: <19990924204205.A93825@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG, Bruce Albrecht References: <199909241014.MAA91015@gratis.grondar.za> <14315.35085.935406.940824@celery.zuhause.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <14315.35085.935406.940824@celery.zuhause.org> X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5593 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bruce Albrecht: > zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net > zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 ^^^^^^^^^^^^^^^ This is plainly wrong. You're not allowed to put IP addresses in MX records. If you have a static address then you should have a PTR pointing to your machine. Use that. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13:14:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id AABC51562A for ; Fri, 24 Sep 1999 13:14:32 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA18573 for current@freebsd.org; Fri, 24 Sep 1999 22:14:19 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8151E8711; Fri, 24 Sep 1999 20:43:19 +0200 (CEST) Date: Fri, 24 Sep 1999 20:43:19 +0200 From: Ollivier Robert To: current@freebsd.org Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-ID: <19990924204319.B93825@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <199909241014.MAA91015@gratis.grondar.za> <199909241600.JAA70710@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199909241600.JAA70710@vashon.polstra.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5593 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to John Polstra: > Strange. I use the RBL on my mail server here, but it really doesn't > accomplish much. In the past 8 days it has blocked only 3 distinct Same here. The DUL is much more effective than the RBL. I'll probably use the RSS too (with monitoring ofc ourse). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 13:38:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id F398914D67 for ; Fri, 24 Sep 1999 13:38:42 -0700 (PDT) (envelope-from sasblc@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id QAA24148 for ; Fri, 24 Sep 1999 16:37:45 -0400 (EDT) Received: from concours.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08764; Fri, 24 Sep 1999 16:37:15 -0400 Received: (from sasblc@localhost) by concours.pc.sas.com (8.9.3/8.8.8) id QAA36690; Fri, 24 Sep 1999 16:36:55 -0400 (EDT) (envelope-from sasblc) From: Brad Chisholm Message-Id: <199909242036.QAA36690@concours.pc.sas.com> Subject: System crash on "vinum start" To: freebsd-current@freebsd.org Date: Fri, 24 Sep 1999 16:36:54 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a problem where the "vinum start" command crashes my system. This happens regardless of whether it's being issued during bootup via /etc/rc or from the command line on a running system. Interestingly, however, if I issue the start command from the vinum interactive prompt, it works properly with no crash. I'm currently running on a snap built this morning (0924), but it was also happening on a snap from 0914. Crash info, vinum config, and disk info are below. Let me know if I can provide any additional information. Thanks, Brad # uname -a FreeBSD 4.0-19990924-SNAP FreeBSD 4.0-19990924-SNAP #1: Fri Sep 24 15:49:04 EDT 1999 root@:/usr/src/sys/compile/PRISMDB i386 (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 IdlePTD 3878912 initial pcb at 332900 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xc018b64b stack pointer = 0x10:0xc94f4bb0 frame pointer = 0x10:0xc94f4be0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 195 (vinum) interrupt mask = bio trap number = 12 panic: page fault syncing disks... 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 112 giving up dumping to dev #wd/0x20001, offset 786432 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 281 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 #1 0xc0169e80 in poweroff_wait (junk=0xc02fd44f, howto=-928026240) at ../../kern/kern_shutdown.c:531 #2 0xc0272269 in trap_fatal (frame=0xc94f4b70, eva=72) at ../../i386/i386/trap.c:907 #3 0xc0271f41 in trap_pfault (frame=0xc94f4b70, usermode=0, eva=72) at ../../i386/i386/trap.c:800 #4 0xc0271beb in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 512, tf_ebp = -917550112, tf_isp = -917550180, tf_ebx = 0, tf_edx = 0, tf_ecx = 8, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072122293, tf_cs = 8, tf_eflags = 66118, tf_esp = -917550000, tf_ss = 512}) at ../../i386/i386/trap.c:426 #5 0xc018b64b in getblk (vp=0x0, blkno=8, size=4096, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:2109 #6 0xc018995a in bread (vp=0x0, blkno=8, size=4096, cred=0x0, bpp=0xc94f4c50) at ../../kern/vfs_bio.c:477 #7 0xc0d65fcf in ?? () #8 0xc0d67072 in ?? () #9 0xc0d64e6d in ?? () #10 0xc0d64ec7 in ?? () #11 0xc0d6af94 in ?? () #12 0xc019dc47 in spec_ioctl (ap=0xc94f4e08) at ../../miscfs/specfs/spec_vnops.c:513 #13 0xc019d4bd in spec_vnoperate (ap=0xc94f4e08) at ../../miscfs/specfs/spec_vnops.c:124 #14 0xc023ef09 in ufs_vnoperatespec (ap=0xc94f4e08) at ../../ufs/ufs/ufs_vnops.c:2313 #15 0xc0197f20 in vn_ioctl (fp=0xc0d29100, com=3288352320, data=0xc0d59000 "read", p=0xc8af7180) at vnode_if.h:395 #16 0xc0176fcb in ioctl (p=0xc8af7180, uap=0xc94f4f80) at ../../sys/file.h:166 #17 0xc02724a6 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 5, tf_esi = -1077950456, tf_ebp = -1077949432, tf_isp = -917549100, tf_ebx = 5, tf_edx = 134794277, tf_ecx = -1077950407, tf_eax = 54, tf_trapno = 12, tf_err = 2, tf_eip = 134659084, tf_cs = 31, tf_eflags = 582, tf_esp = -1077950488, tf_ss = 47}) at ../../i386/i386/trap.c:1056 #18 0xc02654c6 in Xint0x80_syscall () #19 0x804cbc7 in ?? () #20 0x8048492 in ?? () #21 0x80482fd in ?? () #22 0x80480e9 in ?? () # vinum list Configuration summary Drives: 4 (8 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 4 (16 configured) D d0 State: up Device /dev/da0e Avail: 0/17366 MB (0%) D d1 State: up Device /dev/da1e Avail: 0/17366 MB (0%) D d2 State: up Device /dev/da2e Avail: 0/17366 MB (0%) D d3 State: up Device /dev/da3e Avail: 0/17366 MB (0%) V raid5 State: up Plexes: 1 Size: 50 GB P raid5.p0 R5 State: up Subdisks: 4 Size: 50 GB S raid5.p0.s0 State: up PO: 0 B Size: 16 GB S raid5.p0.s1 State: up PO: 512 kB Size: 16 GB S raid5.p0.s2 State: up PO: 1024 kB Size: 16 GB S raid5.p0.s3 State: up PO: 1536 kB Size: 16 GB ----- Disk info from dmesg ----- da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da3 at ahc0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da2 at ahc0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) -- Brad L. Chisholm SAS Institue, Inc. sasblc@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 14:48:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (Postfix) with ESMTP id 0AD3C15623; Fri, 24 Sep 1999 14:48:25 -0700 (PDT) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.1) with SMTP id VAA07272; Fri, 24 Sep 1999 21:47:26 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990924144331.00974220@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 24 Sep 1999 14:43:31 -0700 To: "Jonathan M. Bresler" From: "Kurt D. Zeilenga" Subject: Re: On hub.freebsd.org refusing to talk to dialups Cc: current@FreeBSD.ORG In-Reply-To: <19990924185001.DE27F15F54@hub.freebsd.org> References: <199909241600.JAA70710@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:50 AM 9/24/99 -0700, Jonathan M. Bresler wrote: > insert plug for the FreeBSDcon talk "Stopping Spam--Five Years >in the Trenches" by Jonathan M Bresler ;P But what about "Stopping chat on technical mailing lists..." by ?. :-) Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:11: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D479414CED for ; Fri, 24 Sep 1999 15:10:44 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA04159 for freebsd-current@freebsd.org; Sat, 25 Sep 1999 00:09:18 +0200 (CEST) (envelope-from olli) Date: Sat, 25 Sep 1999 00:09:18 +0200 (CEST) From: Oliver Fromme Message-Id: <199909242209.AAA04159@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Subject: Re: gcc optimizer in -current system ... Organization: Administration Heim 3 Reply-To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darryl Okahata wrote in list.freebsd-current: > "Zach N. Heilig" wrote: > > The application for the tests is mpg123. > > test mp3 playing time: 373 seconds. > [ ... ] > > 1) No Optimization > > 225.08 real 224.30 user 0.23 sys > [ ... ] > > 2) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns > > -fschedule-insns2 > > 141.92 real 141.43 user 0.10 sys > > What do these timings represent? As you say the mp3 playing time > is 373 seconds, but the "real" times vary, the timings don't appear to > be the playing/processing of the mp3 file. Probably something like this: time mpg123 -qt file.mp3 Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:12:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from cartman.fingerhut.com (cartman.fingerhut.com [204.221.45.4]) by hub.freebsd.org (Postfix) with ESMTP id 35FAB1510A for ; Fri, 24 Sep 1999 15:12:21 -0700 (PDT) (envelope-from Bruce.Albrecht@fingerhut.com) Received: from dtcbrg1.fingerhut.com (dtcbrg1.dtcbrg.fhut [151.210.147.35]) by cartman.fingerhut.com (8.9.1/8.9.1) with ESMTP id RAA24098; Fri, 24 Sep 1999 17:10:54 -0500 (CDT) Received: from seag.fingerhut.com (GF007E0.SEAG.fingerhut.com [151.210.140.7]) by dtcbrg1.fingerhut.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id TR8LY131; Fri, 24 Sep 1999 17:10:58 -0500 Received: from gf003e0.fingerhut.com. by seag.fingerhut.com (8.8.8+Sun/SMI-SVR4) id RAA04671; Fri, 24 Sep 1999 17:10:51 -0500 (CDT) Received: (from w246@localhost) by gf003e0.fingerhut.com. (8.8.8+Sun/8.8.8) id RAA04137; Fri, 24 Sep 1999 17:10:49 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14315.63209.521223.907830@fingerhut.com> Date: Fri, 24 Sep 1999 17:10:49 -0500 (CDT) To: Ben Smithurst Cc: current@FreeBSD.ORG Subject: Re: Why do FreeBSD mailing lists ignore MX preference? In-Reply-To: <19990924183641.A30415@lithium.scientia.demon.co.uk> References: <199909241014.MAA91015@gratis.grondar.za> <14315.35085.935406.940824@celery.zuhause.org> <19990924183641.A30415@lithium.scientia.demon.co.uk> X-Mailer: VM 6.71 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst writes: > Bruce Albrecht wrote: > > > Non-authoritative answer: > > zuhause.mn.org preference = 150, mail exchanger = minuet.skypoint.net > > zuhause.mn.org preference = 100, mail exchanger = 205.215.217.178 > > "205.215.217.178." almost certainly does not have an address (A) > record. Mail exchangers must be host names, not IP addresses. Unfortunately, I don't have control over the MX record. When I asked them to change it to my new static IP I gave them a valid PTR address (FQDN) and the new static IP, and they used the static IP instead of the FQDN. I've asked them to correct it, now that I know that it's wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:20:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 04D301510A for ; Fri, 24 Sep 1999 15:20:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA23961 for ; Fri, 24 Sep 1999 15:18:17 -0700 Date: Fri, 24 Sep 1999 15:19:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: DDB && SMP? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just ran across this: Debugger("isp_attach") Stopped at Debugger+0x37: movl $0,in_Debugger db> cont whoa, other_cpus: 0x00000002, stopped_cpus: 0x00000000 panic: stop_cpus() failed mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 Automatic reboot in 15 seconds - press a key on the console to abort Whuffo? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:24:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 741011513E for ; Fri, 24 Sep 1999 15:24:30 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA19995; Sat, 25 Sep 1999 00:07:55 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03005; Fri, 24 Sep 1999 22:59:37 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909242059.WAA03005@yedi.iaf.nl> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> from Gary Schrock at "Sep 24, 1999 1:10:56 pm" To: gary@eyelab.psy.msu.edu (Gary Schrock) Date: Fri, 24 Sep 1999 22:59:37 +0200 (CEST) Cc: freebsd@gndrsh.dnsmgr.net, current@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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Gary Schrock wrote ... > At 03:00 AM 9/24/1999 -0700, you wrote: > >Another thing that ISP coulds start doing (we are in process with > >this now, but on a monitoring only basis, instead of a deny we > >just log them) is to block all outbound from AS tcp 25 setup packets. > > Hmm, maybe I'm interpreting this wrong (I hope so), but I interpret this as > saying that basically you'd only be able to mail things through your local > isp's mailhost. It means that if you use several different mail servers, > all mail would still have to go through the local isp's. Personally, I > would immediately unsubscribe to any isp that decided this was acceptable > behavior on their part. I use the mail server at work for all my outgoing > mail. Why? Because the machine is lightly loaded and I don't have to So, the mailserver at your workplace is an open relay? > worry about my mail getting lost in the depths of my isp's mail server for > a couple hours because their loads tend to run high. (Hell, I don't > generally even use the email account provided by the local isp because of > load issues, my work account is so much more reliable). I'd call this the ultimate reason to get another ISP. Not the relaying stuff. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:30: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 76A221513E for ; Fri, 24 Sep 1999 15:29:44 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA04813 for freebsd-current@FreeBSD.ORG; Sat, 25 Sep 1999 00:29:07 +0200 (CEST) (envelope-from olli) Date: Sat, 25 Sep 1999 00:29:07 +0200 (CEST) From: Oliver Fromme Message-Id: <199909242229.AAA04813@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: ccd build failure Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote in list.freebsd-current: > In message <19990923175400.M10357@futuresouth.com> "Matthew D. Fuller" writes: > : OK: > : #!/bin/sh > : (cvs status | grep '^File:' | grep -v 'Status: Up-to-date$') 2> /dev/null > ^^ -q Hm, that variant does not display the directory names at all. I'd like to propose the following variant. It's a bit longer than my first proposal, but just as efficient (maybe even more efficient, because it doesn't have to fork two greps). #!/bin/sh - cvs status 2>&1 \ | awk '/^File/ && ! /Status: Up-to-date$/ { $1 = dir "/" $2; $2 = ""; print; } /cvs server: Examining/ { dir = $4; }' Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:39:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 5D96414FAF; Fri, 24 Sep 1999 15:39:22 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id SAA14340; Fri, 24 Sep 1999 18:37:03 -0400 (EDT) Date: Fri, 24 Sep 1999 18:37:02 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Mark Murray Cc: "Rodney W. Grimes" , Joe Abley , current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241014.MAA91015@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I totally agree with this, while it doesn;t stop all spam (and some has to be added manually to my own lists) I've dramatically cut down on spam to my machines. DUL, while I'm not sure whether we should take this to -chat or not since we are now getting into noise on the -current list, is also a good thing. simply because noone on a dialup has reason to be sending mail directly to me, they should be sending it through thier ISP's mail servers. overall MAPS is the best thing to come along for spam control since ...I don;t know when. They aren;t as "strict" as ORB and Paul Vixie's attitude towa5rds it has been excellent. Its much easier to get off RBL than it is ORB, especially if you are on it by mistake, like a friend of mine was. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Fri, 24 Sep 1999, Mark Murray wrote: > > Do you know about the RBL? How do you feel about it? We are using > > it via DNS and BGP on a test basis right now. I have had legitimate > > important mail blocked at Freebsd.org due to the source being on the > > RBL, but that is a price I am willing to pay. > > The RBL is great! There is a teensy bit of colateral damage, but not > so much that I worry about it. Here in ZA, our USP traffic provider > (Teleglobe) uses RBL, thus absolving us of the responsibility. Since > we started getting this "cleanfeed", spam has dropped dramatically. > > What I particularly enjoy about the RBL is its strong sense of the > need to listen to its client base, and to adapt as necessary. Paul > Vixie has a high degree of respect, as a consequence. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 15:51:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 4F3F714CFE for ; Fri, 24 Sep 1999 15:51:23 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id SAA14439; Fri, 24 Sep 1999 18:50:07 -0400 (EDT) Date: Fri, 24 Sep 1999 18:50:07 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: "Rodney W. Grimes" Cc: David Wolfskill , current@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909241622.JAA02805@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you use sendmail, this is pretty trivial, its a slight modification to the original RBL check : # DNS based IP address spam lists R$* $: $&{client_addr} R$-.$-.$-.$- $: $(host $4.$3.$2.$1.rbl.maps.vix.com. $: $1.$2.$3.$4 $) R$-.$-.$-.$- $: $(host $4.$3.$2.$1.dul.maps.vix.com. $: OK $) ROK $@ OK R$+ $#error $@ 5.7.1 $: "Mail from " $&{client_addr} " refused by blackhole site rbl.maps.vix.com or dul.maps.vix.com" the last three lines in my email are one line though ;) this is in the rule : check_relay in Ruleset 98 essentially after checking the one, if it passes the first (RBL) it then checks it vs. the second (DUL) if it actually gets an address back... it rejects the mail, with the message. ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Fri, 24 Sep 1999, Rodney W. Grimes wrote: > > >From: "Rodney W. Grimes" > > >Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT) > > > > >Another thing that ISP coulds start doing (we are in process with > > >this now, but on a monitoring only basis, instead of a deny we > > >just log them) is to block all outbound from AS tcp 25 setup packets. > > > > Not quite sure I follow this. > > ipfw add 10250 allow tcp from ${smtpsmarthost} to any 25 setup out via lnc1 > ipfw add 10259 allow log tcp from any to any 25 setup out via lnc1 > > This is placed on all AS border routers, anyone attempting to > do direct port 25 outbound from our AS trips 10259 and gets to talk > to me about what it is they are doing. > > The comptete rules set is a fair bit more complicated than the above > as we are also a transit AS and I have to allow the port 25 setup traffic > from them to work correctly, so I can't just go make 10259 a deny at > this time. > > > > >This prevents your customers from being something that could get you > > >on the RBL or the DUL MAP for bad behavior, it also inforces the use > > >of your smart host relay, as it/they is/are the only way to get a > > >tcp port 25 setup completed. > > > > About the only positive thing I have to say about the DUL is that Vix > > stated that entries are placed on it at the request of the custodians of > > the netblock in question. > > If that is the case then this is ideal. Everyone should be using the > DUL, as the maintainer of that IP space has specifically stated that > they do not want or allow smtp setup connections from that IP space. > > Thus by using the DUL you are simply helping a costodian implement > the policy they have already layed down. > > > > > >Do you know about the RBL? How do you feel about it? We are using > > >it via DNS and BGP on a test basis right now. I have had legitimate > > >important mail blocked at Freebsd.org due to the source being on the > > >RBL, but that is a price I am willing to pay. > > > > I'm far more comfortable with the use of the RBL than the DUL. > > Given what you stated above I don't see how you could favor the > RBL over the DUL, the DUL is stated administrative policy, the RBL > is a reactive to bad behavior and in opposition to stated administrative > policy for almost every entry in it. > > > Indeed, my externally-visible home SMTP server uses the RBL (but not the > > DUL). > > You should probably run both.... I know I am going to go see what it > takes to intergrate DUL into our current scheme of things. And submit > our IP dial up blocks for inclusion in the list. > > -- > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 16:46:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id D2D9B14D5A for ; Fri, 24 Sep 1999 16:46:36 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id BAA38564; Sat, 25 Sep 1999 01:45:44 +0200 (CEST) Message-Id: <199909242345.BAA38564@midten.fast.no> To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: DDB && SMP? From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 24 Sep 1999 15:19:58 -0700 (PDT)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Sat_Sep_25_01:45:29_1999)--" Content-Transfer-Encoding: 7bit Date: Sat, 25 Sep 1999 01:45:43 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Sat_Sep_25_01:45:29_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > I just ran across this: > > Debugger("isp_attach") > Stopped at Debugger+0x37: movl $0,in_Debugger > db> cont > whoa, other_cpus: 0x00000002, stopped_cpus: 0x00000000 > panic: stop_cpus() failed > mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 > Automatic reboot in 15 seconds - press a key on the console to abort > > > Whuffo? The kernel probably entered the debugger after the AP had been started but before it accepts any interrupts. - Tor Egge ----Next_Part(Sat_Sep_25_01:45:29_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/i386/i386/db_interface.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/db_interface.c,v retrieving revision 1.46 diff -u -r1.46 db_interface.c --- db_interface.c 1999/08/28 00:43:42 1.46 +++ db_interface.c 1999/09/24 23:43:34 @@ -167,7 +167,7 @@ #endif /* VERBOSE_CPUSTOP_ON_DDBBREAK */ /* Restart all the CPUs we previously stopped */ - if (stopped_cpus != other_cpus) { + if (stopped_cpus != other_cpus && smp_started != 0) { db_printf("whoa, other_cpus: 0x%08x, stopped_cpus: 0x%08x\n", other_cpus, stopped_cpus); panic("stop_cpus() failed"); Index: sys/i386/include/smp.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/smp.h,v retrieving revision 1.47 diff -u -r1.47 smp.h --- smp.h 1999/08/28 00:44:25 1.47 +++ smp.h 1999/09/24 23:39:47 @@ -177,6 +177,7 @@ /* global data in init_smp.c */ extern int invltlb_ok; extern int smp_active; +extern int smp_started; extern volatile int smp_idle_loops; #endif /* !LOCORE */ ----Next_Part(Sat_Sep_25_01:45:29_1999)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 17:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id BC77114ED8 for ; Fri, 24 Sep 1999 17:12:33 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id RAA40771 for ; Fri, 24 Sep 1999 17:11:20 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37EC1328.AFC8F0AB@MexComUSA.net> Date: Sat, 25 Sep 1999 00:11:20 +0000 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: XFree86-3.3.5/kde-1.1.2/Current today. Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This morning I made world, updated XFree86 and kde, which didnŽt seem to be a problem until I started X and nowI get revers Icon's - silhouettes on the kde background. I get no text but a block where the text is and the mouse will often change to a block. I have never seen anything like it. I have recompiled X-11 3 times and kde twice. I have erased the .kde, .kderc, .klogin, Desktop each time. I have no idea where to look. It was fine yesterday with XFree86-3.3.4 and kde-1.1.1. Also tried twm and same problem so I can assume the it isnŽt kde but .. . Does the same at -bpp 8/16/24/32 and 640x, 800x y 1024x. The video card is a sis-6326 8MB and am running the SVGA server. Thanks in advance or any suggestions. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 18:10:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 54EFA15070 for ; Fri, 24 Sep 1999 18:10:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA66405; Sat, 25 Sep 1999 10:40:24 +0930 (CST) Date: Sat, 25 Sep 1999 10:40:24 +0930 From: Greg Lehey To: Brad Chisholm Cc: freebsd-current@FreeBSD.ORG Subject: Re: System crash on "vinum start" Message-ID: <19990925104024.B54407@freebie.lemis.com> References: <199909242036.QAA36690@concours.pc.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199909242036.QAA36690@concours.pc.sas.com>; from Brad Chisholm on Fri, Sep 24, 1999 at 04:36:54PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 24 September 1999 at 16:36:54 -0400, Brad Chisholm wrote: > I'm having a problem where the "vinum start" command crashes my system. > This happens regardless of whether it's being issued during bootup via > /etc/rc or from the command line on a running system. > > Interestingly, however, if I issue the start command from the vinum > interactive prompt, it works properly with no crash. > > I'm currently running on a snap built this morning (0924), but it was > also happening on a snap from 0914. > > Crash info, vinum config, and disk info are below. Let me know if I > can provide any additional information. Yes. Please read the instructions in vinum(4) about debugging panic dumps. I found a minor bug in 'vinum start' recently, but I doubt it's causing your problem. I'll commit it Real Soon Now. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 19:24:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6EDAC14C9D for ; Fri, 24 Sep 1999 19:24:42 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA19353; Fri, 24 Sep 1999 19:24:37 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA81082; Fri, 24 Sep 1999 19:24:36 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 24 Sep 1999 19:24:36 -0700 (PDT) Message-Id: <199909250224.TAA81082@vashon.polstra.com> To: lynch@bsdunix.net Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Pat Lynch wrote: > If you use sendmail, this is pretty trivial, its a slight modification to > the original RBL check : There's a nice patch for the sendmail 8.9.3 that allows you to specify multiple blacklists easily (e.g., both RBL and DUL). You'll find it here: http://www.sendmail.org/~ca/email/chk-89n.html John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 19:32:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id A893D14BB8 for ; Fri, 24 Sep 1999 19:32:09 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id WAA14699; Fri, 24 Sep 1999 22:35:46 -0400 (EDT) Date: Fri, 24 Sep 1999 22:35:46 -0400 (EDT) From: Ben Rosengart To: "Rodney W. Grimes" Cc: Jacques Vidrine , current@FreeBSD.ORG Subject: Re: Filtering port 25 (was Re: On hub.freebsd.org refusing to talk to dialups) In-Reply-To: <199909241637.JAA02838@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I understand the ISP's POV here, but I have legitimate reasons to telnet to port 25 on various machines (most of them administered by me), and I'd never dream of using an ISP that would stop me from doing so. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 20:52:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ppp136-220.cpis.net [206.155.220.165]) by hub.freebsd.org (Postfix) with ESMTP id 245F514BFC for ; Fri, 24 Sep 1999 20:52:29 -0700 (PDT) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.by-tor.tacorp.net (8.9.3/8.9.3) id XAA00402; Fri, 24 Sep 1999 23:52:26 -0400 (EDT) (envelope-from by-tor) Date: Fri, 24 Sep 1999 23:52:26 -0400 (EDT) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: freebsd-current@freebsd.org Subject: pcm oddity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed a little quirk in the pcm driver -- it is reversing the channels in my sb16! The first couple times I play a certain mp3 that starts out (normally) in the left channel, it plays correctly in the left channel. Then suddenly it will switch, and start out in the right channel. The mixer still works properly, just the DSP (I think anynway) seems to be reversing the channels somewhere internally. It's odd, to say the least. My kernel is -current as of late sept 22. Can anyone else duplicate this? WM -- The difference between genius and stupidity is that genius has its limits. Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 21:14:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 120D414BC6 for ; Fri, 24 Sep 1999 21:14:50 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA17110 for ; Sat, 25 Sep 1999 00:15:13 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199909250415.AAA17110@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199909242229.AAA04813@dorifer.heim3.tu-clausthal.de> Date: Sat, 25 Sep 1999 00:15:13 -0400 (EDT) From: John Baldwin To: freebsd-current@FreeBSD.ORG Subject: Quick 'n' Dirty CVS Status Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [subject updated] On 24-Sep-99 Oliver Fromme wrote: > Hm, that variant does not display the directory names at all. > I'd like to propose the following variant. It's a bit longer > than my first proposal, but just as efficient (maybe even more > efficient, because it doesn't have to fork two greps). > Regards > Oliver If you can grok the flags that 'cvs update' uses.. 'cvs -qn update' is a lot less to type in, and it doesn't have to fork any children outside of cvs. :) --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 21:16:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id A42EB14BC6 for ; Fri, 24 Sep 1999 21:16:35 -0700 (PDT) (envelope-from gary@eyelab.psy.msu.edu) Received: from piper (dyn1-tnt15-75.detroit.mi.ameritech.net [199.179.190.75]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id AAA35916; Sat, 25 Sep 1999 00:16:26 -0400 (EDT) (envelope-from gary@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990924235048.00a4b330@eyelab.msu.edu> X-Sender: gary@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 25 Sep 1999 00:09:29 -0400 To: Wilko Bulte From: Gary Schrock Subject: Re: On hub.freebsd.org refusing to talk to dialups Cc: freebsd@gndrsh.dnsmgr.net, current@FreeBSD.ORG In-Reply-To: <199909242059.WAA03005@yedi.iaf.nl> References: <4.2.0.58.19990924130644.00a84dd0@eyelab.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:59 PM 9/24/99 +0200, Wilko Bulte wrote: >As Gary Schrock wrote ... > > all mail would still have to go through the local isp's. Personally, I > > would immediately unsubscribe to any isp that decided this was acceptable > > behavior on their part. I use the mail server at work for all my outgoing > > mail. Why? Because the machine is lightly loaded and I don't have to > >So, the mailserver at your workplace is an open relay? No, it's definitely not. I've been using a pop before relay scheme that's been working fairly nicely. (Although occaisionally the server gets stuck in a state where it decides it doesn't recognize my pop check and refuses to relay my mail anyways). Back before sendmail started doing relay checking by default, I got hit with a spammer relay that so swamped the server it was immediately noticeable because nothing else was working. I've been very careful ever since then to make sure servers I'm responsible for don't leave relaying open. (As a defense, this was back when this was something that was still relatively new, and there wasn't a whole lot in the way of information about preventing relaying. These day's it's a lot easier to fix that problem). > > worry about my mail getting lost in the depths of my isp's mail server for > > a couple hours because their loads tend to run high. (Hell, I don't > > generally even use the email account provided by the local isp because of > > load issues, my work account is so much more reliable). > >I'd call this the ultimate reason to get another ISP. Not the relaying >stuff. Why? The last thing I need is another email account, so I don't even *use* the email stuff from my isp. For everything besides occaisional issues with the load on their mail servers my isp is pretty good. However, for me it makes a lot more sense to use hte mail server at work, simply because that's a machine that's got few users, and I get the instant gratification of my mail going out immediately. For what it's worth, to clarify my viewpoint on this issue, I don't really object to the DUL, and quite honestly, after reading the information about it, I might even consider enabling it. It's not something that will affect my mail, because I *do* send the mail through a legit mail server. My objection is with the idea that an ISP would block my ability to use my mail host at work by blocking outside access through port 25. Why should my mail take an hour or two to filter through the local isp when it can go immediately through work? (And for the argument choose an isp that has a better mail relayer, that's not always practical. Say you're using adsl or cable modem, where you might not really have a choice on the isp, are you really going to give up the faster connection because a mail relay you don't use happens to be slow? I sure as hell wouldn't). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 21:25:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id D2F7414BC6 for ; Fri, 24 Sep 1999 21:25:05 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id XAA23875; Fri, 24 Sep 1999 23:29:07 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990925002425.00a667e8@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 25 Sep 1999 00:24:25 -0400 To: Edwin Culp From: Tom Embt Subject: Re: XFree86-3.3.5/kde-1.1.2/Current today. Cc: freebsd-current@freebsd.org In-Reply-To: <37EC1328.AFC8F0AB@MexComUSA.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:11 AM 9/25/99 +0000, you wrote: >This morning I made world, updated XFree86 and kde, which didn=B4t seem to >be a problem until I started X and nowI get revers Icon's - silhouettes >on the kde background. I get no text but a block where the text is and >the mouse will often change to a block. I have never seen anything like >it. I have recompiled X-11 3 times and kde twice. I have erased the >.kde, .kderc, .klogin, Desktop each time. I have no idea where to >look. It was fine yesterday with XFree86-3.3.4 and kde-1.1.1. Also >tried twm and same problem so I can assume the it isn=B4t kde but .. . >Does the same at -bpp 8/16/24/32 and 640x, 800x y 1024x. > >The video card is a sis-6326 8MB and am running the SVGA server. > >Thanks in advance or any suggestions. > >ed > IIRC someone changed something in KDE recently to make icons work on big Endian machines, perhaps they botched it. If I'm not imagining this, you could probably find it on www.kde.org. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 21:53:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id 8569914E11 for ; Fri, 24 Sep 1999 21:53:55 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id VAA41521; Fri, 24 Sep 1999 21:53:42 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37EC5556.CC08C48C@MexComUSA.net> Date: Sat, 25 Sep 1999 04:53:43 +0000 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Embt Cc: freebsd-current@freebsd.org Subject: Re: XFree86-3.3.5/kde-1.1.2/Current today. References: <3.0.3.32.19990925002425.00a667e8@mail.embt.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom, Thank you very much. I feel like an idiot, for not having contemplated the possibility of the problem being the driver for the sis6326. After erasing everything that might have anything to do with X11 or Window managers or libraries, I decided as a last resort to substitute the SiS-6326 that worked flawlessly on 3.3.4. I changed it for a Matrox G200 and ran xf86config and it worked perfectly with no other changes and everything else the same. Looks like the SiS-6326 has a strange problem with XFree86-3.3.5. IŽll try some Options, in the XF86Config file tomorrow and then report it to XFree86.org. Does anyone else have one of these running with 3.3.5? Thanks again, ed Tom Embt wrote: > At 12:11 AM 9/25/99 +0000, you wrote: > >This morning I made world, updated XFree86 and kde, which didnŽt seem to > >be a problem until I started X and nowI get revers Icon's - silhouettes > >on the kde background. I get no text but a block where the text is and > >the mouse will often change to a block. I have never seen anything like > >it. I have recompiled X-11 3 times and kde twice. I have erased the > >.kde, .kderc, .klogin, Desktop each time. I have no idea where to > >look. It was fine yesterday with XFree86-3.3.4 and kde-1.1.1. Also > >tried twm and same problem so I can assume the it isnŽt kde but .. . > >Does the same at -bpp 8/16/24/32 and 640x, 800x y 1024x. > > > >The video card is a sis-6326 8MB and am running the SVGA server. > > > >Thanks in advance or any suggestions. > > > >ed > > > > IIRC someone changed something in KDE recently to make icons work on big > Endian machines, perhaps they botched it. If I'm not imagining this, you > could probably find it on www.kde.org. > > Tom Embt > tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 21:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from thequest.net (tnt094.thequest.net [205.198.52.221]) by hub.freebsd.org (Postfix) with ESMTP id AE59C15411 for ; Fri, 24 Sep 1999 21:54:03 -0700 (PDT) (envelope-from znh@thequest.net) Received: by thequest.net (Postfix, from userid 1005) id 4A5A420D4; Sat, 25 Sep 1999 04:36:43 +0000 (GMT) Date: Fri, 24 Sep 1999 23:36:43 -0500 From: "Zach N. Heilig" To: Darryl Okahata Cc: "Zach N. Heilig" , freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Message-ID: <19990924233643.A17222@murkwood.znh.org> References: <19990924082958.A14943@murkwood.znh.org> <199909241543.IAA26573@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199909241543.IAA26573@mina.sr.hp.com>; from Darryl Okahata on Fri, Sep 24, 1999 at 08:43:37AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 24, 1999 at 08:43:37AM -0700, Darryl Okahata wrote: > "Zach N. Heilig" wrote: > > > The application for the tests is mpg123. > > test mp3 playing time: 373 seconds. > [ ... ] > > 1) No Optimization > > 225.08 real 224.30 user 0.23 sys > [ ... ] > > 2) -O3 -mcpu=i486 -march=i486 -fomit-frame-pointer -fschedule-insns > > -fschedule-insns2 > > 141.92 real 141.43 user 0.10 sys > > What do these timings represent? As you say the mp3 playing time > is 373 seconds, but the "real" times vary, the timings don't appear to > be the playing/processing of the mp3 file. Oops, it is 'mpg123 -t' (decode, but don't do any output -- it doesn't go to sleep waiting for /dev/dsp, so it runs as fast as it can). -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 24 23:51:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 2EF281509F; Fri, 24 Sep 1999 23:50:57 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA97143; Sat, 25 Sep 1999 08:50:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909250650.IAA97143@gratis.grondar.za> To: Pat Lynch Cc: "Rodney W. Grimes" , Joe Abley , current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups Date: Sat, 25 Sep 1999 08:50:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DUL, while I'm not sure whether we should take this to -chat or not since > we are now getting into noise on the -current list, is also a good thing. > simply because noone on a dialup has reason to be sending mail directly to > me, they should be sending it through thier ISP's mail servers. There is a list called SPAM-L, where this is all on-topic. There is a lot of flamage, but the content is filterable. Askme if you want to get on... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 0:40:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop2.tky.3web.ne.jp (pop2.tky.3web.ne.jp [202.235.209.39]) by hub.freebsd.org (Postfix) with ESMTP id 5233C14EAC for ; Sat, 25 Sep 1999 00:40:16 -0700 (PDT) (envelope-from info@hypno-college.com) Received: from mx2.tky2.3web.ne.jp (tkyd017.tky.3web.ne.jp [202.235.213.17]) by pop2.tky.3web.ne.jp (8.8.8+2.7Wbeta7/3.7W-99073118) with SMTP id QAA21335 for ; Sat, 25 Sep 1999 16:40:15 +0900 (JST) Date: Sat, 25 Sep 1999 16:40:15 +0900 (JST) Message-Id: <199909250740.QAA21335@pop2.tky.3web.ne.jp> From: =?ISO-2022-JP?B??= To: =?ISO-2022-JP?B??= X-Mailer: Direct Email v0.22 Subject: =?ISO-2022-JP?B?GyRCM1okNyQvM1gkWSRrOkVMMj1ROVY6Qj5SMnAkNyReJDkbKEI=?= Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B:EL2=Q9V=,2q$N$*CN$i$;(B $BFMA3$N%a!<%kBgJQ<:Ni$$$?$7$^$9!#$4ITMW$N>l9g$O!"$*?M$NFyBN$H@:?@$r%3%s%H%m!<%k$9$k!"$9$P$i$7$$(B $BFC&Gd$bNx0&$b@.8y=PMh$k$h$&$K$J$j$^$9!#(B $B;d6&$NAO;O&Gd$G6l$7$s$G$$$kJ}!"(B $B?M4V4X78$GG:$s$G$$$kJ}!"(B $B$<$R$3$N9V=,2q$r\$7$$;qNA$44uK>$NJ}$O%a!<%k$GO"Mm2<$5$$!#(B $B9-Js78(B/ $B0f>e!!H~5*(B e-mail: info@hypno-college.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 2:58:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from Wit389306.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 8D9FD14E81 for ; Sat, 25 Sep 1999 02:58:22 -0700 (PDT) (envelope-from djb@Wit389306.student.utwente.nl) Received: (from djb@localhost) by Wit389306.student.utwente.nl (8.9.3/8.9.3) id LAA54399; Sat, 25 Sep 1999 11:58:33 +0200 (CEST) (envelope-from djb) Date: Sat, 25 Sep 1999 11:58:33 +0200 From: "Dave J. Boers" To: morganw@engr.sc.edu Cc: freebsd-current@freebsd.org Subject: Re: pcm oddity Message-ID: <19990925115833.A54296@relativity.student.utwente.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 24, 1999 at 11:52:26PM -0400, Wes Morgan wrote: > I noticed a little quirk in the pcm driver -- it is reversing the channels > in my sb16! The first couple times I play a certain mp3 that starts out > (normally) in the left channel, it plays correctly in the left channel. > Then suddenly it will switch, and start out in the right channel. > My kernel is -current as of late sept 22. Can anyone else duplicate this? Hi, I can reproduce your findings. I run regular buildworld every few days. I have been having this problem for at least two weeks (and possibly before, I have been away for a few months and was stuck with Irix). An easy way to reproduce the problem is to start x11amp and hit play several times. I also found several other "quirks" in the pcm driver while I was programming: 1. If I read() from /dev/dsp in 16 bits single channel mode, I get rubbish even if the mic and igain mixers are set to zero. If I read some 8 bits single channel data just before you read the 16 bits data, the problem disappears. Seems to be an initialization problem. 2. Reading large blocks from /dev/dsp (like 8192 bytes), generates a kernel panic (uiomove failed). Cutting down the blocksize to 256 bytes appears to solve the problem. Maybe something overflowing or a timing problem. 3. If I change the mixer setttings using ioctl() calls for /dev/dsp, then the settings for /dev/mixer do not change accordingly. I have an original Sb16 PnP. I am running smp for dual celeron on an Abit mainboard. Maybe someone wants to look into this, as I don't have any device driver programming experience (and little time to learn also). Best wishes, Dave. -- Dave J. Boers djb@relativity.student.utwente.nl I will *NOT* read email sent to Graduate student of Theoretical Physics d.j.boers@student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 3:26:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 58C3D14D1D for ; Sat, 25 Sep 1999 03:26:15 -0700 (PDT) (envelope-from john@nlc.net.au) Received: (qmail 12615 invoked from network); 25 Sep 1999 20:26:14 +1000 Received: from pacer.nlc.net.au (HELO pacer) (203.24.133.16) by nhj.nlc.net.au with SMTP; 25 Sep 1999 20:26:14 +1000 Message-ID: <005e01bf0740$4c505e20$31d7fea9@pacer> From: "John Saunders" To: "Bill Fumerola" , "Rodney W. Grimes" Cc: "FreeBSD current" References: Subject: Re: Automating filesystem check at boot time Date: Sat, 25 Sep 1999 20:25:31 +1000 Organization: NORTHLINK COMMUNICATIONS 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 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Thu, 23 Sep 1999, Rodney W. Grimes wrote: > > > You need to find and fix what ever it is that is not dieing when being > > told to die. Your work around is a bandaid that only hides the real > > problem, which is probably a bug some place in something. amd and NFS > > are good first conidates. Just what process does it complain that it > > is unable to kill, or does it just say could not kill? > > Vinum is usually the culprit for me, though I haven't built a world > on most of these machines for a while, so this may be fixed. I would have to agree with that. I had a machine with a vinum striped volume and went back to ccd because a remote reboot had a 0% chance of correctly rebooting. Needless to say my chances now are not 100% but considerably higher than 0%. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 04-1822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 4:38:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 722A414F1F for ; Sat, 25 Sep 1999 04:38:40 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id HAA27575 for ; Sat, 25 Sep 1999 07:37:51 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 25 Sep 1999 07:37:51 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: wierd message Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what does this message mean? Sep 24 18:34:04 culverk /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt I've been getting it alot since I reinstalled -current, it never used to happen before. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 5:34:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 798BD14CE6 for ; Sat, 25 Sep 1999 05:34:27 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Sep 1999 13:34:27 +0100 (BST) To: Edwin Culp Cc: freebsd-current@freebsd.org Subject: Re: XFree86-3.3.5/kde-1.1.2/Current today. In-reply-to: Your message of "Sat, 25 Sep 1999 04:53:43 -0000." <37EC5556.CC08C48C@MexComUSA.net> Date: Sat, 25 Sep 1999 13:34:26 +0100 From: Ian Dowse Message-ID: <199909251334.aa50291@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37EC5556.CC08C48C@MexComUSA.net>, Edwin Culp writes: > >libraries, I decided as a last resort to substitute the SiS-6326 that worked >flawlessly on 3.3.4. I changed it for a Matrox G200 and ran xf86config and >it worked perfectly with no other changes and everything else the same. >Looks like the SiS-6326 has a strange problem with XFree86-3.3.5. IŽll try >some Options, in the XF86Config file tomorrow and then report it to >XFree86.org. Does anyone else have one of these running with 3.3.5? I had what sound like similar problems with a SiS card (sorry, I don't have the model number handy right now) and 3.3.5 on 3.3-STABLE the other day - solid black patches where fonts etc should be. Turning on the option "no_bitblt" did the trick, but you really notice the speed reduction. I just sent back the card and got an ATI Rage Pro instead - I'd never used SiS cards before so I assumed they weren't properly supported by the XFree people. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 5:50:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (Postfix) with ESMTP id D827914FA6 for ; Sat, 25 Sep 1999 05:50:28 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.net (8.9.3/8.9.3) with ESMTP id FAA01224; Sat, 25 Sep 1999 05:50:23 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <37ECC510.BB1CA956@MexComUSA.net> Date: Sat, 25 Sep 1999 12:50:24 +0000 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: freebsd-current@freebsd.org Subject: Re: XFree86-3.3.5/kde-1.1.2/Current today. References: <199909251334.aa50291@salmon.maths.tcd.ie> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you Ian. I had no problem with it in 3.3.4 and I donŽt remember what configuration I had but it didnŽt work with 3.3.5. From your description the problem is the same. IŽm going to play with the card today, but will probably follow your example. IŽver already spent too much time with this. Have a great weekend, ed Ian Dowse wrote: > In message <37EC5556.CC08C48C@MexComUSA.net>, Edwin Culp writes: > > > >libraries, I decided as a last resort to substitute the SiS-6326 that worked > >flawlessly on 3.3.4. I changed it for a Matrox G200 and ran xf86config and > >it worked perfectly with no other changes and everything else the same. > >Looks like the SiS-6326 has a strange problem with XFree86-3.3.5. IŽll try > >some Options, in the XF86Config file tomorrow and then report it to > >XFree86.org. Does anyone else have one of these running with 3.3.5? > > I had what sound like similar problems with a SiS card (sorry, I don't > have the model number handy right now) and 3.3.5 on 3.3-STABLE the other > day - solid black patches where fonts etc should be. Turning on the > option "no_bitblt" did the trick, but you really notice the speed reduction. > > I just sent back the card and got an ATI Rage Pro instead - I'd never > used SiS cards before so I assumed they weren't properly supported by > the XFree people. > > Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 6:11:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7559614CE6 for ; Sat, 25 Sep 1999 06:11:36 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id PAA16335; Sat, 25 Sep 1999 15:07:53 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id PAA20711; Sat, 25 Sep 1999 15:12:04 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id PAA77732; Sat, 25 Sep 1999 15:11:51 +0200 (CEST) (envelope-from ticso) Date: Sat, 25 Sep 1999 15:11:51 +0200 From: Bernd Walter To: Brad Chisholm Cc: freebsd-current@FreeBSD.ORG Subject: Re: System crash on "vinum start" Message-ID: <19990925151151.A77698@cicely8.cicely.de> References: <199909242036.QAA36690@concours.pc.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199909242036.QAA36690@concours.pc.sas.com>; from Brad Chisholm on Fri, Sep 24, 1999 at 04:36:54PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 24, 1999 at 04:36:54PM -0400, Brad Chisholm wrote: > > D d0 State: up Device /dev/da0e Avail: 0/17366 MB (0%) > D d1 State: up Device /dev/da1e Avail: 0/17366 MB (0%) > D d2 State: up Device /dev/da2e Avail: 0/17366 MB (0%) > D d3 State: up Device /dev/da3e Avail: 0/17366 MB (0%) > > da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) > da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) > da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) > da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) > What disk are you booting from? Does it only happen on start or do you have problems using read too? I have one host on which I don't use start, because one removeable drive (SyQuest SQ5200) missbehaves reading while there is no media inserted - but it does not panic the host - it only was trying to read from it longer than my finger needed to reach reset... -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 6:32:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 12C59157AD; Sat, 25 Sep 1999 06:32:03 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk ([192.168.0.3] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.032 #1) id 11Uqzz-000BFd-00; Sat, 25 Sep 1999 13:32:19 +0100 Received: (from ben) by lithium.scientia.demon.co.uk (Exim 3.032 #1) id 11Uqzw-0009BR-00; Sat, 25 Sep 1999 13:32:16 +0100 Date: Sat, 25 Sep 1999 13:32:16 +0100 From: Ben Smithurst To: Pat Lynch Cc: current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups Message-ID: <19990925133215.A35268@lithium.scientia.demon.co.uk> References: <199909241014.MAA91015@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ CC list trimmed ] Pat Lynch wrote: > DUL, while I'm not sure whether we should take this to -chat or not since > we are now getting into noise on the -current list, is also a good thing. > simply because noone on a dialup has reason to be sending mail directly to > me, they should be sending it through thier ISP's mail servers. There are reasons not to use an ISP's smarthost. First, I have no idea how long my mail will stay there. Second, if my mail can't be delivered to the other end immediately, I'd rather be able to find out why by checking my logs. Third, my ISP's smarthost has occasionally been blacklisted by ORBS because it relays mail for its customers, some of whom are running open relays. (This is a completely ridiculous action on ORBS' part, IMO, but that's a discussion for somewhere else.) So far at least, I have never had any problems sending mail from my dialup (which has a static IP address -- I think static IP dialups are exempt from many dialup blocking lists), and I hope this will continue. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 6:44:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 3A7F914C99; Sat, 25 Sep 1999 06:44:32 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id JAA20703; Sat, 25 Sep 1999 09:44:28 -0400 (EDT) Date: Sat, 25 Sep 1999 09:44:28 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Ben Smithurst Cc: current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <19990925133215.A35268@lithium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, Dynamic dialups are the real problems. I have a static dialup, and its essentially mine to do with what I want. its not counted among my ISP's dialup pools. ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Sat, 25 Sep 1999, Ben Smithurst wrote: > [ CC list trimmed ] > > Pat Lynch wrote: > > > DUL, while I'm not sure whether we should take this to -chat or not since > > we are now getting into noise on the -current list, is also a good thing. > > simply because noone on a dialup has reason to be sending mail directly to > > me, they should be sending it through thier ISP's mail servers. > > There are reasons not to use an ISP's smarthost. First, I have no idea > how long my mail will stay there. Second, if my mail can't be delivered > to the other end immediately, I'd rather be able to find out why by > checking my logs. Third, my ISP's smarthost has occasionally been > blacklisted by ORBS because it relays mail for its customers, some of > whom are running open relays. (This is a completely ridiculous action on > ORBS' part, IMO, but that's a discussion for somewhere else.) > > So far at least, I have never had any problems sending mail from my > dialup (which has a static IP address -- I think static IP dialups are > exempt from many dialup blocking lists), and I hope this will continue. > > -- > Ben Smithurst | PGP: 0x99392F7D > ben@scientia.demon.co.uk | key available from keyservers and > | ben+pgp@scientia.demon.co.uk > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 7:31:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id F0993152F4 for ; Sat, 25 Sep 1999 07:31:37 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id QAA21368 for ; Sat, 25 Sep 1999 16:31:36 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id QAA81510 for freebsd-current@freebsd.org; Sat, 25 Sep 1999 16:31:35 +0200 (CEST) Date: Sat, 25 Sep 1999 16:31:35 +0200 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: Boot problems with new -current Message-ID: <19990925163135.A81383@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to update my -current system compiled from July 12 (both kernel and base system). But before all system updating I have tried to compile and run new kernel from today (September 25) - and it won't boot so I'm afraid to update all the system... Booting ends with these lines: wd0: bad sector table no supported wd0s2: bad sector table no supported rootdev=0xc078c180 error=22, panic: cannot mount root (2) I'm sorry but I don't know how to copy all boot messages because of these aren't appearing in /var/log/messages (thanks to early panic). Am I something missing or is it possible it has something to do with latest ATA driver changes? (Yes, I'm using and testing new ATA driver... Hmm, I think I will try to compile and run old wd driver if it will be better...) Here is my kernel configuration file: -- # # USER - User kernel # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id$ machine i386 ident USER maxusers 32 makeoptions DEBUG=-g makeoptions KERNEL="kernel.TEST" # options MAXDSIZ="(256*1024*1024)" # options DFLDSIZ="(256*1024*1024)" # options BLKDEV_IOSIZE=8192 # options PQ_NOOPT options PQ_LARGECACHE # options PQ_HUGECACHE options INCLUDE_CONFIG_FILE # options SMP # options APIC_IO # options NCPU=5 # options NBUS=5 # options NAPIC=2 # options NINTR=25 # cpu I386_CPU # cpu I486_CPU cpu I586_CPU cpu I686_CPU # options CPU_BLUELIGHTNING_FPU_OP_CACHE # options CPU_BLUELIGHTNING_3X # options CPU_BTB_EN # options CPU_DIRECT_MAPPED_CACHE # options CPU_DISABLE_5X86_LSSER # options CPU_FASTER_5X86_FPU # options CPU_I486_ON_386 # options CPU_IORT # options CPU_LOOP_EN # options CPU_RSTK_EN options CPU_SUSP_HLT # options CPU_WT_ALLOC # options CYRIX_CACHE_WORKS # options CYRIX_CACHE_REALLY_WORKS # options NO_F00F_HACK # options MATH_EMULATE # options GPL_MATH_EMULATE options COMPAT_43 # Keep this! options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG # options MD5 options DDB options DDB_UNATTENDED # options GDB_REMOTE_CHAT options KTRACE # options INVARIANTS # options INVARIANT_SUPPORT # options DIAGNOSTIC options PERFMON # options COMPILING_LINT options UCONSOLE options USERCONFIG # options INTRO_USERCONFIG options VISUAL_USERCONFIG # options ROOTDEVNAME=\"da0s2e\" options INET options IPX # options IPXIP # Not available! # options IPTUNNEL # Not available! # options NETATALK # options NS # Broken! # options CCITT # Broken! # options ISO # Broken! # options TPIP # Broken! # options TPCONS # Broken! # options LLC # Broken! # options HDLC # Broken! # options EON # Broken! # options NSIP # Broken! pseudo-device ether # pseudo-device token # pseudo-device fddi # pseudo-device sppp pseudo-device loop pseudo-device bpf # pseudo-device disc pseudo-device tun pseudo-device sl 1 pseudo-device ppp 1 pseudo-device streams # options PPP_BSDCOMP # options PPP_DEFLATE # options PPP_FILTER # options TCP_COMPAT_42 # options MROUTING # options IPFIREWALL # options IPFIREWALL_VERBOSE # options IPFIREWALL_FORWARD # options IPFIREWALL_VERBOSE_LIMIT=100 # options IPFIREWALL_DEFAULT_TO_ACCEPT # options IPDIVERT # options IPFILTER # options IPFILTER_LOG # options IPFILTER_LKM # options IPSTEALTH # options TCPDEBUG # options TCP_DROP_SYNFIN # options TCP_RESTRICT_RST options ICMP_BANDLIM # options DUMMYNET # options BRIDGE # options ATM_CORE # options ATM_IP # options ATM_SIGPVC # options ATM_SPANS # options ATM_UNI # device hea0 # device hfa0 options FFS options MFS # options NFS # options NFS_NOSERVER # options CD9660 # options FDESC # options KERNFS # options MSDOSFS # options NTFS # options NULLFS # options PORTAL # options PROCFS # options UMAPFS # options UNION # options CD9660_ROOT options FFS_ROOT # options MFS_ROOT # options NFS_ROOT # options DEVFS options SOFTUPDATES # options MFS_ROOT_SIZE=10 # options NSWAPDEV=20 # options QUOTA # options CD9660_ROOTDELAY=20 # options SUIDDIR # options NFS_MINATTRTIMO=3 # options NFS_MAXATTRTIMO=60 # options NFS_MINDIRATTRTIMO=30 # options NFS_MAXDIRATTRTIMO=60 # options NFS_GATHERDELAY=10 # options NFS_UIDHASHSIZ=29 # options NFS_WDELAYHASHSIZ=16 # options NFS_MUIDHASHSIZ=63 # options NFS_DEBUG # options CODA # pseudo-device vcoda 4 options EXT2FS options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # controller scbus0 # device ch0 # device da0 # device sa0 # device cd0 # device pass0 # device pt0 at scbus? # options CAMDEBUG # options CAM_DEBUG_BUS=-1 # options CAM_DEBUG_TARGET=-1 # options CAM_DEBUG_LUN=-1 # options CAM_DEBUG_FLAGS="CAM_DEBUG_INFO|CAM_DEBUG_TRACE|CAM_DEBUG_CDB" # options CAM_MAX_HIGHPOWER=4 # options SCSI_NO_SENSE_STRINGS # options SCSI_NO_OP_STRINGS # options SCSI_REPORT_GEOMETRY # options SCSI_DELAY=8000 # options CHANGER_MIN_BUSY_SECONDS=2 # options CHANGER_MAX_BUSY_SECONDS=10 # options SA_SPACE_TIMEOUT="(60)" # options SA_REWIND_TIMEOUT="(2*60)" # options SA_ERASE_TIMEOUT="(4*60)" # options SCSI_PT_DEFAULT_TIMEOUT="60" pseudo-device pty pseudo-device speaker pseudo-device gzip pseudo-device vn pseudo-device md pseudo-device snp 3 # pseudo-device ccd 4 # pseudo-device vinum # options VINUMDEBUG # pseudo-device tb # Broken! # options MSGBUF_SIZE=40960 controller isa0 options AUTO_EOI_1 # options AUTO_EOI_2 # options MAXMEM="(128*1024)" # options TUNE_1542 # options BROKEN_KEYBOARD_RESET # options PAS_JOYSTICK_ENABLE # options PPS_SYNC # options NTIMECOUNTER=20 controller pnp0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 # options ATKBD_DFLT_KEYMAP # makeoptions ATKBD_DFLT_KEYMAP="jp.106" # options KBD_DISABLE_KEYMAP_LOAD # options KBD_INSTALL_CDEV device psm0 at atkbdc? irq 12 # options PSM_HOOKAPM # options PSM_RESETAFTERSUSPEND device vga0 at isa? port ? conflicts # options SC_ALT_SEQACCESS # options VGA_NO_FONT_LOADING # options VGA_NO_MODE_CHANGE # options VGA_SLOW_IOACCESS options VGA_WIDTH90 # options VESA pseudo-device splash # device vt0 at isa? # options XSERVER # options FAT_CURSOR # options PCVT_SCANSET=2 # options PCVT_24LINESDEF # options PCVT_CTRL_ALT_DEL # options PCVT_EMU_MOUSE # options PCVT_FREEBSD=211 # options PCVT_META_ESC # options PCVT_NSCREENS=9 # options PCVT_PRETTYSCRNS # options PCVT_SCREENSAVER # options PCVT_USEKBDSEC # options PCVT_VT220KEYB device sc0 at isa? options MAXCONS=8 # options SC_ALT_MOUSE_IMAGE # options SC_DFLT_FONT # makeoptions SC_DFLT_FONT=cp850 # options SC_DISABLE_DDBKEY # options SC_DISABLE_REBOOT options SC_HISTORY_SIZE=256 # options SC_MOUSE_CHAR=0x3 options SC_PIXEL_MODE # options SC_NO_CUTPASTE # options SC_NO_FONT_LOADING # options SC_NO_HISTORY # options SC_NO_SYSMOUSE device npx0 at nexus? port IO_NPX flags 0x0 irq 13 # controller bt0 at isa? port IO_BT0 irq ? # controller adv0 at isa? port ? irq ? # controller adw0 # controller aha0 at isa? port ? irq ? # controller ida0 # device id0 controller ata0 device atadisk0 device atapicd0 device atapifd0 # device atapist0 # controller ata1 at isa? port IO_WD1 irq 14 # controller ata2 at isa? port IO_WD2 irq 15 # controller wdc0 at isa? port IO_WD1 irq 14 flags 0xA0FF # disk wd0 at wdc0 drive 0 # # disk wd1 at wdc0 drive 1 # controller wdc1 at isa? port IO_WD2 irq 15 flags 0xA0FF # disk wd2 at wdc1 drive 0 # # disk wd3 at wdc1 drive 1 options IDE_DELAY=250 # device wcd0 # device wfd0 # device wst0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 # options FDC_DEBUG # options FDC_YE disk fd0 at fdc0 drive 0 # disk fd1 at fdc0 drive 1 # device fla0 at isa? # device mse0 at isa? port 0x23c irq 5 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # device sio2 at isa? disable port IO_COM3 irq 5 # device sio3 at isa? disable port IO_COM4 irq 9 # options BREAK_TO_DEBUGGER # options CONSPEED=9600 # options COM_ESP # options COM_MULTIPORT # options EXTRA_SIO=2 # device ar0 at isa? port 0x300 irq 10 iomem 0xd0000 # device cs0 at isa? port 0x300 irq ? # device cx0 at isa? port 0x240 irq 15 drq 7 # device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 # device el0 at isa? port 0x300 irq 9 # device ep0 at isa? port 0x300 irq 10 # device ex0 at isa? port? irq? # device fe0 at isa? port 0x300 irq ? # device ie0 at isa? port 0x300 irq 5 iomem 0xd0000 # device ie1 at isa? port 0x360 irq 7 iomem 0xd0000 # device le0 at isa? port 0x300 irq 5 iomem 0xd0000 # device lnc0 at isa? port 0x280 irq 10 drq 0 # device rdp0 at isa? port 0x378 irq 7 flags 2 # device sr0 at isa? port 0x300 irq 5 iomem 0xd0000 # device wi0 at isa? port? irq? # options WLCACHE # options WLDEBUG # device wl0 at isa? port 0x300 irq ? # device xe0 at isa? port? irq ? # device ze0 at isa? port 0x300 irq 5 iomem 0xd8000 # device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 # device oltr0 at isa? # pseudo-device atm # device en0 # device en1 # options NATM # options BROKEN_BUS_CLOCK # options SYMPHONY_PAS # options EXCLUDE_SBPRO # options SBC_IRQ=5 # options GUS_DMA2 # options GUS_DMA # options GUS_IRQ # controller snd0 # device pas0 at isa? port 0x388 irq 10 drq 6 # device sb0 at isa? port 0x220 irq 5 drq 1 # device sbxvi0 at isa? drq 5 # device sbmidi0 at isa? port 0x330 # device awe0 at isa? port 0x620 # device gus0 at isa? port 0x220 irq 12 drq 1 flags 0x3 # device mss0 at isa? port 0x530 irq 10 drq 1 # device css0 at isa? port 0x534 irq 5 drq 1 flags 0x08 # device sscape0 at isa? port 0x330 irq 9 drq 0 # device trix0 at isa? port 0x330 irq 6 drq 0 # device sscape_mss0 at isa? port 0x534 irq 5 drq 1 # device opl0 at isa? port 0x388 # device mpu0 at isa? port 0x330 irq 6 drq 0 # device uart0 at isa? port 0x330 irq 5 device pcm0 at isa? port ? irq 5 drq 3 flags 0x17 # device pca0 at isa? port IO_TIMER1 # device mcd0 at isa? port 0x300 irq 10 # device scd0 at isa? port 0x230 # controller matcd0 at isa? port 0x230 # device wt0 at isa? port 0x300 irq 5 drq 1 # device ctx0 at isa? port 0x230 iomem 0xd0000 # device spigot0 at isa? port 0xad6 irq 15 iomem 0xee000 # device apm0 at nexus? disable flags 0x31 # device gp0 at isa? port 0x2c0 # device gsc0 at isa? port IO_GSC1 drq 3 # device joy0 at isa? port IO_GAME # device alog0 at isa? port 0x260 irq 5 # device cy0 at isa? irq 10 iomem 0xd4000 iosiz 0x2000 # options CY_PCI_FASTINTR # device dgb0 at isa? port 0x220 iomem 0xfc0000 iosiz ? # options NDGBPORTS=16 # device dgm0 at isa? port 0x104 iomem 0xd00000 iosiz ? # device labpc0 at isa? port 0x260 irq 5 # device rc0 at isa? port 0x220 irq 12 # device rp0 at isa? port 0x280 # device tw0 at isa? port 0x380 irq 11 # device si0 at isa? iomem 0xd0000 irq 12 # device asc0 at isa? port IO_ASC1 drq 3 irq 10 # device stl0 at isa? port 0x2a0 irq 10 # device stli0 at isa? port 0x2a0 iomem 0xcc000 flags 23 iosiz 0x1000 # device loran0 at isa? port ? irq 5 # device xrpu0 # controller eisa0 # controller ahb0 # controller ahc0 # controller amd0 # device fea0 # options AHC_ALLOW_MEMIO # options EISA_SLOTS=12 # controller miibus0 # options BKTR_USE_PLL # options BKTR_GPIO_ACCESS # options BKTR_NO_MSP_RESET # options BKTR_430_FX_MODE # options BKTR_SIS_VIA_MODE controller pci0 # controller ahc1 # controller amd0 # controller ncr0 # controller isp0 # options SCSI_ISP_NO_FWLOAD_MASK=0x12 # options SCSI_ISP_NO_NVRAM_MASK=0x1 # options SCSI_ISP_PREFER_MEM_MAP=0 # options SCSI_ISP_FCDUPLEX=0x4 # options ISP_DISABLE_1020_SUPPORT # options ISP_DISABLE_1080_SUPPORT # options ISP_DISABLE_2100_SUPPORT # device al0 # device ax0 # device de0 # device dm0 device fxp0 # device mx0 # device pn0 # device rl0 # device sf0 # device sis0 # device sk0 # device ste0 # device ti0 # device tl0 # device tx0 # device vr0 # device vx0 # device wb0 # device xl0 # device fpa0 # device meteor0 # device oltr0 # device bktr0 # options PCI_QUIET # controller card0 # device pcic0 at card? # device pcic1 at card? # options PCIC_RESUME_RESET # options POWERFAIL_NMI controller smbus0 controller intpm0 # controller alpm0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? # controller pcf0 at isa? port 0x320 irq 5 # options TEL_S0_8 # device isic0 at isa? iomem 0xd0000 irq 5 flags 1 # options TEL_S0_16 # device isic0 at isa? port 0xd80 iomem 0xd0000 irq 5 flags 2 # options TEL_S0_16_3 # device isic0 at isa? port 0xd80 irq 5 flags 3 # options AVM_A1 # device isic0 at isa? port 0x340 irq 5 flags 4 # options USR_STI # device isic0 at isa? port 0x268 irq 5 flags 7 # options ITKIX1 # device isic0 at isa? port 0x398 irq 10 flags 18 # options "ELSA_PCC16" # device isic0 at isa? port 0x360 irq 10 flags 19 # options TEL_S0_16_3_P # device isic0 at isa? port ? irq ? # options CRTX_S0_P # device isic0 at isa? port ? irq ? # options DRN_NGO # device isic0 at isa? port ? irq ? # options SEDLBAUER # device isic0 at isa? port ? irq ? # options DYNALINK # device isic0 at isa? port ? irq ? # options ELSA_QS1ISA # device isic0 at isa? port ? irq ? # options "ITKIX1" # device isic0 at isa? port ? irq ? # options "AVM_PNP" # device isic0 at isa? port ? irq ? # options "SIEMENS_ISURF2" # device isic0 at isa? port ? irq ? # options ELSA_QS1PCI # device isic0 # options "AVM_A1_PCI" # device isic0 # options AVM_A1_PCMCIA # device isic0 at isa? port 0x340 irq 5 flags 10 # device tina0 at isa? port 0x260 irq 10 # pseudo-device "i4bq921" # pseudo-device "i4bq931" # pseudo-device "i4b" # pseudo-device "i4btrc" 4 # pseudo-device "i4bctl" # pseudo-device "i4brbch" 4 # pseudo-device "i4btel" 2 # pseudo-device "i4bipr" 4 # options IPR_VJ # pseudo-device "i4bisppp" 4 # options DEBUG_1284 # options PERIPH_1284 # options DONTPROBE_1284 # options VP0_DEBUG # options LPT_DEBUG # options PPC_DEBUG # options PLIP_DEBUG controller ppbus0 # controller vpo0 at ppbus? device lpt0 at ppbus? # device plip0 at ppbus? # device ppi0 at ppbus? # device pps0 at ppbus? # device lpbb0 at ppbus? # device ppc0 at isa? port? flags 0x40 irq 7 # options BOOTP # options BOOTP_NFSROOT # options BOOTP_NFSV3 # options BOOTP_COMPAT # options BOOTP_WIRED_TO=fxp0 # options HW_WDOG # options PMAP_SHPGPERPROC=201 # options NO_SWAPPING # options NSFBUFS=1024 # options DEBUG_LOCKS # options CLK_CALIBRATION_LOOP # options CLK_USE_I8254_CALIBRATION # options CLK_USE_TSC_CALIBRATION # options TIMER_FREQ="((14318182+6)/12)" # options CLUSTERDEBUG # options COMPAT_LINUX # options CPU_UPGRADE_HW_CACHE # options DEBUG # options DEBUG_VFS_LOCKS # options DISABLE_PSE # options I586_PMC_GUPROF=0x70000 # options IBCS2 # options KEY # options KEY_DEBUG # options LOCKF_DEBUG # options LOUTB # options KBD_MAXRETRY=4 # options KBD_MAXWAIT=6 # options KBD_RESETDELAY=201 # options KBDIO_DEBUG=2 # options MSGMNB=2049 # options MSGMNI=41 # options MSGSEG=2049 # options MSGSSZ=16 # options MSGTQL=41 # options NBUF=512 # options NETATALKDEBUG # options NMBCLUSTERS=1024 # options NPX_DEBUG # options PANIC_REBOOT_WAIT_TIME=16 # options PSM_DEBUG=1 # options SCSI_NCR_DEBUG # options SCSI_NCR_DFLT_TAGS=4 # options SCSI_NCR_MAX_SYNC=10000 # options SCSI_NCR_MAX_WIDE=1 # options SCSI_NCR_MYADDR=7 # options SEMMAP=31 # options SEMMNI=11 # options SEMMNS=61 # options SEMMNU=31 # options SEMMSL=61 # options SEMOPM=101 # options SEMUME=11 # options SHOW_BUSYBUFS # options SHMALL=1025 # options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" # options SHMMAXPGS=1025 # options SHMMIN=2 # options SHMMNI=33 # options SHMSEG=9 # options SI_DEBUG # options SIMPLELOCK_DEBUG # options SPX_HACK # options VFS_BIO_DEBUG # options ENABLE_ALART # controller dpt0 # options DPT_VERIFY_HINTR # options DPT_RESTRICTED_FREELIST #!CAM# options DPT_MEASURE_PERFORMANCE # options DPT_FREELIST_IS_STACK #!CAM# options DPT_HANDLE_TIMEOUTS # options DPT_TIMEOUT_FACTOR=4 # options DPT_INTR_DELAY=200 # options DPT_LOST_IRQ # options DPT_RESET_HBA # options DPT_SHUTDOWN_SLEEP=500 # controller uhci0 # controller ohci0 # controller usb0 # device ugen0 # device uhid0 # device ukbd0 # device ulpt0 # controller umass0 # device ums0 # options UHCI_DEBUG # options OHCI_DEBUG # options USB_DEBUG # options UGEN_DEBUG # options UHID_DEBUG # options UHUB_DEBUG # options UKBD_DEBUG # options ULPT_DEBUG # options UMASS_DEBUG # options UMS_DEBUG # options UKBD_DFLT_KEYMAP # makeoptions UKBD_DFLT_KEYMAP=it.iso # options INIT_PATH="/sbin/init:/stand/sysinstall" -- -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 7:42:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7228314CB5 for ; Sat, 25 Sep 1999 07:42:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA12060; Sat, 25 Sep 1999 16:41:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Cejka Rudolf Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot problems with new -current In-reply-to: Your message of "Sat, 25 Sep 1999 16:31:35 +0200." <19990925163135.A81383@dcse.fee.vutbr.cz> Date: Sat, 25 Sep 1999 16:41:14 +0200 Message-ID: <12058.938270474@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your disk claims to have bad144 enabled, the ata driver doesn't support this. If you need bad144 support (ESDI or ST506 disks, you can recognize them by the two ribbon cables and their 8+ years of age) you need to use the wd driver. Otherwise you need to fix your disklabel (by booting with the wd driver and fixing it). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 8:29:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A360714EAB for ; Sat, 25 Sep 1999 08:29:13 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA64102; Sat, 25 Sep 1999 17:29:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909251529.RAA64102@freebsd.dk> Subject: Re: Boot problems with new -current In-Reply-To: <19990925163135.A81383@dcse.fee.vutbr.cz> from Cejka Rudolf at "Sep 25, 1999 04:31:35 pm" To: cejkar@dcse.fee.vutbr.cz (Cejka Rudolf) Date: Sat, 25 Sep 1999 17:29:09 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Cejka Rudolf wrote: > > I'm trying to update my -current system compiled from July 12 (both > kernel and base system). But before all system updating I have tried to > compile and run new kernel from today (September 25) - and it won't > boot so I'm afraid to update all the system... > Booting ends with these lines: > > wd0: bad sector table no supported > wd0s2: bad sector table no supported > rootdev=0xc078c180 error=22, panic: cannot mount root (2) > > I'm sorry but I don't know how to copy all boot messages because > of these aren't appearing in /var/log/messages (thanks to early panic). > > Am I something missing or is it possible it has something to do > with latest ATA driver changes? > (Yes, I'm using and testing new ATA driver... Hmm, I think I will try > to compile and run old wd driver if it will be better...) The ATA driver has no bad144 support, thats probably why you get the above message. The reason is that modern ATA disks does internal bad block remapping (just as SCSI), and if you have used up all the spares you better swap that disk for another one, its going bad on you no matter what... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 9: 1:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id D8D1414F32 for ; Sat, 25 Sep 1999 09:01:16 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id TAA93908; Sat, 25 Sep 1999 19:59:19 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id UAA03624; Sat, 25 Sep 1999 20:03:10 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199909251603.UAA03624@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: wierd message In-reply-to: Your message of "Sat, 25 Sep 1999 07:37:51 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Sep 1999 20:03:10 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Culver wrote: > what does this message mean? > Sep 24 18:34:04 culverk /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt I don't know how you got it, but here is an easy way to do so: In /etc/rc.conf: network_interfaces="ed0 lo0" ifconfig_ed0="DHCP" (ed0 apparently can be replaced with any other NIC) Then run amd. (I don't know why amd is the first program I tried that trigger it.) The workaround (fix?) is to put lo0 before ed0. But sysinstall put network interfaces in this order :-(. I have seen this when I recently installed 3.3-RELEASE on a new machine. As I ssuspect, this is because DHCP do something like route add -host 127.0.0.1 before lo0 is ifconfiged. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 9:29:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 3ED5D14D36 for ; Sat, 25 Sep 1999 09:29:19 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1413 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 25 Sep 1999 18:29:19 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #13) id m11UuhK-0003lgC; Sat, 25 Sep 99 18:29 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: curses: wrap on write to last column ? To: freebsd-current@freebsd.org (FreeBSD Current) Date: Sat, 25 Sep 1999 18:29:18 +0200 (METDST) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 708 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i have identical applications using curses running on 3.x and a current as of today. On 3.x, the application is able to write to the last column (on an xterm) without automatically wrapping the cursor to the next line, on -current it does wrap to the next line (causing a blank line to be inserted into an autoscroll window). Is this known or am i overseeing something obvious ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 9:50:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from shrewd.knigma.org (host62-6-1-163.btinternet.com [62.6.1.163]) by hub.freebsd.org (Postfix) with ESMTP id 1653714D36 for ; Sat, 25 Sep 1999 09:50:19 -0700 (PDT) (envelope-from markk@knigma.org) Received: from lap.knigma.org (lap.knigma.org [10.141.33.81]) by shrewd.knigma.org (8.9.3/8.9.3) with SMTP id RAA00279 for ; Sat, 25 Sep 1999 17:50:30 +0100 (BST) (envelope-from markk@knigma.org) Message-ID: Date: Sat, 25 Sep 1999 17:49:33 +0100 To: freebsd-current@freebsd.org From: Mark Knight Subject: Panic with BT Speedway / AVM Fritz!PCI ISDN MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 4.02 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Until installing a BT Speedway (AVM Fritz!PCI), ISDN card, my early August 4.0-C box was stable. Since then, I've had numerous panics, complete with advice to increase NTPBUFFERS / maxusers. Despite a new world as of 5/9/99 and greatly increased kernel parameters the panics have not been eliminated. At the moment I'm only using the card to receive voice calls, triggering a call to my ISP. Panics seem related to number of calls since last booted, some sort of leak? Before I start serious debugging, has anyone else got this problem, or even better a solution? Best regards, -- Mark Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 10:16:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A618814BB8; Sat, 25 Sep 1999 10:16:12 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA07859; Sat, 25 Sep 1999 10:12:49 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909251712.KAA07859@gndrsh.dnsmgr.net> Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: from Pat Lynch at "Sep 25, 1999 09:44:28 am" To: lynch@bsdunix.net (Pat Lynch) Date: Sat, 25 Sep 1999 10:12:49 -0700 (PDT) Cc: ben@scientia.demon.co.uk (Ben Smithurst), current@FreeBSD.ORG, chat@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > yes, Dynamic dialups are the real problems. I have a static dialup, and > its essentially mine to do with what I want. its not counted among my > ISP's dialup pools. And if you signed the additional clauses to our AUP that basically places you at legal and financial risk for violation of the other parts of the AUP, with special respect to spamming, your static IP would be excluded from our filter. We just don't like to have to do this for an account that is anything less than a DS-1 loop, though it may be fractional DS-1. We really hate to do it for any dial up services, we will leave that business to the IP's who provide no real service. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 10:38: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 9358414C3F for ; Sat, 25 Sep 1999 10:37:58 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id NAA04316 for ; Sat, 25 Sep 1999 13:37:08 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 25 Sep 1999 13:37:08 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: ata driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been testing the ata driver recently, and I have noticed this message (along with not being able to access that hard drive after the message) ata0_slave: lost contact with device - resetting. then it says it's reset, but nothing can access the disk... I've gone back to the wdc drivers for now... although the wdc drivers appear to be about 3 MB/sec slower on reads for my FreeBSD HD.. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 10:50:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id A1FD614FA6 for ; Sat, 25 Sep 1999 10:50:47 -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 NAA11233 for current@freebsd.org; Sat, 25 Sep 1999 13:52:51 -0400 From: Bill Paul Message-Id: <199909251752.NAA11233@skynet.ctr.columbia.edu> Subject: Beneath The Planet Of The Mondays To: current@freebsd.org Date: Sat, 25 Sep 1999 13:52:50 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1562 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh, hello? Hi? Is this thing on? *tap* *tap* *squeeeeeeeeeel!* Oops, sorry. Listen, does anybody have any idea why there hasn't been a -current snapshot on current.freebsd.org since Septembet 18th? Anyone? People do realize that make release is not the same as make buildworld, and are testing the former at least once in a while, right? I realize this is -current and all and mistakes happen, but make release basically constitutes a 'full build' of FreeBSD and if it doesn't work, especially for a whole week, it looks kinda bad. Unfortunately, when the snapshots on current.freebsd.org fall over, nobody knows exactly what causes the problem except Jordan, and he keeps gnawing through his limbs to excape the traps I set for him. I wish the build logs were online somewhere (hint hint). When somebody breaks the build at M$, the offender is made to wear a viking hat. I would suggest a similar punishment for those who break our own build, except that I suspect many of you are wearing viking hats already. -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-current" in the body of the message From owner-freebsd-current Sat Sep 25 11:18:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 792E914DC9 for ; Sat, 25 Sep 1999 11:18:17 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id OAA25894 for ; Sat, 25 Sep 1999 14:18:09 -0400 (EDT) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA27599 for ; Sat, 25 Sep 1999 14:18:12 -0400 (EDT) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA27595 for ; Sat, 25 Sep 1999 14:18:12 -0400 (EDT) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sat, 25 Sep 1999 14:18:12 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: another error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped about 20 minutes ago and now I get this message when I su to root, or when I start xwindows. It doesn't seem to be hurting anything though: Warning:tty: no si_tty Is it anything to worry about? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix System Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 11:35:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles560.castles.com [208.214.165.124]) by hub.freebsd.org (Postfix) with ESMTP id 99DFA14C1F for ; Sat, 25 Sep 1999 11:35:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA06800; Sat, 25 Sep 1999 11:28:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909251828.LAA06800@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Culver Cc: freebsd-current@freebsd.org Subject: Re: wierd message In-reply-to: Your message of "Sat, 25 Sep 1999 07:37:51 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Sep 1999 11:28:14 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what does this message mean? > Sep 24 18:34:04 culverk /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt > > I've been getting it alot since I reinstalled -current, it never used to > happen before. Check that you haven't got a bogusly-detected lnc interface with an all-1's ethernet address; I saw this the other day. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 11:36:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3C9AC150A7 for ; Sat, 25 Sep 1999 11:36:46 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA26387; Sat, 25 Sep 1999 11:35:02 -0700 Date: Sat, 25 Sep 1999 11:36:43 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tor.Egge@fast.no Cc: freebsd-current@FreeBSD.ORG Subject: Re: DDB && SMP? In-Reply-To: <199909242345.BAA38564@midten.fast.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, that did the trick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 11:42:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C001214C47 for ; Sat, 25 Sep 1999 11:42:19 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA12965; Sat, 25 Sep 1999 20:41:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: another error In-reply-to: Your message of "Sat, 25 Sep 1999 14:18:12 EDT." Date: Sat, 25 Sep 1999 20:41:27 +0200 Message-ID: <12963.938284887@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kenneth Wayne Culver writes: >I cvsupped about 20 minutes ago and now I get this message when I su to >root, or when I start xwindows. It doesn't seem to be hurting anything >though: > >Warning:tty: no si_tty > >Is it anything to worry about? I'm not quite sure yet, I'm still checking. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 13:18:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 606E114BF2 for ; Sat, 25 Sep 1999 13:18:48 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA00896; Sat, 25 Sep 1999 22:18:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199909252018.WAA00896@gratis.grondar.za> To: Poul-Henning Kamp Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: another error Date: Sat, 25 Sep 1999 22:18:26 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message , Kenne th > Wayne Culver writes: > >I cvsupped about 20 minutes ago and now I get this message when I su to > >root, or when I start xwindows. It doesn't seem to be hurting anything > >though: > > > >Warning:tty: no si_tty > > > >Is it anything to worry about? > > I'm not quite sure yet, I'm still checking. 20 minutes is not enough to make world and build a kernel. Are you sure you've done both? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 13:24: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D9666156C7 for ; Sat, 25 Sep 1999 13:23:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA13342; Sat, 25 Sep 1999 22:22:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mark Murray Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: another error In-reply-to: Your message of "Sat, 25 Sep 1999 22:18:26 +0200." <199909252018.WAA00896@gratis.grondar.za> Date: Sat, 25 Sep 1999 22:22:02 +0200 Message-ID: <13340.938290922@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199909252018.WAA00896@gratis.grondar.za>, Mark Murray writes: >> In message , Kenne >th >> Wayne Culver writes: >> >I cvsupped about 20 minutes ago and now I get this message when I su to >> >root, or when I start xwindows. It doesn't seem to be hurting anything >> >though: >> > >> >Warning:tty: no si_tty >> > >> >Is it anything to worry about? >> >> I'm not quite sure yet, I'm still checking. > >20 minutes is not enough to make world and build a kernel. Are you sure >you've done both? He doesn't have to. This was a warning I put in, but it would give too much noise so I've taken it out again. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 13:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id E6CAF15141 for ; Sat, 25 Sep 1999 13:24:30 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id WAA22407 for freebsd-current@FreeBSD.ORG; Sat, 25 Sep 1999 22:24:29 +0200 (CEST) (envelope-from olli) Date: Sat, 25 Sep 1999 22:24:29 +0200 (CEST) From: Oliver Fromme Message-Id: <199909252024.WAA22407@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: gcc optimizer in -current system ... Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just some numbers that I got with a small testsuite. This is the setiathome client running on an AMD Athlon-500 (K7), FreeBSD 4.0-current (as of 1999-09-18). Of course, I've used the same work unit for all tests. I also changed the code to stop after a certain amount of data has processed, because I don't want to wait some hours for each test to complete. ;-) -O1 302.72 real 301.96 user 0.28 sys -O2 315.20 real 314.42 user 0.18 sys -O3 320.01 real 319.23 user 0.35 sys -Os 315.99 real 315.19 user 0.35 sys As you can see, -O1 is fastest, the higher optimization levels are slower. I'm currently running a testsuite with a larger number of optimizer flags combinations, but it'll take a while. On a side note, I downloaded AMD's document about optimizing code for the Athlon, and I found out that gcc does a pretty poor job. :-( Unfortunately, I'm not an expert in writing compilers, and I don't dare to touch the gcc source code. After all, the compiler is one of the most critical parts of the system. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 14:14:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id E90BD15335; Sat, 25 Sep 1999 14:14:30 -0700 (PDT) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id RAA22899; Sat, 25 Sep 1999 17:14:07 -0400 (EDT) Date: Sat, 25 Sep 1999 17:14:07 -0400 (EDT) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: "Rodney W. Grimes" Cc: Ben Smithurst , current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: On hub.freebsd.org refusing to talk to dialups In-Reply-To: <199909251712.KAA07859@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I should clarify, my dialup is actually dedicated. not dialup-when-I-need-it. don;t know if this makes a diofference but I pay ALOT of money for the use of my own guaranteed modem 24/7. -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ On Sat, 25 Sep 1999, Rodney W. Grimes wrote: > > yes, Dynamic dialups are the real problems. I have a static dialup, and > > its essentially mine to do with what I want. its not counted among my > > ISP's dialup pools. > > And if you signed the additional clauses to our AUP that basically places > you at legal and financial risk for violation of the other parts of the > AUP, with special respect to spamming, your static IP would be excluded > from our filter. We just don't like to have to do this for an account > that is anything less than a DS-1 loop, though it may be fractional DS-1. > > We really hate to do it for any dial up services, we will leave that > business to the IP's who provide no real service. > > -- > Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 14:25:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id BD69D15328 for ; Sat, 25 Sep 1999 14:25:55 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 11UzL5-000FDD-00; Sat, 25 Sep 1999 17:26:39 -0400 To: Jacques Vidrine Cc: "Rodney W. Grimes" , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Filtering port 25 (was Re: On hub.freebsd.org refusing to talk to dialups) In-reply-to: Your message of "Fri, 24 Sep 1999 10:24:37 CDT." <19990924152438.F0C2BBE08@gw.nectar.com> Date: Sat, 25 Sep 1999 17:26:33 -0400 Message-ID: <58478.938294793@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jacques Vidrine wrote in message ID <19990924152438.F0C2BBE08@gw.nectar.com>: > > This prevents your customers from being something that could get you > > on the RBL or the DUL MAP for bad behavior, it also inforces the use > > of your smart host relay, as it/they is/are the only way to get a > > tcp port 25 setup completed. > > Evil! How does the ISP know I'm not running some other protocol > (which is none of its business) on port 25? Because then you be failing to follow the relevant RFCs on port assignments. > How does it know that I don't have a policy reason for accessing > some other mail server than its own? It doesn't, but direct-inject and relay-rape spam is a major problem. How do you propose that large ISPs combat abuse of their dialups to create this problem? Forcing the spam to go through their own SMTP servers, where it can be logged, tracked, rate limited and noticed much earlier is a BIG step in the right direction. UU Net is doing this for all of their resold dialups because of the major problems they had. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 14:39:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id D563D14C24 for ; Sat, 25 Sep 1999 14:39:42 -0700 (PDT) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id D931737E9 for ; Sat, 25 Sep 1999 16:39:39 -0500 (CDT) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id QAA16009 for ; Sat, 25 Sep 1999 16:39:39 -0500 (CDT) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Sat, 25 Sep 1999 16:39:39 -0500 (CDT) From: Thomas Veldhouse To: freebsd-current@freebsd.org Subject: ATA drivers - HOWTO? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have noticed over time that many people are test driving the new ATA Drivers. I attempted to do it a while back but I couldn't boot because of the device name changes. I did not know what the new device names were. Anyway - is there a simple HOWTO for using these drivers - and - are there any gotchas I should be aware of? FYI - I would be using them with a Western Digital 6.4G and 8.0G drive under UltraDMA33. Thanks in advance, Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 15:20:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7F7A214E52 for ; Sat, 25 Sep 1999 15:20:32 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id AAA64826; Sun, 26 Sep 1999 00:19:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909252219.AAA64826@freebsd.dk> Subject: Re: ATA drivers - HOWTO? In-Reply-To: from Thomas Veldhouse at "Sep 25, 1999 04:39:39 pm" To: veldy@visi.com (Thomas Veldhouse) Date: Sun, 26 Sep 1999 00:19:55 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thomas Veldhouse wrote: > Hello, > > I have noticed over time that many people are test driving the new > ATA > Drivers. I attempted to do it a while back but I couldn't boot because of > the device name changes. I did not know what the new device names were. > Anyway - is there a simple HOWTO for using these drivers - and - are there > any gotchas I should be aware of? > FYI - I would be using them with a Western Digital 6.4G and 8.0G > drive > under UltraDMA33. For the disks you can continue to use the old wd* devices or the new ad* devices. For the atapi devices you need to use acd (CD) afd (ZIP&LS120) and ast (tape). Remember to MAKEDEV them all with a fairly new MAKEDEV (copy that from usr/src/etc/etc.i386) so the major/minor numbers are correct. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 25 16:31:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4658B14A06 for ; Sat, 25 Sep 1999 16:30:54 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA41683 for FreeBSD-current@FreeBSD.ORG; Sun, 26 Sep 1999 09:00:50 +0930 (CST) Date: Sun, 26 Sep 1999 09:00:50 +0930 From: Greg Lehey To: FreeBSD current users Subject: make world, attempt 5 Message-ID: <19990926090049.B46202@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying for the last 24 hours solid to make a new world. The latest problem is: ===> libwrap cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP -DDAEMON_UMASK=022 -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10 -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME -I/usr/obj/src/PANIC/src/tmp/usr/include -c /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax error before `<' /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: `host_match' declared `static' but never defined /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: `string_match' declared `static' but never defined Could we have a break for those people who would like make world to complete? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message