From owner-freebsd-current Sat Jan 1 0:56:53 2000 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 5B22114EFC for ; Sat, 1 Jan 2000 00:56:40 -0800 (PST) (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.9.3) with ESMTP id AAA02457 for ; Sat, 1 Jan 2000 00:56:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001010856.AAA02457@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: FreeBSD-current@FreeBSD.ORG Subject: Hicup , Hicup .... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jan 2000 00:56:35 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joy and Happiness to All on this New Millenium !! Amancio & Bettina -- 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 Sat Jan 1 0:58:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id AD555151DE for ; Sat, 1 Jan 2000 00:58:16 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by atlrel1.hp.com (Postfix) with ESMTP id 0957ACF34; Sat, 1 Jan 2000 03:58:07 -0500 (EST) 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 AAA18938; Sat, 1 Jan 2000 00:58:45 -0800 (PST) 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 AAA14230; Sat, 1 Jan 2000 00:58:05 -0800 (PST) Message-Id: <200001010858.AAA14230@mina.sr.hp.com> To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Reply-To: Darryl Okahata In-reply-to: Your message of "Fri, 31 Dec 1999 22:55:35." <19991231225535.A8004@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Sat, 01 Jan 2000 00:58:05 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger posted a message with the headers: > Date: Fri, 31 Dec 1999 22:55:35 +875400 > X-Mailer: Mutt 0.93.2i Methinks this version of Mutt may have a Y2K problem, as 875400 hours is roughly (very roughly) a century .... -- 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 Agilent Technologies, 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 Sat Jan 1 1: 1:29 2000 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 1488614DD1 for ; Sat, 1 Jan 2000 01:01:22 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (Postfix) with ESMTP id 5083816E; Sat, 1 Jan 2000 01:01:11 -0800 (PST) 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 BAA19244; Sat, 1 Jan 2000 01:01:48 -0800 (PST) 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 BAA14284; Sat, 1 Jan 2000 01:01:09 -0800 (PST) Message-Id: <200001010901.BAA14284@mina.sr.hp.com> To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Reply-To: Darryl Okahata In-reply-to: Your message of "Fri, 31 Dec 1999 22:55:35." <19991231225535.A8004@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Sat, 01 Jan 2000 01:01:09 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > > Date: Fri, 31 Dec 1999 22:55:35 +875400 > > X-Mailer: Mutt 0.93.2i > > Methinks this version of Mutt may have a Y2K problem, as 875400 hours is > roughly (very roughly) a century .... My brain has a Y2K problem ... make that "one year" instead of "a century". ;-( -- 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 Agilent Technologies, 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 Sat Jan 1 1:24: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id F12D514E67; Sat, 1 Jan 2000 01:24:02 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from bubble.didi.com (sji-ca5-90.ix.netcom.com [209.109.234.90]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id BAA87739; Sat, 1 Jan 2000 01:23:57 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id BAA16585; Sat, 1 Jan 2000 01:23:48 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Date: Sat, 1 Jan 2000 01:23:48 -0800 (PST) Message-Id: <200001010923.BAA16585@bubble.didi.com> X-Authentication-Warning: bubble.didi.com: asami set sender to asami@cs.berkeley.edu using -f To: current@freebsd.org Cc: ports@freebsd.org Reply-To: ports@freebsd.org Subject: new package set for Y2K From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, To celebrate the last year of the millenium (*), I built a new package set for 4-current. You can find it at ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/ Since this is the first build with the signal changes, there have been many changes to 4-current and thus many more breakages than before. You can find those at http://bento.FreeBSD.org/errorlogs/errorlogs/e.4.19991230/ There are a whopping 213 (!) errors, or almost twice as many as in 3-stable. (In particular, the ones that say "new compiler error" is what I believe to be caused by the upgrade to the new gcc in 4-current. At least the error messages don't look familiar.) If you can fix any of those and send in fixes via send-pr, I'm sure everyone will be eternally grateful. Thanks and Happy New Year to you all! -PW and the awesome ports team (*) - Actually, it's just that Bill fixed the serial console of bento a couple of days ago, enabling me to upgrade bento and the package building cluster to 4-current, enabling me to use a new chroot environment with the latest bindist, but that doesn't sound as exciting.... (!) - It is not good. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 2:12:10 2000 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 122F614E67 for ; Sat, 1 Jan 2000 02:12:08 -0800 (PST) (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 LAA67994; Sat, 1 Jan 2000 11:11:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Fri, 31 Dec 1999 22:55:35." <19991231225535.A8004@Denninger.Net> Date: Sat, 01 Jan 2000 11:11:51 +0100 Message-ID: <67992.946721511@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991231225535.A8004@Denninger.Net>, Karl Denninger writes: >This is not a port, its part of the RELEASE! > >Its several YEARS old, and doesn't work right - you get lots of STEP changes >instead of what you SHOULD get, which is a slew on the system clock. Remember to get the kernel code involved. To do this: create a driftfile containing "0 1\n" start xntpd That will help. The new ntpd is 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 Sat Jan 1 2:54:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id D47C814DE1 for ; Sat, 1 Jan 2000 02:54:38 -0800 (PST) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id LAA15150 for ; Sat, 1 Jan 2000 11:54:37 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id LAA11825 for ; Sat, 1 Jan 2000 11:54:37 +0100 (MET) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id LAA03266 for ; Sat, 1 Jan 2000 11:54:36 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id KAA19311 for freebsd-current@freebsd.org; Sat, 1 Jan 2000 10:54:38 GMT (envelope-from ust) Date: Sat, 1 Jan 2000 11:54:38 +0100 From: Udo Schweigert To: freebsd-current@freebsd.org Subject: Problem with rlogin and /etc/pam.conf Message-ID: <20000101115418.A19176@alaska.cert.siemens.de> Mail-Followup-To: freebsd-current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, on two 4.0-CURRENT boxes (cvsuped today) I got the following response when trying to rlogin to it: # rlogin indiana assword: A typed-in password is echoed in cleartext. The only thing that helps is to comment out the second-last line in /etc/pam.conf: # other auth required pam_unix.so try_first_pass But this gives an error message when first using the login at the console. Any help on this? Did I miss something? Best regards and HAPPY NEW YEAR ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 41166 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 3:18:17 2000 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 BAA1C14E7B; Sat, 1 Jan 2000 03:18:14 -0800 (PST) (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 MAA25151; Sat, 1 Jan 2000 12:15:26 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA52595; Sat, 1 Jan 2000 00:34:24 +0100 (CET) (envelope-from wilko) Date: Sat, 1 Jan 2000 00:34:24 +0100 From: Wilko Bulte To: Chuck Robey Cc: Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices (MAKEDEV) Message-ID: <20000101003424.A52465@yedi.iaf.nl> References: <19991231171314.A92878@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Fri, Dec 31, 1999 at 03:15:02PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 31, 1999 at 03:15:02PM -0500, Chuck Robey wrote: > On Fri, 31 Dec 1999, Wilko Bulte wrote: > > > > > Why are "certain" devices wildly different than all other ones? I've > > > > never encountered that kind of syntax before, and I can't see that it's > > > > documented anywhere at all. Certainly, MAKEDEV itself (in it's > > > > comments) treats cd* just like all the others, specifying that the number > > > > following is a unit number, and *not* a quantity. I don't know when this > > > > happened, but it's surely not obvious. Not one word in the handbook, > > > > either. > > > > > > *shrug* This is the only rationality I could think of. Obviously, this > > > breaks POLA, so it should be changed (with ample warning). > > > > As for ample warning: I've seen MAKEDEVs display a list of the devices > > they are creating. I think the Tru64 version does this. I myself think this > > is a good behaviour (and hope people won't start yelling 'bloat' for once) > > I'd like to hack about a bit on MAKEDEV, but I was wondering, does > sysinstall, in any way, use MAKEDEV? I *don't* want to mess with > sysinstall! :) I guess the only way to find out short of studying sysinstall source code is asking Jordan. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 Sat Jan 1 5:52:30 2000 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 D63AF14F52 for ; Sat, 1 Jan 2000 05:52:26 -0800 (PST) (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 IAA22438 for ; Sat, 1 Jan 2000 08:52:23 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15040; Sat, 1 Jan 2000 08:51:53 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id IAA12347 for freebsd-current@freeBSD.org; Sat, 1 Jan 2000 08:51:53 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001011351.IAA12347@bb01f39.unx.sas.com> Subject: This looks like a Good Snap :-) To: freebsd-current@freeBSD.org Date: Sat, 1 Jan 2000 08:51:53 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well folks, Happy New Years... :-) It looks like 'make world && make release' run ok today... ---> Sat Jan 1 02:32:28 EST 2000 - Nightly build attempt for 4.0-20000101-SNAP ---> Sat Jan 1 02:32:28 EST 2000 - make world ... Many Many lines deleted... ---> Sat Jan 1 07:58:20 EST 2000 - Creating /pub/FreeBSD/4.0-20000101-SNAP ---> Sat Jan 1 08:04:05 EST 2000 - build of 4.0-20000101-SNAP was a success. ---> make world/release ran 331 min 1 sec I'll have to install this one and give it a whirl... at least for a while I can say I'm running one-one ... Have a great weekend folk, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 6:23:51 2000 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 F125414FDA for ; Sat, 1 Jan 2000 06:23:46 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id PAA21153 for current@freebsd.org; Sat, 1 Jan 2000 15:23:46 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id EC4678864; Sat, 1 Jan 2000 15:13:52 +0100 (CET) Date: Sat, 1 Jan 2000 15:13:52 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000101151352.A18198@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19991231225535.A8004@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991231225535.A8004@Denninger.Net> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Karl Denninger: > This is not a port, its part of the RELEASE! Part of 3.4-R yes. I removed xntpd (3.4e) from current a month ago and put ntpd (4.0.98f, soon to be 4.1.0) in its place. > What does (someone) need to do to get this changed out/updated? I can't > send it in as a port, since its part of the base package (setting > it up as a port would be pretty trivial from what I can see) As it is a feature change, it was decided not to put it into STABLE. ntpd will compile and run w/o any problem on STABLE though. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 7:26:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 1827414E16 for ; Sat, 1 Jan 2000 07:26:54 -0800 (PST) (envelope-from leif@neland.dk) Received: from localhost (leif@localhost) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id QAA47605 for ; Sat, 1 Jan 2000 16:26:45 +0100 (CET) (envelope-from leif@neland.dk) Date: Sat, 1 Jan 2000 16:26:44 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: 2 hours to compile mysql? 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 So far it has been taking 2 hours to compile sql_yacc.cc from mysql3.22. I had to find an old disk for swap, and it's swapping all the time. top shows 156M size and 46M res., run time 20min's for cc1plus. That probably means it's been waiting for swapping in 1h40m... The box is a 333MHz PII, with 64M ram. Do I just need more ram to be able to compile in reasonable time, or is something broken? I'm running FreeBSD current from 01/01/2000. Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 7:39:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 6FA8D14D84 for ; Sat, 1 Jan 2000 07:39:09 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id JAA11908; Sat, 1 Jan 2000 09:39:05 -0600 (CST) Message-ID: <20000101093905.B11872@Denninger.Net> Date: Sat, 1 Jan 2000 09:39:05 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <19991231225535.A8004@Denninger.Net> <67992.946721511@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <67992.946721511@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jan 01, 2000 at 11:11:51AM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 01, 2000 at 11:11:51AM +0100, Poul-Henning Kamp wrote: > In message <19991231225535.A8004@Denninger.Net>, Karl Denninger writes: > > >This is not a port, its part of the RELEASE! > > > >Its several YEARS old, and doesn't work right - you get lots of STEP changes > >instead of what you SHOULD get, which is a slew on the system clock. > > Remember to get the kernel code involved. To do this: > > create a driftfile containing "0 1\n" > start xntpd > > That will help. No it won't. I've been running xntpd for oh, four or five years now on various things. Yes, the drift file is there (and has been). Still got the step time messages. > The new ntpd is in -CURRENT. Ok. I built it as a local binary and install THAT, and the problem disappeared, so I assume the old "included" one had some kind of problem. Oh, BTW, Mutt is Y2K complient. I get no "odd" time displays with messages I send myself :-) -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 8: 4:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr759667-a.nvcr1.bc.wave.home.com (cr759667-a.nvcr1.bc.wave.home.com [24.113.130.83]) by hub.freebsd.org (Postfix) with ESMTP id 8FE0C14F20; Sat, 1 Jan 2000 08:04:30 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (will@23-132.008.popsite.net [209.69.197.132]) by cr759667-a.nvcr1.bc.wave.home.com (8.9.3/8.9.3) with ESMTP id IAA92678; Sat, 1 Jan 2000 08:02:38 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id LAA00651; Sat, 1 Jan 2000 11:04:24 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 01 Jan 2000 11:04:24 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Leif Neland Subject: RE: 2 hours to compile mysql? Cc: freebsd-ports@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ moved to freebsd-ports ] On 01-Jan-00 Leif Neland wrote: > So far it has been taking 2 hours to compile sql_yacc.cc from mysql3.22. This is an indication that something is SERIOUSLY wrong! MySQL has never taken my PII-450 w/ 128MB RAM more than, say, 10-15 minutes to build/install. It would be nice if you showed the transcript of your MySQL build. I hope you're doing this from the port.. (that reminds me, this should really have gone to freebsd-ports, not freebsd-current). -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 8:16:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id 3FAD214FF2; Sat, 1 Jan 2000 08:16:33 -0800 (PST) (envelope-from oschonef@TechFak.Uni-Bielefeld.DE) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id RAA09914; Sat, 1 Jan 2000 17:16:31 +0100 (MET) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id RAA23768; Sat, 1 Jan 2000 17:16:30 +0100 Message-Id: <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: Re: ida driver in -current and eisa bus attachment To: msmith@freebsd.org (Mike Smith) Date: Sat, 1 Jan 100 17:16:30 +0100 (MET) Cc: freebsd-current@freebsd.org In-Reply-To: <199912312040.MAA02777@mass.cdrom.com> from "Mike Smith" at Dec 31, 99 12:40:04 pm X-Mailer: ELM [version 2.4 PL25 PGP6] 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 wonder what is happening to the ida driver for comapq's smart array > > controller series. > > Work on this driver is stalled owing to the fact that nobody that can and > wants to work on it has access to the Compaq hardware required. You > can't use these controllers except in Compaq systems, which makes things > very difficult. that's true :-( > If someone has a complete system featuring one or more of these > controllers (a mixed PCI/EISA system would be best), there are several > people that could put it to good use. well, as you meight have guesses, i own one of these nice little compaq servers. unfortunatly it is an eisa-only version. the good thing is i own two compaq smart array controllers (right now, one is in the machine) and the computer is accessible via internet. for people willing to develop the drivers, i offer access to this machine since i doubt there are any developters living in my town and sending the server to the states is no option. -- -------------------------------------------------------- And remember: "Life sucks and then you die!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 8:22:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 2510E14DDC for ; Sat, 1 Jan 2000 08:22:30 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 89464 invoked from network); 1 Jan 2000 16:20:45 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.182]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 1 Jan 2000 16:20:45 -0000 Message-ID: <386E2993.64662523@pipeline.ch> Date: Sat, 01 Jan 2000 17:21:39 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Schonefeld Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: ida driver in -current and eisa bus attachment References: <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Schonefeld wrote: [all snipped] Here we go: Sat, 1 Jan 100 17:16:30 +0100 (MET) The first "millenium" bug on our mailing lists! Oliver, how old is your PC? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 9:33:34 2000 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 8083C14C24 for ; Sat, 1 Jan 2000 09:33:32 -0800 (PST) (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 JAA05524; Sat, 1 Jan 2000 09:33:31 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA45198; Sat, 1 Jan 2000 09:33:31 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 1 Jan 2000 09:33:31 -0800 (PST) Message-Id: <200001011733.JAA45198@vashon.polstra.com> To: karl@Denninger.Net Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <19991231225535.A8004@Denninger.Net> References: <19991231225535.A8004@Denninger.Net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991231225535.A8004@Denninger.Net>, Karl Denninger wrote: > > What does (someone) need to do to get this changed out/updated? I can't > send it in as a port, since its part of the base package (setting > it up as a port would be pretty trivial from what I can see) There already _is_ a port of it (net/ntp). And there are hooks in /etc/rc.conf ("xntpd_program") to use the ports version instead of the one in the base system. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 9:38: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id EA1AE15057 for ; Sat, 1 Jan 2000 09:37:59 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id LAA22363; Sat, 1 Jan 2000 11:37:50 -0600 (CST) Message-ID: <20000101113750.B89903@Denninger.Net> Date: Sat, 1 Jan 2000 11:37:50 -0600 From: Karl Denninger To: John Polstra Cc: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <19991231225535.A8004@Denninger.Net> <200001011733.JAA45198@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001011733.JAA45198@vashon.polstra.com>; from John Polstra on Sat, Jan 01, 2000 at 09:33:31AM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 01, 2000 at 09:33:31AM -0800, John Polstra wrote: > In article <19991231225535.A8004@Denninger.Net>, > Karl Denninger wrote: > > > > What does (someone) need to do to get this changed out/updated? I can't > > send it in as a port, since its part of the base package (setting > > it up as a port would be pretty trivial from what I can see) > > There already _is_ a port of it (net/ntp). And there are hooks in > /etc/rc.conf ("xntpd_program") to use the ports version instead of the > one in the base system. > > John Thanks; I just updated /usr/src and saw the changes. This has been broken for a *long* time - at least since the 4.0 branch began. Its definitely a kernel interface problem with the older code; while the adjtime call is being made its not happening and eventually the code executes a "step" instead (which is a bad news; those should basically never happen once xntpd settles down in a day or three after a cold start) It looks like ntpd (the new one) works correctly; I grabbed the latest from the official site last night and by this morning the dispersion and offsets were stable. Ntpd is the "official" code line now - the "x" line is considered deprecated by the official maintainers, so if you're going to support the ntpd line in the base system the other(s) should probably be removed entirely. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 9:47:44 2000 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 36D2814D35 for ; Sat, 1 Jan 2000 09:47:42 -0800 (PST) (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 JAA05592; Sat, 1 Jan 2000 09:47:41 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA45272; Sat, 1 Jan 2000 09:47:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 1 Jan 2000 09:47:40 -0800 (PST) Message-Id: <200001011747.JAA45272@vashon.polstra.com> To: karl@Denninger.Net Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000101113750.B89903@Denninger.Net> References: <19991231225535.A8004@Denninger.Net> <200001011733.JAA45198@vashon.polstra.com> <20000101113750.B89903@Denninger.Net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000101113750.B89903@Denninger.Net>, Karl Denninger wrote: > > It looks like ntpd (the new one) works correctly; I grabbed the latest > from the official site last night and by this morning the dispersion > and offsets were stable. BTW, you might want to add these lines (from LINT) to your kernel config if you haven't already: ##################################################################### # POSIX P1003.1B # Real time extensions added int the 1993 Posix # P1003_1B: Infrastructure # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING # _KPOSIX_VERSION: Version kernel is built for options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" Current versions of ntpd use these features if they're available. I think "_KPOSIX_VERSION=199309L" is the default, so that one probably isn't strictly necessary. > Ntpd is the "official" code line now - the "x" line is considered deprecated > by the official maintainers, so if you're going to support the ntpd line in > the base system the other(s) should probably be removed entirely. I'm sure we'll get there eventually. Things move at a stately pace in -stable. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 9:47:49 2000 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 369F414F68; Sat, 1 Jan 2000 09:47:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA56307; Sat, 1 Jan 2000 10:47:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA24913; Sat, 1 Jan 2000 10:47:35 -0700 (MST) Message-Id: <200001011747.KAA24913@harmony.village.org> To: Andre Oppermann Subject: Re: ida driver in -current and eisa bus attachment Cc: Oliver Schonefeld , Mike Smith , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 Jan 2000 17:21:39 +0100." <386E2993.64662523@pipeline.ch> References: <386E2993.64662523@pipeline.ch> <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> Date: Sat, 01 Jan 2000 10:47:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <386E2993.64662523@pipeline.ch> Andre Oppermann writes: : Sat, 1 Jan 100 17:16:30 +0100 (MET) : Oliver, how old is your PC? It isn't a pc bug, but rather a bug in his mail transfer agent. Someone thought that tm_year was the last two digits of the year rather than year - 1900. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 9:58:51 2000 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 2BE2B14D84; Sat, 1 Jan 2000 09:58:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA61161; Sat, 1 Jan 2000 09:58:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Wilko Bulte Cc: Chuck Robey , Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices (MAKEDEV) In-reply-to: Your message of "Sat, 01 Jan 2000 00:34:24 +0100." <20000101003424.A52465@yedi.iaf.nl> Date: Sat, 01 Jan 2000 09:58:15 -0800 Message-ID: <61158.946749495@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Everything that sysinstall does WRT devs is abstracted by libdisk. > On Fri, Dec 31, 1999 at 03:15:02PM -0500, Chuck Robey wrote: > > On Fri, 31 Dec 1999, Wilko Bulte wrote: > > > > > > > Why are "certain" devices wildly different than all other ones? I've > > > > > never encountered that kind of syntax before, and I can't see that it 's > > > > > documented anywhere at all. Certainly, MAKEDEV itself (in it's > > > > > comments) treats cd* just like all the others, specifying that the nu mber > > > > > following is a unit number, and *not* a quantity. I don't know when this > > > > > happened, but it's surely not obvious. Not one word in the handbook, > > > > > either. > > > > > > > > *shrug* This is the only rationality I could think of. Obviously, thi s > > > > breaks POLA, so it should be changed (with ample warning). > > > > > > As for ample warning: I've seen MAKEDEVs display a list of the devices > > > they are creating. I think the Tru64 version does this. I myself think th is > > > is a good behaviour (and hope people won't start yelling 'bloat' for once ) > > > > I'd like to hack about a bit on MAKEDEV, but I was wondering, does > > sysinstall, in any way, use MAKEDEV? I *don't* want to mess with > > sysinstall! > > :) I guess the only way to find out short of studying sysinstall source code > is asking Jordan. > > -- > Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 10: 4:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 5DAAD15085 for ; Sat, 1 Jan 2000 10:04:24 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 89600 invoked from network); 1 Jan 2000 18:02:40 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.182]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 1 Jan 2000 18:02:40 -0000 Message-ID: <386E4177.EED2724E@pipeline.ch> Date: Sat, 01 Jan 2000 19:03:35 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Oliver Schonefeld , freebsd-current@FreeBSD.ORG Subject: Re: ida driver in -current and eisa bus attachment References: <386E2993.64662523@pipeline.ch> <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> <200001011747.KAA24913@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <386E2993.64662523@pipeline.ch> Andre Oppermann writes: > : Sat, 1 Jan 100 17:16:30 +0100 (MET) > : Oliver, how old is your PC? > > It isn't a pc bug, but rather a bug in his mail transfer agent. Hmm... His MTA looks fine: Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id RAA23768; Sat, 1 Jan 2000 17:16:30 +0100 > Someone thought that tm_year was the last two digits of the year > rather than year - 1900. Is ELM [version 2.4 PL25 PGP6] that much broken? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 10:19:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id 9DA4E14DD4 for ; Sat, 1 Jan 2000 10:19:24 -0800 (PST) (envelope-from oschonef@TechFak.Uni-Bielefeld.DE) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id TAA10583; Sat, 1 Jan 2000 19:19:22 +0100 (MET) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id TAA24115; Sat, 1 Jan 2000 19:19:22 +0100 Message-Id: <200001011819.TAA24115@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: Re: ida driver in -current and eisa bus attachment To: oppermann@pipeline.ch (Andre Oppermann) Date: Sat, 1 Jan 100 19:19:22 +0100 (MET) Cc: freebsd-current@freebsd.org In-Reply-To: <386E4177.EED2724E@pipeline.ch> from "Andre Oppermann" at Jan 1, 0 07:03:35 pm X-Mailer: ELM [version 2.4 PL25 PGP6] 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 Eines schoenen Tages schrieb Andre Oppermann: > > Warner Losh wrote: > > > > In message <386E2993.64662523@pipeline.ch> Andre Oppermann writes: > > : Sat, 1 Jan 100 17:16:30 +0100 (MET) > > : Oliver, how old is your PC? it's not a pc ... it's a sun ultra 1 ... and unfortunatly it's not mine. it belongs to my university :-(( > Is ELM [version 2.4 PL25 PGP6] that much broken? yes ... my elm is propably broken :-) maybe i should consider using mutt or something else ... nut that does not really solve the problem with the compaq array controller ... -- -------------------------------------------------------- And remember: "Life sucks and then you die!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 10:43:22 2000 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 86AE214D52 for ; Sat, 1 Jan 2000 10:43:19 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA56520; Sat, 1 Jan 2000 11:43:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA25196; Sat, 1 Jan 2000 11:43:18 -0700 (MST) Message-Id: <200001011843.LAA25196@harmony.village.org> To: Andre Oppermann Subject: Re: ida driver in -current and eisa bus attachment Cc: Oliver Schonefeld , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 01 Jan 2000 19:03:35 +0100." <386E4177.EED2724E@pipeline.ch> References: <386E4177.EED2724E@pipeline.ch> <386E2993.64662523@pipeline.ch> <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> <200001011747.KAA24913@harmony.village.org> Date: Sat, 01 Jan 2000 11:43:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <386E4177.EED2724E@pipeline.ch> Andre Oppermann writes: : Hmm... His MTA looks fine: MUA. : > Someone thought that tm_year was the last two digits of the year : > rather than year - 1900. : : Is ELM [version 2.4 PL25 PGP6] that much broken? Looks that way... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 11:25:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id 9F92215053 for ; Sat, 1 Jan 2000 11:25:27 -0800 (PST) (envelope-from oschonef@TechFak.Uni-Bielefeld.DE) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id UAA10988; Sat, 1 Jan 2000 20:25:21 +0100 (MET) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id UAA27052; Sat, 1 Jan 2000 20:25:21 +0100 Message-Id: <200001011925.UAA27052@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: Re: ida driver in -current and eisa bus attachment To: imp@village.org (Warner Losh) Date: Sat, 1 Jan 2000 20:25:21 +0100 (MET) Cc: freebsd-current@freebsd.org In-Reply-To: <200001011843.LAA25196@harmony.village.org> from "Warner Losh" at Jan 01, 2000 11:43:18 AM X-Mailer: ELM [version 2.5 PL2] 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 Eines schoenen Tages schrieb Warner Losh: > : > Someone thought that tm_year was the last two digits of the year > : > rather than year - 1900. > : > : Is ELM [version 2.4 PL25 PGP6] that much broken? > > Looks that way... just compiled elm 2.5.2 ... looks to me, that is fixes my "problem" ... but elm is not really a problem on my bsd box, since this mail is written from an account in my university .. they are running sunos ... -- -------------------------------------------------------- And remember: "Life sucks and then you die!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 11:31:20 2000 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 01E4114E7B for ; Sat, 1 Jan 2000 11:31:14 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id UAA03636 for current@freebsd.org; Sat, 1 Jan 2000 20:31:06 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 65DF58864; Sat, 1 Jan 2000 19:41:18 +0100 (CET) Date: Sat, 1 Jan 2000 19:41:18 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000101194118.A19381@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19991231225535.A8004@Denninger.Net> <200001011733.JAA45198@vashon.polstra.com> <20000101113750.B89903@Denninger.Net> <200001011747.JAA45272@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <200001011747.JAA45272@vashon.polstra.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to John Polstra: > Current versions of ntpd use these features if they're available. I The ntpd daemon in -CURRENT doesn't use these as we cannot be sure the user has enabled them. We should make them standard IMO. > I'm sure we'll get there eventually. Things move at a stately > pace in -stable. :-) A MFC would be very straightforward, I already tested what's in CURRENT on a STABLE system. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 11:32:25 2000 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 E599214FD3 for ; Sat, 1 Jan 2000 11:32:22 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA00966; Sat, 1 Jan 2000 13:32:19 -0600 (CST) (envelope-from dan) Date: Sat, 1 Jan 2000 13:32:19 -0600 From: Dan Nelson To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: 2 hours to compile mysql? Message-ID: <20000101133219.C612@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from "Leif Neland" on Sat Jan 1 16:26:44 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 01), Leif Neland said: > So far it has been taking 2 hours to compile sql_yacc.cc from > mysql3.22. > > I had to find an old disk for swap, and it's swapping all the time. > > top shows 156M size and 46M res., run time 20min's for cc1plus. That > probably means it's been waiting for swapping in 1h40m... > > The box is a 333MHz PII, with 64M ram. Do I just need more ram to be > able to compile in reasonable time, or is something broken? You probably need more RAM. sql_yacc.cc is one of those "worst-case" programs as far as gcc is concerned; I don't think gcc can parse large case statements like this efficiently. Adding "--with-low-memory" to your port Makefile, in the CONFIGURE_ARGS line, will help. -- 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 Sat Jan 1 12: 2: 5 2000 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 0E42714FA6 for ; Sat, 1 Jan 2000 12:02:02 -0800 (PST) (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 MAA06009; Sat, 1 Jan 2000 12:02:00 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA45455; Sat, 1 Jan 2000 12:02:00 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 1 Jan 2000 12:02:00 -0800 (PST) Message-Id: <200001012002.MAA45455@vashon.polstra.com> To: roberto@keltia.freenix.fr Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000101194118.A19381@keltia.freenix.fr> References: <19991231225535.A8004@Denninger.Net> <20000101113750.B89903@Denninger.Net> <200001011747.JAA45272@vashon.polstra.com> <20000101194118.A19381@keltia.freenix.fr> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000101194118.A19381@keltia.freenix.fr>, Ollivier Robert wrote: > According to John Polstra: > > Current versions of ntpd use these features if they're available. I > > The ntpd daemon in -CURRENT doesn't use these as we cannot be sure the user > has enabled them. I don't understand why they're disabled in -current. Empirically, it appears that the standard ntpd (from the port) still works fine if the features aren't in the kernel. It emits a warning at start-up time, but then it runs fine after that. > We should make them standard IMO. I agree. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 13: 9:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 1F62814FCD for ; Sat, 1 Jan 2000 13:09:56 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id NAA00322; Sat, 1 Jan 2000 13:09:40 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000101125410.00a976b0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 01 Jan 2000 13:09:40 -0800 To: Cameron Grant , Seigo Tanimura , dmmiller@cvzoom.net From: Manfred Antar Subject: Re: Newpcm is broken again for mpg123 (ESS 1868 isa sound card) Cc: current@FreeBSD.ORG, Seigo Tanimura In-Reply-To: <001f01bf5414$02bbbb80$0304020a@rings> References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386AB7A8.DC369061@cvzoom.net> <14445.33821.200059.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> 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 04:52 AM 1/1/00 +0000, Cameron Grant wrote: > > Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS > > Donn> 1868, of course. Well, I (wisely) saved my old kernel as > > Donn> /kernel.good and just booted into that. > > > > Donn> Could you also say what was fixed if you get around to it? I'd > > Donn> to learn a little more about the sound driver. > > > The following things were in the recent mail of mine: > > > > - All ioctl(2)s go to see the secondary buffer(if I have forget nothing). > > - chn_setblocksize() changes the size of the secondary buffer. > > - chn_mmap() maps the secondary buffer. > > - chn_poll() invokes DMA. > > - chn_wrintr() performs DMA emulation for pcm devices with no DMA > > functionality(requested by nyan). > > - SNDCTL_DSP_SETFRAGMENT handles the count correctly. > > - GETI/OSPACE returns the number of fragments. > > - DMA transfer keeps running upon underrun. Some DSPs seem to end up > > with an unpredictable result if the DMA gets stopped followed by > > immediate restart. This revokes the change in >sys/dev/sound/pcm/channel.c > > rev 1.12. > > - chn_write() and chn_read() returns EAGAIN for nonblocking if there > > are no space to write or data to read. > >the ess problem was a result of me reducing the buffer size to 8k instead of >64k to see what would happen. only ess cards seem to have problems, so it's >back to 64k for them but 8k for other isa cards. > > - cameron I have the same problem with a motherboard with built in Crystal Audio : pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x120-0x127 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 It works fine with revision 1.14 of channel.c and 1.12 of dsp.c and the corresponding header files. The new versions break sound. Example using the rsynth port With old version #say happy new year I get "happy new year" out of spaekers With new version : #say happy new year all that comes out of speakers is "happy" Also other problems occur with new version when playing au files. Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 13:51:43 2000 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 EFE9714CAB; Sat, 1 Jan 2000 13:51:37 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA09754; Sat, 1 Jan 2000 15:51:36 -0600 (CST) Date: Sat, 1 Jan 2000 15:51:36 -0600 From: "Matthew D. Fuller" To: Brian Fundakowski Feldman Cc: Chuck Robey , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices Message-ID: <20000101155136.C3800@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 31, 1999 at 01:45:31AM -0500, a little birdie told me that Brian Fundakowski Feldman remarked > The way certain devices, like cd with its monotonically increasing counter > where devices are probed in order and assigned device based on precedence > and not hardwiring/controller connection, work is consistent between > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > that way. Disks don't, because there is potential for hard-wiring > there, and will often be gaps. FWIW, MAKEDEV for vty's (and pty's too? dunno) works the same. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "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 Sat Jan 1 15: 8: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 5EE2314C45 for ; Sat, 1 Jan 2000 15:07:59 -0800 (PST) (envelope-from leif@neland.dk) Received: from localhost (leif@localhost) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id AAA57087; Sun, 2 Jan 2000 00:07:45 +0100 (CET) (envelope-from leif@neland.dk) Date: Sun, 2 Jan 2000 00:07:45 +0100 (CET) From: Leif Neland To: monty@tcx.se Cc: Paul DuBois , mysql@lists.mysql.com, freebsd-current@freebsd.org Subject: Re: 2 hours to compile mysql? In-Reply-To: <14446.19685.932082.417212@monty.pp.sci.fi> 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 reason for this is that some gcc optimizations stages takes > exponentially more memory when compiling big functions. > bison produces one big function for the grammar parsing and its > this that takes a long time to compile; To compile sql_yacc.cc quickly > on Intel, you nead at least 160M of free ram. On a PentiumII 400mz with 256M > ram, it takes 11 seconds to compile sql_yacc.o. Having to use swap > can easily make things 1000 times slower > Is amount of ram available (portably) to configure? So configure could decide to use --low-memory by itself? Allowing overrides, naturally. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 15:54:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id ED75D14FB9 for ; Sat, 1 Jan 2000 15:54:29 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Sun, 2 Jan 2000 10:47:29 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: gcc compiler problem part deux To: current@FreeBSD.ORG Message-Id: <00Jan2.104729est.40326@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Sun, 2 Jan 2000 10:47:24 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >Last time I checked (I haven't moved to the latest gcc, so I can't >confirm it there), one significant difference between 'cc -E' and >/usr/libexec/cpp was that the latter would read from a pipe, whilst >the former wouldn't. It seems I was wrong. As several people have pointed out, both 'cc -E -' and 'cc -x c -E /dev/stdin' work. I'll crawl back into the woodwork for a while :-). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 16:15:24 2000 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 5D56114D10 for ; Sat, 1 Jan 2000 16:15:20 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA23825; Sun, 2 Jan 2000 01:15:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 09:39:05 CST." <20000101093905.B11872@Denninger.Net> Date: Sun, 02 Jan 2000 01:15:13 +0100 Message-ID: <23804.946772113@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101093905.B11872@Denninger.Net>, Karl Denninger writes: >On Sat, Jan 01, 2000 at 11:11:51AM +0100, Poul-Henning Kamp wrote: >> In message <19991231225535.A8004@Denninger.Net>, Karl Denninger writes: >> >> >This is not a port, its part of the RELEASE! >> > >> >Its several YEARS old, and doesn't work right - you get lots of STEP changes >> >instead of what you SHOULD get, which is a slew on the system clock. >> >> Remember to get the kernel code involved. To do this: >> >> create a driftfile containing "0 1\n" >> start xntpd >> >> That will help. > >No it won't. I've been running xntpd for oh, four or five years now on >various things. Yes, the drift file is there (and has been). Still got the >step time messages. Uhm, Karl, please try to calm down, OK ? I didn't talk about having a driftfile, I talked about using the kernel PLL: ("Remember to get the kernel code involved.") With xntpd the kernel-pll is very optional, in fact only the source tells you that the magic secret second field in your driftfile controls if the kernel-PLL should be used or not. Anyway, ntpd4 is 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 Sat Jan 1 16:17:43 2000 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 B187E15034 for ; Sat, 1 Jan 2000 16:17:29 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA26941; Sun, 2 Jan 2000 01:17:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: karl@Denninger.Net, current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 09:47:40 PST." <200001011747.JAA45272@vashon.polstra.com> Date: Sun, 02 Jan 2000 01:17:15 +0100 Message-ID: <26939.946772235@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001011747.JAA45272@vashon.polstra.com>, John Polstra writes: >In article <20000101113750.B89903@Denninger.Net>, >Karl Denninger wrote: >> >> It looks like ntpd (the new one) works correctly; I grabbed the latest >> from the official site last night and by this morning the dispersion >> and offsets were stable. > >BTW, you might want to add these lines (from LINT) to your kernel >config if you haven't already: > >##################################################################### ># POSIX P1003.1B > ># Real time extensions added int the 1993 Posix ># P1003_1B: Infrastructure ># _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING ># _KPOSIX_VERSION: Version kernel is built for > >options "P1003_1B" >options "_KPOSIX_PRIORITY_SCHEDULING" >options "_KPOSIX_VERSION=199309L" > >Current versions of ntpd use these features if they're available. I >think "_KPOSIX_VERSION=199309L" is the default, so that one probably >isn't strictly necessary. I seriously doubt using these will do anything for NTPDs performance. -- 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 Jan 1 16:25:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 7821D14C16 for ; Sat, 1 Jan 2000 16:25:38 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA17467; Sat, 1 Jan 2000 18:25:18 -0600 (CST) Message-ID: <20000101182518.A17456@Denninger.Net> Date: Sat, 1 Jan 2000 18:25:18 -0600 From: Karl Denninger To: Poul-Henning Kamp , John Polstra Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <200001011747.JAA45272@vashon.polstra.com> <26939.946772235@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <26939.946772235@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 01:17:15AM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 01:17:15AM +0100, Poul-Henning Kamp wrote: > In message <200001011747.JAA45272@vashon.polstra.com>, John Polstra writes: > >In article <20000101113750.B89903@Denninger.Net>, > >Karl Denninger wrote: > >> > >> It looks like ntpd (the new one) works correctly; I grabbed the latest > >> from the official site last night and by this morning the dispersion > >> and offsets were stable. > > > >BTW, you might want to add these lines (from LINT) to your kernel > >config if you haven't already: > > > >##################################################################### > ># POSIX P1003.1B > > > ># Real time extensions added int the 1993 Posix > ># P1003_1B: Infrastructure > ># _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING > ># _KPOSIX_VERSION: Version kernel is built for > > > >options "P1003_1B" > >options "_KPOSIX_PRIORITY_SCHEDULING" > >options "_KPOSIX_VERSION=199309L" > > > >Current versions of ntpd use these features if they're available. I > >think "_KPOSIX_VERSION=199309L" is the default, so that one probably > >isn't strictly necessary. > > I seriously doubt using these will do anything for NTPDs performance. It won't, but it will stop ntpd from bitching in the syslog about them being missing :-) - Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 16:27: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id B721F1501B for ; Sat, 1 Jan 2000 16:27:02 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA17473; Sat, 1 Jan 2000 18:26:50 -0600 (CST) Message-ID: <20000101182650.B17456@Denninger.Net> Date: Sat, 1 Jan 2000 18:26:50 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000101093905.B11872@Denninger.Net> <23804.946772113@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <23804.946772113@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 01:15:13AM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 01:15:13AM +0100, Poul-Henning Kamp wrote: > In message <20000101093905.B11872@Denninger.Net>, Karl Denninger writes: > >On Sat, Jan 01, 2000 at 11:11:51AM +0100, Poul-Henning Kamp wrote: > >> In message <19991231225535.A8004@Denninger.Net>, Karl Denninger writes: > >> > >> >This is not a port, its part of the RELEASE! > >> > > >> >Its several YEARS old, and doesn't work right - you get lots of STEP changes > >> >instead of what you SHOULD get, which is a slew on the system clock. > >> > >> Remember to get the kernel code involved. To do this: > >> > >> create a driftfile containing "0 1\n" > >> start xntpd > >> > >> That will help. > > > >No it won't. I've been running xntpd for oh, four or five years now on > >various things. Yes, the drift file is there (and has been). Still got the > >step time messages. > > Uhm, Karl, please try to calm down, OK ? > > I didn't talk about having a driftfile, I talked about using the kernel > PLL: ("Remember to get the kernel code involved.") > > With xntpd the kernel-pll is very optional, in fact only the source tells > you that the magic secret second field in your driftfile controls if > the kernel-PLL should be used or not. Yes, and my driftfile had that parameter in there. Uhm, Poul, remember I've been at this for just a LITTLE while. Xntpd is something I had deployed back in my *Sun* days (back when FreeBSD was, well, non-existent) > Anyway, ntpd4 is in CURRENT... Now it is. And it works correctly too. Thanks anyway, even with the attitude. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 16:29: 4 2000 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 815EC14D0B for ; Sat, 1 Jan 2000 16:28:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA28368; Sun, 2 Jan 2000 01:28:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: John Polstra , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 18:25:18 CST." <20000101182518.A17456@Denninger.Net> Date: Sun, 02 Jan 2000 01:28:44 +0100 Message-ID: <28366.946772924@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101182518.A17456@Denninger.Net>, Karl Denninger writes: >> >options "P1003_1B" >> >options "_KPOSIX_PRIORITY_SCHEDULING" >> >options "_KPOSIX_VERSION=199309L" >> > >> >Current versions of ntpd use these features if they're available. I >> >think "_KPOSIX_VERSION=199309L" is the default, so that one probably >> >isn't strictly necessary. >> >> I seriously doubt using these will do anything for NTPDs performance. > >It won't, but it will stop ntpd from bitching in the syslog about them being >missing :-) Hm, I actually thought I managed to get somebody to solve that somehow, maybe I didn't quite succeed :-) -- 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 Jan 1 16:30:21 2000 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 1427714F3D for ; Sat, 1 Jan 2000 16:30:17 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id QAA16793; Sat, 1 Jan 2000 16:29:49 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001020029.QAA16793@gndrsh.dnsmgr.net> Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <23804.946772113@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 2, 2000 01:15:13 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 1 Jan 2000 16:29:49 -0800 (PST) Cc: karl@Denninger.Net (Karl Denninger), 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 > In message <20000101093905.B11872@Denninger.Net>, Karl Denninger writes: > >On Sat, Jan 01, 2000 at 11:11:51AM +0100, Poul-Henning Kamp wrote: > >> In message <19991231225535.A8004@Denninger.Net>, Karl Denninger writes: > >> > >> >This is not a port, its part of the RELEASE! > >> > > >> >Its several YEARS old, and doesn't work right - you get lots of STEP changes > >> >instead of what you SHOULD get, which is a slew on the system clock. > >> > >> Remember to get the kernel code involved. To do this: > >> > >> create a driftfile containing "0 1\n" > >> start xntpd > >> > >> That will help. > > > >No it won't. I've been running xntpd for oh, four or five years now on > >various things. Yes, the drift file is there (and has been). Still got the > >step time messages. > > Uhm, Karl, please try to calm down, OK ? > > I didn't talk about having a driftfile, I talked about using the kernel > PLL: ("Remember to get the kernel code involved.") > > With xntpd the kernel-pll is very optional, in fact only the source tells > you that the magic secret second field in your driftfile controls if > the kernel-PLL should be used or not. Does it help in the 3.4-stable version to set the second value in ntpdrift to 1? And why has the manual page never been updated, it is clearly wrong when it talks about the contents of driftfile! :-( > > Anyway, ntpd4 is in CURRENT... Well... that won't help the 20 or so boxes here doing this all the time: Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 1 16:31:36 2000 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 25ED014D74 for ; Sat, 1 Jan 2000 16:31:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA29323; Sun, 2 Jan 2000 01:31:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 18:26:50 CST." <20000101182650.B17456@Denninger.Net> Date: Sun, 02 Jan 2000 01:31:25 +0100 Message-ID: <29321.946773085@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101182650.B17456@Denninger.Net>, Karl Denninger writes: >Yes, and my driftfile had that parameter in there. Uhm, Poul, remember I've >been at this for just a LITTLE while. Xntpd is something I had deployed >back in my *Sun* days (back when FreeBSD was, well, non-existent) Karl, remember who was there too ? :-) >> Anyway, ntpd4 is in CURRENT... > >Now it is. > >And it works correctly too. In general yes, but not if you use the hardpps() with a refclock, it works better after I fixed a couple of almost-mutually-canceling sign-bugs, but the parameters of the hardpps() PLL relative to the FLL are wrong. >Thanks anyway, even with the attitude. Many happy returns :-) -- 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 Jan 1 16:41:31 2000 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 8622F14DF5 for ; Sat, 1 Jan 2000 16:41:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id BAA31432; Sun, 2 Jan 2000 01:41:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Rodney W. Grimes" Cc: karl@Denninger.Net (Karl Denninger), current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 16:29:49 PST." <200001020029.QAA16793@gndrsh.dnsmgr.net> Date: Sun, 02 Jan 2000 01:41:08 +0100 Message-ID: <31430.946773668@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001020029.QAA16793@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes : >Does it help in the 3.4-stable version to set the second value in ntpdrift >to 1? Yes, although I have never checked all the boundary conditions to make sure the kernel-pll is stable over the entire envelope. I'm doing that for the NTPv4/nanokernel combo, and I'm resolving the problems I find with Dave Mills. >And why has the manual page never been updated, it is clearly wrong >when it talks about the contents of driftfile! :-( I updated neither the manpage nor the code because of the above. >> Anyway, ntpd4 is in CURRENT... > >Well... that won't help the 20 or so boxes here doing this all the >time: >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340 Your clock is too sick, (or our calibration of it is hosed), no version of {X}NTP will touch a clock which is outside +/- 500ppm. Could you try to measure the 14.31818... MHz base frequency and the 32768 kHz wristwatch xtal as well (I know you're RadioActive, so I pressume you have a counter ?) If they're both OK, then we have a code problem... -- 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 Jan 1 16:49: 5 2000 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 969E61502B for ; Sat, 1 Jan 2000 16:49:00 -0800 (PST) (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 TAA04373 for ; Sat, 1 Jan 2000 19:48:59 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA27819; Sat, 1 Jan 2000 19:48:29 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id TAA01819 for freebsd-current@freebsd.org; Sat, 1 Jan 2000 19:48:29 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001020048.TAA01819@bb01f39.unx.sas.com> Subject: maxfiles same as maxfilesperproc ?? To: freebsd-current@freebsd.org Date: Sat, 1 Jan 2000 19:48:29 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On a FreeBSD 4.0-19991223-SNAP system... I just ran into a situation that caused me to have to reboot the machine before understanding what had really happenned... The problems comes down to: kern.maxfiles: 4136 kern.maxfilesperproc: 4136 Thus, because I had a root uid server that looped chewing up file descriptors, it also filled up the system file table. I realize this is end-user/administrator fixable, but I'm not sure the default should have these be the same... Thanks, John kernel config below: # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.217 1999/12/19 20:33:05 billf Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident BBKERN maxusers 128 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device 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 SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device 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 SEMMNI=1024 # 1024 semaphore ids options SEMMNS=1024 # 1024 semaphores # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 #controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices controller ata0 at isa? port IO_WD1 irq 14 controller ata1 at isa? port IO_WD2 irq 15 controller ata2 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers # A single entry for any of these controllers (ahb, ahc, amd, ncr, etc...) is # sufficient for any number of installed devices. #controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices #controller amd0 # AMD 53C974 (Teckram DC-390(T)) #controller dpt0 # DPT Smartcache - See LINT for options! #controller isp0 # Qlogic family #controller ncr0 # NCR/Symbios Logic #controller sym0 # NCR/Symbios Logic (do not mix with ncr, it conflicts) #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? #controller aic0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # RAID controllers #device amr0 # AMI MegaRAID #device mlx0 # Mylex DAC960 family # atkbdc0 controls 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 # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console 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 # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at isa? #device pcic1 at isa? # Serial (COM) ports 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 # PCI Ethernet NICs. #device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device tx0 # SMC 9432TX (83c170 ``EPIC'') device vx0 # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. controller miibus0 # MII bus support #device dc0 # DEC/Intel 21143 and various workalikes #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 (``Starfire'') #device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 #device ste0 # Sundance ST201 (D-Link DFE-550TX) #device tl0 # Texas Instruments ThunderLAN #device vr0 # VIA Rhine, Rhine II #device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex0 at isa? port? irq? # NOTE: This removes the isa attachment so that the pccard unit numbers # come out right. device ep0 # WaveLAN/IEEE 802.1 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi0 # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 irq ? #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? irq ? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP #pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 17: 7:37 2000 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 BF16C14E1E for ; Sat, 1 Jan 2000 17:07:32 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id CAA18255 for current@FreeBSD.ORG; Sun, 2 Jan 2000 02:07:28 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6C58F8864; Sun, 2 Jan 2000 02:06:04 +0100 (CET) Date: Sun, 2 Jan 2000 02:06:04 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000102020604.A25645@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <20000101182518.A17456@Denninger.Net> <28366.946772924@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <28366.946772924@critter.freebsd.dk> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > Hm, I actually thought I managed to get somebody to solve that somehow, > maybe I didn't quite succeed :-) I tried to get that patch in but Harlan didn't liked it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 17:27:26 2000 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 B9D8D15015 for ; Sat, 1 Jan 2000 17:27:23 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA16873; Sat, 1 Jan 2000 17:27:11 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001020127.RAA16873@gndrsh.dnsmgr.net> Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <31430.946773668@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 2, 2000 01:41:08 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 1 Jan 2000 17:27:11 -0800 (PST) Cc: karl@Denninger.Net (Karl Denninger), 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 > In message <200001020029.QAA16793@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes > : > > >Does it help in the 3.4-stable version to set the second value in ntpdrift > >to 1? > > Yes, although I have never checked all the boundary conditions > to make sure the kernel-pll is stable over the entire envelope. > > I'm doing that for the NTPv4/nanokernel combo, and I'm resolving > the problems I find with Dave Mills. Keep up the work, hopefully it can be MFC'd soon.... > > >And why has the manual page never been updated, it is clearly wrong > >when it talks about the contents of driftfile! :-( > > I updated neither the manpage nor the code because of the above. > > >> Anyway, ntpd4 is in CURRENT... > > > >Well... that won't help the 20 or so boxes here doing this all the > >time: > >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s > >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s > > (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340 > > Your clock is too sick, (or our calibration of it is hosed), no > version of {X}NTP will touch a clock which is outside +/- 500ppm. I see this on 20 systems... so we need to do some work, even if the clocks really are off that much as it seems this is going to be quite common. > > Could you try to measure the 14.31818... MHz base frequency and > the 32768 kHz wristwatch xtal as well (I know you're RadioActive, > so I pressume you have a counter ?) I'll have to wait tell later this week when I am out at the place all the RadioActive toys are to get my hands on a counter. Alls I have hear are scopes and DMM's, and the scope hasn't seen a cal lab in 20+ years, so I don't trust it for anything like this. :-) > > If they're both OK, then we have a code problem... I'll let you know what I find. Just for grins I restarted a few of them with driftfile="0 1" to see what it does... can't hurt me much :-) -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 1 17:42:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 3AC7214D7C for ; Sat, 1 Jan 2000 17:42:14 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id TAA17589; Sat, 1 Jan 2000 19:42:10 -0600 (CST) Message-ID: <20000101194210.A17585@Denninger.Net> Date: Sat, 1 Jan 2000 19:42:10 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000101182650.B17456@Denninger.Net> <29321.946773085@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <29321.946773085@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 01:31:25AM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 01:31:25AM +0100, Poul-Henning Kamp wrote: > In message <20000101182650.B17456@Denninger.Net>, Karl Denninger writes: > > >Yes, and my driftfile had that parameter in there. Uhm, Poul, remember I've > >been at this for just a LITTLE while. Xntpd is something I had deployed > >back in my *Sun* days (back when FreeBSD was, well, non-existent) > > Karl, remember who was there too ? :-) > > >> Anyway, ntpd4 is in CURRENT... > > > >Now it is. > > > >And it works correctly too. > > In general yes, but not if you use the hardpps() with a refclock, > it works better after I fixed a couple of almost-mutually-canceling > sign-bugs, but the parameters of the hardpps() PLL relative to the > FLL are wrong. You're still a bunch of revs back - the current is either "h" or "i", and it has a bunch of fixes (including one here, I think) > >Thanks anyway, even with the attitude. > > Many happy returns :-) Thy be welcome. -- Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 17:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id A4CA114E83 for ; Sat, 1 Jan 2000 17:43:36 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id TAA17595; Sat, 1 Jan 2000 19:43:18 -0600 (CST) Message-ID: <20000101194318.B17585@Denninger.Net> Date: Sat, 1 Jan 2000 19:43:18 -0600 From: Karl Denninger To: Poul-Henning Kamp , "Rodney W. Grimes" Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <200001020029.QAA16793@gndrsh.dnsmgr.net> <31430.946773668@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <31430.946773668@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 01:41:08AM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 01:41:08AM +0100, Poul-Henning Kamp wrote: > In message <200001020029.QAA16793@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes > : > > >Does it help in the 3.4-stable version to set the second value in ntpdrift > >to 1? > > Yes, although I have never checked all the boundary conditions > to make sure the kernel-pll is stable over the entire envelope. > > I'm doing that for the NTPv4/nanokernel combo, and I'm resolving > the problems I find with Dave Mills. > > >And why has the manual page never been updated, it is clearly wrong > >when it talks about the contents of driftfile! :-( > > I updated neither the manpage nor the code because of the above. > > >> Anyway, ntpd4 is in CURRENT... > > > >Well... that won't help the 20 or so boxes here doing this all the > >time: > >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s > >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s > > (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340 > > Your clock is too sick, (or our calibration of it is hosed), no > version of {X}NTP will touch a clock which is outside +/- 500ppm. > > Could you try to measure the 14.31818... MHz base frequency and > the 32768 kHz wristwatch xtal as well (I know you're RadioActive, > so I pressume you have a counter ?) > > If they're both OK, then we have a code problem... You have a code problem ;-) I can confirm this behavior; its been consistent with xntpd for a LONG time, which is why I raised the issue (it FINALLY got to the top of my "annoyance" list). -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 17:50:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from monty.pp.sci.fi (monty.pp.sci.fi [195.74.24.156]) by hub.freebsd.org (Postfix) with ESMTP id E51ED15024 for ; Sat, 1 Jan 2000 17:50:30 -0800 (PST) (envelope-from monty@monty.pp.sci.fi) Received: (from monty@localhost) by monty.pp.sci.fi (8.9.3/8.8.7) id DAA21424; Sun, 2 Jan 2000 03:50:58 +0200 From: Michael Widenius MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14446.44802.533912.420861@monty.pp.sci.fi> Date: Sun, 2 Jan 2000 03:50:58 +0200 (EET) To: Leif Neland Cc: Paul DuBois , mysql@lists.mysql.com, freebsd-current@freebsd.org Subject: Re: 2 hours to compile mysql? In-Reply-To: References: <14446.19685.932082.417212@monty.pp.sci.fi> X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Reply-To: monty@tcx.se Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Leif" == Leif Neland writes: >> The reason for this is that some gcc optimizations stages takes >> exponentially more memory when compiling big functions. >> bison produces one big function for the grammar parsing and its >> this that takes a long time to compile; To compile sql_yacc.cc quickly >> on Intel, you nead at least 160M of free ram. On a PentiumII 400mz with 256M >> ram, it takes 11 seconds to compile sql_yacc.o. Having to use swap >> can easily make things 1000 times slower >> Leif> Is amount of ram available (portably) to configure? I don't think thats easy to check for.. Aother problem is also that even if you have only little ram, you may still want to compile MySQL without --low-memory, because the final code is much better if you don't have to use --low-memory. Leif> So configure could decide to use --low-memory by itself? Allowing Leif> overrides, naturally. Leif> Leif Regards, Monty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 18:49:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 38DEB14F3D for ; Sat, 1 Jan 2000 18:49:32 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id LAA20673 for ; Sun, 2 Jan 2000 11:49:30 +0900 (JST) Received: from rhea.sky.rim.or.jp by mail1.rim.or.jp (8.9.3+Sun/3.7W/) id LAA09100; Sun, 2 Jan 2000 11:49:28 +0900 (JST) (envelope-from kuriyama@sky.rim.or.jp) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id LAA18504 for ; Sun, 2 Jan 2000 11:49:27 +0900 (JST) Date: Sun, 02 Jan 2000 11:49:18 +0900 Message-ID: <14446.48302.292419.80479F@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: panic at kern/uipc_socket2.c User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know what I did at that time, but my box is panic'ed with this message. ----- Jan 1 16:19:21 leda kernel: panic: sbflush: cc 0 || mb 0xc05a7400 || mbcnt 256 ----- It seems that this message is created by sbflush() in kern/uipc_socket2.c. Should I add some hooks into this function to display details preparing for when I get this panic()? Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 1 20: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id DEDE114C0F for ; Sat, 1 Jan 2000 20:05:06 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id XAA25924; Sat, 1 Jan 2000 23:03:39 -0500 (EST) Date: Sat, 1 Jan 2000 23:03:39 -0500 (EST) From: Bosko Milekic To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c In-Reply-To: <14446.48302.292419.80479F@localhost.sky.rim.or.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, 2 Jan 2000, Jun Kuriyama wrote: !> !>I don't know what I did at that time, but my box is panic'ed with this !>message. !> !>----- !>Jan 1 16:19:21 leda kernel: panic: sbflush: cc 0 || mb 0xc05a7400 || mbcnt 256 !>----- !> !>It seems that this message is created by sbflush() in !>kern/uipc_socket2.c. !> !>Should I add some hooks into this function to display details !>preparing for when I get this panic()? !> !> !>Jun Kuriyama // kuriyama@sky.rim.or.jp !> // kuriyama@FreeBSD.org !> You don't happen to have a backtrace? Was anything particular happening at the time of the crash? Do you have any way to not necessarily directly reproduce the panic but rather "force" it to happen (e.g. as a consequence of execution of something or, even as a result of some external "trigger")? -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 0:57:41 2000 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 71F2014C44 for ; Sun, 2 Jan 2000 00:57:32 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id AAA20182; Sun, 2 Jan 2000 00:57:15 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 00:57:15 -0800 Date: Sun, 2 Jan 2000 00:57:15 -0800 (PST) From: Kip Macy To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: maxfiles same as maxfilesperproc ?? In-Reply-To: <200001020048.TAA01819@bb01f39.unx.sas.com> 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: jwd@unx.sas.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 I made the same comment several months ago and received a rather cool reception. I was simply told to change it to my liking in login.conf. -Kip On Sat, 1 Jan 2000, John W. DeBoskey wrote: > Hi, > > On a FreeBSD 4.0-19991223-SNAP system... > > I just ran into a situation that caused me to have to reboot > the machine before understanding what had really happenned... > > The problems comes down to: > > kern.maxfiles: 4136 > kern.maxfilesperproc: 4136 > > > Thus, because I had a root uid server that looped chewing > up file descriptors, it also filled up the system file table. > > I realize this is end-user/administrator fixable, but I'm > not sure the default should have these be the same... > > Thanks, > John > > kernel config below: > > # > # For more information on this file, please read the handbook section on > # Kernel Configuration Files: > # > # http://www.freebsd.org/handbook/kernelconfig-config.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the ./LINT configuration file. If you are > # in doubt as to the purpose or necessity of a line, check first in LINT. > # > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.217 1999/12/19 20:33:05 billf Exp $ > > machine i386 > #cpu I386_CPU > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident BBKERN > maxusers 128 > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options MFS #Memory Filesystem > options MD_ROOT #MD is a potential root device > 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 SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device > 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 SEMMNI=1024 # 1024 semaphore ids > options SEMMNS=1024 # 1024 semaphores > > # To make an SMP kernel, the next two are needed > #options SMP # Symmetric MultiProcessor Kernel > #options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > #options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > controller isa0 > #controller eisa0 > controller pci0 > > # Floppy drives > controller fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > device fd1 at fdc0 drive 1 > > # ATA and ATAPI devices > controller ata0 at isa? port IO_WD1 irq 14 > controller ata1 at isa? port IO_WD2 irq 15 > controller ata2 > device atadisk0 # ATA disk drives > device atapicd0 # ATAPI CDROM drives > device atapifd0 # ATAPI floppy drives > device atapist0 # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > # SCSI Controllers > # A single entry for any of these controllers (ahb, ahc, amd, ncr, etc...) is > # sufficient for any number of installed devices. > #controller ahb0 # EISA AHA1742 family > controller ahc0 # AHA2940 and onboard AIC7xxx devices > #controller amd0 # AMD 53C974 (Teckram DC-390(T)) > #controller dpt0 # DPT Smartcache - See LINT for options! > #controller isp0 # Qlogic family > #controller ncr0 # NCR/Symbios Logic > #controller sym0 # NCR/Symbios Logic (do not mix with ncr, it conflicts) > > #controller adv0 at isa? port ? irq ? > #controller adw0 > #controller bt0 at isa? port ? irq ? > #controller aha0 at isa? port ? irq ? > #controller aic0 at isa? port ? irq ? > > # SCSI peripherals > # Only one of each of these is needed, they are dynamically allocated. > controller scbus0 # SCSI bus (required) > device da0 # Direct Access (disks) > device sa0 # Sequential Access (tape etc) > device cd0 # CD > device pass0 # Passthrough device (direct SCSI access) > > # RAID controllers > #device amr0 # AMI MegaRAID > #device mlx0 # Mylex DAC960 family > > # atkbdc0 controls 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 > > # splash screen/screen saver > pseudo-device splash > > # syscons is the default console driver, resembling an SCO console > 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 > # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines > #options PCVT_SCANSET=2 # IBM keyboards are non-std > > # Floating point support - do not disable. > device npx0 at nexus? port IO_NPX irq 13 > > # Power management support (see LINT for more options) > #device apm0 at nexus? disable flags 0x20 # Advanced Power Management > > # PCCARD (PCMCIA) support > #controller card0 > #device pcic0 at isa? > #device pcic1 at isa? > > # Serial (COM) ports > 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 > > > # PCI Ethernet NICs. > #device de0 # DEC/Intel DC21x4x (``Tulip'') > device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) > #device tx0 # SMC 9432TX (83c170 ``EPIC'') > device vx0 # 3Com 3c590, 3c595 (``Vortex'') > > # PCI Ethernet NICs that use the common MII bus controller code. > controller miibus0 # MII bus support > #device dc0 # DEC/Intel 21143 and various workalikes > #device rl0 # RealTek 8129/8139 > #device sf0 # Adaptec AIC-6915 (``Starfire'') > #device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 > #device ste0 # Sundance ST201 (D-Link DFE-550TX) > #device tl0 # Texas Instruments ThunderLAN > #device vr0 # VIA Rhine, Rhine II > #device wb0 # Winbond W89C840F > device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # ISA Ethernet NICs. > #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > #device ex0 at isa? port? irq? > # NOTE: This removes the isa attachment so that the pccard unit numbers > # come out right. > device ep0 > # WaveLAN/IEEE 802.1 wireless NICs. Note: the WaveLAN/IEEE really > # exists only as a PCMCIA device, so there is no ISA attatement needed > # and resources will always be dynamically assigned by the pccard code. > #device wi0 > # The probe order of these is presently determined by i386/isa/isa_compat.c. > #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 > #device fe0 at isa? port 0x300 irq ? > #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 > #device lnc0 at isa? port 0x280 irq 10 drq 0 > #device cs0 at isa? port 0x300 irq ? > #device sn0 at isa? port 0x300 irq 10 > # requires PCCARD (PCMCIA) support to be activated > #device xe0 at isa? port? irq ? > > # Pseudo devices - the number indicates how many units to allocated. > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > #pseudo-device sl 1 # Kernel SLIP > pseudo-device ppp 1 # Kernel PPP > #pseudo-device tun # Packet tunnel. > pseudo-device pty # Pseudo-ttys (telnet etc) > pseudo-device md # Memory "disks" > > # The `bpf' pseudo-device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > pseudo-device bpf #Berkeley packet filter > > # USB support > #controller uhci0 # UHCI PCI->USB interface > #controller ohci0 # OHCI 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 > > > 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 Jan 2 2:18:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 5093514C7F; Sun, 2 Jan 2000 02:18:56 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA33626; Sun, 2 Jan 2000 02:18:55 -0800 (PST) Date: Sun, 2 Jan 2000 02:18:55 -0800 (PST) From: Julian Elischer To: ports@freebsd.org Cc: current@freebsd.org Subject: Re: new package set for Y2K In-Reply-To: <200001010923.BAA16585@bubble.didi.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 you may want to check the xspread port last I checked (a few weeks a go) it couldn;t handle dates past 1999 (possibly also ss and sc as they are related) julian On Sat, 1 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > Hi All, > > To celebrate the last year of the millenium (*), I built a new package > set for 4-current. You can find it at > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/ > > Since this is the first build with the signal changes, there have > been many changes to 4-current and thus many more breakages than > before. You can find those at > > http://bento.FreeBSD.org/errorlogs/errorlogs/e.4.19991230/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 3:20:53 2000 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 0C57314DF2 for ; Sun, 2 Jan 2000 03:20:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA50508; Sun, 2 Jan 2000 12:20:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 19:42:10 CST." <20000101194210.A17585@Denninger.Net> Date: Sun, 02 Jan 2000 12:20:35 +0100 Message-ID: <50506.946812035@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101194210.A17585@Denninger.Net>, Karl Denninger writes: >> >> Anyway, ntpd4 is in CURRENT... >> > >> >Now it is. >> > >> >And it works correctly too. >> >> In general yes, but not if you use the hardpps() with a refclock, >> it works better after I fixed a couple of almost-mutually-canceling >> sign-bugs, but the parameters of the hardpps() PLL relative to the >> FLL are wrong. > >You're still a bunch of revs back - the current is either "h" or "i", and it >has a bunch of fixes (including one here, I think) No, the NTP distribution doesn't contain the kernel code, it only interfaces to it. I'm sure Ollivier will upgrade us every so often now :-) -- 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 Jan 2 3:22:54 2000 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 9299114F1A for ; Sun, 2 Jan 2000 03:22:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA50521; Sun, 2 Jan 2000 12:22:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sat, 01 Jan 2000 19:43:18 CST." <20000101194318.B17585@Denninger.Net> Date: Sun, 02 Jan 2000 12:22:38 +0100 Message-ID: <50519.946812158@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000101194318.B17585@Denninger.Net>, Karl Denninger writes: >> >Well... that won't help the 20 or so boxes here doing this all the >> >time: >> >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s >> >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s >> >> (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340 >> >> Your clock is too sick, (or our calibration of it is hosed), no >> version of {X}NTP will touch a clock which is outside +/- 500ppm. >> >> Could you try to measure the 14.31818... MHz base frequency and >> the 32768 kHz wristwatch xtal as well (I know you're RadioActive, >> so I pressume you have a counter ?) >> >> If they're both OK, then we have a code problem... > >You have a code problem ;-) If you have access to a frequency counter, could you try to make the same measurements please ? Do you have any refclocks we can use to measure against ? -- 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 Jan 2 3:41:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 28A4D14BCC for ; Sun, 2 Jan 2000 03:41:07 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 6214618 invoked from network); 2 Jan 2000 11:41:11 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 2 Jan 2000 11:41:11 -0000 Message-ID: <386F398C.20F61BB5@cybercable.fr> Date: Sun, 02 Jan 2000 12:42:04 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Weird interaction between cvs and a recent kernel References: <20000101093905.B11872@Denninger.Net> <23804.946772113@critter.freebsd.dk> <20000101182650.B17456@Denninger.Net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm rebuilding my -Current box. it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT snapshot. I have on another box the full repository of FreeBSD (source, ports, docs, ...) on another box, running 3.3-Stable and exporting the repository via NFS. I've tried to remake the world to the latest sources I had (got on 12/31 around 4PM GMT). I can't get the "cvs co src" to finish properly : each time I launch "cvs co src", the kernel crashes with page fault while in supervisor mode : page not present (I don't have a serial console, so this is not the full message). The instruction address for the faulting instruction is always the same, in the "generic_bzero" (from a "nm" run on the kernel). The running process is always "cvs". I have been able to check the sources out (one subdirectory after another) and the machine has completed a full make world. I also run the corresponding kernel. with the new sources, there is the same problem with cvs : I have not been able to check out the ports tree in one step (same error, in the same routine). The machine works fine : I have just completed a X11 3.3.5 build. As I have got plenty of RAM, I'm not quite sure a full crash dump would be usable. Open to any suggestions TfH PS : dmesg for the box : Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 2 10:07:04 CET 2000 root@multi.herbelot.nom:/usr/src/sys/compile/multiUP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 402653184 (393216K bytes) config> q avail memory = 387637248 (378552K bytes) Preloaded elf kernel "kernel" at 0xc02be000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02be09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 5 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 12 chip1: at device 7.3 on pci0 ed0: irq 10 at device 13.0 on pci0 ed0: address 00:4f:49:08:17:72, type NE2000 (16 bit) ata-pci1: irq 11 at device 19.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xd800 irq 11 on ata-pci1 ata-pci2: irq 11 at device 19.1 on pci0 ata-pci2: Busmastering DMA supported devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed1: not probed (disabled) unknown: can't assign resources unknown0: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b, 0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0xf0-0xff irq 13 on isa0 unknown4: at iomem 0-0x9ffff,0xfffe0000-0xffffffff, 0xfec00000-0xfec0ffff,0xfee00000-0xfee0ffff,0x100000-0x17ffffff on isa0 unknown5: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff, 0xf8000-0xfffff,0xd1800-0xd3fff on isa0 unknown6: at port 0x294-0x297,0x4d0-0x4d1,0xcf8-0xcff, 0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad2: ATA-4 disk at ata1 as master ad2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 32 depth queue, UDMA33 ad4: ATA-5 disk at ata2 as master ad4: 17418MB (35673120 sectors), 35390 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 Mounting root from ufs:/dev/ad4s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 7:42:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id F0ED914D24 for ; Sun, 2 Jan 2000 07:42:08 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id JAA22748; Sun, 2 Jan 2000 09:42:05 -0600 (CST) Message-ID: <20000102094205.A22738@Denninger.Net> Date: Sun, 2 Jan 2000 09:42:05 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000101194210.A17585@Denninger.Net> <50506.946812035@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <50506.946812035@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 12:20:35PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 12:20:35PM +0100, Poul-Henning Kamp wrote: > In message <20000101194210.A17585@Denninger.Net>, Karl Denninger writes: > > >> >> Anyway, ntpd4 is in CURRENT... > >> > > >> >Now it is. > >> > > >> >And it works correctly too. > >> > >> In general yes, but not if you use the hardpps() with a refclock, > >> it works better after I fixed a couple of almost-mutually-canceling > >> sign-bugs, but the parameters of the hardpps() PLL relative to the > >> FLL are wrong. > > > >You're still a bunch of revs back - the current is either "h" or "i", and it > >has a bunch of fixes (including one here, I think) > > No, the NTP distribution doesn't contain the kernel code, it only interfaces > to it. Well yes.... you're saying that the bug was *in* the kernel and not ntpd then? Ok.. > I'm sure Ollivier will upgrade us every so often now :-) No problem. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 7:45:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 390091507C for ; Sun, 2 Jan 2000 07:45:15 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id JAA22754; Sun, 2 Jan 2000 09:45:00 -0600 (CST) Message-ID: <20000102094459.B22738@Denninger.Net> Date: Sun, 2 Jan 2000 09:44:59 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000101194318.B17585@Denninger.Net> <50519.946812158@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <50519.946812158@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 12:22:38PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 12:22:38PM +0100, Poul-Henning Kamp wrote: > In message <20000101194318.B17585@Denninger.Net>, Karl Denninger writes: > > >> >Well... that won't help the 20 or so boxes here doing this all the > >> >time: > >> >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s > >> >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s > >> > >> (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340 > >> > >> Your clock is too sick, (or our calibration of it is hosed), no > >> version of {X}NTP will touch a clock which is outside +/- 500ppm. > >> > >> Could you try to measure the 14.31818... MHz base frequency and > >> the 32768 kHz wristwatch xtal as well (I know you're RadioActive, > >> so I pressume you have a counter ?) > >> > >> If they're both OK, then we have a code problem... > > > >You have a code problem ;-) > > If you have access to a frequency counter, could you try to make the > same measurements please ? I don't have one handy, BUT I saw this SAME problem across oh, 20 machines. Every one. Every time. And oh, by the way, when one of them (mine) was upgraded to the newest ntpd, it *WENT AWAY*. Thus, I think its quite reasonable to say its not the clock and must be the code (since the hardware could not have magically changed :-) > Do you have any refclocks we can use to measure against ? Had one at MCS (Spectracom WWV receiver), but its there and I'm here. It appears from their strata change (from 1 to 2; I chime off them) that they turned it off. I should have taken it with me when I left :-) BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver that (1) has an external-able antenna that will work with somewhere between 50 and 100 feet of lead, and (2) has the appropriate pps outputs and such so it can be used for this? -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 7:56: 1 2000 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 BB26614E51 for ; Sun, 2 Jan 2000 07:55:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA08428; Sun, 2 Jan 2000 16:55:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 09:44:59 CST." <20000102094459.B22738@Denninger.Net> Date: Sun, 02 Jan 2000 16:55:44 +0100 Message-ID: <8426.946828544@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver >that (1) has an external-able antenna that will work with somewhere between >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such >so it can be used for this? I will (as always) recommend the Motorola Oncore UT+. If you buy it from syngergy-gps it comes mounted in their nice box and the cable has the PPS on DCD and is ready to plug into a serial port. I paid $605.73 for the one I'm delivering to the Danish Internet eXchange point, that included antenna and 15m of cable. -- 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 Jan 2 8:17:34 2000 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 5DA3914D24 for ; Sun, 2 Jan 2000 08:17:32 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id RAA23018 for current@FreeBSD.ORG; Sun, 2 Jan 2000 17:17:31 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 577518864; Sun, 2 Jan 2000 16:34:04 +0100 (CET) Date: Sun, 2 Jan 2000 16:34:04 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000102163404.A30092@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <20000101194210.A17585@Denninger.Net> <50506.946812035@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <50506.946812035@critter.freebsd.dk> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > I'm sure Ollivier will upgrade us every so often now :-) '98i' looks like a nice release candidate and will probably become 4.1.0 soon. I'll update us to that level of course. Still no feature freeze for 4.0 BTW? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 8:26:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id DC81514BE9 for ; Sun, 2 Jan 2000 08:26:03 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id BAA21871 for ; Mon, 3 Jan 2000 01:26:02 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id BAA01242; Mon, 3 Jan 2000 01:26:01 +0900 (JST) Received: from localhost ([192.168.245.156]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id BAA21100; Mon, 3 Jan 2000 01:25:59 +0900 (JST) To: freebsd-current@freebsd.org Subject: [solicite review and confirmation of tcp for IPv6 patches] X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000103012633S.shin@nd.net.fujitsu.co.jp> Date: Mon, 03 Jan 2000 01:26:33 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 23 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I prepared tcp for IPv6 patches to the current. I would like it to be reviewed and confirmed in many environment before committing it, because I think updating tcp code is very critical to system stability. (Apps for tcp/IPv6 is not yet ready, but I think confirming that it doesn't harmful to IPv4 environment is important at first.) The patches are placed below. http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.20000103 http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228 Anyone interested, please give me comments for them or please try to apply those patches to some of your freebsd-current machines. Either confimation on INET6 defined kernel and INET6 non defined kernel will be helpful. Thanks in advance, Yoshinobu Inoue KAME project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 8:27: 2 2000 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 75DF514BE5 for ; Sun, 2 Jan 2000 08:26:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA08527; Sun, 2 Jan 2000 17:26:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 16:34:04 +0100." <20000102163404.A30092@keltia.freenix.fr> Date: Sun, 02 Jan 2000 17:26:55 +0100 Message-ID: <8525.946830415@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102163404.A30092@keltia.freenix.fr>, Ollivier Robert writes: >According to Poul-Henning Kamp: >> I'm sure Ollivier will upgrade us every so often now :-) > >'98i' looks like a nice release candidate and will probably become 4.1.0 >soon. I'll update us to that level of course. > >Still no feature freeze for 4.0 BTW? Feature freeze is in effect I think, but minor upgrades and bugfixes are not only allowed, they're mandatory :-) -- 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 Jan 2 8:37:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 472F114D24 for ; Sun, 2 Jan 2000 08:37:40 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id KAA23008; Sun, 2 Jan 2000 10:37:33 -0600 (CST) Message-ID: <20000102103732.A23004@Denninger.Net> Date: Sun, 2 Jan 2000 10:37:32 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <8426.946828544@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 04:55:44PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: > > >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver > >that (1) has an external-able antenna that will work with somewhere between > >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such > >so it can be used for this? > > I will (as always) recommend the Motorola Oncore UT+. If you buy it > from syngergy-gps it comes mounted in their nice box and the cable > has the PPS on DCD and is ready to plug into a serial port. I paid > $605.73 for the one I'm delivering to the Danish Internet eXchange > point, that included antenna and 15m of cable. That's EXPENSIVE. Common handheld GPS units with NEMA outputs on them are well under $200 these days! -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 8:42:36 2000 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 030AF14CB4 for ; Sun, 2 Jan 2000 08:42:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id RAA08600; Sun, 2 Jan 2000 17:42:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 10:37:32 CST." <20000102103732.A23004@Denninger.Net> Date: Sun, 02 Jan 2000 17:42:24 +0100 Message-ID: <8598.946831344@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102103732.A23004@Denninger.Net>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: >> >> >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver >> >that (1) has an external-able antenna that will work with somewhere between >> >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such >> >so it can be used for this? >> >> I will (as always) recommend the Motorola Oncore UT+. If you buy it >> from syngergy-gps it comes mounted in their nice box and the cable >> has the PPS on DCD and is ready to plug into a serial port. I paid >> $605.73 for the one I'm delivering to the Danish Internet eXchange >> point, that included antenna and 15m of cable. > >That's EXPENSIVE. > >Common handheld GPS units with NEMA outputs on them are well under $200 >these days! Common handheld GPS units are pointless as NTP refclocks because they lack (a decent) PPS output. -- 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 Jan 2 8:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 888D514EB0 for ; Sun, 2 Jan 2000 08:49:39 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id KAA23046; Sun, 2 Jan 2000 10:49:32 -0600 (CST) Message-ID: <20000102104932.B23036@Denninger.Net> Date: Sun, 2 Jan 2000 10:49:32 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102103732.A23004@Denninger.Net> <8598.946831344@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <8598.946831344@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 05:42:24PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That sucks severely - NONE of the common units have the PPS output?! Barf. Oh well. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 05:42:24PM +0100, Poul-Henning Kamp wrote: > In message <20000102103732.A23004@Denninger.Net>, Karl Denninger writes: > >On Sun, Jan 02, 2000 at 04:55:44PM +0100, Poul-Henning Kamp wrote: > >> > >> >BTW, speaking of which, does anyone know of a reasonably-cheap GPS receiver > >> >that (1) has an external-able antenna that will work with somewhere between > >> >50 and 100 feet of lead, and (2) has the appropriate pps outputs and such > >> >so it can be used for this? > >> > >> I will (as always) recommend the Motorola Oncore UT+. If you buy it > >> from syngergy-gps it comes mounted in their nice box and the cable > >> has the PPS on DCD and is ready to plug into a serial port. I paid > >> $605.73 for the one I'm delivering to the Danish Internet eXchange > >> point, that included antenna and 15m of cable. > > > >That's EXPENSIVE. > > > >Common handheld GPS units with NEMA outputs on them are well under $200 > >these days! > > Common handheld GPS units are pointless as NTP refclocks because they > lack (a decent) PPS output. > > -- > 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 Jan 2 11: 1:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon2.gun.de [192.109.159.15]) by hub.freebsd.org (Postfix) with ESMTP id E66F414DC1 for ; Sun, 2 Jan 2000 11:01:29 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id UAA00991 for ; Sun, 2 Jan 2000 20:01:26 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id UAA01911 for current@FreeBSD.ORG; Sun, 2 Jan 2000 20:00:03 +0100 (CET) (envelope-from andreas) Date: Sun, 2 Jan 2000 20:00:03 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: several procmail jobs hang ... Message-ID: <20000102200003.A1618@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few days ago I updated -current and build /usr/local completely new. One remaining problem is, that procmail jobs seems to hang. First it was a port problem, I installed some (for me) basic services in /home/local and procmail tried to call /usr/local/bin/formail. Now I recompiled procmail using normal /usr/local as PREFIX, but the jobs still hang. After some time they seem to timeout and mail seems to be delivered. Can't say exactly if I have some mail loss. Here, what a ps -axuww shows. andreas 1038 0.0 0.5 1024 704 ?? INs 7:28PM 0:00.03 procmail -f owner -freebsd-chat@FreeBSD.ORG -Y -a -d andreas andreas 1039 0.0 0.5 1024 704 ?? RN 7:28PM 0:00.00 procmail -f owner -freebsd-chat@FreeBSD.ORG -Y -a -d andreas andreas 1041 0.0 0.5 1024 704 ?? SNs 7:28PM 0:00.59 procmail -f owner -freebsd-ports@FreeBSD.ORG -Y -a -d andreas andreas 1338 0.0 0.5 1024 704 ?? INs 7:45PM 0:00.02 procmail -f owner -freebsd-chat@FreeBSD.ORG -Y -a -d andreas andreas 1339 0.0 0.5 1024 704 ?? RN 7:45PM 0:00.00 procmail -f owner -freebsd-chat@FreeBSD.ORG -Y -a -d andreas andreas 1612 0.0 0.5 1024 712 ?? SNs 7:53PM 0:00.04 procmail -f owner -de-bsd-questions@DE.FreeBSD.ORG -Y -a -d andreas root@titan{1006} $ ps -axuww | grep sendmail root 173 0.0 0.7 1372 1060 ?? Is 7:16PM 0:00.15 sendmail: accepti ng connections on port 25 (sendmail) root 1035 0.0 0.7 1420 1124 ?? I 7:28PM 0:00.10 /usr/sbin/sendmai l -oee -odi -oi -pUUCP -fowner-freebsd-chat@FreeBSD.ORG andreas@klemm.gtn.com root 1040 0.0 0.7 1420 1120 ?? I 7:28PM 0:00.09 /usr/sbin/sendmai l -oee -odi -oi -pUUCP -fowner-freebsd-ports@FreeBSD.ORG andreas@klemm.gtn.com root 1337 0.0 0.7 1420 1124 ?? I 7:45PM 0:00.08 /usr/sbin/sendmai l -oee -odi -oi -pUUCP -fowner-freebsd-chat@FreeBSD.ORG andreas@klemm.gtn.com root 1611 0.0 0.7 1420 1128 ?? I 7:53PM 0:00.09 /usr/sbin/sendmai l -oee -odi -oi -pUUCP -fowner-de-bsd-questions@DE.FreeBSD.ORG andreas@klemm.gtn .com When recompiling procmail I noticed, that procmail port has been updated as well. Is this port related or might this be due to signal changes in current, which I read shortly in the lists ??? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 11:10:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon2.gun.de [192.109.159.15]) by hub.freebsd.org (Postfix) with ESMTP id 5623314DC1; Sun, 2 Jan 2000 11:10:49 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id UAA01360; Sun, 2 Jan 2000 20:10:45 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id UAA04622; Sun, 2 Jan 2000 20:10:39 +0100 (CET) (envelope-from andreas) Date: Sun, 2 Jan 2000 20:10:39 +0100 From: Andreas Klemm To: Andreas Klemm Cc: current@FreeBSD.org, ache@FreeBSD.org Subject: Re: several procmail jobs hang ... Message-ID: <20000102201039.A4336@titan.klemm.gtn.com> References: <20000102200003.A1618@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000102200003.A1618@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Sun, Jan 02, 2000 at 08:00:03PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, found out, that I don't have any problems using the previous version of procmail 3.13.1. So it's solved for me now. The remaining question is, is this a procmail 3.14 bug, or does the new procmail version introduce some new features in area where in -current is something wrong. Not easy to say for me ... Remains to tell Andrey, that new procmail port is broken for -current. Andreas /// On Sun, Jan 02, 2000 at 08:00:03PM +0100, Andreas Klemm wrote: > A few days ago I updated -current and build /usr/local completely new. > One remaining problem is, that procmail jobs seems to hang. > First it was a port problem, I installed some (for me) basic services > in /home/local and procmail tried to call /usr/local/bin/formail. > Now I recompiled procmail using normal /usr/local as PREFIX, but > the jobs still hang. After some time they seem to timeout and > mail seems to be delivered. Can't say exactly if I have some mail > loss. > > Here, what a ps -axuww shows. > > andreas 1038 0.0 0.5 1024 704 ?? INs 7:28PM 0:00.03 procmail -f owner > -freebsd-chat@FreeBSD.ORG -Y -a -d andreas > andreas 1039 0.0 0.5 1024 704 ?? RN 7:28PM 0:00.00 procmail -f owner > -freebsd-chat@FreeBSD.ORG -Y -a -d andreas > andreas 1041 0.0 0.5 1024 704 ?? SNs 7:28PM 0:00.59 procmail -f owner > -freebsd-ports@FreeBSD.ORG -Y -a -d andreas > andreas 1338 0.0 0.5 1024 704 ?? INs 7:45PM 0:00.02 procmail -f owner > -freebsd-chat@FreeBSD.ORG -Y -a -d andreas > andreas 1339 0.0 0.5 1024 704 ?? RN 7:45PM 0:00.00 procmail -f owner > -freebsd-chat@FreeBSD.ORG -Y -a -d andreas > andreas 1612 0.0 0.5 1024 712 ?? SNs 7:53PM 0:00.04 procmail -f owner > -de-bsd-questions@DE.FreeBSD.ORG -Y -a -d andreas > root@titan{1006} $ ps -axuww | grep sendmail > root 173 0.0 0.7 1372 1060 ?? Is 7:16PM 0:00.15 sendmail: accepti > ng connections on port 25 (sendmail) > root 1035 0.0 0.7 1420 1124 ?? I 7:28PM 0:00.10 /usr/sbin/sendmai > l -oee -odi -oi -pUUCP -fowner-freebsd-chat@FreeBSD.ORG andreas@klemm.gtn.com > root 1040 0.0 0.7 1420 1120 ?? I 7:28PM 0:00.09 /usr/sbin/sendmai > l -oee -odi -oi -pUUCP -fowner-freebsd-ports@FreeBSD.ORG andreas@klemm.gtn.com > root 1337 0.0 0.7 1420 1124 ?? I 7:45PM 0:00.08 /usr/sbin/sendmai > l -oee -odi -oi -pUUCP -fowner-freebsd-chat@FreeBSD.ORG andreas@klemm.gtn.com > root 1611 0.0 0.7 1420 1128 ?? I 7:53PM 0:00.09 /usr/sbin/sendmai > l -oee -odi -oi -pUUCP -fowner-de-bsd-questions@DE.FreeBSD.ORG andreas@klemm.gtn > .com > > When recompiling procmail I noticed, that procmail port has been > updated as well. > > Is this port related or might this be due to signal changes in current, > which I read shortly in the lists ??? > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > http://www.freebsd.org/~fsmp/SMP/SMP.html > powered by Symmetric MultiProcessor FreeBSD > Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 12:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 7BCC614C15 for ; Sun, 2 Jan 2000 12:19:32 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 2 Jan 2000 12:19:31 -0800 From: "David Schwartz" To: "Karl Denninger" , "Poul-Henning Kamp" Cc: Subject: RE: xntpd - VERY old folks, how about updating? :-) Date: Sun, 2 Jan 2000 12:19:30 -0800 Message-ID: <000501bf555e$ad254190$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <20000102104932.B23036@Denninger.Net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That sucks severely - NONE of the common units have the PPS output?! > > Barf. Oh well. Many of them do, but it's still not meant for precision timekeeping and the exact relationship between its PPS pulse edges and UTC's second boundaries may not be precisely specified. It's not a good idea to use a GPS unit not specifically made for timing as an NTP reference clock. Sorry to plug myself, but I offer a GPS timing unit that is made specifically for timing use. It's $375 (quantity one) and more info is available at http://www.gpsclock.com/ PPS output is specified as +/- 1 us of UTC second boundary. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 12:21:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 705F714DD3 for ; Sun, 2 Jan 2000 12:21:56 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 17650048 invoked from network); 2 Jan 2000 20:22:06 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 2 Jan 2000 20:22:06 -0000 Message-ID: <386FB39A.1E4D4046@cybercable.fr> Date: Sun, 02 Jan 2000 21:22:50 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: False alarm ? (was Re: Weird interaction between cvs and a recent kernel) References: <20000101093905.B11872@Denninger.Net> <23804.946772113@critter.freebsd.dk> <20000101182650.B17456@Denninger.Net> <386F398C.20F61BB5@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bonsoir, Well, I don't remember indulging (Lagavulin, Glen Deveron, what else ...), but I'm stumped : I can't reproduce what I've seen : a full "cvs co" of the ports and src has been running ok till its normal end. more after some make world's TfH Thierry Herbelot wrote: > > Hello, > > I'm rebuilding my -Current box. > > it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT > snapshot. > > I have on another box the full repository of FreeBSD (source, ports, > docs, ...) on another box, running 3.3-Stable and exporting the > repository via NFS. > > I've tried to remake the world to the latest sources I had (got on 12/31 > around 4PM GMT). > > I can't get the "cvs co src" to finish properly : each time I launch > "cvs co src", the kernel crashes with page fault while in supervisor > mode : page not present (I don't have a serial console, so this is not > the full message). The instruction address for the faulting instruction > is always the same, in the "generic_bzero" (from a "nm" run on the > kernel). > > The running process is always "cvs". > > I have been able to check the sources out (one subdirectory after > another) and the machine has completed a full make world. I also run the > corresponding kernel. > > with the new sources, there is the same problem with cvs : I have not > been able to check out the ports tree in one step (same error, in the > same routine). > > The machine works fine : I have just completed a X11 3.3.5 build. > > As I have got plenty of RAM, I'm not quite sure a full crash dump would > be usable. > > Open to any suggestions > > TfH > > PS : dmesg for the box : > [SNIP] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 13:31:23 2000 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 13AF014D2E for ; Sun, 2 Jan 2000 13:31:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA59894; Sun, 2 Jan 2000 14:31:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31362; Sun, 2 Jan 2000 14:31:18 -0700 (MST) Message-Id: <200001022131.OAA31362@harmony.village.org> To: Poul-Henning Kamp Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 16:55:44 +0100." <8426.946828544@critter.freebsd.dk> References: <8426.946828544@critter.freebsd.dk> Date: Sun, 02 Jan 2000 14:31:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <8426.946828544@critter.freebsd.dk> Poul-Henning Kamp writes: : I will (as always) recommend the Motorola Oncore UT+. If you buy it We've also had excellent luck with the OEM version of the Oncore that we embed in our products. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 13:31:53 2000 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 18FB414D1F for ; Sun, 2 Jan 2000 13:31:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA59899; Sun, 2 Jan 2000 14:31:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31375; Sun, 2 Jan 2000 14:31:49 -0700 (MST) Message-Id: <200001022131.OAA31375@harmony.village.org> To: Poul-Henning Kamp Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: Ollivier Robert , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 17:26:55 +0100." <8525.946830415@critter.freebsd.dk> References: <8525.946830415@critter.freebsd.dk> Date: Sun, 02 Jan 2000 14:31:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : >Still no feature freeze for 4.0 BTW? : : Feature freeze is in effect I think, but minor upgrades and bugfixes are : not only allowed, they're mandatory :-) Jordan told me that the feature freeze was put off until Jan 15. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 13:33:38 2000 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 4ECC814BCE for ; Sun, 2 Jan 2000 13:33:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA59912; Sun, 2 Jan 2000 14:33:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA31402; Sun, 2 Jan 2000 14:33:35 -0700 (MST) Message-Id: <200001022133.OAA31402@harmony.village.org> To: Karl Denninger Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 10:37:32 CST." <20000102103732.A23004@Denninger.Net> References: <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> Date: Sun, 02 Jan 2000 14:33:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102103732.A23004@Denninger.Net> Karl Denninger writes: : That's EXPENSIVE. Worth every penny. We've seen sub-micro second syncronization with our unit on good hardware, and 1-2us on the 486 based hardware. : Common handheld GPS units with NEMA outputs on them are well under $200 : these days! NEMA gives you only millisecond accuracy, if you are lucky. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:10:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 273B515218 for ; Sun, 2 Jan 2000 14:10:37 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id QAA25894; Sun, 2 Jan 2000 16:10:29 -0600 (CST) Message-ID: <20000102161029.A25883@Denninger.Net> Date: Sun, 2 Jan 2000 16:10:29 -0600 From: Karl Denninger To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001022133.OAA31402@harmony.village.org>; from Warner Losh on Sun, Jan 02, 2000 at 02:33:35PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 02:33:35PM -0700, Warner Losh wrote: > In message <20000102103732.A23004@Denninger.Net> Karl Denninger writes: > : That's EXPENSIVE. > > Worth every penny. We've seen sub-micro second syncronization with > our unit on good hardware, and 1-2us on the 486 based hardware. > > : Common handheld GPS units with NEMA outputs on them are well under $200 > : these days! > > NEMA gives you only millisecond accuracy, if you are lucky. > > Warner Why spend twice what Mr. Schwartz seems to want to charge? For the Motorola name? Sorry, the Batwing Menace to employee's rights was long ago placed on my "do not buy, do not recommend, actively boycott" list. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:17:23 2000 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 314C914BCE for ; Sun, 2 Jan 2000 14:17:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA00718; Sun, 2 Jan 2000 23:17:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 16:10:29 CST." <20000102161029.A25883@Denninger.Net> Date: Sun, 02 Jan 2000 23:17:00 +0100 Message-ID: <716.946851420@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102161029.A25883@Denninger.Net>, Karl Denninger writes: >Why spend twice what Mr. Schwartz seems to want to charge? > >For the Motorola name? Sorry, the Batwing Menace to employee's rights was >long ago placed on my "do not buy, do not recommend, actively boycott" list. Well, suit your own political manifests as you will, but the Motorola unit is the best time receiver you can buy for humane amounts of money. You can see some of my measurements at http://phk.freebsd.dk -- 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 Jan 2 14:32: 4 2000 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 4522014C13 for ; Sun, 2 Jan 2000 14:32:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA60079; Sun, 2 Jan 2000 15:32:00 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA31807; Sun, 2 Jan 2000 15:32:00 -0700 (MST) Message-Id: <200001022232.PAA31807@harmony.village.org> To: Karl Denninger Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 16:10:29 CST." <20000102161029.A25883@Denninger.Net> References: <20000102161029.A25883@Denninger.Net> <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> Date: Sun, 02 Jan 2000 15:32:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102161029.A25883@Denninger.Net> Karl Denninger writes: : Why spend twice what Mr. Schwartz seems to want to charge? Because we need a PPS that is < 10nS from the true start of second for our application? 1uS is really really bad for the timing geeks in the audience. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:38:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 4FB78150F6 for ; Sun, 2 Jan 2000 14:38:15 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id QAA25955; Sun, 2 Jan 2000 16:38:02 -0600 (CST) Message-ID: <20000102163802.A25936@Denninger.Net> Date: Sun, 2 Jan 2000 16:38:02 -0600 From: Karl Denninger To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102161029.A25883@Denninger.Net> <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001022232.PAA31807@harmony.village.org>; from Warner Losh on Sun, Jan 02, 2000 at 03:32:00PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 03:32:00PM -0700, Warner Losh wrote: > In message <20000102161029.A25883@Denninger.Net> Karl Denninger writes: > : Why spend twice what Mr. Schwartz seems to want to charge? > > Because we need a PPS that is < 10nS from the true start of second for > our application? 1uS is really really bad for the timing geeks in the > audience. > > Warner And on what hardware do you think you can obtain 10ns resolution RELIABLY at the software level in the Unix environment and under FreeBSD? Answer: NONE! The actual usable resolution of a timing source is determined by the maximum slop in ANY part of the complete system. I challenge you to get actual REPEATABLE 10ns results while a multi-tasking anything is running on the recipient of that data. - -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:40:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 9B2E8150EF for ; Sun, 2 Jan 2000 14:40:20 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id QAA25970; Sun, 2 Jan 2000 16:40:12 -0600 (CST) Message-ID: <20000102164012.C25936@Denninger.Net> Date: Sun, 2 Jan 2000 16:40:12 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102161029.A25883@Denninger.Net> <716.946851420@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <716.946851420@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 11:17:00PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: > In message <20000102161029.A25883@Denninger.Net>, Karl Denninger writes: > > > >Why spend twice what Mr. Schwartz seems to want to charge? > > > >For the Motorola name? Sorry, the Batwing Menace to employee's rights was > >long ago placed on my "do not buy, do not recommend, actively boycott" list. > > Well, suit your own political manifests as you will, but the Motorola > unit is the best time receiver you can buy for humane amounts of money. > > You can see some of my measurements at http://phk.freebsd.dk Yeah, so what? Your system can't resolve events to that degree of accuracy, so the ability of the receiver to deliver them is irrelavent. More geek nonsense - about what I expected. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:42:32 2000 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 87F1F15142 for ; Sun, 2 Jan 2000 14:42:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA60119; Sun, 2 Jan 2000 15:42:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA31877; Sun, 2 Jan 2000 15:42:24 -0700 (MST) Message-Id: <200001022242.PAA31877@harmony.village.org> To: Karl Denninger Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 16:38:02 CST." <20000102163802.A25936@Denninger.Net> References: <20000102163802.A25936@Denninger.Net> <20000102161029.A25883@Denninger.Net> <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> Date: Sun, 02 Jan 2000 15:42:24 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102163802.A25936@Denninger.Net> Karl Denninger writes: : And on what hardware do you think you can obtain 10ns resolution RELIABLY : at the software level in the Unix environment and under FreeBSD? : : Answer: NONE! WRONG. : The actual usable resolution of a timing source is determined by the : maximum slop in ANY part of the complete system. : : I challenge you to get actual REPEATABLE 10ns results while a multi-tasking : anything is running on the recipient of that data. We have hardware timers that let us get into the pico second range on a regular basis. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:43:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id DE39614DE6 for ; Sun, 2 Jan 2000 14:43:51 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-2ivf7bt.dialup.mindspring.com [165.247.157.125]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA02762 for ; Sun, 2 Jan 2000 17:43:47 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.3/8.9.3) id RAA01469; Sun, 2 Jan 2000 17:40:36 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <200001022240.RAA01469@vger.foo.com> Subject: tip features (cdelay and ldelay)? To: freebsd-current@freebsd.org Date: Sun, 2 Jan 2000 17:40:36 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a couple of really dumb devices that I use 'tip' to talk to. One is a Motorola 6811 microcontroller and the other is an old EEPROM burner. I find that 'tip' overflows these devices when I'm sending Motorola s-record and Intel Hex formatted files. It looks like tip's 'cdelay' and 'ldelay' features do just the trick. However, they are disabled, surrounded by '#ifdef notdef' sequences. Just to make sure, I re-enabled them locally, and re-implemented the apparently lost 'nap()' function to make sure that these features work for my application, and they do. My question is: does anyone remember why these were disabled in the first place? Is there an equivalent replacement feature that I can use instead to pace the outgoing characters so that I don't overrun dumb devices with no flow control? Thanks, -Brian -- Brian Dean brdean@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:45:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id E1A0B15036 for ; Sun, 2 Jan 2000 14:45:22 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id QAA26010; Sun, 2 Jan 2000 16:45:19 -0600 (CST) Message-ID: <20000102164519.A25992@Denninger.Net> Date: Sun, 2 Jan 2000 16:45:19 -0600 From: Karl Denninger To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102161029.A25883@Denninger.Net> <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001022242.PAA31877@harmony.village.org>; from Warner Losh on Sun, Jan 02, 2000 at 03:42:24PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 03:42:24PM -0700, Warner Losh wrote: > In message <20000102163802.A25936@Denninger.Net> Karl Denninger writes: > : And on what hardware do you think you can obtain 10ns resolution RELIABLY > : at the software level in the Unix environment and under FreeBSD? > : > : Answer: NONE! > > WRONG. > > : The actual usable resolution of a timing source is determined by the > : maximum slop in ANY part of the complete system. > : > : I challenge you to get actual REPEATABLE 10ns results while a multi-tasking > : anything is running on the recipient of that data. > > We have hardware timers that let us get into the pico second range on > a regular basis. > > Warner Yes, you have HARDWARE timers that do that. So what? I'm talking about TIME SERVERS on UNIX machines. You know, ntpd and friends? Yes, that. Now explain to me how stability of your timing source ON THOSE MACHINES is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. I'm simply not interested in NON-GERMANE devices to the discussion; we were talking about FreeBSD on REAL computers, not specialty hardware for process control or nuclear physics experiments. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:49:28 2000 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 3E2C214D8B for ; Sun, 2 Jan 2000 14:49:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA00879; Sun, 2 Jan 2000 23:49:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 16:40:12 CST." <20000102164012.C25936@Denninger.Net> Date: Sun, 02 Jan 2000 23:49:08 +0100 Message-ID: <877.946853348@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102164012.C25936@Denninger.Net>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: >> In message <20000102161029.A25883@Denninger.Net>, Karl Denninger writes: >> >> >Why spend twice what Mr. Schwartz seems to want to charge? >> >> Well, suit your own political manifests as you will, but the Motorola >> unit is the best time receiver you can buy for humane amounts of money. >> >> You can see some of my measurements at http://phk.freebsd.dk > >Yeah, so what? > >Your system can't resolve events to that degree of accuracy, so the ability >of the receiver to deliver them is irrelavent. Karl, In fact I *do* have a computer that can resolve events to +/- 10nsec (http://gps.freebsd.dk) so I need it. In fact that machine is probably one of the best NTP servers in the entire world right now. >More geek nonsense - about what I expected. Call it "geek nonsense" if you want to. Warner is employed by the company that builds the stuff which figures out what time it is for NIST and although my professional affiliation isn't anywhere near that level, I can claim to be the first person to truly split the microsecond with a standard UNIX box. Listen, it is really too bad that you didn't get that pony for X-mas, and I can understand you why you are disappointed about it, but when do you plan to stop being grumpy about it ? :-) If you intend to keep up this "sour grapes" attitude, despite all the helpful answers you have gotten so far, you should consider stopping before you have worn out your 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 Sun Jan 2 14:50:21 2000 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 D05D9151B8 for ; Sun, 2 Jan 2000 14:50:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA00900; Sun, 2 Jan 2000 23:50:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 16:38:02 CST." <20000102163802.A25936@Denninger.Net> Date: Sun, 02 Jan 2000 23:50:09 +0100 Message-ID: <898.946853409@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102163802.A25936@Denninger.Net>, Karl Denninger writes: >On Sun, Jan 02, 2000 at 03:32:00PM -0700, Warner Losh wrote: >> In message <20000102161029.A25883@Denninger.Net> Karl Denninger writes: >> : Why spend twice what Mr. Schwartz seems to want to charge? >> >> Because we need a PPS that is < 10nS from the true start of second for >> our application? 1uS is really really bad for the timing geeks in the >> audience. >> >> Warner > >And on what hardware do you think you can obtain 10ns resolution RELIABLY >at the software level in the Unix environment and under FreeBSD? > >Answer: NONE! > >The actual usable resolution of a timing source is determined by the >maximum slop in ANY part of the complete system. > >I challenge you to get actual REPEATABLE 10ns results while a multi-tasking >anything is running on the recipient of that data. What rides on this challenge ? What is the prize ? I would use some cash, and this will be like picking cherries... -- 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 Jan 2 14:50:34 2000 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 50E8415350 for ; Sun, 2 Jan 2000 14:50:31 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA26532; Sun, 2 Jan 2000 14:50:18 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 14:50:18 -0800 Date: Sun, 2 Jan 2000 14:48:53 -0800 (PST) From: Kip Macy To: freebsd-current@freebsd.org Subject: latest version of threads library 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: 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 I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? I am running: FreeBSD io.lyris.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Dec 27 15:20:33 PST 1999 kip@io.lyris.com:/usr/src/sys/compile/KMM i386 Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:50:41 2000 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 3FCA21507A for ; Sun, 2 Jan 2000 14:50:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA60166; Sun, 2 Jan 2000 15:50:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA31962; Sun, 2 Jan 2000 15:50:35 -0700 (MST) Message-Id: <200001022250.PAA31962@harmony.village.org> To: Karl Denninger Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 16:45:19 CST." <20000102164519.A25992@Denninger.Net> References: <20000102164519.A25992@Denninger.Net> <20000102161029.A25883@Denninger.Net> <20000102103732.A23004@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> Date: Sun, 02 Jan 2000 15:50:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102164519.A25992@Denninger.Net> Karl Denninger writes: : Yes, you have HARDWARE timers that do that. : : So what? : : I'm talking about TIME SERVERS on UNIX machines. So am I. : You know, ntpd and friends? Yes, that. That's one of the things in our application. : Now explain to me how stability of your timing source ON THOSE MACHINES : is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH : between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. It is better because the variance in the measurements that we make is much smaller than 1uS would give. : I'm simply not interested in NON-GERMANE devices to the discussion; we were : talking about FreeBSD on REAL computers, not specialty hardware for process : control or nuclear physics experiments. Get a life Karl. I was telling you about my experiences and if you don't like it, take a chill pill or go play in traffic. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:54: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id E92BE151AF for ; Sun, 2 Jan 2000 14:54:03 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id QAA26052; Sun, 2 Jan 2000 16:53:56 -0600 (CST) Message-ID: <20000102165355.A26048@Denninger.Net> Date: Sun, 2 Jan 2000 16:53:55 -0600 From: Karl Denninger To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102164012.C25936@Denninger.Net> <877.946853348@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <877.946853348@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Jan 02, 2000 at 11:49:08PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: > In message <20000102164012.C25936@Denninger.Net>, Karl Denninger writes: > >On Sun, Jan 02, 2000 at 11:17:00PM +0100, Poul-Henning Kamp wrote: > >> In message <20000102161029.A25883@Denninger.Net>, Karl Denninger writes: > >> > >> >Why spend twice what Mr. Schwartz seems to want to charge? > >> > >> Well, suit your own political manifests as you will, but the Motorola > >> unit is the best time receiver you can buy for humane amounts of money. > >> > >> You can see some of my measurements at http://phk.freebsd.dk > > > >Yeah, so what? > > > >Your system can't resolve events to that degree of accuracy, so the ability > >of the receiver to deliver them is irrelavent. > > Karl, > > In fact I *do* have a computer that can resolve events to +/- 10nsec > (http://gps.freebsd.dk) so I need it. In fact that machine is > probably one of the best NTP servers in the entire world right now. > > >More geek nonsense - about what I expected. > > Call it "geek nonsense" if you want to. Warner is employed by the > company that builds the stuff which figures out what time it is > for NIST and although my professional affiliation isn't anywhere > near that level, I can claim to be the first person to truly split > the microsecond with a standard UNIX box. > > > Listen, it is really too bad that you didn't get that pony for > X-mas, and I can understand you why you are disappointed about it, > but when do you plan to stop being grumpy about it ? :-) > > If you intend to keep up this "sour grapes" attitude, despite all > the helpful answers you have gotten so far, you should consider > stopping before you have worn out your 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! Go fuck yourself Poul. Yes, the "F-word". You have no ability to determine "my welcome". -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 14:55:42 2000 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 7F60914FFC for ; Sun, 2 Jan 2000 14:55:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA00949; Sun, 2 Jan 2000 23:55:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Denninger Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-reply-to: Your message of "Sun, 02 Jan 2000 16:45:19 CST." <20000102164519.A25992@Denninger.Net> Date: Sun, 02 Jan 2000 23:55:22 +0100 Message-ID: <947.946853722@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000102164519.A25992@Denninger.Net>, Karl Denninger writes: > >Yes, you have HARDWARE timers that do that. > >So what? I have a commercially available PCI card which costs about the same as a good diskdrive... >I'm talking about TIME SERVERS on UNIX machines. > >You know, ntpd and friends? Yes, that. Yes, exactly. Suggest you poke gps.freebsd.dk a bit and see what performance it shows. >I'm simply not interested in [...] Karl, I'm simply not interested in continuing to listen to your belly aching. Unless you all of sudden develop something constructive to say, you will see this as my last reply. -- 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 Jan 2 15: 5:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8A86114BF3 for ; Sun, 2 Jan 2000 15:05:50 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 2 Jan 2000 15:05:49 -0800 From: "David Schwartz" To: "Karl Denninger" , "Warner Losh" Cc: Subject: RE: xntpd - VERY old folks, how about updating? :-) Date: Sun, 2 Jan 2000 15:05:49 -0800 Message-ID: <000101bf5575$e8b342e0$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-reply-to: <20000102164519.A25992@Denninger.Net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now explain to me how stability of your timing source ON THOSE MACHINES > is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. A battle you would win is if you said, "synchronizing the time of other UNIX machines without specialized hardware over a LAN or WAN". :) You can see 2 microsecond differences inside a single machine with no specialized hardware. You can see 5 microseconds over a good LAN. For example, youknow.youwant.to is synchronized to both tick.gpsclock.com and tock.gpsclock.com through a full-duplex 100Mbps LAN switch. Watch this: > ntpdate -q -p 8 209.133.29.16 209.133.29.20 server 209.133.29.16, stratum 1, offset -0.000298, delay 0.02579 server 209.133.29.20, stratum 1, offset -0.000302, delay 0.02579 2 Jan 15:01:01 ntpdate[2491]: adjust time server 209.133.29.20 offset -0.000302 sec Note that it claims that Tick and Tock agree with each other to 5 microseconds. But it has been unable to keep its own time to any better than 300 microseconds (it's been under heavy load, swapping in fact). In actual reality, the GPSClock 200 is better than the specifications indicate. If it really did alternate between 1us early pulses and 1us late pulses, stability would be measurably impacted. NTP is very good at smoothing things out anyway, especially since it only probes the clock every 64 seconds or so. David Schwartz http://www.gpsclock.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:11:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 8D2A514E41 for ; Sun, 2 Jan 2000 15:11:46 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26098; Sun, 2 Jan 2000 17:11:40 -0600 (CST) Message-ID: <20000102171140.B26048@Denninger.Net> Date: Sun, 2 Jan 2000 17:11:40 -0600 From: Karl Denninger To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> <20000102164519.A25992@Denninger.Net> <200001022250.PAA31962@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001022250.PAA31962@harmony.village.org>; from Warner Losh on Sun, Jan 02, 2000 at 03:50:35PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 03:50:35PM -0700, Warner Losh wrote: > In message <20000102164519.A25992@Denninger.Net> Karl Denninger writes: > : Yes, you have HARDWARE timers that do that. > : > : So what? > : > : I'm talking about TIME SERVERS on UNIX machines. > > So am I. > > : You know, ntpd and friends? Yes, that. > > That's one of the things in our application. So what? > : Now explain to me how stability of your timing source ON THOSE MACHINES > : is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > : between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. > > It is better because the variance in the measurements that we make is > much smaller than 1uS would give. Not possible without custom hardware. The inherent uncertainty in a PPS interface delivered through a parallel port in the interrupt context of a common grade-processor is greater than picosecond claims. Now the *integration* of many of these signals may not be, but the point still holds. That you FLUNKED your first science course where the uncertainty of measurements was discussed, and the boundaries on certainty were laid out, does not change those FACTS. You CANNOT declare a measurement (no matter what it is) to be more precise than the sum of ALL uncertainties in the measurement domain. This is a material FACT, and no amount of posturing changes it. PAYING for precision in a measurement source that is a few orders of magnitude beyond the response windows of what it is connected to is *STUPID*. This includes your claim of anything approaching 10ns resolution on consumer-grade computer hardware. > : I'm simply not interested in NON-GERMANE devices to the discussion; we were > : talking about FreeBSD on REAL computers, not specialty hardware for process > : control or nuclear physics experiments. > > Get a life Karl. I was telling you about my experiences and if you > don't like it, take a chill pill or go play in traffic. > > Warner Go stick your finger in a 220V socket, or sit on whatever Poul uses to do what I asked HIM to do just a few minutes ago. Perhaps that would reduce the population of this group by two people who don't deserve the term "scientist" applied to them. Scientists. BAH! You'd have to flunk first-semester physical science courses to not understand how the boundaries of uncertainty in measurements work, and why buying a reference source that is more precise than the LEAST PRECISE element in your entire measurement chain is almost always a COMPLETE waste of money. If you have two elements in a measurement chain, and one has 10ns repeatability and the other has 10us repeatability, the measurement you obtain is FOR ALL INTENTS AND PURPOSES equivalent to the 10us one. Even if the OTHER timebase is only accurate to 10us, the TOTAL inaccuracy is 20us MAXIMUM. What, Warner, is the INTERRUPT LATENCY (including processing time) specification on a Pentium? You know, the amount of time the chip requires to (1) recognize the INTERRUPT being dragged, (2) save the current context, (3) switch to the interrupt context, and (4) execute the FIRST instructions in that context. Now add to that the ACTUAL gate delays for ALL the gates between your piece of wire and the processor. Then tell me that this sums to ~10ns. You're smoking hard drugs - the processor cannot respond to the interrupt until (potentially) a multi-cycle instruction has been COMPLETED. Further, the act of responding itself requires several MORE cycles, as does the physical act (in the interrupt context) of reading the input latch. In fact, for an ISA parallel port, the speed involved in reading that latch is limited by ISA bus speed! Be careful with the pontification here Warner - some of us actually HAVE done hard real-time work and some of us also know a bit about how MPUs REALLY work in the REAL world. Posturing does NOT work with me on topics like this. You ain't getting no 10ns resolution off any production FreeBSD box without specialized timekeeping hardware that READS the pps output and has its OWN high-precision clock so it can tell the processor how many ticks elapsed from the time IT saw the PPS output until the processor got around to reading the latch. No way in hell. You want to claim otherwise? Fine - show me a gate analysis on the port you connect that clock to (from the wire to the processor's INTERRUPT pin), along with a gate propagation analysis on the processor and the execution path it must take, both worst and best case, from receipt of a signal on the interrupt pin until the FIRST instruction in the handler is executed. Have fun. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:13:13 2000 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 5D79714DCB for ; Sun, 2 Jan 2000 15:13:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA24516; Sun, 2 Jan 2000 15:13:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA56161; Sun, 2 Jan 2000 15:13:11 -0800 (PST) (envelope-from obrien) Date: Sun, 2 Jan 2000 15:13:10 -0800 From: "David O'Brien" To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000102151310.A53691@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000102164012.C25936@Denninger.Net> <877.946853348@critter.freebsd.dk> <20000102165355.A26048@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000102165355.A26048@Denninger.Net>; from karl@Denninger.Net on Sun, Jan 02, 2000 at 04:53:55PM -0600 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 Sun, Jan 02, 2000 at 04:53:55PM -0600, Karl Denninger wrote: > On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: ..snip.. > > If you intend to keep up this "sour grapes" attitude, despite all > > the helpful answers you have gotten so far, you should consider > > stopping before you have worn out your welcome. > > Go fuck yourself Poul. > > Yes, the "F-word". > You have no ability to determine "my welcome". Karl you are one fscking asshole. As a member of this list, you *HAVE* worn out your welcome in my inbox. You asked Poul-Henning about *good* timekeeping HW. He told you. $600 isn't that much for computer server related hardware. Warner seconded the recommendation. You pay less, you don't get the best. Its up to you to weigh your needs vs. what you are willing to pay. And you want to bitch?? What is your fscking problem? -- -- 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 Jan 2 15:18:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 09AA314DCB for ; Sun, 2 Jan 2000 15:18:43 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id SAA14513; Sun, 2 Jan 2000 18:17:59 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 18:17:59 -0500 (EST) From: Chuck Robey To: Karl Denninger Cc: Poul-Henning Kamp , Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000102165355.A26048@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > > If you intend to keep up this "sour grapes" attitude, despite all > > the helpful answers you have gotten so far, you should consider > > stopping before you have worn out your welcome. > > > > -- > > Poul-Henning Kamp FreeBSD coreteam member > > > > Yes, the "F-word". > > You have no ability to determine "my welcome". Karl, you've now managed to irritate a lot of folks. Jumping on Steve, who is normally a huge worker, and totally inoffensive, was really pushing things, but then jumping on Poul, who is somewhat easier to touch off, well, you have been just about advertising "I want a fight!", although no one's really given you much reason for it. Poul's response was right, you should come back in a few days, when you've had time to cool off. No one else really wants to keep the fight going. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:19:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id F15D014F1B; Sun, 2 Jan 2000 15:19:34 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26140; Sun, 2 Jan 2000 17:19:31 -0600 (CST) Message-ID: <20000102171931.E26048@Denninger.Net> Date: Sun, 2 Jan 2000 17:19:31 -0600 From: Karl Denninger To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102164012.C25936@Denninger.Net> <877.946853348@critter.freebsd.dk> <20000102165355.A26048@Denninger.Net> <20000102151310.A53691@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20000102151310.A53691@dragon.nuxi.com>; from David O'Brien on Sun, Jan 02, 2000 at 03:13:10PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 03:13:10PM -0800, David O'Brien wrote: > On Sun, Jan 02, 2000 at 04:53:55PM -0600, Karl Denninger wrote: > > On Sun, Jan 02, 2000 at 11:49:08PM +0100, Poul-Henning Kamp wrote: > ..snip.. > > > If you intend to keep up this "sour grapes" attitude, despite all > > > the helpful answers you have gotten so far, you should consider > > > stopping before you have worn out your welcome. > > > > Go fuck yourself Poul. > > > > Yes, the "F-word". > > You have no ability to determine "my welcome". > > Karl you are one fscking asshole. As a member of this list, you *HAVE* > worn out your welcome in my inbox. So what? > You asked Poul-Henning about *good* timekeeping HW. He told you. $600 > isn't that much for computer server related hardware. Warner seconded > the recommendation. So what? > You pay less, you don't get the best. Its up to you to weigh your needs > vs. what you are willing to pay. Shilling for a difference that is irrelavent is horseshit. It amounts to lying. Statistically these two time sources are almost EXACTLY equivalent. > And you want to bitch?? What is your fscking problem? Its a bullshit argument David and is nothing other than BLATENT shilling for Motorola - at someone else's expense! Without a specialized board that counts these nanosecond ticks from the time it gets the PPS signal to the time the latch is read this kind of accuracy claim is worth exactly NOTHING. WITHOUT it, which is EXACTLY what REAL WORLD use of these devices is going to be running under, the impact is ZERO. Further, the ACTUAL impact in the real world of time stability to the dozen-nanosecond-range is ALSO zero, with the possible exception of physical control processes in the nuclear research field (such applications are NOT running on "standard" Unix machines!) Finally, in the world of sync'ing time between systems (say, in a multiple server cluster) that kind of precision is ALSO worth ZERO! NOBODY with off-the-shelf hardware can obtain repeatable 10ns results from a standard Unix machine. NOBODY. And THAT is a fact, easily determined through nothing more than Intel's databooks on their processors and the interrupt response time they exhibit. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:21:58 2000 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 DD30614FC7 for ; Sun, 2 Jan 2000 15:21:56 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id PAA26686; Sun, 2 Jan 2000 15:21:44 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 15:21:44 -0800 Date: Sun, 2 Jan 2000 15:21:44 -0800 (PST) From: Kip Macy To: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000102151310.A53691@dragon.nuxi.com> 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: 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 Although your interaction is amusing, I subscribe to this mailing list to keep up to date on -current and not to see the script for the latest sitcom for geeks. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:23: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id B3A3114C4C for ; Sun, 2 Jan 2000 15:22:58 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26154; Sun, 2 Jan 2000 17:22:47 -0600 (CST) Message-ID: <20000102172247.F26048@Denninger.Net> Date: Sun, 2 Jan 2000 17:22:47 -0600 From: Karl Denninger To: Chuck Robey Cc: Poul-Henning Kamp , Warner Losh , current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102165355.A26048@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Sun, Jan 02, 2000 at 06:17:59PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 06:17:59PM -0500, Chuck Robey wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > > If you intend to keep up this "sour grapes" attitude, despite all > > > the helpful answers you have gotten so far, you should consider > > > stopping before you have worn out your welcome. > > > > > > -- > > > Poul-Henning Kamp FreeBSD coreteam member > > > > > > > > Yes, the "F-word". > > > > You have no ability to determine "my welcome". > > Karl, you've now managed to irritate a lot of folks. Jumping on Steve, > who is normally a huge worker, and totally inoffensive, was really pushing > things, but then jumping on Poul, who is somewhat easier to touch off, > well, you have been just about advertising "I want a fight!", although no > one's really given you much reason for it. > > Poul's response was right, you should come back in a few days, when you've > had time to cool off. No one else really wants to keep the fight going. I don't give a shit what Poul wants - or what you want. Corporate shilling does NOT go past me without a response, and Paol is completely full of shit in the context (time servers used by HUMANS for ORDINARY uses) that we were discussing at the time. Sticking custom PCI boards into a PC that count nanosecond-level clock transitions before the processor can get around to reading the input latch (at a cost of several hundred dollars MORE as a one-off science project) *DOES NOT COUNT*. Since I see the FreeBSD "treehouse" mentality hasn't changed, I guess my ORIGINAL assessment was correct. Duplicity and bullshit still rule the roost, just as they did a couple of years ago. Why the hell Walnut Creek wastes their money on your type REMAINS beyond my comprehension. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:30:23 2000 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 BFE03151B8 for ; Sun, 2 Jan 2000 15:30:21 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id AAFC61C4A; Sun, 2 Jan 2000 18:31:22 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id A653D3815; Sun, 2 Jan 2000 18:31:22 -0500 (EST) Date: Sun, 2 Jan 2000 18:31:22 -0500 (EST) From: Bill Fumerola To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000102172247.F26048@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > Why the hell Walnut Creek wastes their money on your type REMAINS beyond > my comprehension. It really hasn't been a problem for anyone but you. It's more successful, then say, alternative top level domain projects that have gone nowhere. -- - 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 Sun Jan 2 15:32: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id D4C9814EBE for ; Sun, 2 Jan 2000 15:32:01 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26176; Sun, 2 Jan 2000 17:31:55 -0600 (CST) Message-ID: <20000102173155.G26048@Denninger.Net> Date: Sun, 2 Jan 2000 17:31:55 -0600 From: Karl Denninger To: David Schwartz , Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102164519.A25992@Denninger.Net> <000101bf5575$e8b342e0$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <000101bf5575$e8b342e0$021d85d1@youwant.to>; from David Schwartz on Sun, Jan 02, 2000 at 03:05:49PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 03:05:49PM -0800, David Schwartz wrote: > > > Now explain to me how stability of your timing source ON THOSE MACHINES > > is MATERIALLY different to any process WHICH THAT DEVICE MAY INTERACT WITH > > between 10ns and 1us, AS SEEN FROM THE UNIX MACHINE. > > A battle you would win is if you said, "synchronizing the time of other > UNIX machines without specialized hardware over a LAN or WAN". :) Of course, which is my point. > You can see 2 microsecond differences inside a single machine with no > specialized hardware. MICROseconds. *NOT* NANOseconds, which is what Paol was claiming! > You can see 5 microseconds over a good LAN. For > example, youknow.youwant.to is synchronized to both tick.gpsclock.com and > tock.gpsclock.com through a full-duplex 100Mbps LAN switch. Watch this: > > > ntpdate -q -p 8 209.133.29.16 209.133.29.20 > server 209.133.29.16, stratum 1, offset -0.000298, delay 0.02579 > server 209.133.29.20, stratum 1, offset -0.000302, delay 0.02579 > 2 Jan 15:01:01 ntpdate[2491]: adjust time server 209.133.29.20 > offset -0.000302 sec > > Note that it claims that Tick and Tock agree with each other to 5 > microseconds. But it has been unable to keep its own time to any better than > 300 microseconds (it's been under heavy load, swapping in fact). Correct. And the issue there is that its the COMPLETE timekeeping environment, not some bullshit-manufacturered claim of 10ns time stability that is CLEARLY bogus. As soon as you put a REAL workload on the machine(s) involved interrupt latency starts to cause trouble. Hell, just READING THE FRIGGING PORT to SEE the PPS output involves interrupt latency which is INDETERMINATE beyond a LOT more elapsed time than 10ns! > In actual reality, the GPSClock 200 is better than the specifications > indicate. If it really did alternate between 1us early pulses and 1us late > pulses, stability would be measurably impacted. NTP is very good at > smoothing things out anyway, especially since it only probes the clock every > 64 seconds or so. > > David Schwartz > http://www.gpsclock.com/ Yep. My entire point, David, is that there is ZERO actual, real-world difference between your reasonably-priced receiver and the shilled-for Motorola receiver that Poul and others like to promote at twice the price. Now if you're willing to stuff a custom PCI board (that in and of itself probably violates all manner of FCC regulations in terms of emissions) to keep nanosecond-level track of the number of "ticks" between seeing a PPS signal and the processor getting around to reading the latch, then Poul and the shills might be right on a TECHNICAL level - as long as they never actually USE that computer for anything, never access a disk, and never hit any other I/O port. But that's not the real world, its not a real application, and geeking-up something just to prove you can (while probably breaking the law in terms of emissions - the clock rates to get nanosecond timing accuracy are non-trivial, and that board would need FCC appoval here in the states) doesn't count. It also has ZERO relavence to those of us who want to keep time on our networks. It is precisely this kind of elitism and bullshit that I continually run into when trying to deal with the "treehouse" FreeBSD kids, and in this particular instance its so blatent that I simply refuse to shut up about it. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:33: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 54D1714DC9 for ; Sun, 2 Jan 2000 15:33:05 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26190; Sun, 2 Jan 2000 17:32:55 -0600 (CST) Message-ID: <20000102173255.H26048@Denninger.Net> Date: Sun, 2 Jan 2000 17:32:55 -0600 From: Karl Denninger To: Bill Fumerola Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102172247.F26048@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bill Fumerola on Sun, Jan 02, 2000 at 06:31:22PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 06:31:22PM -0500, Bill Fumerola wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > Why the hell Walnut Creek wastes their money on your type REMAINS beyond > > my comprehension. > > It really hasn't been a problem for anyone but you. It's more successful, > then say, alternative top level domain projects that have gone nowhere. > > -- > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - Really? How many millions does Paol have to count in HIS bank as a result of this shilling and "advocacy"? SOME OF US have *REAL* successes to point to - not just bullshit pats on the back. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:36:31 2000 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 21B0214D2D for ; Sun, 2 Jan 2000 15:36:28 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 20E521C4A; Sun, 2 Jan 2000 18:37:31 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 1C9203815; Sun, 2 Jan 2000 18:37:31 -0500 (EST) Date: Sun, 2 Jan 2000 18:37:31 -0500 (EST) From: Bill Fumerola To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) In-Reply-To: <20000102173255.H26048@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > How many millions does Paol have to count in HIS bank as a result of this > shilling and "advocacy"? > > SOME OF US have *REAL* successes to point to - not just bullshit pats on the > back. Like eDNS, right? -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - PS. Some of us aren't in it for the money. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:38:28 2000 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 B71D9151B8 for ; Sun, 2 Jan 2000 15:38:18 -0800 (PST) (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 AAA21055; Mon, 3 Jan 2000 00:37:53 +0100 (MET) 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 AAA38385; Mon, 3 Jan 2000 00:38:22 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA87787; Mon, 3 Jan 2000 00:37:56 +0100 (CET) (envelope-from ticso) Date: Mon, 3 Jan 2000 00:37:56 +0100 From: Bernd Walter To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: several procmail jobs hang ... Message-ID: <20000103003755.B87713@cicely8.cicely.de> References: <20000102200003.A1618@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000102200003.A1618@titan.klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 08:00:03PM +0100, Andreas Klemm wrote: > A few days ago I updated -current and build /usr/local completely new. > One remaining problem is, that procmail jobs seems to hang. > First it was a port problem, I installed some (for me) basic services > in /home/local and procmail tried to call /usr/local/bin/formail. > Now I recompiled procmail using normal /usr/local as PREFIX, but > the jobs still hang. After some time they seem to timeout and > mail seems to be delivered. Can't say exactly if I have some mail > loss. I don't know that much about procmail itself and how you use it, but with the default local delivery you can get such a situation if there's a stale lock file in /var/mail. -- 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 Sun Jan 2 15:43:53 2000 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 D59C314FCA for ; Sun, 2 Jan 2000 15:43:45 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac6.wam.umd.edu (root@rac6.wam.umd.edu [128.8.10.146]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id SAA03746 for ; Sun, 2 Jan 2000 18:43:39 -0500 (EST) Received: from rac6.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac6.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA10112 for ; Sun, 2 Jan 2000 18:43:39 -0500 (EST) Received: from localhost (culverk@localhost) by rac6.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA10108 for ; Sun, 2 Jan 2000 18:43:39 -0500 (EST) X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs Date: Sun, 2 Jan 2000 18:43:39 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: new PCM problems 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 OK, there is still the static problem with the pcm driver with a ViBRA16X soundcard. It also seems that the problem with xmms's analyzer is gone. However, now whenever a sound that is shorter than roughly 1 second or so plays, it gets cut short. The sound doesn't completely play. I just thought I'd let someone know what is going on here on my -CURRENT box. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems 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 Sun Jan 2 15:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 75B7B1514A for ; Sun, 2 Jan 2000 15:45:01 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26229; Sun, 2 Jan 2000 17:44:57 -0600 (CST) Message-ID: <20000102174457.A26207@Denninger.Net> Date: Sun, 2 Jan 2000 17:44:57 -0600 From: Karl Denninger To: Bill Fumerola Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102173255.H26048@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bill Fumerola on Sun, Jan 02, 2000 at 06:37:31PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 06:37:31PM -0500, Bill Fumerola wrote: > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > How many millions does Paol have to count in HIS bank as a result of this > > shilling and "advocacy"? > > > > SOME OF US have *REAL* successes to point to - not just bullshit pats on the > > back. > > Like eDNS, right? > > -- > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - > > > PS. Some of us aren't in it for the money. No, you're in it to pat yourself on the back and play "treehouse". We can point to the Internet's evolution of these "treehouse" organizations and show off how PROUD we are of them and those who support them. Let's start a nice short list, shall we? Network Solutions. ARIN. FreeBSD-CORE. Shall I keep going? .....At least the folks in it for the money are honest - you know exactly what their goals are. With the rest you have real trouble figuring out exactly what REALLY drives them. I prefer my cards face up, thank you very much. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:45:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id A0B2A152A4; Sun, 2 Jan 2000 15:45:43 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas1-40-78.dial.proxad.net [212.27.40.78]) by postfix2.free.fr (Postfix) with ESMTP id 4488C744D8; Mon, 3 Jan 2000 00:45:36 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id AAA13389; Mon, 3 Jan 2000 00:49:10 +0100 (CET) (envelope-from nsouch) Message-ID: <20000103004910.41467@armor.free.fr> Date: Mon, 3 Jan 2000 00:49:10 +0100 From: Nicolas Souchu To: hackers@freebsd.org Cc: current@freebsd.org, nsouch@freebsd.org Subject: HEADS-UP newppbus for beta-testing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD armor 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there! FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current A major ppbus(4) release is available for beta-testing. It includes the port of the ppbus framework to the newbus system. http://www.freebsd.org/~nsouch/ppbus.html provides usefull notes about the configuration of ppbus through the MACHINE file and the newppbus developement progression (stability, caveats...) The newppbus will come in remplacement to the previous standalone ppbus architectural system. I did not read recent announces about future FreeBSD 4.x releases :( Of course, newppbus introduction would better before any -stable jump. Note that, only probe/attach and function interfaces were concerned by the port and tests are consequently only regression tests. The port was not to hard and the result should not be too bad. Moreover the current ppbus high level drivers stress the system well I think: vpo (SCSI controller), lpt (with PS data filtered by ghostscript and interrupts) Feel free to contact me for more, Nicholas. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sun Jan 2 15:55:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 0487014C38; Sun, 2 Jan 2000 15:55:36 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id RAA26369; Sun, 2 Jan 2000 17:55:35 -0600 (CST) Message-ID: <20000102175534.D26321@Denninger.Net> Date: Sun, 2 Jan 2000 17:55:34 -0600 From: Karl Denninger To: current@freebsd.org Subject: [Majordomo@FreeBSD.ORG: Majordomo results: which] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, so the treehouse maggots continue to fester, eh? Nice move shitheads. Do you intend to continue? Consider this forwarded to Steve, a withdrawal of my port, and notice of my intent to post it along with a transcript on my web page for HomeDaemon. Who is the two-bit-peckerhead who removed my subscription to several of the lists? -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! ----- Forwarded message from Majordomo@FreeBSD.ORG ----- To: karl@Denninger.Net From: Majordomo@FreeBSD.ORG Subject: Majordomo results: which Reply-To: Majordomo@FreeBSD.ORG Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) -- >>>> which denninger.net NOTE: the "which" command does not show subscriptions to either freebsd-arch or freebsd-security-notifications The string 'denninger.net' appears in the following entries in lists served by Majordomo@FreeBSD.ORG: List Address ==== ======= freebsd-hackers karl@Denninger.Net freebsd-ports karl@Denninger.Net freebsd-scsi karl@Denninger.Net freebsd-security karl@Denninger.Net >>>> ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 15:59: 1 2000 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 4E20114FCA for ; Sun, 2 Jan 2000 15:58:59 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60466; Sun, 2 Jan 2000 16:58:57 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA32450; Sun, 2 Jan 2000 16:58:57 -0700 (MST) Message-Id: <200001022358.QAA32450@harmony.village.org> To: Karl Denninger Subject: Re: xntpd - VERY old folks, how about updating? :-) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jan 2000 17:11:40 CST." <20000102171140.B26048@Denninger.Net> References: <20000102171140.B26048@Denninger.Net> <20000102094459.B22738@Denninger.Net> <8426.946828544@critter.freebsd.dk> <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> <20000102164519.A25992@Denninger.Net> <200001022250.PAA31962@harmony.village.org> Date: Sun, 02 Jan 2000 16:58:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl, I was my hands of this conversation. You aren't listening. We have custom hardware. We're a control and measurement system. The <10ns is needed for that control and measurement part. The sync we get of the system clock, like I said before, is on the order of a few hundred ns on pentium hardware and a few us on 486 hardware. That's why we spend more $$ on the hardware. If you don't like it, forget the chill pill and just play in traffic. I'm done with this conversation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16: 5:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD91A14FCA for ; Sun, 2 Jan 2000 16:05:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA03619; Sun, 2 Jan 2000 16:03:09 -0800 Date: Sun, 2 Jan 2000 16:05:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] In-Reply-To: <20000102175534.D26321@Denninger.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 Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if there was a mail bounce. It may be a stupid mail robot problem, not a human out to get you. If so, you've directed your vituperation at the wrong ip address/port combo- try port 9 instead of port 25. On Sun, 2 Jan 2000, Karl Denninger wrote: > Oh, so the treehouse maggots continue to fester, eh? > > Nice move shitheads. > > Do you intend to continue? > > Consider this forwarded to Steve, a withdrawal of my port, and notice of my > intent to post it along with a transcript on my web page for HomeDaemon. > > Who is the two-bit-peckerhead who removed my subscription to several of > the lists? > > -- > -- > Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org > Isn't it time we started putting KIDS first? See the above URL for > a plan to do exactly that! > > > ----- Forwarded message from Majordomo@FreeBSD.ORG ----- > > To: karl@Denninger.Net > From: Majordomo@FreeBSD.ORG > Subject: Majordomo results: which > Reply-To: Majordomo@FreeBSD.ORG > Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) > > -- > > >>>> which denninger.net > > > NOTE: the "which" command does not show subscriptions > to either freebsd-arch or freebsd-security-notifications > > > The string 'denninger.net' appears in the following > entries in lists served by Majordomo@FreeBSD.ORG: > > List Address > ==== ======= > freebsd-hackers karl@Denninger.Net > freebsd-ports karl@Denninger.Net > freebsd-scsi karl@Denninger.Net > freebsd-security karl@Denninger.Net > > >>>> > > ----- End forwarded message ----- > > > 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 Jan 2 16: 8:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 4DB0414D2D for ; Sun, 2 Jan 2000 16:08:36 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA26487; Sun, 2 Jan 2000 18:08:31 -0600 (CST) Message-ID: <20000102180831.A26472@Denninger.Net> Date: Sun, 2 Jan 2000 18:08:31 -0600 From: Karl Denninger To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) References: <20000102103732.A23004@Denninger.Net> <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> <20000102164519.A25992@Denninger.Net> <200001022250.PAA31962@harmony.village.org> <20000102171140.B26048@Denninger.Net> <200001022358.QAA32450@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001022358.QAA32450@harmony.village.org>; from Warner Losh on Sun, Jan 02, 2000 at 04:58:57PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 04:58:57PM -0700, Warner Losh wrote: > Karl, I was my hands of this conversation. You aren't listening. > > We have custom hardware. We're a control and measurement system. The > <10ns is needed for that control and measurement part. The sync we > get of the system clock, like I said before, is on the order of a few > hundred ns on pentium hardware and a few us on 486 hardware. > > That's why we spend more $$ on the hardware. If you don't like it, > forget the chill pill and just play in traffic. > > I'm done with this conversation. > > Warner That's fine Warner, but isn't germane to the point. Poul claimed that his favorite device was *superior* in *ordinary* use. Then he admitted that he needed custom hardware (as you do as well) to get that kind of accuracy. Recommending something that is twice as expensive for people trying to keep network time when the INHERENT stability of the system clock is at least a couple orders of magnitude worse than the proclaimed PPS stability is just flat STUPID. Maintaining and defending that position when it is pointed out in bold letters that the uncertainty on the system clock and interrupt latency is FAR greater than the claimed 10ns resolution has only three possible explainations: 1. The poster has an interest in the device being shilled for. 2. The poster has an IQ below that of tap water's temperature in Celcius. 3. The poster has never in their life had to specify an uncertainty with a measurement, which in and of itself disqualifies them for the discussion at hand. As for whoever the person is who force-removed me from the list, trust me on this - I won't forget that act, and until you're identified and permanently removed from both the list and the entire project you'll have no contributions from me to your little treehouse project in any way, shape or form. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16: 9:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 6E18E15235 for ; Sun, 2 Jan 2000 16:09:45 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA26498; Sun, 2 Jan 2000 18:09:37 -0600 (CST) Message-ID: <20000102180937.B26472@Denninger.Net> Date: Sun, 2 Jan 2000 18:09:37 -0600 From: Karl Denninger To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] References: <20000102175534.D26321@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew Jacob on Sun, Jan 02, 2000 at 04:05:22PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh, Matthew, I have the system logs here. I'm root. There was no bounce. And yes, I do know how SMTP works too. Nice try though. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 04:05:22PM -0800, Matthew Jacob wrote: > > Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if > there was a mail bounce. > > It may be a stupid mail robot problem, not a human out to get you. If so, > you've directed your vituperation at the wrong ip address/port combo- try > port 9 instead of port 25. > > On Sun, 2 Jan 2000, Karl Denninger wrote: > > > Oh, so the treehouse maggots continue to fester, eh? > > > > Nice move shitheads. > > > > Do you intend to continue? > > > > Consider this forwarded to Steve, a withdrawal of my port, and notice of my > > intent to post it along with a transcript on my web page for HomeDaemon. > > > > Who is the two-bit-peckerhead who removed my subscription to several of > > the lists? > > > > -- > > -- > > Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org > > Isn't it time we started putting KIDS first? See the above URL for > > a plan to do exactly that! > > > > > > ----- Forwarded message from Majordomo@FreeBSD.ORG ----- > > > > To: karl@Denninger.Net > > From: Majordomo@FreeBSD.ORG > > Subject: Majordomo results: which > > Reply-To: Majordomo@FreeBSD.ORG > > Date: Sun, 2 Jan 2000 15:52:37 -0800 (PST) > > > > -- > > > > >>>> which denninger.net > > > > > > NOTE: the "which" command does not show subscriptions > > to either freebsd-arch or freebsd-security-notifications > > > > > > The string 'denninger.net' appears in the following > > entries in lists served by Majordomo@FreeBSD.ORG: > > > > List Address > > ==== ======= > > freebsd-hackers karl@Denninger.Net > > freebsd-ports karl@Denninger.Net > > freebsd-scsi karl@Denninger.Net > > freebsd-security karl@Denninger.Net > > > > >>>> > > > > ----- End forwarded message ----- > > > > > > 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 Jan 2 16:21: 0 2000 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 438CC1523F for ; Sun, 2 Jan 2000 16:20:56 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA37696; Mon, 3 Jan 2000 10:50:40 +1030 (CST) Date: Mon, 3 Jan 2000 10:50:40 +1030 From: Greg Lehey To: Karl Denninger Cc: mjacob@feral.com, current@FreeBSD.ORG Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] Message-ID: <20000103105040.I1528@freebie.lemis.com> References: <20000102175534.D26321@Denninger.Net> <20000102180937.B26472@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000102180937.B26472@Denninger.Net> 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 Sunday, 2 January 2000 at 18:09:37 -0600, Karl Denninger wrote: > On Sun, Jan 02, 2000 at 04:05:22PM -0800, Matthew Jacob wrote: >> On Sun, 2 Jan 2000, Karl Denninger wrote: >> >>> Oh, so the treehouse maggots continue to fester, eh? >>> >>> Nice move shitheads. >>> >>> Do you intend to continue? >>> >>> Consider this forwarded to Steve, a withdrawal of my port, and notice of my >>> intent to post it along with a transcript on my web page for HomeDaemon. >>> >>> Who is the two-bit-peckerhead who removed my subscription to several of >>> the lists? >> >> Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if >> there was a mail bounce. >> >> It may be a stupid mail robot problem, not a human out to get you. If so, >> you've directed your vituperation at the wrong ip address/port combo- try >> port 9 instead of port 25. > > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. > > And yes, I do know how SMTP works too. > > Nice try though. Karl, based on the behaviour you have shown and continue to show, I think you've given every reason for being removed from the mailing lists. But you appear only to have been removed from one, and anyway, you get warned before you're removed. So I suspect that it's been some other glitch; they do happen. On the other hand, I would be really grateful if you would go away and shut up. If it requires forcibly removing you from the mailing lists to get this to happen, then I'm in favour of doing so. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:32:21 2000 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 193E714D2D for ; Sun, 2 Jan 2000 16:32:20 -0800 (PST) (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 124vQt-000Owc-00; Sun, 2 Jan 2000 19:33:11 -0500 To: Karl Denninger Cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] In-reply-to: Your message of "Sun, 02 Jan 2000 18:09:37 CST." <20000102180937.B26472@Denninger.Net> Date: Sun, 02 Jan 2000 19:33:10 -0500 Message-ID: <95889.946859590@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote in message ID <20000102180937.B26472@Denninger.Net>: > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. Wrong side of the SMTP transaction Karl. Logs on the receiver mean *NOTHING*. And you don't have an account, or root, or access to the majordomo bounce mailbox on hub, so your claim isn't worth the electrons you used to send it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:37:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from pistol.cde.com (pistol.cde.com [204.117.195.6]) by hub.freebsd.org (Postfix) with ESMTP id 5E84914DCB for ; Sun, 2 Jan 2000 16:37:17 -0800 (PST) (envelope-from dev-null@no-id.com) Received: (from nobody@localhost) by pistol.cde.com (8.8.8/8.8.5) id TAA12468; Sun, 2 Jan 2000 19:37:08 -0500 Date: Sun, 2 Jan 2000 19:37:08 -0500 From: dev-null@no-id.com Message-Id: <200001030037.TAA12468@pistol.cde.com> To: freebsd-current@freebsd.org Reply-To: freebsd-current@freebsd.org Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In all the years I've known you, Karl, you've always thought you were so far above everyone else. Apparently, you get off on treating people like shit. Go away, we don't need your "contributions" here... I'm not sure we ever did. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:37:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 73B2715287 for ; Sun, 2 Jan 2000 16:37:23 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA26610; Sun, 2 Jan 2000 18:37:15 -0600 (CST) Message-ID: <20000102183715.C26547@Denninger.Net> Date: Sun, 2 Jan 2000 18:37:15 -0600 From: Karl Denninger To: Gary Palmer Cc: current@FreeBSD.ORG Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] References: <20000102180937.B26472@Denninger.Net> <95889.946859590@noop.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <95889.946859590@noop.colo.erols.net>; from Gary Palmer on Sun, Jan 02, 2000 at 07:33:10PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doesn't change the facts Gary. This isn't the first time either Gary. Plausable deniability isn't going to wash here. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sun, Jan 02, 2000 at 07:33:10PM -0500, Gary Palmer wrote: > Karl Denninger wrote in message ID > <20000102180937.B26472@Denninger.Net>: > > Uh, Matthew, I have the system logs here. I'm root. There was no bounce. > > Wrong side of the SMTP transaction Karl. Logs on the receiver mean > *NOTHING*. And you don't have an account, or root, or access to the > majordomo bounce mailbox on hub, so your claim isn't worth the > electrons you used to send it. > > > 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 Jan 2 16:38:16 2000 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 677CC14E20 for ; Sun, 2 Jan 2000 16:38:13 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id QAA27263; Sun, 2 Jan 2000 16:38:01 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 16:38:01 -0800 Date: Sun, 2 Jan 2000 16:38:01 -0800 (PST) From: Kip Macy To: current@freebsd.org Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] In-Reply-To: <95889.946859590@noop.colo.erols.net> 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: 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 Any pointers to web pages on setting up a killfile? The signal to noise ratio on this list is dropping rapidly. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:39:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from pistol.cde.com (pistol.cde.com [204.117.195.6]) by hub.freebsd.org (Postfix) with ESMTP id 4725114E20 for ; Sun, 2 Jan 2000 16:39:29 -0800 (PST) (envelope-from dev-null@no-id.com) Received: (from nobody@localhost) by pistol.cde.com (8.8.8/8.8.5) id TAA12474; Sun, 2 Jan 2000 19:39:25 -0500 Date: Sun, 2 Jan 2000 19:39:25 -0500 From: dev-null@no-id.com Message-Id: <200001030039.TAA12474@pistol.cde.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: CORE-treehouse felling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Naw, it ain't worth the gas for the chainsaw. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:50:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id D649215133; Sun, 2 Jan 2000 16:50:18 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA26714; Sun, 2 Jan 2000 18:50:17 -0600 (CST) Message-ID: <20000102185017.C26655@Denninger.Net> Date: Sun, 2 Jan 2000 18:50:17 -0600 From: Karl Denninger To: current@freebsd.org, ports@freebsd.org Subject: One final note and a "bite me" to you Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for those of you who think this whole "magical unsubscribe" is a "fluke"; All unsubscribes and subscribes to FreeBSD's lists must be authenticated. Majordomo is set to confirm all transactions. Whoever did this did it directly by logging into Freefall and editing the mailing list files themselves, or otherwise forged the request so as to get the "key" for the response. Have a nice year folks. THIS time, with only other people to benefit from my participation here, I'm not willing to play. Some of you will remember that about two years ago a SIMILAR forged unsubscribe was sent in for me during a heated discussion right here on this list. Theo was right in splitting off from you folks. I should have followed him a couple of years ago and done my own split. Now, its simply not worth it. This makes twice - and that's enough for me. As for you Paol, perhaps some day you'll stop trying to bullshit people. Occasionally when you do that you run into someone who has AT LEAST a single class in physical science and understands the uncertainty of measurements. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:53:30 2000 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 D37DA14CC7; Sun, 2 Jan 2000 16:53:26 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id QAA27412; Sun, 2 Jan 2000 16:53:13 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 16:53:13 -0800 Date: Sun, 2 Jan 2000 16:53:13 -0800 (PST) From: Kip Macy To: Karl Denninger Cc: current@freebsd.org, ports@freebsd.org Subject: Re: One final note and a "bite me" to you In-Reply-To: <20000102185017.C26655@Denninger.Net> 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: karl@Denninger.Net,current@freebsd.org,ports@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 Grow up. -Kip On Sun, 2 Jan 2000, Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; > > All unsubscribes and subscribes to FreeBSD's lists must be > authenticated. Majordomo is set to confirm all transactions. > > Whoever did this did it directly by logging into Freefall and editing the > mailing list files themselves, or otherwise forged the request so as > to get the "key" for the response. > > Have a nice year folks. THIS time, with only other people to benefit from > my participation here, I'm not willing to play. > > Some of you will remember that about two years ago a SIMILAR forged > unsubscribe was sent in for me during a heated discussion right here > on this list. > > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. > > This makes twice - and that's enough for me. > > As for you Paol, perhaps some day you'll stop trying to bullshit people. > Occasionally when you do that you run into someone who has AT LEAST a > single class in physical science and understands the uncertainty of > measurements. > > -- > -- > Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org > Isn't it time we started putting KIDS first? See the above URL for > a plan to do exactly that! > > > 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 Jan 2 16:53:56 2000 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 6E94215036 for ; Sun, 2 Jan 2000 16:53:48 -0800 (PST) (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 BAA02838; Mon, 3 Jan 2000 01:53:35 +0100 (CET) Date: Mon, 3 Jan 2000 01:53:35 +0100 From: Stephan van Beerschoten To: Dan Nelson Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: 2 hours to compile mysql? Message-ID: <20000103015335.F2577@supra.rotterdam.luna.net> References: <20000101133219.C612@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000101133219.C612@dan.emsphone.com>; from Dan Nelson on Sat, Jan 01, 2000 at 01:32:19PM -0600 Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 01, 2000 at 01:32:19PM -0600, Dan Nelson wrote: > > The box is a 333MHz PII, with 64M ram. Do I just need more ram to be > > able to compile in reasonable time, or is something broken? > > You probably need more RAM. sql_yacc.cc is one of those "worst-case" > programs as far as gcc is concerned; I don't think gcc can parse large > case statements like this efficiently. Adding "--with-low-memory" to > your port Makefile, in the CONFIGURE_ARGS line, will help. I have the same thing compiling mysql (daily updated cvs of ports, and just yesterday recompiled my world). I have a P2 450 with 256MB of ram. So, I don't think that RAM is an issue here... -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:57:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from asgaard.whispering.org (208-241-93-179.hsacorp.net [208.241.93.179]) by hub.freebsd.org (Postfix) with ESMTP id 884A314D69; Sun, 2 Jan 2000 16:56:54 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (will@15-148.008.popsite.net [209.69.195.148]) by asgaard.whispering.org (8.9.3/8.9.3) with ESMTP id TAA75320; Sun, 2 Jan 2000 19:56:36 -0500 (EST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id TAA64151; Sun, 2 Jan 2000 19:56:41 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000102185017.C26655@Denninger.Net> Date: Sun, 02 Jan 2000 19:56:40 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Karl Denninger Subject: RE: One final note and a "bite me" to you Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-00 Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; > > All unsubscribes and subscribes to FreeBSD's lists must be > authenticated. Majordomo is set to confirm all transactions. It is still possible for Majordomo to screw up by itself. > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. Theo split from NetBSD. Again, further ignorance. I suggest you sit down with a copy of /usr/share/misc/bsd-family-tree and read a little history that you seem to have missed. Besides, with all your commercial "work" to do, what purpose would it serve to have done your own split? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:58:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 6AB2614A16; Sun, 2 Jan 2000 16:58:16 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.205]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FNQ007POIKK9W@mta4.snfc21.pbi.net>; Sun, 2 Jan 2000 16:55:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id ABC299160B; Sun, 02 Jan 2000 16:55:37 -0800 (PST) Date: Sun, 02 Jan 2000 16:55:37 -0800 (PST) From: Alex Zepeda Subject: Re: One final note and a "bite me" to you In-reply-to: <20000102185017.C26655@Denninger.Net> To: Karl Denninger Cc: current@FreeBSD.ORG, ports@FreeBSD.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 Sun, 2 Jan 2000, Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; This does not involve any of the rest of the list subscribers, and I'm sure the majority of us don't really want to see EITHER side's rantings. Really, grow up. If you want to flame each other, start a mailing list and do so, if you want to split, do so. Regardless, I don't care for your language nor your spamming of your political (ambiguous at that) beliefs. Just go away or be useful. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:58:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 636D815133 for ; Sun, 2 Jan 2000 16:58:24 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id TAA14841 for ; Sun, 2 Jan 2000 19:58:09 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 19:58:09 -0500 (EST) From: Chuck Robey To: FreeBSD-current@freebsd.org Subject: Karl's day off 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 OK, enough of this, let Karl be on his own for a while. Stop responding, Karl's too mad to think clearly, and you guys are just baiting him. Anyone responding is asking for addition to the kill-file. I already posted this to ports, where the other part of this has unfortunately spilled into. I won't post again. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 16:59:59 2000 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 6D9BF14DEF for ; Sun, 2 Jan 2000 16:59:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA24921; Sun, 2 Jan 2000 16:59:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA57098; Sun, 2 Jan 2000 16:59:14 -0800 (PST) (envelope-from obrien) Date: Sun, 2 Jan 2000 16:59:13 -0800 From: "David O'Brien" To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000102165913.E53691@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001022133.OAA31402@harmony.village.org> <20000102161029.A25883@Denninger.Net> <200001022232.PAA31807@harmony.village.org> <20000102163802.A25936@Denninger.Net> <200001022242.PAA31877@harmony.village.org> <20000102164519.A25992@Denninger.Net> <200001022250.PAA31962@harmony.village.org> <20000102171140.B26048@Denninger.Net> <200001022358.QAA32450@harmony.village.org> <20000102180831.A26472@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000102180831.A26472@Denninger.Net>; from karl@Denninger.Net on Sun, Jan 02, 2000 at 06:08:31PM -0600 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 Sun, Jan 02, 2000 at 06:08:31PM -0600, Karl Denninger wrote: > As for whoever the person is who force-removed me from the list, trust > me on this - I won't forget that act, and until you're identified and > permanently removed from both the list and the entire project you'll > have no contributions from me to your little treehouse project in any > way, shape or form. Do you promise?? We'll really have *NO* contributions from you? Including contributing your emails to this list?? Pretty please!!! Oh please say this is true. -- -- 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 Jan 2 17: 2:18 2000 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 C8AE614C4C for ; Sun, 2 Jan 2000 17:02:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA24938; Sun, 2 Jan 2000 17:01:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA57121; Sun, 2 Jan 2000 17:01:59 -0800 (PST) (envelope-from obrien) Date: Sun, 2 Jan 2000 17:01:59 -0800 From: "David O'Brien" To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000102170159.F53691@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000102173255.H26048@Denninger.Net> <20000102174457.A26207@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000102174457.A26207@Denninger.Net>; from karl@Denninger.Net on Sun, Jan 02, 2000 at 05:44:57PM -0600 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 Sun, Jan 02, 2000 at 05:44:57PM -0600, Karl Denninger wrote: > > We can point to the Internet's evolution of these "treehouse" organizations > and show off how PROUD we are of them and those who support them. > Let's start a nice short list, shall we? > > Network Solutions. > ARIN. > FreeBSD-CORE. > > > Shall I keep going? Yes, all the way to switching everyone of your machines to RedHat Linux, or OpenBSD (since in the past you've claimed to be so security concerned); and then removing yourself from anything even remotely FreeBSD related. I'm sure the various Linux lists and development groups would greet you with open arms and would be so very glad to benefit from your "contributions". -- -- 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 Jan 2 17:40:23 2000 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 A003015204 for ; Sun, 2 Jan 2000 17:40:17 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id CAA17589 for current@FreeBSD.org; Mon, 3 Jan 2000 02:40:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 881938863; Mon, 3 Jan 2000 02:02:44 +0100 (CET) Date: Mon, 3 Jan 2000 02:02:44 +0100 From: Ollivier Robert To: current@FreeBSD.org Subject: Re: several procmail jobs hang ... Message-ID: <20000103020244.A33752@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.org References: <20000102200003.A1618@titan.klemm.gtn.com> <20000102201039.A4336@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <20000102201039.A4336@titan.klemm.gtn.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Andreas Klemm: > procmail 3.14 bug, or does the new procmail version introduce > some new features in area where in -current is something wrong. > Not easy to say for me ... Check your locking settings on both versions. You may find that you're using different locking mechanisms... PS : and please, don't quote your own entire message, everybody including you has already seen it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 18:30:19 2000 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 64766150BA; Sun, 2 Jan 2000 18:30:15 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 116201C4A; Sun, 2 Jan 2000 21:31:20 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 0C71C3819; Sun, 2 Jan 2000 21:31:20 -0500 (EST) Date: Sun, 2 Jan 2000 21:31:20 -0500 (EST) From: Bill Fumerola To: Karl Denninger Cc: current@freebsd.org, ports@freebsd.org Subject: Re: One final note and a "bite me" to you In-Reply-To: <20000102185017.C26655@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > Theo was right in splitting off from you folks. I should have followed > him a couple of years ago and done my own split. Now, its simply not > worth it. Not that you'll listen, but: OpenBSD split from NetBSD. FreeBSD is and always has been a seperate project from NetBSD. Your credibility isn't getting any better. -- - 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 Sun Jan 2 18:50: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 7861714F06; Sun, 2 Jan 2000 18:50:01 -0800 (PST) From: "Jonathan M. Bresler" To: karl@Denninger.Net Cc: current@freebsd.org, ports@freebsd.org In-reply-to: <20000102185017.C26655@Denninger.Net> (message from Karl Denninger on Sun, 2 Jan 2000 18:50:17 -0600) Subject: Recent cat fighting in the FreeBSD mailing lists. Message-Id: <20000103025001.7861714F06@hub.freebsd.org> Date: Sun, 2 Jan 2000 18:50:01 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl, Hi, my name is Jonathan Bresler. I am the postmaster for FreeBSD. Usually, I tend to stay in the background and do the postmastering. The recent fractious behavior in the mailing lists has become so galling that I am forced to "come out from behind the curtain." Lets set the record straight on a couple items: 1. Karl, you are still subscribed to both of the "missing" mailing lists. I disabled the "which" command for those two lists: freebsd-arch and freebsd-security-notifications. That is why your subscription to those two lists did not appear when you sent the "which " request to majordomo. 2. I remove people that bounce mail. I dont send them email to tell them that I am reomving them for bouncing mail....I sincerely expect that the notification email would bounce. A bounced email is one that appears in the list(s)-owners mailbox on hub. So, sites with problems that do *not* result in immediate bounces and that fix their mail problems before the email is aged out of the queue, dont have to worry. If you suspect that you have been removed, or that I might remove you, send me an email...explain that you have been having a mail problem and when you expect the problem to be resolved. 3. Everyone, the FreeBSD mailing lists are a community resource. While there are many lists. There is only one set of lists. We all share in that set of lists. When one or more people significantly degrade the quality of the lists, the only option is to remove that person from the lists. I have done this about six times in my role as postmaster these past 5 or 6 years. 4. Core recently published guidelines for committers. These guidelines included a minimal acceptable behavior standard. The recent emails fail to come within a country mile of meeting those standards. Which perhaps does not matter as the author is not a committer. Nonetheless, the author is degrading our mailing lists and I am empowered to act on behalf to the project to prevent people from degrading the quality of the lists. It seems that today around 4:51pm PST, Karl unsubscribed from freebsd-{security,hackers,ports,scsi}. So what's the upshot of all this? Karl, take a two week sabbatical from the FreeBSD mailing lists. Consider it enforced leave. I will remove you from the remaining two mailing lists: freebsd-{announce,security-notifications}. That's all folks! I am going back "behind the curtain" to continue my spam fighting efforts. Try to behave a little better out here. Some of the mailing list subscribers are trying to sleep. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19: 1:41 2000 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 F387A15269 for ; Sun, 2 Jan 2000 19:01:37 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id TAA01725; Sun, 2 Jan 2000 19:01:26 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 19:01:26 -0800 Date: Sun, 2 Jan 2000 19:01:26 -0800 (PST) From: Kip Macy To: freebsd-current@freebsd.org Subject: latest version of threads library Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna.lyris.com X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: 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 Sorry for sending this again but when I first sent it -current was embroiled in a flame war. I would like to use the latest threads source because my application does not work correctly with the signal handling bugs in 3.x's threads. However, it does not appear that I can change it without replacing all of libc. Is this correct? Or is there some simple change I can make to the files in libc that include pthread_private.h when compiled in libc_r? I am running: FreeBSD io.lyris.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Dec 27 15:20:33 PST 1999 kip@io.lyris.com:/usr/src/sys/compile/KMM i386 Thanks. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19: 4:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 8462515269; Sun, 2 Jan 2000 19:04:33 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA53118; Sun, 2 Jan 2000 23:04:23 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 2 Jan 2000 23:04:23 -0400 (AST) From: The Hermit Hacker To: Karl Denninger Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: One final note and a "bite me" to you In-Reply-To: <20000102185017.C26655@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > Just for those of you who think this whole "magical unsubscribe" is > a "fluke"; I run/maintain the PostgreSQL mailing lists ... there is a piece of software that you can "add on" called bouncefilter that auto-unsubscribes based on various criteria ... ... and those criteria don't require the subscriber to authenticate his unsubscription ... last time this thread went through, I believe Paol(sp?) was doing similar manually? 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 Sun Jan 2 19: 5:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 85CB114EBB; Sun, 2 Jan 2000 19:05:50 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA53126; Sun, 2 Jan 2000 23:05:39 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 2 Jan 2000 23:05:38 -0400 (AST) From: The Hermit Hacker To: Will Andrews Cc: Karl Denninger , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: One final note and a "bite me" to you 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, 2 Jan 2000, Will Andrews wrote: > Theo split from NetBSD. Again, further ignorance. I suggest you sit down with a > copy of /usr/share/misc/bsd-family-tree and read a little history that you seem > to have missed. Cool, I never even knew that was there...now I have something to look at when I tell ppl that Unix has been around for 30+ years :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:11:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 8A0A315273; Sun, 2 Jan 2000 19:11:05 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id VAA27342; Sun, 2 Jan 2000 21:11:03 -0600 (CST) Message-ID: <20000102211103.A27302@Denninger.Net> Date: Sun, 2 Jan 2000 21:11:03 -0600 From: Karl Denninger To: "Jonathan M. Bresler" Cc: ports@freebsd.org, current@freebsd.org Subject: Your misleading, no, LYING message to me References: <20000103025550.C6A1B14EAC@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20000103025550.C6A1B14EAC@hub.freebsd.org>; from Jonathan M. Bresler on Sun, Jan 02, 2000 at 06:55:50PM -0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 06:55:50PM -0800, Jonathan M. Bresler wrote: > From: "Jonathan M. Bresler" > To: karl@Denninger.Net > Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG > In-reply-to: <20000102185017.C26655@Denninger.Net> (message from Karl > Denninger on Sun, 2 Jan 2000 18:50:17 -0600) > Subject: Recent cat fighting in the FreeBSD mailing lists. > Message-Id: <20000103025001.7861714F06@hub.freebsd.org> > Date: Sun, 2 Jan 2000 18:50:01 -0800 (PST) > Sender: jmb@FreeBSD.ORG > > > Karl, > > Hi, my name is Jonathan Bresler. I am the postmaster for > FreeBSD. Usually, I tend to stay in the background and do the > postmastering. The recent fractious behavior in the mailing lists has > become so galling that I am forced to "come out from behind the > curtain." > > Lets set the record straight on a couple items: > > 1. Karl, you are still subscribed to both of the "missing" mailing > lists. I disabled the "which" command for those two lists: > freebsd-arch and freebsd-security-notifications. That is why your > subscription to those two lists did not appear when you sent the > "which " request to majordomo. That's not the issue. Someone logged into HUB the EDITED me out of the CURRENT mailing list. You are mis-representing the facts. Exactly what I expect from CORE. > 2. I remove people that bounce mail. I dont send them email to tell > them that I am reomving them for bouncing mail....I sincerely expect > that the notification email would bounce. A bounced email is one that > appears in the list(s)-owners mailbox on hub. So, sites with problems > that do *not* result in immediate bounces and that fix their mail > problems before the email is aged out of the queue, dont have to > worry. If you suspect that you have been removed, or that I might > remove you, send me an email...explain that you have been having a > mail problem and when you expect the problem to be resolved. That's not the issue either. Again, someone logged into HUB and removed me. Again, who was su'd or logged into the majordomo account (or any account with write access to the list directories) a few hours ago? > 3. Everyone, the FreeBSD mailing lists are a community resource. > While there are many lists. There is only one set of lists. We all > share in that set of lists. When one or more people significantly > degrade the quality of the lists, the only option is to remove that > person from the lists. I have done this about six times in my role as > postmaster these past 5 or 6 years. Yeah, so who's the asshole who signed in and removed me? > 4. Core recently published guidelines for committers. These > guidelines included a minimal acceptable behavior standard. The recent > emails fail to come within a country mile of meeting those standards. > Which perhaps does not matter as the author is not a committer. > Nonetheless, the author is degrading our mailing lists and I am > empowered to act on behalf to the project to prevent people from > degrading the quality of the lists. > > It seems that today around 4:51pm PST, Karl unsubscribed from > freebsd-{security,hackers,ports,scsi}. Yes, *AFTER* I was removed by a fraud who signed into HUB. *I* unsubscribed from those lists LATER, after resubscribing to current, posting my "where" command, and making it known that someone else had been tampering. Go look at the DATE AND TIME STAMPED messages, AND the logs on hub. Or would you prefer to protect the GUILTY? > So what's the upshot of all this? > > Karl, take a two week sabbatical from the FreeBSD mailing lists. > Consider it enforced leave. I will remove you from the remaining two > mailing lists: freebsd-{announce,security-notifications}. Jonathan, two words for you: Go Stuff. Got it? It ain't a two-week sabbatical. Its a permanent one. You and your blow-hard assholes can go shove this "enforced leave" up your puny pucker and leave it there until it explodes. I beg in front of NOBODY, and that goes double for puny-brained cowards such as yourself who try to deliberately cover up for the unethical and inappropriate actions of other "annointed ones". You DISGUST me. I've had it. You Lord-Mighty-and-all-things-shitheaded have pulled this crap before. Yes, YOU. YOU is a plural Jonathan, for YOU speak for CORE. YOU identify as CORE and Postmaster. I want to know who the person was who su'd on Hub and removed me from the lists. I want that person ejected from your systems and publically called out for what they did. IN PUBLIC. I know damn well you won't do it, but the call remains the same, and until and unless you *DO* take this action your posting here is nothing other than YET ANOTHER fraud and piece of deceit. You should be ashamed of yourself for trying to cover up the actions of a member of your own crew. Yet that is EXACTLY what I have come to expect from FreeBSD-CORE - insular, treehouse behavior unfitting of anything except public illumination. Walnut Creek should be ashamed. And once again, for the second time in two years, I will be compelled to send a letter to Walnut Creek telling them not only of YOUR little band's actions, but also the fact that I will actively encourage people NOT to buy their CDROMs, NOT to subscribe to their pay-for-update services, and to instead TAKE what they want without renumeration. Why? Because no firm that SPONSORS the kind of bullshit that THEY DO deserves my support, and I will make damn sure that everyone who I have contact with knows why! > That's all folks! I am going back "behind the curtain" to > continue my spam fighting efforts. Try to behave a little better out > here. Some of the mailing list subscribers are trying to sleep. Yeah, sleep is about it. It goes right together with covering up the truth. Something you and Paol are so very, very good at, and which is at the ROOT of this entire controversy. Some day, you will have integrity. It will not be today. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:19:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id AA23614C29; Sun, 2 Jan 2000 19:19:07 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA53200; Sun, 2 Jan 2000 23:19:04 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 2 Jan 2000 23:19:04 -0400 (AST) From: The Hermit Hacker To: Karl Denninger Cc: "Jonathan M. Bresler" , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Note about Majordomo (Re: Your misleading, no, LYING message to me) In-Reply-To: <20000102211103.A27302@Denninger.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 Sun, 2 Jan 2000, Karl Denninger wrote: > That's not the issue either. Again, someone logged into HUB and > removed me. > > Again, who was su'd or logged into the majordomo account (or any account > with write access to the list directories) a few hours ago? This isn't required ... with nothing more then the admin password to the mailing list, anyone around the world could easily have removed anyone else from the list by sending an administrative request to the majordomo account... 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 Sun Jan 2 19:22: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 7628414EFA for ; Sun, 2 Jan 2000 19:22:05 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id WAA27520; Sun, 2 Jan 2000 22:22:01 -0500 (EST) Date: Sun, 2 Jan 2000 22:22:01 -0500 (EST) From: Daniel Eischen Message-Id: <200001030322.WAA27520@pcnet1.pcnet.com> To: freebsd-current@FreeBSD.ORG, kip@lyris.com Subject: Re: latest version of threads library Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kip Macy wrote: > Sorry for sending this again but when I first sent it -current was > embroiled in a flame war. > > I would like to use the latest threads source because my application does > not work correctly with the signal handling bugs in 3.x's threads. > However, it does not appear that I can change it without replacing all of > libc. Is this correct? Or is there some simple change I can make to the > files in libc that include pthread_private.h when compiled in libc_r? Hmm, I think the only thing that will bite you in bringing in -currents libc_r are the socket.h changes that went in around Nov 24, 1999. I haven't tried it myself... YMMV Someone is working on merging -current libc_r into -stable, so perhaps if you want to hold out a little longer, it'll get done for you. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:30:23 2000 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 47F3614E14; Sun, 2 Jan 2000 19:30:21 -0800 (PST) (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.9.3) with ESMTP id TAA01403; Sun, 2 Jan 2000 19:30:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001030330.TAA01403@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 21:11:03 CST." <20000102211103.A27302@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jan 2000 19:30:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to say that PHK has become the MASTER at pissing people off, ensuring that his opponent goes the deep end and staying calm so the blame obviously does not fall on him. Got to admit his formula is very very nice 8) By a long shot the problem is NOT Karl. It takes at least TWO to engage in a combatitive conflict -- that is if you are not schizophreniac. The proper tactic to resolve the conflict should have been to wait a cool off period and then slug it off technically. Nevertheless, instead of waiting for Karl to cool off and attempt to ration with him , it was much easier to drive him further down: hence thru censorship the "technical" argument was won with virtually no technical effort at all -- Like I said earlier very very nice tactic ! -- 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 Sun Jan 2 19:30:56 2000 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 E5BC615305 for ; Sun, 2 Jan 2000 19:30:51 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id TAA01837; Sun, 2 Jan 2000 19:30:13 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 02 Jan 2000 19:30:12 -0800 Date: Sun, 2 Jan 2000 19:30:12 -0800 (PST) From: Kip Macy To: Daniel Eischen Cc: freebsd-current@FreeBSD.ORG Subject: Re: latest version of threads library In-Reply-To: <200001030322.WAA27520@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna.lyris.com X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: eischen@vigrid.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 Do you know what the timeline is on this integration? -Kip On Sun, 2 Jan 2000, Daniel Eischen wrote: > Kip Macy wrote: > > Sorry for sending this again but when I first sent it -current was > > embroiled in a flame war. > > > > I would like to use the latest threads source because my application does > > not work correctly with the signal handling bugs in 3.x's threads. > > However, it does not appear that I can change it without replacing all of > > libc. Is this correct? Or is there some simple change I can make to the > > files in libc that include pthread_private.h when compiled in libc_r? > > Hmm, I think the only thing that will bite you in bringing in -currents > libc_r are the socket.h changes that went in around Nov 24, 1999. I > haven't tried it myself... YMMV > > Someone is working on merging -current libc_r into -stable, so perhaps > if you want to hold out a little longer, it'll get done for you. > > Dan Eischen > eischen@vigrid.com > > > 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 Jan 2 19:40:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 27796152E7; Sun, 2 Jan 2000 19:40:17 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id TAA26082; Sun, 2 Jan 2000 19:39:07 -0800 (PST) Message-Id: <200001030339.TAA26082@implode.root.com> To: Karl Denninger Cc: "Jonathan M. Bresler" , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 21:11:03 CST." <20000102211103.A27302@Denninger.Net> From: David Greenman Reply-To: dg@root.com Date: Sun, 02 Jan 2000 19:39:07 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Someone logged into HUB the EDITED me out of the CURRENT mailing list. As near as I can tell, noone with the ability to su was logged into hub earlier today when you claim that you were removed. As far as I know, noone had removed you. I have not seen any messages (other than your claim) or any other evidence that would indicate such an action occured. >Again, who was su'd or logged into the majordomo account (or any account >with write access to the list directories) a few hours ago? Noone as far as I can tell. Jonathan is a man of exceptional integrity and you have no basis for making the accusations that you have against him. I think you owe him an apology. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:44: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from swan.en-bio.com.au (swan.en-bio.com.au [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id 09FDD152C1 for ; Sun, 2 Jan 2000 19:44:05 -0800 (PST) (envelope-from Tony.Maher@eBioinformatics.com) Received: from shad.internal.en-bio (www-cache.en-bio.com.au [203.35.254.2]) by swan.en-bio.com.au (8.9.1a/8.9.1) with ESMTP id OAA02550; Mon, 3 Jan 2000 14:43:50 +1100 Received: (from tonym@localhost) by shad.internal.en-bio (8.9.1b+Sun/8.9.1) id OAA27236; Mon, 3 Jan 2000 14:43:30 +1100 (EST) Date: Mon, 3 Jan 2000 14:43:30 +1100 (EST) From: Tony Maher Message-Id: <200001030343.OAA27236@shad.internal.en-bio> To: hasty@rah.star-gate.com Cc: current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) I dont think so. Whatever PHK may or may not have done in the past his answers in this latest storm in a tea cup were more than reasonable and informative. > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. Yes it was two - Karl vs reasoned discussion. tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:49:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 5654D14E14; Sun, 2 Jan 2000 19:49:27 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id TAA26132; Sun, 2 Jan 2000 19:47:51 -0800 (PST) Message-Id: <200001030347.TAA26132@implode.root.com> To: Amancio Hasty Cc: Karl Denninger , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 19:30:12 PST." <200001030330.TAA01403@rah.star-gate.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 02 Jan 2000 19:47:51 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have to say that PHK has become the MASTER at pissing >people off, ensuring that his opponent goes the deep end >and staying calm so the blame obviously does not fall on >him. Got to admit his formula is very very nice 8) > > >By a long shot the problem is NOT Karl. It takes at least >TWO to engage in a combatitive conflict -- that is if >you are not schizophreniac. > >The proper tactic to resolve the conflict should have >been to wait a cool off period and then slug it off >technically. Nevertheless, instead of waiting for >Karl to cool off and attempt to ration with him , >it was much easier to drive him further down: hence >thru censorship the "technical" argument was won >with virtually no technical effort at all -- Like I said >earlier very very nice tactic ! May I respectfully request that people not jump to conclusions without a lot more to go on than some angry accusations. I would also like to say that Poul-Henning's behavior in this thread was exceptional and that Karl had no reason to react the way he did. I think Karl owes a lot of people some apologies. His behavior was clearly inappropriate and continues to be so. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 19:56:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from pistol.cde.com (pistol.cde.com [204.117.195.6]) by hub.freebsd.org (Postfix) with ESMTP id 5A95E152A4 for ; Sun, 2 Jan 2000 19:56:39 -0800 (PST) (envelope-from dev-null@no-id.com) Received: (from nobody@localhost) by pistol.cde.com (8.8.8/8.8.5) id WAA13364; Sun, 2 Jan 2000 22:56:35 -0500 Date: Sun, 2 Jan 2000 22:56:35 -0500 From: dev-null@no-id.com Message-Id: <200001030356.WAA13364@pistol.cde.com> To: freebsd-current@freebsd.org Reply-To: freebsd-current@freebsd.org Subject: Your misleading, no, LYING message to me Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Congratulations, Karl. You just proven to the world what a complete asshole you really are. Now get out of here. We don't want you. -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20: 3: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 65B7B14FB8 for ; Sun, 2 Jan 2000 20:02:59 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac6.wam.umd.edu (root@rac6.wam.umd.edu [128.8.10.146]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA04902 for ; Sun, 2 Jan 2000 23:02:50 -0500 (EST) Received: from rac6.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac6.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA02865 for ; Sun, 2 Jan 2000 23:02:53 -0500 (EST) Received: from localhost (culverk@localhost) by rac6.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA02861 for ; Sun, 2 Jan 2000 23:02:53 -0500 (EST) X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs Date: Sun, 2 Jan 2000 23:02:53 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-Reply-To: <200001030356.WAA13364@pistol.cde.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 Alright, that was childish and uncalled for. People need to learn to deal with these kinds of things differently. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 2 Jan 2000 dev-null@no-id.com wrote: > Congratulations, Karl. You just proven to the world what a complete asshole you really are. > > Now get out of here. We don't want you. > > -- > This message has been sent via an anonymous mail relay at www.no-id.com. > > > > 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 Jan 2 20: 3:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id 1EE1514E41 for ; Sun, 2 Jan 2000 20:03:50 -0800 (PST) (envelope-from smccloud@tcainternet.com) Received: from q4h7k8 ([208.180.62.127]) by mail.tyler.net (Post.Office MTA Undefined release Undefined ID# 0-54929U30000L30000S0V35) with SMTP id net for ; Sun, 2 Jan 2000 22:02:48 -0600 Message-ID: <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> From: "----" To: References: <200001030356.WAA13364@pistol.cde.com> Subject: Re: Your misleading, no LYING message to me Date: Sun, 2 Jan 2000 21:59:28 -0600 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.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG He is just expressing his point. From what I can tell someone removed him from the list with no reason and now he is angry. I probably would be too. Also, I can tell that someone is doing some good covering up. Its ashame to see leaders do this. Sam ----- Original Message ----- From: To: Sent: Sunday, January 02, 2000 9:56 PM Subject: Your misleading, no, LYING message to me > Congratulations, Karl. You just proven to the world what a complete asshole you really are. > > Now get out of here. We don't want you. > > -- > This message has been sent via an anonymous mail relay at www.no-id.com. > > > > 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 Jan 2 20:17:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id EA9D814D4B; Sun, 2 Jan 2000 20:17:15 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA15359; Sun, 2 Jan 2000 23:16:43 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 23:16:43 -0500 (EST) From: Chuck Robey To: Amancio Hasty Cc: Karl Denninger , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-Reply-To: <200001030330.TAA01403@rah.star-gate.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, 2 Jan 2000, Amancio Hasty wrote: > I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) > > > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. > > The proper tactic to resolve the conflict should have > been to wait a cool off period and then slug it off > technically. Nevertheless, instead of waiting for > Karl to cool off and attempt to ration with him , > it was much easier to drive him further down: hence > thru censorship the "technical" argument was won > with virtually no technical effort at all -- Like I said > earlier very very nice tactic ! Amancio, you are making assumptions, ones that are completely incorrect here. Karl's frothing started with a lot of raging at Steve on the ports list, and at the entire structure of ports. Poul didn't get into it until quite a bit later, and it was Karl who went after Poul, not vice versa. Poul reacted to someone accusing him of a complete lack of integrity (with no more evidence than McCarthy had in the 50's) merely by asking him to step back a little ways before he really annoyed folks. I wonder if I would react as well? What's more, while you're right that Poul's sometimes been abrasive in the past, his behaviour has been so above reproach here that I felt it necessary to jump in, just to highlight the fact, and maybe to avoid having people jump at the assumption you made (I referenced that directly in my post). I've never met Poul personally, but I *have* met Jonathan Bresler. That last post of Karl's, well, if that doesn't categorize him in your eyes, then I guess nothing will. Believe me, Amancio, Jonathan didn't deserve that. I think everyone really should let this darn thread die ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20:20:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 3B03615292 for ; Sun, 2 Jan 2000 20:20:47 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA15379 for ; Sun, 2 Jan 2000 23:20:30 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 23:20:29 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: The mails from dev-null In-Reply-To: <200001030356.WAA13364@pistol.cde.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, 2 Jan 2000 dev-null@no-id.com wrote: > Congratulations, Karl. You just proven to the world what a complete > asshole you really are. > > Now get out of here. We don't want you. Will whoever this is, please stop? There is no valid reason for anonymity here (and to be honest, in this situation, it rather strikes me as cowardly) and we don't need the sentiments, because you're only going to provoke this further. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20:21:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id EBFE515427 for ; Sun, 2 Jan 2000 20:21:28 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id UAA26206; Sun, 2 Jan 2000 20:20:55 -0800 (PST) Message-Id: <200001030420.UAA26206@implode.root.com> To: "----" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 21:59:28 CST." <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 02 Jan 2000 20:20:55 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >He is just expressing his point. From what I can tell someone removed him >from the list with no reason and now he is angry. I probably would be too. That is not at all what happend. Karl went off the deep end about phk recommending a Motorola GPS to do timekeeping. Then, after a pile of insulting messages from Karl, Karl made an accusation that someone removed him from three of the mailing lists. For at least two of those lists, he was simply wrong. For the third (freebsd-current), there is no evidence to support his claim. >Also, I can tell that someone is doing some good covering up. Its ashame to >see leaders do this. How can you tell that? There is no evidence to support that. *I'm* certainly not covering anything up and I've seen no reason to believe that anyone else is, either. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20:29:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id 4DE11152A4 for ; Sun, 2 Jan 2000 20:29:50 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id FAA18323 for ; Mon, 3 Jan 2000 05:29:25 +0100 Received: (qmail 66213 invoked from network); 3 Jan 2000 04:29:06 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 3 Jan 2000 04:29:06 -0000 Received: (qmail 6724 invoked by uid 500); 3 Jan 2000 04:29:05 -0000 Date: Mon, 3 Jan 2000 05:29:05 +0100 From: Sascha Schumann To: ---- Cc: freebsd-current@freebsd.org Subject: Re: Your misleading, no LYING message to me Message-ID: <20000103052905.A3438@schumann.cx> References: <200001030356.WAA13364@pistol.cde.com> <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net>; from smccloud@tcainternet.com on Sun, Jan 02, 2000 at 09:59:28PM -0600 X-Notice: Copyright (c) 1999 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.13 #10 Mon Dec 27 20:35:15 CET 1999 alpha Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 09:59:28PM -0600, ---- wrote: > He is just expressing his point. From what I can tell someone removed him > from the list with no reason and now he is angry. I probably would be too. That does not excuse his style of communication. Shouting and calling people names is no solution. It will damage the relationship between the involved parties and will make an agreement among them impossible. You can express emotions, but please do it in a civilized and controlled way. I usually recommened the following books to disagreeing parties. They are easy to read and tell you much about communication. Getting to Yes, by Fisher and Ury, ISBN 0140157352 (Focusing on Interests, not on Positions) Getting Past No, by Ury, ISBN 0553371312 (Negotiating Your Way from Confrontation to Cooperation) -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20:33:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 36F8714F3A for ; Sun, 2 Jan 2000 20:33:27 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id UAA00361; Sun, 2 Jan 2000 20:33:23 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000102203021.00aa69f0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 02 Jan 2000 20:33:22 -0800 To: dg@root.com, ---- From: Manfred Antar Subject: Re: Your misleading, no LYING message to me Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200001030420.UAA26206@implode.root.com> References: <"Your message of Sun, 02 Jan 2000 21:59:28 CST." <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> 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 08:20 PM 1/2/00 -0800, David Greenman wrote: > >He is just expressing his point. From what I can tell someone removed him > >from the list with no reason and now he is angry. I probably would be too. > > That is not at all what happend. Karl went off the deep end about phk >recommending a Motorola GPS to do timekeeping. Then, after a pile of >insulting messages from Karl, Karl made an accusation that someone removed >him from three of the mailing lists. For at least two of those lists, he >was simply wrong. For the third (freebsd-current), there is no evidence >to support his claim. > > >Also, I can tell that someone is doing some good covering up. Its ashame to > >see leaders do this. > > How can you tell that? There is no evidence to support that. *I'm* >certainly not covering anything up and I've seen no reason to believe that >anyone else is, either. > >-DG PLEASE STOP THIS There are things that need fixing and this is going nowhere. You are all very talented people. Enough Enough Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 20:48:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust128.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 67E7714F5C; Sun, 2 Jan 2000 20:48:10 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 2 Jan 2000 23:48:07 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org, cg@FreeBSD.org, tanimura@FreeBSD.org Subject: Re: new PCM problems 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, 2 Jan 2000, Kenneth Wayne Culver wrote: > OK, there is still the static problem with the pcm driver with a ViBRA16X > soundcard. It also seems that the problem with xmms's analyzer is gone. > However, now whenever a sound that is shorter than roughly 1 second or so > plays, it gets cut short. The sound doesn't completely play. I just > thought I'd let someone know what is going on here on my -CURRENT box. I'm noticing the exact same thing. I'll CC this to cg and tanimura, since they're the big maintainers of the driver. > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= (I didn't know you lived so close :) -- 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 Sun Jan 2 20:48:22 2000 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 56E0514EE1; Sun, 2 Jan 2000 20:48:17 -0800 (PST) (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.9.3) with ESMTP id UAA02064; Sun, 2 Jan 2000 20:48:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001030448.UAA02064@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com Cc: Karl Denninger , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 19:47:51 PST." <200001030347.TAA26132@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jan 2000 20:48:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, My post is not really based upon the last Karl vs. Pohl thread. It is more on what I have observed quietly over the last few months . If the behavior is left unchecked you can rest assure that their will be more flares up. Again, to have waited for Karl to cool off is not that unreasonable to ask if the interested party wanted to reason with him. I supposed that there are some who are a virtuoso at calming and reasoning with extremely angry people. I have always opted to wait for the person to calm down and then try to reason with them. Perhaps , in this new WWW world my ways are wrong and old fashioned... Take Care Guys, I am back to hacking and yes I am having a great time ! -- 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 Sun Jan 2 21: 4:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust128.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0ED8B152DA; Sun, 2 Jan 2000 21:04:08 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 3 Jan 2000 00:04:05 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kip Macy Cc: current@freebsd.org Subject: Re: [Majordomo@FreeBSD.ORG: Majordomo results: which] 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, 2 Jan 2000, Kip Macy wrote: > > Any pointers to web pages on setting up a killfile? The signal to noise > ratio on this list is dropping rapidly. I haven't done it myself, but I know that you can read some of the documentation for procmail (/usr/ports/mail/procmail) and easily forward certain mail to /dev/null. If you want an example, I'm certain I could come up with one for you :) > -Kip -- 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 Sun Jan 2 21:34:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 6BEC8151FC; Sun, 2 Jan 2000 21:34:30 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA06837; Mon, 3 Jan 2000 00:34:25 -0500 (EST) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA08420; Mon, 3 Jan 2000 00:34:27 -0500 (EST) Received: from localhost (culverk@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA08416; Mon, 3 Jan 2000 00:34:27 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Mon, 3 Jan 2000 00:34:27 -0500 (EST) From: Kenneth Wayne Culver To: Brian Fundakowski Feldman Cc: freebsd-current@FreeBSD.ORG, cg@FreeBSD.ORG, tanimura@FreeBSD.ORG Subject: Re: new PCM problems 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 Thanks. I would've tried to fix it myself, but I am not too familiar with programming for a soundcard. I'm only famaliar with the ata driver right now. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 2 Jan 2000, Brian Fundakowski Feldman wrote: > On Sun, 2 Jan 2000, Kenneth Wayne Culver wrote: > > > OK, there is still the static problem with the pcm driver with a ViBRA16X > > soundcard. It also seems that the problem with xmms's analyzer is gone. > > However, now whenever a sound that is shorter than roughly 1 second or so > > plays, it gets cut short. The sound doesn't completely play. I just > > thought I'd let someone know what is going on here on my -CURRENT box. > > I'm noticing the exact same thing. I'll CC this to cg and tanimura, > since they're the big maintainers of the driver. > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best OS around. | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: AgRSkaterq | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > (I didn't know you lived so close :) > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 22:12:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mentisworks.com (valkery.mentisworks.com [207.227.89.226]) by hub.freebsd.org (Postfix) with ESMTP id D56A814D76 for ; Sun, 2 Jan 2000 22:12:04 -0800 (PST) (envelope-from nathank@mentisworks.com) Received: from [24.29.246.53] (HELO mentisworks.com) by mentisworks.com (CommuniGate Pro SMTP 3.2b7) with ESMTP id 640953 for freebsd-current@freebsd.org; Mon, 03 Jan 2000 00:12:14 -0600 Received: from [192.168.245.111] (HELO mentisworks.com) by mentisworks.com (CommuniGate Pro SMTP 3.2b9) with ESMTP id 2230017 for freebsd-current@freebsd.org; Mon, 03 Jan 2000 00:12:04 -0600 Message-ID: <38703D1E.14E37458@mentisworks.com> Date: Mon, 03 Jan 2000 00:09:34 -0600 From: Nathan Kinsman Organization: Mentisworks, LLC X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy all, I'm putting together some specs for a type of firewall appliance using the eventual released version of FreeBSD 4 (targeting 4.x because I need GCC 2.95.x as core compiler). My current machine specs use the following hardware which I am not yet sure will be well supported. FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) AMD K6-III/450 processor (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) Poware IM-7500 IDE Hot Swappable IDE RAID device Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp devices?) I have not been running CURRENT extensively, so I would like to know anyone's experiences with any of the above hardware, or any recommendations on hardware with a better price/performance ratio at a low thermal (chassis is very compact). I was also considering using a NIC from 3COM, or Netgear, or even Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently the best option. I understand the 3C905 may also be good, but it lacks an onboard processor. Anything with better performance and lower CPU utilization then the EtherExpress PRO/100+?? Thanks for any assistance. -- Nathan Kinsman |nathank@mentisworks.com| |http://www.mentisworks.com| Managing Partner / Network Systems Architect, Mentisworks LLC Voice/Fax: | Chicago | +1 312 803-2220 | Sydney | + 61 2 9475 4500 All correspondence should be considered confidential. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 22:42:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 1F8B814D89 for ; Sun, 2 Jan 2000 22:42:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA13891; Sun, 2 Jan 2000 22:47:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001030647.WAA13891@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nathan Kinsman Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested In-reply-to: Your message of "Mon, 03 Jan 2000 00:09:34 CST." <38703D1E.14E37458@mentisworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jan 2000 22:47:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm putting together some specs for a type of firewall appliance using > the eventual released version of FreeBSD 4 (targeting 4.x because I need > GCC 2.95.x as core compiler). My current machine specs use the > following hardware which I am not yet sure will be well supported. > > FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) > AMD K6-III/450 processor > (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) These should all be fine, although you may want to go for something in the 5400rpm range if thermal issues concern you. The speed differential isn't massive, and disk speed probably isn't an issue for you. > Poware IM-7500 IDE Hot Swappable IDE RAID device This one might be interesting. Does it do automatic rebuilds? > Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp > devices?) Yup. > I have not been running CURRENT extensively, so I would like to know > anyone's experiences with any of the above hardware, or any > recommendations on hardware with a better price/performance ratio at a > low thermal (chassis is very compact). You might want a slower and cooler CPU (consider a Celeron), a board with less cache (cooler), and slower disks. Without any sort of benchmarking feel for your application, it's hard to know where tradeoffs are worthwhile. > I was also considering using a NIC from 3COM, or Netgear, or even > Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently > the best option. I understand the 3C905 may also be good, but it lacks > an onboard processor. The EtherExpress Pro/100 also 'lacks an onboard processor'. Both the Intel and 3Com adapters are good choices; I would be choosing based on price and performance in your application. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 22:44:52 2000 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 B4A4E15135 for ; Sun, 2 Jan 2000 22:44:48 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id WAA51630; Sun, 2 Jan 2000 22:44:45 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 2 Jan 2000 22:44:44 -0800 (PST) From: Doug White To: Marcel Moolenaar Cc: current@freebsd.org Subject: Re: SUBMIT: compat.linux.pathmunge In-Reply-To: <386FA009.15B46B3F@scc.nl> 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 bringing this back up to -current to kick around some more. We may want to move it to -emulators. On Sun, 2 Jan 2000, Marcel Moolenaar wrote: > > This isn't intended as a 'final solution' :-) The problem is *very* > > difficult since you're asking the syscall to intuit what the user/program > > intends to do with the file. > Hmmm.. What we want is a way to tell the Linuxulator on a process/binary > level whether we want /compat/linux overlaying or not. Indeed, backup > clients will pick up /compat/linux as an ordinary directory without > overlaying and that is exactly what we want. In most cases we do want > the overlaying. Having process/binary granularity would be more useful, but is hard to implement in an inobrusive way, as we're discovering below. :) Binary granulatirty could be an issue for shells. > > If you could tag dynamic loader open()s you could have a selective > > translator for just that, but when it's hunting for /etc/host.conf, which > > one do you give it? Is it a call from resolv+ looking for it's > > configuration, or a backup client putting it on tape? > > What about brandelf? When a static ELF binary is branded as `Linux', we > have overlaying; when it's branded as 'LinuxBSD' (or what's in a name) > it's a Linux binary that don't want/need overlaying. Dynamic ELF > binaries are more tricky, but can make to work by setting > LD_LIBRARY_PATH in a wrapper. Yuck. brandelf is an agreed-on standard (or is supposed to be) and it wouldn't be appropriate to abuse it. I'd be more apt to run the target app in a wrapper that makes a 'shut off translation for this pid' type syscall then execve()s the app. Kinda like nohup. > > I don't have any ideas at this point. I'd be willing to add some features > > to this patch (i.e. specify arbitrary root) but I don't want to sit on it > > until linuxmode grows a psychic user mind reader. :) > > :-) It isn't as easy as it looks, eh? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Jan 2 22:58:49 2000 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 A076914D79 for ; Sun, 2 Jan 2000 22:58:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA02376; Sun, 2 Jan 2000 22:58:41 -0800 (PST) (envelope-from dillon) Date: Sun, 2 Jan 2000 22:58:41 -0800 (PST) From: Matthew Dillon Message-Id: <200001030658.WAA02376@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no LYING message to me Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------> enters stage right ... opens door ... heeeeeyyyyyy a party! And nobody invited me! Ummmm, Why's the piano broken in two and all the tables overturned? Ahhh, whats with all the stares? guys? Guys! exits stage left (at a run) ------> -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 23:16:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id EE49314D89 for ; Sun, 2 Jan 2000 23:16:19 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id CAA16212; Mon, 3 Jan 2000 02:16:02 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 3 Jan 2000 02:16:02 -0500 (EST) From: Chuck Robey To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no LYING message to me In-Reply-To: <200001030658.WAA02376@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 Sun, 2 Jan 2000, Matthew Dillon wrote: > ------> enters stage right > > ... opens door ... > heeeeeyyyyyy a party! And nobody invited me! > > Ummmm, Why's the piano broken in two and all the tables > overturned? Ahhh, whats with all the stares? guys? > Guys! > > exits stage left (at a run) ------> > > -Matt Aww, you missed it! We had a broken bottle with your name on it! :-) ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 23:37:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucc.gu.uwa.edu.au (moray.ucc.gu.uwa.edu.au [130.95.13.9]) by hub.freebsd.org (Postfix) with ESMTP id 2D6EC14EC7 for ; Sun, 2 Jan 2000 23:37:15 -0800 (PST) (envelope-from unclemib@ucc.gu.uwa.edu.au) Received: from mussel.ucc.gu.uwa.edu.au (root@mussel.ucc.gu.uwa.edu.au [130.95.13.18]) by ucc.gu.uwa.edu.au (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA22659 for ; Mon, 3 Jan 2000 15:37:10 +0800 Received: (from unclemib@localhost) by mussel.ucc.gu.uwa.edu.au (8.9.3/8.9.3/Debian/GNU) id PAA13109 for current@freebsd.org; Mon, 3 Jan 2000 15:37:09 +0800 Date: Mon, 3 Jan 2000 15:37:09 +0800 From: Richard Sather Message-Id: <200001030737.PAA13109@mussel.ucc.gu.uwa.edu.au> To: current@freebsd.org Subject: Mr Denninger has a problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG will somebody filter Mr Denninger from the list his postings are beginning to to irritate and look more and more like the ravings of an offensive lunatic who drank too much methanol during new years celebrations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 23:43:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mentisworks.com (valkery.mentisworks.com [207.227.89.226]) by hub.freebsd.org (Postfix) with ESMTP id 6B87E14F39; Sun, 2 Jan 2000 23:43:15 -0800 (PST) (envelope-from nathank@mentisworks.com) Received: from [24.29.246.53] (HELO mentisworks.com) by mentisworks.com (CommuniGate Pro SMTP 3.2b7) with ESMTP id 640961; Mon, 03 Jan 2000 01:43:24 -0600 Received: from [192.168.245.111] (HELO mentisworks.com) by mentisworks.com (CommuniGate Pro SMTP 3.2b9) with ESMTP id 2230024; Mon, 03 Jan 2000 01:43:15 -0600 Message-ID: <3870527D.4771B6F7@mentisworks.com> Date: Mon, 03 Jan 2000 01:40:45 -0600 From: Nathan Kinsman Organization: Mentisworks, LLC X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested References: <200001030647.WAA13891@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I'm putting together some specs for a type of firewall appliance using > > the eventual released version of FreeBSD 4 (targeting 4.x because I need > > GCC 2.95.x as core compiler). My current machine specs use the > > following hardware which I am not yet sure will be well supported. > > > > FIC PAG-2130 Micro-ATX motherboard with 2/MB cache (Apollo MVP4 chipset) > > AMD K6-III/450 processor > > (2) 10.1GB Maxtor DiamondMAX Plus 40 7200 RPM IDE HDDs (mirrored) > > These should all be fine, although you may want to go for something in the > 5400rpm range if thermal issues concern you. The speed differential > isn't massive, and disk speed probably isn't an issue for you. This hard drive seems to be somewhat extraordinary in regards to heat generation. I'm using two now in a test machine, it remains cool to the touch after a 'make world -j4' under FreeBSD 3.3 even though enclosed in a standard single fan cooled ATX case. It also outperformed a 10k WD Digital Advantage SCSI drive in the same task by about 7%. I have to really hand it to Maxtor for releasing some exceedingly high quality drives as of late. I'm concerned about possible poor interactions with the new ATA driver however. I have seen very little posted regarding the MVP3 or MVP4 chipset in freebsd-current. > > Poware IM-7500 IDE Hot Swappable IDE RAID device > > This one might be interesting. Does it do automatic rebuilds? > Yes, it claims to do on-line recovery. It is also OS independent. I will be testing a few of these units this month. Try http://www.poware.com.tw for more info. > > Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp > > devices?) > > Yup. > > > I have not been running CURRENT extensively, so I would like to know > > anyone's experiences with any of the above hardware, or any > > recommendations on hardware with a better price/performance ratio at a > > low thermal (chassis is very compact). > > You might want a slower and cooler CPU (consider a Celeron), a board with > less cache (cooler), and slower disks. Without any sort of benchmarking > feel for your application, it's hard to know where tradeoffs are > worthwhile. I was looking at the PPGA Celerons earlier. I'm a little concerned about the cache size though. What is interesting to me is the K6-III/450's and their 64KB Level 1 cache and 256KB Level 2 cache. I am guessing that coupled with the FIC PAG-2130's 2MB Level 3 cache, there could be a significant performance advantage for memory intensive processing. I may put together a Celeron 500 system and benchmark it against a K6-III/450 with the FIC motherboard. Perhaps the K6-III cache size advantage is just theoretical. Processing performance is critical as I would like to minimize as much as possible the additional latency added by the firewall and filtering applications, as the amount of conditions being processed is extensive. > > I was also considering using a NIC from 3COM, or Netgear, or even > > Kingston, but it seems that the Intel EtherExpress PRO/100+ is currently > > the best option. I understand the 3C905 may also be good, but it lacks > > an onboard processor. > > The EtherExpress Pro/100 also 'lacks an onboard processor'. Both the > Intel and 3Com adapters are good choices; I would be choosing based on > price and performance in your application. Aah, yes, I was thinking of the Pro/100 Intelligent Server Adapter with the i960 processor (I'm don't see any driver support for this one). Hmm... is there any supported NICs with a processor to offload the main CPU? What about the Thunderlan based cards? Perhaps spending more on a NIC could justify a lower powered CPU. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com Thanks for the insights. -- Nathan Kinsman |nathank@mentisworks.com| |http://www.mentisworks.com| Managing Partner / Network Systems Architect, Mentisworks LLC Voice/Fax: | Chicago | +1 312 803-2220 | Sydney | + 61 2 9475 4500 All correspondence should be considered confidential. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 23:48:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 5FFCD14F56; Sun, 2 Jan 2000 23:48:20 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca3-67.ix.netcom.com [209.109.233.67]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id XAA04984; Sun, 2 Jan 2000 23:46:53 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id XAA18992; Sun, 2 Jan 2000 23:46:48 -0800 (PST) (envelope-from asami) To: ports@freebsd.org, current@freebsd.org Subject: Re: Your misleading, no, LYING message to me References: <20000103025550.C6A1B14EAC@hub.freebsd.org> <20000102211103.A27302@Denninger.Net> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 02 Jan 2000 23:46:48 -0800 In-Reply-To: Karl Denninger's message of "Sun, 2 Jan 2000 21:11:03 -0600" Message-ID: Lines: 8 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Karl Denninger Wow, that was good! I'm going to nominate this for "this century's most amusing message on the FreeBSD lists" award. :) Satoshi "you can figure out which century I'm talking about" Asami To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 2 23:54: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from pistol.cde.com (pistol.cde.com [204.117.195.6]) by hub.freebsd.org (Postfix) with ESMTP id 55476152D3 for ; Sun, 2 Jan 2000 23:53:59 -0800 (PST) (envelope-from dev-null@no-id.com) Received: (from nobody@localhost) by pistol.cde.com (8.8.8/8.8.5) id CAA14240; Mon, 3 Jan 2000 02:53:56 -0500 Date: Mon, 3 Jan 2000 02:53:56 -0500 From: dev-null@no-id.com Message-Id: <200001030753.CAA14240@pistol.cde.com> To: freebsd-current@freebsd.org Reply-To: freebsd-current@freebsd.org Subject: Mr Denninger Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, I think he douched with a molatov cocktail, after his boyfriend fisted him. >will somebody filter Mr Denninger from the list his >postings are beginning to to irritate and look more and >more like the ravings of an offensive lunatic who drank too much methanol during new years celebrations -- This message has been sent via an anonymous mail relay at www.no-id.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 0: 4:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 9F0EB14FDD for ; Mon, 3 Jan 2000 00:04:52 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id AAA44374 for ; Mon, 3 Jan 2000 00:04:52 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: Subject: RE: Mr Denninger Date: Mon, 3 Jan 2000 00:04:57 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <200001030753.CAA14240@pistol.cde.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of > dev-null@no-id.com > Sent: Sunday, January 02, 2000 11:54 PM > To: freebsd-current@FreeBSD.ORG > Subject: Mr Denninger > > > Oh, I think he douched with a molatov cocktail, after his > boyfriend fisted him. > > >will somebody filter Mr Denninger from the list his >postings > are beginning to to irritate and look more and >more like the > ravings of an offensive lunatic who drank too much methanol > during new years celebrations > > -- > This message has been sent via an anonymous mail relay at www.no-id.com. > Can this site be filtered as well? FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" > > > 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 Jan 3 0:52: 4 2000 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 AB2A114C47; Mon, 3 Jan 2000 00:52:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA00994; Mon, 3 Jan 2000 00:52:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Jonathan M. Bresler" , current@freebsd.org Subject: Re: Your misleading, no, LYING message to me In-reply-to: Your message of "Sun, 02 Jan 2000 21:11:03 CST." <20000102211103.A27302@Denninger.Net> Date: Mon, 03 Jan 2000 00:52:04 -0800 Message-ID: <991.946889524@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear friends, I know that many of you may feel slightly let-down by the fact that nothing truly significant seems to have happened during our transition to the year 2000, a good many button-clicks on www.cnn.com having gone for naught as the hour approached and receded, nothing following yet more nothing as we waited for calamities which never came. I was certainly expecting at least one big bomb to go off somewhere, if not an actual nuclear device, and I know many others had their money on some sort of significant terrorist attack on the western nations or, failing that, at least the mass-arrest and deportation of thousands of "shady characters" and some hasty amendments to the American constitution which allowed more expeditious handling of such people in the future. No such luck. Not even a plummeting Chinese airliner (with their minister for transportation on board) enlivened the headlines and it was all just so frightfully dull dull dull the entire time. Believe me, I commiserate with all of you. However, even so I must object to this rather flagrantly transparent attempt to cheer up (?) the doom-sayers by stage-mastering an "apocalyptic flame war" in the -current mailing list. A TRULY apocalyptic flame war, with people resigning their positions and switching to The HURD left and right, that might have actually been kind of interesting and gone, in a rather pathetic way, some ways towards redressing the balance for the disappointing lack of a [not]millennial world-wide conflagration. This, however, was just too camp to be believable and, as much as I have to thank Karl for trying, he just went a little bit TOO far in his attempt to spray spittle in a convincing fashion and the whole suspension of disbelief thing just collapsed for me, so in the end I really just couldn't find it as enlivening as the genuine article. I know Karl's heart was in the right place though and I appreciate the gesture. That's our Karl, always thinking of others. A big man with a big heart! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 1:28: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id 5099514EFA for ; Mon, 3 Jan 2000 01:28:01 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id KAA30399; Mon, 3 Jan 2000 10:27:55 +0100 (MET) Date: Mon, 3 Jan 2000 10:27:55 +0100 From: Martin Cracauer To: Nathan Kinsman Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 4.0-RELEASE hardware specs, advice/experience requested Message-ID: <20000103102755.A29541@cons.org> References: <38703D1E.14E37458@mentisworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38703D1E.14E37458@mentisworks.com>; from Nathan Kinsman on Mon, Jan 03, 2000 at 12:09:34AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <38703D1E.14E37458@mentisworks.com>, Nathan Kinsman wrote: > Intel EtherExpress PRO/100+ Dual Port NIC (this is recognized as two fxp > devices?) > > I have not been running CURRENT extensively, so I would like to know > anyone's experiences with any of the above hardware, or any > recommendations on hardware with a better price/performance ratio at a > low thermal (chassis is very compact). Last time I checked the fxp chips got much hotter than either a DEC 21143 or a realtek 8139 (which is otherwise unrecommended). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 1:46:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 946C315462; Mon, 3 Jan 2000 01:46:20 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 12544A-0002ic-00; Mon, 3 Jan 2000 09:46:18 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA08139; Mon, 3 Jan 2000 10:46:14 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38706FE6.2D995C0C@scc.nl> Date: Mon, 03 Jan 2000 10:46:14 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: current@freebsd.org, emulation@freebsd.org Subject: Re: SUBMIT: compat.linux.pathmunge References: 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 started on -hackers, went private and now pops up in -emulation through -current. You may want to look in -hackers to see the original posting by Doug White] Doug White wrote: > > I'm bringing this back up to -current to kick around some more. We may > want to move it to -emulators. I added -emulation so that current can be removed on the reply. > > Hmmm.. What we want is a way to tell the Linuxulator on a process/binary > > level whether we want /compat/linux overlaying or not. Indeed, backup > > clients will pick up /compat/linux as an ordinary directory without > > overlaying and that is exactly what we want. In most cases we do want > > the overlaying. > > Having process/binary granularity would be more useful, but is hard to > implement in an inobrusive way, as we're discovering below. :) Binary > granulatirty could be an issue for shells. I don't think it's that hard to do. It basicly needs a bit in struc proc, a test in linux_emul_find and a way to set the bit. It's generic enough to be used by other emulators as well. We just need to figure out what good ways there are to set the bit. Alternatively, we don't have it apply to all file access. We could have the 'no overlaying' property apply to opening directories only so that a directory scan will yield the native directories only. > > > If you could tag dynamic loader open()s you could have a selective > > > translator for just that, but when it's hunting for /etc/host.conf, which > > > one do you give it? Is it a call from resolv+ looking for it's > > > configuration, or a backup client putting it on tape? > > > > What about brandelf? When a static ELF binary is branded as `Linux', we > > have overlaying; when it's branded as 'LinuxBSD' (or what's in a name) > > it's a Linux binary that don't want/need overlaying. Dynamic ELF > > binaries are more tricky, but can make to work by setting > > LD_LIBRARY_PATH in a wrapper. > > Yuck. brandelf is an agreed-on standard (or is supposed to be) and it > wouldn't be appropriate to abuse it. Are any other OS's branding ELF binaries? > I'd be more apt to run the target > app in a wrapper that makes a 'shut off translation for this pid' type > syscall then execve()s the app. Kinda like nohup. What about inheritence? Setting `the bit' for a process is one thing, but what about it's children? I think we should implement the 'no overlaying' property as a static property and not a dynamic one. Having it a static property means that we need to tag it to a binary. -- 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 Mon Jan 3 4: 1:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id E3D2814E4D; Mon, 3 Jan 2000 04:01:29 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id DAA49010; Mon, 3 Jan 2000 03:59:10 -0800 (PST) Date: Mon, 3 Jan 2000 03:59:10 -0800 (PST) From: Bob Vaughan Message-Id: <200001031159.DAA49010@tantivy.stanford.edu> To: chuckr@picnic.mat.net, hasty@rah.star-gate.com Subject: Re: Your misleading, no, LYING message to me Cc: current@FreeBSD.ORG, jmb@hub.freebsd.org In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: I've been hearing from karl for years on IRC related lists.. I was rather suprised to see him on the freebsd-* lists, and I was even more suprised to see that he was being civil.. I guess his prozac prescription expired (y2k bug?) We're better off without him.. next thing you know, he will be threatening to sue us because he was (in his imagination) unfairly removed from the lists. if there is interest in a week or so, I may dig out the old dirt, and post a summary of his antics on operlist a few years back. (but only if there is interest.) -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 19792, Stanford, Ca 94309 -- 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 Mon Jan 3 4:25:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id B153A14E6F; Mon, 3 Jan 2000 04:25:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA09366; Mon, 3 Jan 2000 13:25:12 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000103025001.7861714F06@hub.freebsd.org> References: <20000103025001.7861714F06@hub.freebsd.org> Date: Mon, 3 Jan 2000 12:03:21 +0100 To: "Jonathan M. Bresler" From: Brad Knowles Subject: Re: Recent cat fighting in the FreeBSD mailing lists. Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:50 PM -0800 2000/1/2, Jonathan M. Bresler wrote: > That's all folks! I am going back "behind the curtain" to > continue my spam fighting efforts. Try to behave a little better out > here. Some of the mailing list subscribers are trying to sleep. I'd like to publicly thank you for all your hard work in all the things you do, and in particular stepping up to the plate to help us out in a sane manner on this particular issue. I'm sure that I am not alone in this matter. -- 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 Jan 3 5:14:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 2029A14E6F for ; Mon, 3 Jan 2000 05:14:26 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp137.dialup.st.keio.ac.jp [131.113.27.137]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id WAA05343; Mon, 3 Jan 2000 22:14:20 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id WAA21436; Mon, 3 Jan 2000 22:12:47 +0900 (JST) Message-Id: <200001031312.WAA21436@lavender.yy.cs.keio.ac.jp> Subject: kernel panic with newpcm/CS4236 (IBM ThinkPAD600) Cc: FreeBSD-current@FreeBSD.org X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 03 Jan 2000 22:12:47 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm playing latest 4-current/newpcm sound driver with IBM ThinkPad 600/CS4236. It was probed like this: pcm0: at port 0x52c-0x533 irq 5 drq 1 flags 0xa110 on isa0 bus_dmamap_load: Too many segs! buf_len = 0xdf00 bus_dmamap_load: Too many segs! buf_len = 0xdf00 But if I playback audio file like this, always no sound and paniced with latest driver.... % cat test.au > /dev/audio panic: isa_dmastart: bad nounce buffer <---- kernel message <<< kernel panic >>> kernel configuration was as belwo: device pcm0 at isa? port 0x52C irq 5 drq 1 flags 0x10 I think at middle of 1999/Dec, I could play with this sound card and sound driver. MIHIRA Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 5:24: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 555BB14D26; Mon, 3 Jan 2000 05:24:01 -0800 (PST) From: "Jonathan M. Bresler" To: hasty@rah.star-gate.com Cc: current@FreeBSD.ORG In-reply-to: <200001030330.TAA01403@rah.star-gate.com> (message from Amancio Hasty on Sun, 02 Jan 2000 19:30:12 -0800) Subject: Re: Your misleading, no, LYING message to me Message-Id: <20000103132401.555BB14D26@hub.freebsd.org> Date: Mon, 3 Jan 2000 05:24:01 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Sun, 02 Jan 2000 19:30:12 -0800 > From: Amancio Hasty > [snip] > > The proper tactic to resolve the conflict should have > been to wait a cool off period and then slug it off > technically. Nevertheless, instead of waiting for > Karl to cool off and attempt to ration with him , > it was much easier to drive him further down: hence > thru censorship the "technical" argument was won > with virtually no technical effort at all -- Like I said > earlier very very nice tactic ! the stipulated cooling-off period is two weeks. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 5:32:56 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id A94EF14F39; Mon, 3 Jan 2000 05:32:55 -0800 (PST) From: "Jonathan M. Bresler" To: smccloud@tcainternet.com Cc: freebsd-current@freebsd.org In-reply-to: <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> (smccloud@tcainternet.com) Subject: Re: Your misleading, no LYING message to me Message-Id: <20000103133255.A94EF14F39@hub.freebsd.org> Date: Mon, 3 Jan 2000 05:32:55 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sam, If you believe that either 1. someone removed Karl from the freebsd-current list or 2. that someone is covering this up, please call me at 410-320-7108. thanks jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 5:54: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from asgaard.whispering.org (208-241-93-179.hsacorp.net [208.241.93.179]) by hub.freebsd.org (Postfix) with ESMTP id 870F914E6F; Mon, 3 Jan 2000 05:53:47 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (will@14-078.008.popsite.net [209.69.195.78]) by asgaard.whispering.org (8.9.3/8.9.3) with ESMTP id IAA79124; Mon, 3 Jan 2000 08:53:29 -0500 (EST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id IAA01229; Mon, 3 Jan 2000 08:53:34 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 03 Jan 2000 08:53:33 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: (Satoshi - Ports Wraith - Asami) Subject: Re: Your misleading, no, LYING message to me Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-00 Satoshi - Ports Wraith - Asami wrote: > Wow, that was good! I'm going to nominate this for "this century's > most amusing message on the FreeBSD lists" award. :) > > Satoshi "you can figure out which century I'm talking about" Asami It started in December, actually. I think it was my fault, because I'm the one who sent him a (hardly incensifying) message regarding his port's PLIST. So.. he started flaming Steve Price.. (who spent a lot of time helping Karl improve his HomeDaemon port and saw it flushed down a shoddy wooden toilet!) and it went from there. I'm done with this thread, now and forever. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 7:11:49 2000 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 13A59150EA for ; Mon, 3 Jan 2000 07:11:48 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id D7AD63E37; Mon, 3 Jan 2000 16:11:46 +0100 (CET) Date: Mon, 3 Jan 2000 16:11:46 +0100 From: Jesper Skriver To: ---- Cc: freebsd-current@freebsd.org Subject: Re: Your misleading, no LYING message to me Message-ID: <20000103161146.C40159@skriver.dk> References: <200001030356.WAA13364@pistol.cde.com> <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <005701bf559e$ef1b4a00$7f3eb4d0@tcac.net>; from smccloud@tcainternet.com on Sun, Jan 02, 2000 at 09:59:28PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 02, 2000 at 09:59:28PM -0600, ---- wrote: > He is just expressing his point. From what I can tell someone removed him > from the list with no reason and now he is angry. I probably would be too. Please cool it, it has happened to me more than once, and I believe I havn't insulted any on these mailinglists, it's probably a "feature" of majordomo, as I've also seen it here with some of our mailing lists, this one just had a particular bad timing ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) 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 Mon Jan 3 8: 8:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [207.249.162.252]) by hub.freebsd.org (Postfix) with ESMTP id F2D7915069 for ; Mon, 3 Jan 2000 08:08:40 -0800 (PST) (envelope-from ales@megared.net.mx) Received: from ales (ales.megared.net.mx [207.249.163.251]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id KAA52790 for ; Mon, 3 Jan 2000 10:08:15 -0600 (CST) (envelope-from ales@megared.net.mx) Message-ID: <01f501bf5604$c9d37680$d2630a0a@megared.net.mx> From: "Alejandro Ramirez" To: Subject: RV: login error Date: Mon, 3 Jan 2000 10:08:34 -0600 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 Redirected to -current ----- Original Message ----- From: To: Sent: Wednesday, December 29, 1999 9:09 PM Subject: login error > Hello, I have FreeBSD 4.0 installed on my 486, and I noticed an > interesting problem. I switched from csh to bsh, and now, for some > reason, every first time I log in as root it rejects my password, but > the second time it always accepts it. This has happened repeatedly. I > was recently "messing" around with the chmod command with my /root dir, > does that have anything to do with it? Is there a "quick" fix I can use > in order for this login error to disappear? > > Thanks in advance > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 8: 9:34 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id CB4A71506A; Mon, 3 Jan 2000 08:08:52 -0800 (PST) From: "Jonathan M. Bresler" To: freebsd@gtonet.net Cc: freebsd-current@FreeBSD.ORG In-reply-to: Subject: no-id.com Message-Id: <20000103160852.CB4A71506A@hub.freebsd.org> Date: Mon, 3 Jan 2000 08:08:52 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG they are now spam filtered. jmb > > -- > > This message has been sent via an anonymous mail relay at www.no-id.com. > > > > Can this site be filtered as well? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 8:31:52 2000 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 76E4D15345; Mon, 3 Jan 2000 08:31:50 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id LAA37546; Mon, 3 Jan 2000 11:41:47 -0500 (EST) Date: Mon, 3 Jan 2000 11:41:46 -0500 (EST) From: Ben Rosengart To: Bob Vaughan Cc: chuckr@picnic.mat.net, hasty@rah.star-gate.com, current@FreeBSD.ORG, jmb@hub.freebsd.org Subject: Re: Your misleading, no, LYING message to me In-Reply-To: <200001031159.DAA49010@tantivy.stanford.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 On Mon, 3 Jan 2000, Bob Vaughan wrote: > if there is interest in a week or so, I may dig out the old dirt, and post a > summary of his antics on operlist a few years back. (but only if there is > interest.) I think it would be better for all concerned if we just let this die. -- 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 Mon Jan 3 8:38:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id C632D1516C for ; Mon, 3 Jan 2000 08:38:50 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 1E0CB1F7E; Mon, 3 Jan 2000 17:38:45 +0100 (CET) Date: Mon, 3 Jan 2000 17:38:45 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: buildworld fails Message-ID: <20000103173845.A31416@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With sources cvsup-ed earlier today ... buildworld bails out with the following: ===> gnu/lib/libreadline/readline/doc cat /usr/src/gnu/lib/libreadline/readline/doc/../../../../../contrib/libreadline /doc/rlman.texinfo > readline.texi makeinfo --no-split -I /usr/src/gnu/lib/libreadline/readline/doc -I /usr/src/gnu /lib/libreadline/readline/doc/../../../../../contrib/libreadline/doc readline.te xi -o readline.info gzip -cn readline.info > readline.info.gz ===> gnu/lib/libstdc++ ===> gnu/lib/libstdc++/doc make: don't know how to make iostream.info. Stop *** Error code 2 -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 9: 1: 7 2000 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 DA70914FAC for ; Mon, 3 Jan 2000 09:01:04 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id MAA37736 for ; Mon, 3 Jan 2000 12:12:17 -0500 (EST) Date: Mon, 3 Jan 2000 12:12:17 -0500 (EST) From: Ben Rosengart To: FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices In-Reply-To: <19991231171314.A92878@yedi.iaf.nl> 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 Fri, 31 Dec 1999, Wilko Bulte wrote: > As for ample warning: I've seen MAKEDEVs display a list of the devices > they are creating. I think the Tru64 version does this. I myself think this > is a good behaviour (and hope people won't start yelling 'bloat' for once) I like this idea a *lot*. -- 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 Mon Jan 3 9: 3:16 2000 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 AB1811531F for ; Mon, 3 Jan 2000 09:03:14 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA05308; Mon, 3 Jan 2000 09:02:51 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 03 Jan 2000 09:02:51 -0800 Date: Mon, 3 Jan 2000 09:02:51 -0800 (PST) From: Kip Macy To: Jesper Skriver Cc: ---- , freebsd-current@freebsd.org Subject: Majordomo has major shortcomings was Re: Your misleading, no LYING message to me In-Reply-To: <20000103161146.C40159@skriver.dk> 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: jesper@skriver.dk,smccloud@tcainternet.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 I am inclined to agree. An obscure company like Lyris would not be making money hand over fist if majordomo were that great. -Kip On Mon, 3 Jan 2000, Jesper Skriver wrote: > On Sun, Jan 02, 2000 at 09:59:28PM -0600, ---- wrote: > > He is just expressing his point. From what I can tell someone removed him > > from the list with no reason and now he is angry. I probably would be too. > > Please cool it, it has happened to me more than once, and I believe I > havn't insulted any on these mailinglists, it's probably a "feature" of > majordomo, as I've also seen it here with some of our mailing lists, > this one just had a particular bad timing ... > > /Jesper > > -- > Jesper Skriver, jesper(at)skriver(dot)dk > Work: Network manager @ AS3292 (Tele Danmark DataNetworks) > Private: Geek @ AS2109 (A much smaller network ;-) > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 9: 7: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id CE6351522A for ; Mon, 3 Jan 2000 09:06:45 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id MAA12629; Mon, 3 Jan 2000 12:06:14 -0500 (EST) Date: Mon, 3 Jan 2000 12:06:14 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Kip Macy Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: maxfiles same as maxfilesperproc ?? 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 Well, maybe a patch will get things moving. I just submitted kern/15860 with a simple patch which reduces the default maxfilesperproc to be 20 less than maxfiles. I got the mailing list reference wrong in the PR, but -hackers has it's share of similar requests :). Kelly On Sun, 2 Jan 2000, Kip Macy wrote: > I made the same comment several months ago and received a rather cool > reception. I was simply told to change it to my liking in login.conf. > > > -Kip > > On Sat, 1 Jan 2000, John W. DeBoskey wrote: > > > Hi, > > > > On a FreeBSD 4.0-19991223-SNAP system... > > > > I just ran into a situation that caused me to have to reboot > > the machine before understanding what had really happenned... > > > > The problems comes down to: > > > > kern.maxfiles: 4136 > > kern.maxfilesperproc: 4136 > > > > > > Thus, because I had a root uid server that looped chewing > > up file descriptors, it also filled up the system file table. > > > > I realize this is end-user/administrator fixable, but I'm > > not sure the default should have these be the same... > > > > Thanks, > > John > > -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 9:20:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 10BCE151CC for ; Mon, 3 Jan 2000 09:20:54 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 785FB137F69 for ; Mon, 3 Jan 2000 12:20:51 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id MAA98427; Mon, 3 Jan 2000 12:20:50 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14448.55922.567144.901107@trooper.velocet.net> Date: Mon, 3 Jan 2000 12:20:50 -0500 (EST) To: freebsd-current@freebsd.org Subject: BOOTP still broken? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've followed the BOOTP threads in -current from the archives, but I can't find any resolution of the issue. I cvsup'd -current last night and still have a non-working BOOTP kernel. Many of the posts centered around PXE negating the need for BOOTP kernel support. Just how are you supposed to mount root in that case? Anyways, with both an ed0 and an ep0, the kernel ends up telling me... Bootpc: hardware address is Bootpc-call: sosend: 13 state 000000 panic: BOOTP call failed ... I suppose I could run -STABLE on this machine, but I'd rather not have two complete bin trees. 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 Mon Jan 3 10: 7: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat200.60.mpoweredpc.net [142.177.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 31C5C14DC5 for ; Mon, 3 Jan 2000 10:07:01 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id OAA61288; Mon, 3 Jan 2000 14:06:39 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 3 Jan 2000 14:06:39 -0400 (AST) From: The Hermit Hacker To: David Greenman Cc: ---- , freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no LYING message to me In-Reply-To: <200001030420.UAA26206@implode.root.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, 2 Jan 2000, David Greenman wrote: > >Also, I can tell that someone is doing some good covering up. Its ashame to > >see leaders do this. > > How can you tell that? There is no evidence to support that. *I'm* > certainly not covering anything up and I've seen no reason to believe that > anyone else is, either. As a *non* CORE member, I'm still looking for this alleged cover-up too...Karl alleges that someone logged in and modified those files manually, which, if anyone has every admin'd majordomo knows, is not a requirement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 10:47:16 2000 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 7769514C0B for ; Mon, 3 Jan 2000 10:47:12 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 24DBA1CA0; Tue, 4 Jan 2000 02:47:09 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: The Hermit Hacker Cc: David Greenman , ---- , freebsd-current@FreeBSD.ORG Subject: Re: Your misleading, no LYING message to me In-Reply-To: Message from The Hermit Hacker of "Mon, 03 Jan 2000 14:06:39 -0400." Date: Tue, 04 Jan 2000 02:47:09 +0800 From: Peter Wemm Message-Id: <20000103184709.24DBA1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > On Sun, 2 Jan 2000, David Greenman wrote: > > > >Also, I can tell that someone is doing some good covering up. Its ashame t o > > >see leaders do this. > > > > How can you tell that? There is no evidence to support that. *I'm* > > certainly not covering anything up and I've seen no reason to believe that > > anyone else is, either. > > As a *non* CORE member, I'm still looking for this alleged cover-up > too...Karl alleges that someone logged in and modified those files > manually, which, if anyone has every admin'd majordomo knows, is not a > requirement. Just take a look at the last week of bugtraq about majordomo.. if somebody edited files, it could have been *anyone* with an account on hub - root or not. That leaves about 296 people who could have logged in, done it and logged out again. 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 Jan 3 11: 6:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from web2105.mail.yahoo.com (web2105.mail.yahoo.com [128.11.68.249]) by hub.freebsd.org (Postfix) with SMTP id 2FDAF15166 for ; Mon, 3 Jan 2000 11:06:37 -0800 (PST) (envelope-from valsho@yahoo.com) Received: (qmail 17639 invoked by uid 60001); 3 Jan 2000 19:06:36 -0000 Message-ID: <20000103190636.17638.qmail@web2105.mail.yahoo.com> Received: from [147.226.5.3] by web2105.mail.yahoo.com; Mon, 03 Jan 2000 11:06:36 PST Date: Mon, 3 Jan 2000 11:06:36 -0800 (PST) From: "Valentin S. Chopov" Subject: ata-all.o(.text+0x534): undefined reference to `pci_read_config' 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 It seems there is something for #if NPCI > 0 ... #endif ---- linking kernel ata-all.o: In function `ataintr': ata-all.o(.text+0x534): undefined reference to `pci_read_config' *** Error code 1 ------ Val __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 11:44:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by hub.freebsd.org (Postfix) with ESMTP id BEACE14C18 for ; Mon, 3 Jan 2000 11:44:19 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from gab200r1.ems.att.com ([135.37.94.32]) by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id OAA02957 for ; Mon, 3 Jan 2000 14:44:16 -0500 (EST) Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id OAA17565; Mon, 3 Jan 2000 14:45:04 -0500 (EST) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Mon, 3 Jan 2000 14:44:16 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'current@freebsd.org'" Subject: new device drivers Date: Mon, 3 Jan 2000 14:07:16 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I've written a couple of drivers and would like to include them in current. What the procedure to add new device driver to current? Who is the point of contact? I think, I could not commit it to the cvs tree or can I? Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 11:55:41 2000 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 115FC151A0 for ; Mon, 3 Jan 2000 11:55:39 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA22755; Mon, 3 Jan 2000 14:55:29 -0500 (EST) Date: Mon, 3 Jan 2000 14:55:29 -0500 (EST) From: "Matthew N. Dodd" To: "Valentin S. Chopov" Cc: current@FreeBSD.ORG Subject: Re: ata-all.o(.text+0x534): undefined reference to `pci_read_config' In-Reply-To: <20000103190636.17638.qmail@web2105.mail.yahoo.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 Mon, 3 Jan 2000, Valentin S. Chopov wrote: > It seems there is something for > > #if NPCI > 0 ... #endif > ---- > > ata-all.o: In function `ataintr': > ata-all.o(.text+0x534): undefined reference to > `pci_read_config' > *** Error code 1 This is yet another reason why bus front-end code should live in their own files. -- | 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 Mon Jan 3 12: 1:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 082FA1537D for ; Mon, 3 Jan 2000 12:01:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA09160; Mon, 3 Jan 2000 21:01:36 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001032001.VAA09160@freebsd.dk> Subject: Re: ata-all.o(.text+0x534): undefined reference to `pci_read_config' In-Reply-To: <20000103190636.17638.qmail@web2105.mail.yahoo.com> from "Valentin S. Chopov" at "Jan 3, 2000 11:06:36 am" To: valsho@yahoo.com (Valentin S. Chopov) Date: Mon, 3 Jan 2000 21:01:36 +0100 (CET) Cc: 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 Valentin S. Chopov wrote: > > It seems there is something for > > #if NPCI > 0 ... #endif Yup, forgot that one, fixed. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 12:17: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 772CE151E5; Mon, 3 Jan 2000 12:16:46 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-46.iptelecom.net.ua [212.9.227.110]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id WAA29137; Mon, 3 Jan 2000 22:19:16 +0200 (EET) Message-ID: <3870F784.2B1E8126@altavista.net> Date: Mon, 03 Jan 2000 21:24:52 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Nicolas Souchu Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, nsouch@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > Hi there! > > FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current > > A major ppbus(4) release is available for beta-testing. Good work! Now plip, which has been broken for ages, works perfectly - no more lockups, spontaneous reboots, panics, etc! To test it I even managed to get X and NFS working over plip line, things which was impossible with oldppbus. Count on my vote to commit it before branch split because IMHO it should be considered as a bugfix rather that a new feature. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 12:26:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 07F1D15230 for ; Mon, 3 Jan 2000 12:26:43 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 414C1104CB4; Mon, 3 Jan 2000 14:26:41 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id 3D37EFB101 for ; Mon, 3 Jan 2000 14:26:41 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id CCC2EBC4CE; Mon, 3 Jan 2000 14:26:33 -0600 (CST) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id A87CFB2A42 for ; Mon, 3 Jan 2000 14:26:33 -0600 (CST) From: Bruce Burden Posted-Date: Mon, 3 Jan 2000 14:27:14 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id OAA00540 for freebsd-current@freebsd.org; Mon, 3 Jan 2000 14:22:44 -0600 (CST) Message-Id: <200001032022.OAA00540@panther.txn.cpqcorp.net> Subject: 01/01/2000 buildworld failure in kdump, truss To: freebsd-current@freebsd.org Date: Mon, 3 Jan 2000 14:22:43 -0600 (CST) Reply-To: bruce.burden@compaq.com X-Mailer: ELM [version 2.5 PL2] 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 did a cvsup on 01/01/2000, and then did a buildworld. It failed in kdump and truss in /usr/src/usr.bin. Thinking the problem was the "make" picking up the wrong include file, I redid the build once I did a make installworld with the latest build (less kdump and truss!). Same problem. Since kdump and truss were last modified on 12/03 (or so), it would seem I am doing something wrong, since the archives don't have any references to this problem. Any pointers? ===> usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:90: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition In file included from ioctl.c:87: /usr/obj/usr/src/i386/usr/include/sys/joystick.h:36: redefinition of `struct joystick' *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Same thing happens when building "truss" as well. /usr/src/usr.bin/Makefile: # From: @(#)Makefile 8.3 (Berkeley) 1/7/94 # $FreeBSD: src/usr.bin/Makefile,v 1.141 1999/12/23 11:10:23 marcel Exp $ /usr/src/usr.bin/kdump/Makefile: # @(#)Makefile 8.1 (Berkeley) 6/6/93 # $FreeBSD: src/usr.bin/kdump/Makefile,v 1.4 1999/12/03 12:50:01 marcel Exp $ /usr/src/usr.bin/truss/Makefile: # $FreeBSD: src/usr.bin/truss/Makefile,v 1.10 1999/12/03 17:35:34 marcel Exp $ Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 12:29:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id DE3A314EEB for ; Mon, 3 Jan 2000 12:29:27 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA00570; Mon, 3 Jan 2000 15:29:23 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001032029.PAA00570@blackhelicopters.org> Subject: Re: new device drivers In-Reply-To: from "Yevmenkin, Maksim N, CSCIO" at "Jan 3, 2000 2: 7:16 pm" To: myevmenkin@att.com (Yevmenkin Maksim N CSCIO) Date: Mon, 3 Jan 2000 15:29:23 -0500 (EST) Cc: 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 Hello, From a long time lurking on -current, I would suggest that you do the following. (This might not be strictly official, but it's how it's worked on this list in the past. ;) Put the driver up on a web page. Post a message on -current giving the URL and specifics of the drivers. Request testers. Take feedback from testers, patch, and repeat. When not only you are happy with them, but your testers are happy, use send-pr. By the time you finish testing, however, you'll probably have enough offers from committers who will be willing to commit the drivers that you won't need to use send-pr. ==ml [Charset koi8-r unsupported, filtering to ASCII...] > Hello All, > > I've written a couple of drivers and would like to include them in current. > > What the procedure to add new device driver to current? > Who is the point of contact? > > I think, I could not commit it to the cvs tree or can I? > > Thanks, > emax > > > 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 Jan 3 15: 5:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 98F4E15180 for ; Mon, 3 Jan 2000 15:05:30 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id PAA46928; Mon, 3 Jan 2000 15:05:23 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Bob Vaughan" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: Your misleading, no, LYING message to me Date: Mon, 3 Jan 2000 15:05:35 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <200001031159.DAA49010@tantivy.stanford.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG techie, I, too, remember Karl from IRC, but this isn't the place (there's probably also some things one could dig up on you, prae, piker, mjr and myself) for that type of post, so please don't. This isn't operlist and hopefully the antics here are over too. oh, and you'll never guess what nick I oper'd under :P (and I'll never tell) FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Bob Vaughan > Sent: Monday, January 03, 2000 3:59 AM > To: chuckr@picnic.mat.net; hasty@rah.star-gate.com > Cc: current@FreeBSD.ORG; jmb@hub.freebsd.org > Subject: Re: Your misleading, no, LYING message to me > > > FYI: I've been hearing from karl for years on IRC related lists.. > I was rather suprised to see him on the freebsd-* lists, and I > was even more > suprised to see that he was being civil.. > > I guess his prozac prescription expired (y2k bug?) > > We're better off without him.. next thing you know, he will be > threatening > to sue us because he was (in his imagination) unfairly removed > from the lists. > > if there is interest in a week or so, I may dig out the old dirt, > and post a > summary of his antics on operlist a few years back. (but only if there is > interest.) > > -- Welcome My Son, Welcome To The Machine -- > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > | P.O. Box 19792, Stanford, Ca 94309 > -- 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 15: 7:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-1.cpinternet.com [208.149.16.1]) by hub.freebsd.org (Postfix) with ESMTP id EE44214BC9 for ; Mon, 3 Jan 2000 15:07:34 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id RAA03838; Mon, 3 Jan 2000 17:07:31 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 3 Jan 2000 17:07:31 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: ipfw not logging? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14449.10490.920996.589948@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Logging has stopped working here. I don't know exactly when, but after I switched from stable to current in November. In particular, this rule is demonstrably not logging: 11000 6 360 deny log logamount 100 ip from any to any via tun1 6 denied, none logged -- I did 'ipfw resetlog 11000' too. These are the related kernel options: options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_FORWARD options IPDIVERT options DUMMYNET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 16:40:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 996D515130 for ; Mon, 3 Jan 2000 16:40:47 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 83EA51FC9; Tue, 4 Jan 2000 01:40:46 +0100 (CET) Date: Tue, 4 Jan 2000 01:40:46 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: NewPCM causes kernel panics ! Message-ID: <20000104014046.A769@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With CURRENT sources updated earlier today ... my system now crash-and-burns when trying to play audio. i have foudn these messages in /var/log/messages: Jan 4 01:30:26 shadowmere /kernel: gusc0: at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 Jan 4 01:30:26 shadowmere /kernel: pcm0: on gusc0 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 If any more info is needed let me know. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id C4BFE14C26 for ; Mon, 3 Jan 2000 18:08:08 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Tue, 4 Jan 2000 13:00:55 +1100 Content-return: prohibited From: Peter Jeremy Subject: No cvs-cur CTM deltas To: chuckr@picnic.mat.net Cc: current@FreeBSD.ORG Message-Id: <00Jan4.130055est.40327@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Tue, 4 Jan 2000 13:00:54 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived just over 24 hours ago. Is there a problem with the CTM generation? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:13:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.60]) by hub.freebsd.org (Postfix) with ESMTP id C75FB14FBA for ; Mon, 3 Jan 2000 18:13:15 -0800 (PST) (envelope-from yaldabaoth@geocities.com) Received: from 207-172-145-221.s30.as7.fdk.md.dialup.rcn.com ([207.172.145.221] helo=geocities.com) by smtp01.mrf.mail.rcn.net with esmtp (Exim 2.12 #3) id 125JSh-00067i-00; Mon, 3 Jan 2000 21:12:40 -0500 Message-ID: <38715720.4501679@geocities.com> Date: Mon, 03 Jan 2000 21:12:48 -0500 From: Andrew Sherrod X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: ixkatl@yahoo.com, apricot@erols.com, btirg@uis.doleta.gov, btiggn@uis.doleta.gov, current@freebsd.org, fug-Washdc@Sytex.Net Subject: Y2K problems? I thought it was over. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guess ELM 2.4 isn't Y2K compliant. Not a huge problem, but annoying. FreeBSD: Received: from cscfx.sytex.com (rwc@cscfx.sytex.com [205.147.190.131]) by sytex2.sytex.com (8.9.1/8.9.1) with SMTP id LAA03024 for ; Tue, 4 Jan 2000 11:57:16 -0500 (EST) From: rcramer@Sytex.Net X-Mailer: ELM [version 2.4 PL24] Date: Mon, 3 Jan 100 11:58:45 Linux: Received: (qmail 22202 invoked by uid 529); 2 Jan 2000 19:33:06 -0000 From: Solar Designer X-Mailer: ELM [version 2.4ME+ PL31 (25)] Date: Sun, 2 Jan 100 22:30:34 +0300 (MSK) (Interestingly, my yahoo mail reads this as 01/02/2020, while Netscape reads it as 12/31/1969 [obviously the epoch -1 day]) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:16:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-8.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.136]) by hub.freebsd.org (Postfix) with ESMTP id BA86E1504F for ; Mon, 3 Jan 2000 18:16:24 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA86318; Tue, 4 Jan 2000 01:46:48 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA03280; Tue, 4 Jan 2000 01:50:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001040150.BAA03280@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Alexander Langer Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: date(1) and -v-1m In-Reply-To: Message from Alexander Langer of "Fri, 31 Dec 1999 15:08:29 +0100." <19991231150829.A28634@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 01:50:12 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > The behaviour of date(1) is probably specified by POSIX, but I think, > date -v-1m should at least return a date a month _before_ the current > month. > > Example: > Mi 1 Dez 1999 15:06:47 CET > > (Dez. has 31, so it should be Nov 30, I think). > > More confusing is something like: > alex:~ $ date -v-1m +%Y-%m > 1999-12 > > what I wanted to use to create backup folders for my mail-system (all > mails of the last month are moved to a folder of the last month). > > That's weird, somehow. > > Is this a bug or a feature? > Is this POSIX-compilant? It's an arbitrary choice I made when I wrote the code :-I It's not POSIX I'm afraid. > Do we want an additional option? (I want :-)) I certainly wouldn't object to -V doing the same as -v but rounding down.... this could also decide how to behave when a -v adjusts the time onto a non-existent time (say 1:30 when the clocks go forward). > Alex > > -- > I doubt, therefore I might be. I'm pink, therefore I'm spam. -- 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 Mon Jan 3 18:22:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D73114CAA for ; Mon, 3 Jan 2000 18:22:06 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id MAA17441; Tue, 4 Jan 2000 12:21:53 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <200001040221.MAA17441@mail.theinternet.com.au> Subject: Re: Y2K problems? I thought it was over. In-Reply-To: <38715720.4501679@geocities.com> from Andrew Sherrod at "Jan 3, 2000 9:12:48 pm" To: yaldabaoth@geocities.com (Andrew Sherrod) Date: Tue, 4 Jan 2000 12:21:53 +1000 (EST) Cc: ixkatl@yahoo.com, apricot@erols.com, btirg@uis.doleta.gov, btiggn@uis.doleta.gov, current@FreeBSD.ORG, fug-Washdc@Sytex.Net 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 +----[ Andrew Sherrod ]--------------------------------------------- | Guess ELM 2.4 isn't Y2K compliant. Not a huge problem, but annoying. | | FreeBSD: | | Received: from cscfx.sytex.com (rwc@cscfx.sytex.com [205.147.190.131]) | by sytex2.sytex.com (8.9.1/8.9.1) with SMTP id LAA03024 for | ; Tue, 4 Jan 2000 11:57:16 -0500 (EST) | From: rcramer@Sytex.Net | X-Mailer: ELM [version 2.4 PL24] | Date: Mon, 3 Jan 100 11:58:45 | | Linux: | | Received: (qmail 22202 invoked by uid 529); 2 Jan 2000 19:33:06 -0000 | From: Solar Designer | X-Mailer: ELM [version 2.4ME+ PL31 (25)] | Date: Sun, 2 Jan 100 22:30:34 +0300 (MSK) Date: Tue, 4 Jan 2000 12:19:38 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sure it is, get a later version. That version was available as of April '99 (last time I did anything to that machine(. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.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 Jan 3 18:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.sashanet.com (www.sashanet.com [209.181.82.105]) by hub.freebsd.org (Postfix) with ESMTP id 66E8B152EB for ; Mon, 3 Jan 2000 18:23:58 -0800 (PST) (envelope-from sasha@mysql.com) Received: from mysql.com (apachev@localhost [127.0.0.1]) by www.sashanet.com (8.9.3/8.9.3) with ESMTP id TAA28532; Mon, 3 Jan 2000 19:23:40 -0700 Message-ID: <387159A8.C46C69E1@mysql.com> Date: Mon, 03 Jan 2000 19:23:36 -0700 From: Sasha Pachev Organization: MySQL X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.33 i586) X-Accept-Language: ru MIME-Version: 1.0 To: Leif Neland Cc: monty@tcx.se, Paul DuBois , mysql@lists.mysql.com, freebsd-current@freebsd.org Subject: Re: 2 hours to compile mysql? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > The reason for this is that some gcc optimizations stages takes > > exponentially more memory when compiling big functions. > > bison produces one big function for the grammar parsing and its > > this that takes a long time to compile; To compile sql_yacc.cc quickly > > on Intel, you nead at least 160M of free ram. On a PentiumII 400mz with 256M > > ram, it takes 11 seconds to compile sql_yacc.o. Having to use swap > > can easily make things 1000 times slower > > > > Is amount of ram available (portably) to configure? > So configure could decide to use --low-memory by itself? Allowing > overrides, naturally. > > Leif > There is actually a method to portably guess how much RAM your have available from configure -- just write a small C program that will keep malloc()-ing until it gets an error, but I do not think it is worth the effort. -- Sasha Pachev +------------------------------------------------------------------+ | TcX ____ __ _____ _____ ___ == mysql@tcx.se | | /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sasha Pachev | | /*/ /*/ /*/ \*\_ |*| |*||*| mailto:sasha@mysql.com | | /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Provo, Utah, USA | | /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____ | | ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^ | | /*/ \*\ Developers Team | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:26:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.60]) by hub.freebsd.org (Postfix) with ESMTP id 4252F14F9C for ; Mon, 3 Jan 2000 18:26:17 -0800 (PST) (envelope-from yaldabaoth@geocities.com) Received: from 207-172-145-221.s30.as7.fdk.md.dialup.rcn.com ([207.172.145.221] helo=geocities.com) by smtp01.mrf.mail.rcn.net with esmtp (Exim 2.12 #3) id 125Jex-0000QT-00; Mon, 3 Jan 2000 21:25:20 -0500 Message-ID: <38715A19.EAC0E8F7@geocities.com> Date: Mon, 03 Jan 2000 21:25:30 -0500 From: Andrew Sherrod X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Kenneth Milton , current@freebsd.org Subject: Re: Y2K problems? I thought it was over. References: <200001040221.MAA17441@mail.theinternet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you know which version is shipping with FreeBSD 3.4? Andrew Kenneth Milton wrote: > +----[ Andrew Sherrod ]--------------------------------------------- > | Guess ELM 2.4 isn't Y2K compliant. Not a huge problem, but annoying. > | > | FreeBSD: > | > | Received: from cscfx.sytex.com (rwc@cscfx.sytex.com [205.147.190.131]) > | by sytex2.sytex.com (8.9.1/8.9.1) with SMTP id LAA03024 for > | ; Tue, 4 Jan 2000 11:57:16 -0500 (EST) > | From: rcramer@Sytex.Net > | X-Mailer: ELM [version 2.4 PL24] > | Date: Mon, 3 Jan 100 11:58:45 > | > | Linux: > | > | Received: (qmail 22202 invoked by uid 529); 2 Jan 2000 19:33:06 -0000 > | From: Solar Designer > | X-Mailer: ELM [version 2.4ME+ PL31 (25)] > | Date: Sun, 2 Jan 100 22:30:34 +0300 (MSK) > > Date: Tue, 4 Jan 2000 12:19:38 +1000 (EST) > X-Mailer: ELM [version 2.4ME+ PL43 (25)] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > Sure it is, get a later version. That version was available as of April '99 > (last time I did anything to that machine(. > > -- > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.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 Jan 3 18:28:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 3A14D14CE0 for ; Mon, 3 Jan 2000 18:28:33 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA12519; Tue, 4 Jan 2000 12:57:58 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <387159A8.C46C69E1@mysql.com> Date: Tue, 04 Jan 2000 12:57:57 +1030 (CST) From: "Daniel O'Connor" To: Sasha Pachev Subject: Re: 2 hours to compile mysql? Cc: freebsd-current@freebsd.org, mysql@lists.mysql.com, Paul DuBois , monty@tcx.se, Leif Neland Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-00 Sasha Pachev wrote: > There is actually a method to portably guess how much RAM your have > available > from configure -- just write a small C program that will keep > malloc()-ing until > it gets an error, but I do not think it is worth the effort. Especially since different users have different memory size limits.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:33:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id 87ACD1504F for ; Mon, 3 Jan 2000 18:33:43 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id DAA23879 for ; Tue, 4 Jan 2000 03:33:37 +0100 Received: (qmail 83929 invoked from network); 4 Jan 2000 02:33:12 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 4 Jan 2000 02:33:12 -0000 Received: (qmail 28297 invoked by uid 500); 4 Jan 2000 02:33:12 -0000 Date: Tue, 4 Jan 2000 03:33:12 +0100 From: Sascha Schumann To: Sasha Pachev Cc: Leif Neland , monty@tcx.se, Paul DuBois , mysql@lists.mysql.com, freebsd-current@freebsd.org Subject: Re: 2 hours to compile mysql? Message-ID: <20000104033311.A28282@schumann.cx> References: <387159A8.C46C69E1@mysql.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387159A8.C46C69E1@mysql.com>; from sasha@mysql.com on Mon, Jan 03, 2000 at 07:23:36PM -0700 X-Notice: Copyright (c) 2000 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.13 #10 Mon Dec 27 20:35:15 CET 1999 alpha Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 03, 2000 at 07:23:36PM -0700, Sasha Pachev wrote: > Leif Neland wrote: > > > > > The reason for this is that some gcc optimizations stages takes > > > exponentially more memory when compiling big functions. > > > bison produces one big function for the grammar parsing and its > > > this that takes a long time to compile; To compile sql_yacc.cc quickly > > > on Intel, you nead at least 160M of free ram. On a PentiumII 400mz with 256M > > > ram, it takes 11 seconds to compile sql_yacc.o. Having to use swap > > > can easily make things 1000 times slower > > > > > > > Is amount of ram available (portably) to configure? > > So configure could decide to use --low-memory by itself? Allowing > > overrides, naturally. > > > > Leif > > > > There is actually a method to portably guess how much RAM your have available > from configure -- just write a small C program that will keep malloc()-ing until > it gets an error, but I do not think it is worth the effort. There is also no guarantee that the allocated memory will be available for real use (keyword resource overcommitting). -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:36:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id BCD5F1536C for ; Mon, 3 Jan 2000 18:36:28 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id UAA34754; Mon, 3 Jan 2000 20:36:07 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200001040236.UAA34754@celery.dragondata.com> Subject: Re: 2 hours to compile mysql? To: sasha@mysql.com (Sasha Pachev) Date: Mon, 3 Jan 2000 20:36:07 -0600 (CST) Cc: leif@neland.dk (Leif Neland), monty@tcx.se, paul@snake.net (Paul DuBois), mysql@lists.mysql.com, freebsd-current@FreeBSD.ORG In-Reply-To: <387159A8.C46C69E1@mysql.com> from "Sasha Pachev" at Jan 03, 2000 07:23:36 PM X-Mailer: ELM [version 2.5 PL1] 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 > > Is amount of ram available (portably) to configure? > > So configure could decide to use --low-memory by itself? Allowing > > overrides, naturally. > > > > Leif > > > > There is actually a method to portably guess how much RAM your have available > from configure -- just write a small C program that will keep malloc()-ing until > it gets an error, but I do not think it is worth the effort. > > -- > Sasha Pachev How much ram you have and how much ram+swap you have before you hit your limit is quite different. :) # sysctl hw.physmem hw.physmem: 400883712 This will return the amount of ram you have minus your kernel size, though. Perhaps helpful if you really want to do this. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 18:43: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id ADA3015028; Mon, 3 Jan 2000 18:42:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D0F21CD625; Mon, 3 Jan 2000 18:42:54 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 3 Jan 2000 18:42:54 -0800 (PST) From: Kris Kennaway To: Andrew Sherrod Cc: Andrew Kenneth Milton , current@freebsd.org Subject: Re: Y2K problems? I thought it was over. In-Reply-To: <38715A19.EAC0E8F7@geocities.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 Mon, 3 Jan 2000, Andrew Sherrod wrote: > Do you know which version is shipping with FreeBSD 3.4? http://www.freebsd.org/ports/mail.html says elm-2.4ME+61 Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 19:22:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id B588A153EE for ; Mon, 3 Jan 2000 19:22:12 -0800 (PST) (envelope-from evmax@earthlink.net) Received: from earthlink.net (sdn-ar-001njnbruP153.dialsprint.net [168.191.62.89]) by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id TAA21338 for ; Mon, 3 Jan 2000 19:22:10 -0800 (PST) Message-ID: <387167A7.1C9FD005@earthlink.net> Date: Mon, 03 Jan 2000 22:23:19 -0500 From: Maksim Yevmenkin X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Granch serial port tty driver for -current Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I've written a tty driver for SBNI-12x Granch Serial Cards. Granch serial is a short range modem. It provides up to 2MB over just plain couple of wires. More detail http://www.granch.ru (sorry russian only). This card is very popular in Russia, because of poor telephone lines. This is great "last mile" solution for ISP. The driver sources and description can be found at: http://home.earthlink.net/~evmax/gs-fbsd-current.tar.gz (~20K) It would be realy nice, if some of the commiters review the code and may be add it to the source tree. Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 19:54:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 24A7415357 for ; Mon, 3 Jan 2000 19:54:21 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA25538; Mon, 3 Jan 2000 22:52:55 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 3 Jan 2000 22:52:54 -0500 (EST) From: Chuck Robey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: No cvs-cur CTM deltas In-Reply-To: <00Jan4.130055est.40327@border.alcanet.com.au> 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, 4 Jan 2000, Peter Jeremy wrote: > The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived > just over 24 hours ago. Is there a problem with the CTM generation? Right. Login problem. Fixed real quick now. > > Peter > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 21: 8:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C9D5E14E01 for ; Mon, 3 Jan 2000 21:08:20 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA25846; Tue, 4 Jan 2000 00:07:51 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 4 Jan 2000 00:07:50 -0500 (EST) From: Chuck Robey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: No cvs-cur CTM deltas In-Reply-To: <00Jan4.130055est.40327@border.alcanet.com.au> 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, 4 Jan 2000, Peter Jeremy wrote: > The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived > just over 24 hours ago. Is there a problem with the CTM generation? Fixed that problem (security thing) found another. Still working on it. > > Peter > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 21:43:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by hub.freebsd.org (Postfix) with ESMTP id C627214D30; Mon, 3 Jan 2000 21:43:51 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id VAA23901; Mon, 3 Jan 2000 21:43:11 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id VAA23973; Mon, 3 Jan 2000 21:43:49 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Mon, 3 Jan 2000 21:43:49 -0800 (PST) From: Brian Beattie To: "Jordan K. Hubbard" Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me In-Reply-To: <991.946889524@zippy.cdrom.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 Having read, the first article or so on this subject, I decided that it had absolutely no merit. However; seeing an article by you I figured that it would be at least interesting. I was not disapointed. Thank you. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 21:51:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 0948F14D45; Mon, 3 Jan 2000 21:51:10 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA26227; Tue, 4 Jan 2000 00:50:40 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 4 Jan 2000 00:50:40 -0500 (EST) From: Chuck Robey To: Brian Beattie Cc: "Jordan K. Hubbard" , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: Your misleading, no, LYING message to me 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, 3 Jan 2000, Brian Beattie wrote: > Having read, the first article or so on this subject, I decided that it > had absolutely no merit. However; seeing an article by you I figured that > it would be at least interesting. I was not disapointed. > > Thank you. Please, I know you meant well, but THIS THREAD MUST DIE!!! Please give it a rest! > > Brian Beattie | The only problem with > beattie@aracnet.com | winning the rat race ... > www.aracnet.com/~beattie | in the end you're still a rat > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 21:54: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id 2BF1D14C83 for ; Mon, 3 Jan 2000 21:53:59 -0800 (PST) (envelope-from veldy@visi.com) Received: from barley (nic-25-c112-208.mn.mediaone.net [24.25.112.208]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id AAA10268 for ; Tue, 4 Jan 2000 00:53:47 -0500 (EST) Message-ID: <004201bf5678$5d05f900$0100a8c0@veldy.org> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: newpcm with EMU10K1 chipset (Sound Blaster PCI 512 and Sound Blaster Live)? Date: Mon, 3 Jan 2000 23:55:31 -0600 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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the Sound Blaster PCI 512 card now and I was wondering if it is supported with newpcm. It uses the EMU10K1 processor, the same as Sound Blaster Live. I am aware that the Linux source is has been open sourced by Creative, so ... 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 Mon Jan 3 21:57:41 2000 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 1485814CDE; Mon, 3 Jan 2000 21:57:38 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA07921; Tue, 4 Jan 2000 00:57:36 -0500 (EST) (envelope-from luoqi) Date: Tue, 4 Jan 2000 00:57:36 -0500 (EST) From: Luoqi Chen Message-Id: <200001040557.AAA07921@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, ust@cert.siemens.de Subject: Re: Problem with rlogin and /etc/pam.conf Cc: markm@FreeBSD.ORG, mharo@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > > on two 4.0-CURRENT boxes (cvsuped today) I got the following response when > trying to rlogin to it: > > # rlogin indiana > assword: > > A typed-in password is echoed in cleartext. > > The only thing that helps is to comment out the second-last line in > /etc/pam.conf: > > # other auth required pam_unix.so try_first_pass > > But this gives an error message when first using the login at the console. > > Any help on this? Did I miss something? > My work around to this problem is to add the following line to /etc/pam.conf, rshd auth sufficient pam_deny.so We probably should change the last two default entries to use the pam_deny module, pam_unix requires stdin/out/err/ctty, which may not be present in all cases. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 22:10:54 2000 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 F1FEA14EB0 for ; Mon, 3 Jan 2000 22:10:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e046APw12146; Tue, 4 Jan 2000 08:10:25 +0200 (SAST) Message-Id: <200001040610.e046APw12146@gratis.grondar.za> To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with rlogin and /etc/pam.conf References: <200001040557.AAA07921@lor.watermarkgroup.com> In-Reply-To: <200001040557.AAA07921@lor.watermarkgroup.com> ; from Luoqi Chen "Tue, 04 Jan 2000 00:57:36 EST." Date: Tue, 04 Jan 2000 08:10:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My work around to this problem is to add the following line to /etc/pam.conf, > rshd auth sufficient pam_deny.so What timing! I just committed something that looks identical! 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 Jan 3 22:41:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust68.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 79CAC14D5A; Mon, 3 Jan 2000 22:41:12 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 4 Jan 2000 01:41:09 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: current@FreeBSD.org Cc: sos@FreeBSD.dk Subject: ATA atapi-all.c problems/fixes/cleanups 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 noticed a problem with the ATA driver with my (not quite, but to me) new CD-R drive. The behavior is that underruns and overruns are handled incorrectly, due to a mixup between variables. The end result is that too much data is sent to the drive and it chokes, borking my entire 2nd ATA bus and thereforeo my box. Enclosed is my fix in the form of a patch to atapi-all.c. The changes are: * general cleanups * the bugfixes * make the {over,under}run messages easier to understand/more helpful * more use of ATA_16BIT_ONLY and *l functions to maintain consistency I'm pretty certain that the bugfixes are correct, since it fixed the problem for me, but I don't know about the ATA_16BIT_ONLY usage. My uncertainty there lies in wondering if packets have to be a certain modulus. From the code, I'd assume that all packets would have a modulus of 4 bytes. Is this correct? Anyone else experiencing lockups when an underrun/overrun occurs, try this patch; it has fixed the problem for me, and now I'm on my way to writing music CDs :) The current way to hack around that bug must be to use the "obs" operand to dd(1), since that's what came naturally to me :) -- 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 Mon Jan 3 22:53:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust68.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B1A5614F9A; Mon, 3 Jan 2000 22:53:22 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 4 Jan 2000 01:53:19 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: current@FreeBSD.org Cc: sos@FreeBSD.dk Subject: Re: ATA atapi-all.c problems/fixes/cleanups 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 Tue, 4 Jan 2000, Brian Fundakowski Feldman wrote: > Anyone else experiencing lockups when an underrun/overrun occurs, try > this patch; it has fixed the problem for me, and now I'm on my way to > writing music CDs :) The current way to hack around that bug must be > to use the "obs" operand to dd(1), since that's what came naturally to > me :) Correction: I meant using "conv=osync" as an operand to dd(1), not just "bs"/"obs". -- 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 Mon Jan 3 23:18:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn18.fwn.rug.nl [129.125.32.168]) by hub.freebsd.org (Postfix) with ESMTP id 34D3914F79; Mon, 3 Jan 2000 23:18:10 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00337; Mon, 3 Jan 2000 14:48:06 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 3 Jan 2000 14:48:05 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Cameron Grant Cc: FreeBSD CURRENT Mailing List Subject: panic: isa_dmastart: bad bounce buffer 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 Starting mpg123 with a random mpg3 file produces the following panic within half a second. The kernel is current as of this morning. THe panic is reproducable (as in, I cannot play the mpg3 file). kernel plus core available if needed. Dec 15 14:55:25 henny /kernel: ESS1879: adding io range 0x220-0x22f, size=0x10, align=0 Dec 15 14:55:25 henny /kernel: ESS1879: adding io range 0x388-0x38b, size=0x4, align=0 Dec 15 14:55:25 henny /kernel: ESS1879: adding irq mask 0x20 Dec 15 14:55:25 henny /kernel: ESS1879: adding dma mask 0x2 Dec 15 14:55:25 henny /kernel: ESS1879: adding dma mask 0x20 Dec 15 14:55:25 henny /kernel: ESS1879: start dependant Dec 15 14:55:25 henny /kernel: pnpbios: handle 1 device ID ESS1879 (79187316) Dec 19 17:10:48 henny /kernel: sbc0: at port 0x220-0x22f,0x388-0x38b irq 5 drq 1,5 on isa0 Dec 19 17:10:48 henny /kernel: pcm0: on sbc0 Nick #9 0xc014c4dc in panic (fmt=0xc0276340 "isa_dmastart: bad bounce buffer") at ../../kern/kern_shutdown.c:551 #10 0xc0243f1e in isa_dmastart (flags=524288, addr=0xc4546000 "", nbytes=65280, chan=1) at ../../i386/isa/isa_dma.c:242 #11 0xc0206ea8 in buf_isadma (b=0xc08b4b4c, go=1) at ../../dev/sound/pcm/channel.c:842 #12 0xc022214f in esschan_trigger (data=0xc08b211c, go=1) at ../../dev/sound/isa/sb.c:943 #13 0xc0207558 in chn_trigger (c=0xc08b4b00, go=1) at ../../dev/sound/pcm/channel.c:1153 #14 0xc020653a in chn_wrintr (c=0xc08b4b00) at ../../dev/sound/pcm/channel.c:378 #15 0xc0206662 in chn_write (c=0xc08b4b00, buf=0xc8e91eec) at ../../dev/sound/pcm/channel.c:465 #16 0xc02054ab in dsp_write (d=0xc08b6e00, chan=0, buf=0xc8e91eec, flag=1) at ../../dev/sound/pcm/dsp.c:196 #17 0xc02049fd in sndwrite (i_dev=0xc08c5f80, buf=0xc8e91eec, flag=1) at ../../dev/sound/pcm/sound.c:319 #18 0xc0185e51 in spec_write (ap=0xc8e91ea0) at ../../miscfs/specfs/spec_vnops.c:280 #19 0xc01f2b84 in ufsspec_write (ap=0xc8e91ea0) at ../../ufs/ufs/ufs_vnops.c:1831 #20 0xc01f3021 in ufs_vnoperatespec (ap=0xc8e91ea0) at ../../ufs/ufs/ufs_vnops.c:2277 #21 0xc01806e6 in vn_write (fp=0xc0987340, uio=0xc8e91eec, cred=0xc0986480, flags=0, p=0xc8bcac80) at vnode_if.h:363 #22 0xc015a199 in dofilewrite (p=0xc8bcac80, fp=0xc0987340, fd=4, buf=0x8083000, nbyte=16384, offset=-1, flags=0) at ../../sys/file.h:156 #23 0xc015a09f in write (p=0xc8bcac80, uap=0xc8e91f80) at ../../kern/sys_generic.c:297 #24 0xc023b4a6 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134650736, tf_esi = 134662912, tf_ebp = 0, tf_isp = -924246060, tf_ebx = 134660608, tf_edx = 0, tf_ecx = 134733184, tf_eax = 4, tf_trapno = 12, tf_err = 2, tf_eip = 671900176, tf_cs = 31, tf_eflags = 659, tf_esp = -1077938712, tf_ss = 47}) at ../../i386/i386/trap.c:1057 -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 23:22:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 69ADD14C4F; Mon, 3 Jan 2000 23:22:26 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA72101; Tue, 4 Jan 2000 08:22:24 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001040722.IAA72101@freebsd.dk> Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: from Brian Fundakowski Feldman at "Jan 4, 2000 01:41:09 am" To: green@FreeBSD.org (Brian Fundakowski Feldman) Date: Tue, 4 Jan 2000 08:22:24 +0100 (CET) Cc: 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 Brian Fundakowski Feldman wrote: > I just noticed a problem with the ATA driver with my (not quite, but to me) > new CD-R drive. The behavior is that underruns and overruns are handled > incorrectly, due to a mixup between variables. The end result is that > too much data is sent to the drive and it chokes, borking my entire 2nd ATA > bus and thereforeo my box. > Enclosed is my fix in the form of a patch to atapi-all.c. The changes > are: > * general cleanups > * the bugfixes > * make the {over,under}run messages easier to understand/more helpful > * more use of ATA_16BIT_ONLY and *l functions to maintain consistency > I'm pretty certain that the bugfixes are correct, since it fixed the problem > for me, but I don't know about the ATA_16BIT_ONLY usage. My uncertainty > there lies in wondering if packets have to be a certain modulus. From the > code, I'd assume that all packets would have a modulus of 4 bytes. Is this > correct? Either the patch is very short, or you forgot to include it :) The ATA_16BIT_ONLY thing is to only do 16bit wide inb/outb instructions as old ISA HW don't allow 32bit wide access. This option is now deprecated as it is switched on automagically for ISA cards. > Anyone else experiencing lockups when an underrun/overrun occurs, try > this patch; it has fixed the problem for me, and now I'm on my way to > writing music CDs :) The current way to hack around that bug must be > to use the "obs" operand to dd(1), since that's what came naturally to > me :) You _should_ _always_ have dd (or whatever you use) pad the output to the given blocksize, or you will run into problems. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 3 23:52:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust168.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4CAAB150D3; Mon, 3 Jan 2000 23:52:09 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 4 Jan 2000 02:52:07 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.org Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001040722.IAA72101@freebsd.dk> Message-ID: 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 On Tue, 4 Jan 2000, Soren Schmidt wrote: > Either the patch is very short, or you forgot to include it :) *LOL* I can't believe I did that :) It'll be on this one!! > > The ATA_16BIT_ONLY thing is to only do 16bit wide inb/outb instructions > as old ISA HW don't allow 32bit wide access. This option is now deprecated > as it is switched on automagically for ISA cards. Is all data a multiple of 4 bytes, though? > > You _should_ _always_ have dd (or whatever you use) pad the output to the > given blocksize, or you will run into problems. IMHO, it should be better to use a larger multiple of block size (2352) to not perform so many operations in userland (since the kernel does a great job of doing writes in the right size in order). Then, it would be pessimal to use "conv=osync" because you'd lose more room from the media. But anyway, the padding should work properly, no matter what :) Thanks for the prompt reply! Now I'll remember that patch... > -Søren -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' cvs diff: Diffing . Index: atapi-all.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-all.c,v retrieving revision 1.28 diff -u -r1.28 atapi-all.c --- atapi-all.c 1999/12/21 20:18:55 1.28 +++ atapi-all.c 2000/01/04 06:26:31 @@ -71,6 +71,10 @@ /* defines */ #define ATAPI_MAX_RETRIES 5 +/* This is temporary until I can read up more on the specs WRT packet length. */ +#undef ATA_16BIT_ONLY +#define ATA_16BIT_ONLY + static __inline int apiomode(struct atapi_params *ap) { @@ -546,58 +550,70 @@ atapi_read(struct atapi_request *request, int32_t length) { int8_t **buffer = (int8_t **)&request->data; + int32_t minlen = min(request->bytecount, length); int32_t resid; if (request->ccb[0] == ATAPI_REQUEST_SENSE) *buffer = (int8_t *)&request->sense; - if (request->bytecount < length) { - printf("%s: read data overrun %d/%d\n", - request->device->devname, length, request->bytecount); + if (minlen < length) { + printf("%s: read data overrun (%d < %d); some data discarded.\n", + request->device->devname, minlen, length); #ifdef ATA_16BIT_ONLY insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)((uintptr_t)*buffer), minlen / sizeof(int16_t)); #else insl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int32_t)); + (void *)((uintptr_t)*buffer), minlen / sizeof(int32_t)); #endif - for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA); - } + for (resid = minlen; resid < length; resid += sizeof(int16_t)) + (void)inw(request->device->controller->ioaddr + ATA_DATA); + } else +#ifdef ATA_16BIT_ONLY insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + (void *)((uintptr_t)*buffer), minlen / sizeof(int16_t)); +#else + insl(request->device->controller->ioaddr + ATA_DATA, + (void *)((uintptr_t)*buffer), minlen / sizeof(int32_t)); +#endif + request->bytecount -= minlen; + *buffer += minlen; } static void atapi_write(struct atapi_request *request, int32_t length) { int8_t **buffer = (int8_t **)&request->data; + int32_t minlen = min(request->bytecount, length); int32_t resid; if (request->ccb[0] == ATAPI_REQUEST_SENSE) *buffer = (int8_t *)&request->sense; - if (request->bytecount < length) { - printf("%s: write data underrun %d/%d\n", - request->device->devname, length, request->bytecount); + if (minlen < length) { + printf("%s: write data underrun (%d < %d); padding to full length.\n", + request->device->devname, minlen, length); #ifdef ATA_16BIT_ONLY outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)((uintptr_t)*buffer), minlen / sizeof(int16_t)); #else outsl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int32_t)); + (void *)((uintptr_t)*buffer), minlen / sizeof(int32_t)); #endif - for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA, 0); } else +#ifdef ATA_16BIT_ONLY outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + (void *)((uintptr_t)*buffer), minlen / sizeof(int16_t)); +#else + outsl(request->device->controller->ioaddr + ATA_DATA, + (void *)((uintptr_t)*buffer), minlen / sizeof(int32_t)); +#endif + request->bytecount -= minlen; + *buffer += minlen; } static void @@ -619,7 +635,7 @@ /* retries all used up, return error */ request->result = ATAPI_SK_RESERVED | ATAPI_E_ABRT; wakeup((caddr_t)request); - } + } ata_reinit(atp->controller); } @@ -737,7 +753,7 @@ (atp->controller->status & ATA_S_READY)) break; DELAY (10); - } + } if (timeout <= 0) return -1; if (!mask) @@ -749,9 +765,9 @@ if ((atp->controller->status & mask) == mask) return (atp->controller->status & ATA_S_ERROR); DELAY (10); - } + } return -1; -} +} static void atapi_init(void) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 0:13:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6351415080; Tue, 4 Jan 2000 00:13:26 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA84062; Tue, 4 Jan 2000 09:13:25 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001040813.JAA84062@freebsd.dk> Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: from Brian Fundakowski Feldman at "Jan 4, 2000 02:52:07 am" To: green@FreeBSD.org (Brian Fundakowski Feldman) Date: Tue, 4 Jan 2000 09:13:25 +0100 (CET) Cc: 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 Brian Fundakowski Feldman wrote: > On Tue, 4 Jan 2000, Soren Schmidt wrote: > > > Either the patch is very short, or you forgot to include it :) > > *LOL* I can't believe I did that :) It'll be on this one!! Yup, this time there is a patch :) > > The ATA_16BIT_ONLY thing is to only do 16bit wide inb/outb instructions > > as old ISA HW don't allow 32bit wide access. This option is now deprecated > > as it is switched on automagically for ISA cards. > > Is all data a multiple of 4 bytes, though? Not really, ie there is nothing that says so. However ALL requests should be of length N*blocksize where N can be from 1 to 254. Blocksize is depending on the format used but normally 2048 or 2352 bytes... > > You _should_ _always_ have dd (or whatever you use) pad the output to the > > given blocksize, or you will run into problems. > > IMHO, it should be better to use a larger multiple of block size (2352) > to not perform so many operations in userland (since the kernel does a > great job of doing writes in the right size in order). Then, it would > be pessimal to use "conv=osync" because you'd lose more room from the > media. But anyway, the padding should work properly, no matter what :) The problem here is that you will then do a lot of unneeded padding as the driver will attempt to pad to the blocksize used which is not wanted. You HAVE to use the right blocksize especially for audio, or you will get "silent" ie zero padded blocks on disk, and thats not what you want is it ? > Thanks for the prompt reply! Now I'll remember that patch... Your'e welcome... What should be done is that we need a new util instead of wormcontrol and dd to do burning. I dont see me having time anytime soon, too much to do (DVD + DVD-RAM support, more chipsets etc etc), so I'm on my way to add an ioctl interface that cdrecord can use.... -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 Jan 4 0:28:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn18.fwn.rug.nl [129.125.32.168]) by hub.freebsd.org (Postfix) with ESMTP id 5B43314D9B for ; Tue, 4 Jan 2000 00:28:11 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id JAA01445; Tue, 4 Jan 2000 09:03:07 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 4 Jan 2000 09:03:07 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Eric D. Futch" Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: USB broken? 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 recommend using USB on 3.4. It's a lot less reliable than the version in CURRENT. The reason for it being there (in a hidden fashion) is historic and nothing to be proud of. Nick On Wed, 29 Dec 1999, Eric D. Futch wrote: > Oh hehe damn did it again. Keep getting my lists mixed up. This machine > is running 3.4-stable and I should have probably posted this to -stable. > Sorry about that... but I really do have 4.0-current running on another > machine.. so I'm not totally crazy :) > > -- > Eric Futch New York Connect.Net, Ltd. > efutch@nyct.net Technical Support Staff > http://www.nyct.net (212) 293-2620 > "Bringing New York The Internet Access It Deserves" > > > On Wed, 29 Dec 1999, Bill Paul wrote: > > Of all the gin joints in all the towns in all the world, Eric D. Futch > had to walk into mine and say: > > > I'm running -current that's about a week old. > > Erm... are you sure? I'm having trouble believing you. > > > I configed my kernel for > > USB support. After turning on the USB interface in BIOS kernel panics > > after it probes uchi0. Below is the panic screen, I don't have much else > > to go on. > > > > --- > > uhci0: rev 0x01 int d irq 10 on pci0.7.2> > > kernel trap 12 with interrupts disabled > > See this kernel probe output here? This is not from a 4.0-CURRENT > kernel from a week ago. This is what the probe output from a recent > -current system should look like: > > uhci0: irq 11 at device 7.2 on pci0 > > Notice the difference? It's been like that for a *long* time now. > Therefore I can only conclude that either you're not actually running > -current, or else you thought it would be okay to substitute in a really > stale entry from a system log file from a 3.x system. Either way, you > need to re-evaluate the situation and provide more info. > > Now rather than being vague, go back and show us what uname -a says > on this allegedly -current system and show it to us. Show us the > *entire* dmesg output too, while you're at it. > > Furthermore, you should be able to test USB support without recompiling > the kernel. All you need to do is kldload usb. That will load the usb.ko > kernel module, which should find the UHCI controller. > > >From the panic message you showed here, you're using SMP. Have you > tested it with a UP kernel? (Yes, it's supposed to work either way, > but it would be nice if you would just test it to rule out some sort > of SMP-related condition.) > > What you should do is this: > > - Compile a kernel with options DDB, but *WITHOUT* USB support. > - Boot this kernel. > - Type kldload usb > - See if the system crashes. > - If it does, it will drop into the debugger. > - Type 'trace' > - Report 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 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 1: 4:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id A1ED414F9F for ; Tue, 4 Jan 2000 01:04:05 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p51.rlz.netvision.net.il [62.0.168.53]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id LAA21422 for ; Tue, 4 Jan 2000 11:04:01 +0200 (IST) Message-ID: <3871B806.79F8AE2B@freenet.co.uk> Date: Tue, 04 Jan 2000 09:06:14 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Ouch! Something broke (possibly ATA) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today's -current: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #21: Tue Jan 4 08:00:34 GMT 2000 Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (333.35-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 126709760 (123740K bytes) Preloaded elf kernel "kernel.test" at 0xc02e2000. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc0294fa0 (1000040) VESA: CHIPS 6x555 Super VGA npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 1.2 chip1: at device 1.3 on pci0 vga-pci0: at device 6.0 on pci0 pcic-pci0: at device 7.0 on pci0 pcic-pci1: at device 7.1 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: not probed (disabled) sio2: configured irq 3 not in bitmap of probed irqs 0 sio2 at port 0x3e8-0x3ef irq 3 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbff21000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0214ffe stack pointer = 0x10:0xc02f6b58 frame pointer = 0x10:0xc02f6b8c 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 = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort % nm /kernel.test | grep c0214f c0214f68 T bus_dmamap_load c0214f28 T bus_dmamem_free Would you like to know more? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 1:11:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id B616D1519A for ; Tue, 4 Jan 2000 01:11:01 -0800 (PST) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id 3FC2562E4E; Tue, 4 Jan 2000 19:40:55 +1030 (CST) Date: Tue, 4 Jan 2000 19:40:55 +1030 From: Ian West To: Alex Cc: freebsd-current@freebsd.org Subject: Re: Ouch! Something broke (possibly ATA) Message-ID: <20000104194055.R52226@rose.niw.com.au> References: <3871B806.79F8AE2B@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3871B806.79F8AE2B@freenet.co.uk>; from Alex on Tue, Jan 04, 2000 at 09:06:14AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 09:06:14AM +0000, Alex wrote: > Today's -current: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #21: Tue Jan 4 08:00:34 GMT 2000 > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (333.35-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf > AMD Features=0x80000800 > real memory = 134217728 (131072K bytes) > avail memory = 126709760 (123740K bytes) > Preloaded elf kernel "kernel.test" at 0xc02e2000. > VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc0294fa0 (1000040) > VESA: CHIPS 6x555 Super VGA > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 1.0 on pci0 > isa0: on isab0 > ata-pci0: at device 1.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, > dev=0x7112) at 1.2 > chip1: at device 1.3 on pci0 > vga-pci0: device> at device 6.0 on pci0 > pcic-pci0: at device 7.0 on pci0 > pcic-pci1: at device 7.1 on pci0 > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > pcic0: at irq 10 on isa0 > pccard0: on pcic0 > pccard1: on pcic0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: not probed (disabled) > sio2: configured irq 3 not in bitmap of probed irqs 0 > sio2 at port 0x3e8-0x3ef irq 3 on isa0 > sio2: type 16550A > ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > plip0: on ppbus 0 > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > pcm0: at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 > on isa0 > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xbff21000 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0214ffe > stack pointer = 0x10:0xc02f6b58 > frame pointer = 0x10:0xc02f6b8c > 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 = net tty bio cam > trap number = 12 > panic: page fault > Uptime: 0s > Automatic reboot in 15 seconds - press a key on the console to abort > > > % nm /kernel.test | grep c0214f > c0214f68 T bus_dmamap_load > c0214f28 T bus_dmamem_free > > > Would you like to know more? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I got exactly this from compiling a kernel (accidentally) with the development port of GCC. I am not sure if the same feature exists with the latest GCC imported into the tree, but as of two days ago it didn't. I am currently doing a make world on a spare machine to check it with the latest compiler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 1:12:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7F4F414E9C for ; Tue, 4 Jan 2000 01:12:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA97868; Tue, 4 Jan 2000 10:12:03 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001040912.KAA97868@freebsd.dk> Subject: Re: Ouch! Something broke (possibly ATA) In-Reply-To: <3871B806.79F8AE2B@freenet.co.uk> from Alex at "Jan 4, 2000 09:06:14 am" To: ak@freenet.co.uk (Alex) Date: Tue, 4 Jan 2000 10:12:02 +0100 (CET) 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 Alex wrote: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xbff21000 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0214ffe > stack pointer = 0x10:0xc02f6b58 > frame pointer = 0x10:0xc02f6b8c > 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 = net tty bio cam > trap number = 12 > panic: page fault > Uptime: 0s > Automatic reboot in 15 seconds - press a key on the console to abort > > > % nm /kernel.test | grep c0214f > c0214f68 T bus_dmamap_load > c0214f28 T bus_dmamem_free Those are not used by the ata driver.... -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 Jan 4 1:28:13 2000 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 CAFC814E9C for ; Tue, 4 Jan 2000 01:28:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA03630; Tue, 4 Jan 2000 09:29:41 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 4 Jan 2000 09:27:54 +0000 (GMT) From: Doug Rabson To: Pascal Hofstee Cc: freebsd-current@freebsd.org Subject: Re: NewPCM causes kernel panics ! In-Reply-To: <20000104014046.A769@shadowmere.student.utwente.nl> 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, 4 Jan 2000, Pascal Hofstee wrote: > Hi, With CURRENT sources updated earlier today ... my system now > crash-and-burns when trying to play audio. > > i have foudn these messages in /var/log/messages: > > Jan 4 01:30:26 shadowmere /kernel: gusc0: at port > 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 > Jan 4 01:30:26 shadowmere /kernel: pcm0: on gusc0 > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > = 0xdf00 > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > = 0xdf00 > > If any more info is needed let me know. This looks like a buffer which spans >1 non-contiguous physical ranges. Was the buffer allocated with contigmalloc? -- 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 Tue Jan 4 2:28:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 20502150C5 for ; Tue, 4 Jan 2000 02:28:21 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk ([62.0.169.227]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id MAA13601; Tue, 4 Jan 2000 12:28:12 +0200 (IST) Message-ID: <3871CBBE.496E36F1@freenet.co.uk> Date: Tue, 04 Jan 2000 10:30:22 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG, gandalf@vilnya.demon.co.uk Subject: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) References: <200001040912.KAA97868@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Alex wrote: > > pcm0: at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 > > on isa0 > > > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xbff21000 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc0214ffe > > stack pointer = 0x10:0xc02f6b58 > > frame pointer = 0x10:0xc02f6b8c > > 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 = net tty bio cam > > trap number = 12 > > panic: page fault > > Uptime: 0s > > Automatic reboot in 15 seconds - press a key on the console to abort > > > > > > % nm /kernel.test | grep c0214f > > c0214f68 T bus_dmamap_load > > c0214f28 T bus_dmamem_free > > Those are not used by the ata driver.... > > -Søren ....and I apologise for wrongfully accusing it. The panic is in fact caused by newpcm (Cameron CC'd). DDB trace can be provided upon request (is there a way to save it into a file instead of having to write it down on a piece of paper?) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 2:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 8D23B1522F for ; Tue, 4 Jan 2000 02:43:37 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 1E2CF1FD2; Tue, 4 Jan 2000 11:43:36 +0100 (CET) Date: Tue, 4 Jan 2000 11:43:36 +0100 From: Pascal Hofstee To: Doug Rabson Cc: Pascal Hofstee , freebsd-current@freebsd.org Subject: Re: NewPCM causes kernel panics ! Message-ID: <20000104114336.B89670@shadowmere.student.utwente.nl> References: <20000104014046.A769@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dfr@nlsystems.com on Tue, Jan 04, 2000 at 09:27:54AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 09:27:54AM +0000, Doug Rabson wrote: > On Tue, 4 Jan 2000, Pascal Hofstee wrote: > > > Hi, With CURRENT sources updated earlier today ... my system now > > crash-and-burns when trying to play audio. > > > > i have foudn these messages in /var/log/messages: > > > > Jan 4 01:30:26 shadowmere /kernel: gusc0: at port > > 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 > > Jan 4 01:30:26 shadowmere /kernel: pcm0: on gusc0 > > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > > = 0xdf00 > > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > > = 0xdf00 > > > > If any more info is needed let me know. > > This looks like a buffer which spans >1 non-contiguous physical ranges. > Was the buffer allocated with contigmalloc? I don't know this is what came directly from the NewPCM-probe/attach code. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 2:46:35 2000 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 4905B14A0A for ; Tue, 4 Jan 2000 02:46:33 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id F1B772CE4E; Tue, 4 Jan 2000 12:46:25 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 5C2C675; Tue, 4 Jan 2000 12:46:28 +0200 (EET) Date: Tue, 4 Jan 2000 12:46:28 +0200 From: Vallo Kallaste To: Alex Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) Message-ID: <20000104124628.A40560@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <200001040912.KAA97868@freebsd.dk> <3871CBBE.496E36F1@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3871CBBE.496E36F1@freenet.co.uk>; from Alex on Tue, Jan 04, 2000 at 10:30:22AM +0000 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 10:30:22AM +0000, Alex wrote: > ....and I apologise for wrongfully accusing it. The panic is in fact > caused by newpcm (Cameron CC'd). DDB trace can be provided upon request > (is there a way to save it into a file instead of having to write it > down on a piece of paper?) Sure. Hook up serial console or some terminal program to appropriate serial port using null-modem cable, then rebuild your kernel and boot with right flag. Look at sys/i386/LINT, man sio(4) and man boot(8). -- 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 Tue Jan 4 3:26:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (Postfix) with ESMTP id DC3CB15243 for ; Tue, 4 Jan 2000 03:26:06 -0800 (PST) (envelope-from regnauld@ftf.net) Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged)) by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id MAA21229 for ; Tue, 4 Jan 2000 12:25:57 +0100 (CET) X-Authentication-Warning: mail.ftf.dk: Host fw2.ftf.dk [192.168.1.2] (may be forged) claimed to be ns.int.ftf.net Received: (from regnauld@localhost) by ns.int.ftf.net (8.9.2/8.9.3) id MAA53791; Tue, 4 Jan 2000 12:38:05 +0100 (CET) Message-ID: <20000104123804.23965@ns.int.ftf.net> Date: Tue, 4 Jan 2000 12:38:04 +0100 From: Phil Regnauld To: freebsd-current@freebsd.org Subject: NFS Race Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just saw this passing on the console while compiling teTeX on an NFS mounted dir: NFS append race @0:19 NFS append race @0:135 NFS append race @0:60 NFS append race @0:102 NFS append race @0:60 NFS append race @0:12 NFS append race @0:24 NFS append race @0:66 NFS append race @0:512 NFS append race @0:958 What does that mean ? A few more popped up while I type this. conf: FreeBSD xx 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Jan 3 14:23:12 CET 2000 regnauld@xx:/usr/src/sys/compile/AYLEE i386 mount options: bofh:/src/ports /usr/ports nfs rw,bg,intr,soft,-r=8192,-w=8192 0 0 Any ideas ? -- Y2k happened without any problems. To remind us of how it could have been, Microsoft has just released Windows 2000. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 4:37:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 7A14B14C35 for ; Tue, 4 Jan 2000 04:37:03 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id OAA86711; Tue, 4 Jan 2000 14:33:20 +0200 (EET) (envelope-from ru) Date: Tue, 4 Jan 2000 14:33:20 +0200 From: Ruslan Ermilov To: Paul Eggert Cc: obrien@NUXI.com, alainm@rcsm.ece.mcgill.ca, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <20000104143320.D10970@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1" X-Mailer: Mutt 0.95.3i In-Reply-To: <199911130445.UAA03345@green.twinsun.com> X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii On Fri, Nov 12, 1999 at 20:45:10 -0800, Paul Eggert wrote: > > Date: Fri, 12 Nov 1999 17:23:21 -0800 > From: "David O'Brien" > > I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU > longopt. > > Another possibility would be to follow the example of the existing > --directories=ACTION option, e.g. something like this: > > --binary-files=ACTION how to handle binary files > ACTION is 'read', 'skip', or 'summarize' (default) > -I equivalent to --binary-files=skip > -a, --text equivalent to --binary-files=read > Paul, could you please consider applying the following patch (it is against virgin grep-2.4 sources). Could you please also let me know when the Alpha with this feature will be made available, so I could import it into FreeBSD. Or maybe tell me an address of appropriate "announce" mailing list... Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="grep.c.patch" --- grep.c.orig Sat Nov 13 18:31:55 1999 +++ grep.c Tue Jan 4 14:11:09 2000 @@ -60,7 +60,7 @@ /* Short options. */ static char const short_options[] = -"0123456789A:B:C::EFGHUVX:abcd:e:f:hiLlnqrsuvwxyZz"; +"0123456789A:B:C::EFGHIUVX:Y:abcd:e:f:hiLlnqrsuvwxyZz"; /* Long options equivalences. */ static struct option long_options[] = @@ -68,6 +68,7 @@ {"after-context", required_argument, NULL, 'A'}, {"basic-regexp", no_argument, NULL, 'G'}, {"before-context", required_argument, NULL, 'B'}, + {"binary-files", required_argument, NULL, 'Y'}, {"byte-offset", no_argument, NULL, 'b'}, {"context", optional_argument, NULL, 'C'}, {"count", no_argument, NULL, 'c'}, @@ -120,6 +121,14 @@ SKIP_DIRECTORIES } directories; +/* How to handle binary files. */ +static enum + { + SUMMARIZE_BINARIES, + READ_BINARIES, + SKIP_BINARIES + } binaries; + static int ck_atoi PARAMS ((char const *, int *)); static void usage PARAMS ((int)) __attribute__((noreturn)); static void error PARAMS ((const char *, int)); @@ -476,7 +485,6 @@ } /* Flags controlling the style of output. */ -static int always_text; /* Assume the input is always text. */ static int filename_mask; /* If zero, output nulls after filenames. */ static int out_quiet; /* Suppress all normal output. */ static int out_invert; /* Print nonmatching stuff. */ @@ -732,11 +740,14 @@ return nlines; } - not_text = (! (always_text | out_quiet) + not_text = (binaries != READ_BINARIES && memchr (bufbeg, eol ? '\0' : '\200', buflim - bufbeg)); done_on_match += not_text; out_quiet += not_text; + if (not_text && binaries == SKIP_BINARIES) + goto finish_grep; + for (;;) { lastnl = bufbeg; @@ -993,10 +1004,13 @@ -H, --with-filename print the filename for each match\n\ -h, --no-filename suppress the prefixing filename on output\n\ -q, --quiet, --silent suppress all normal output\n\ - -a, --text do not suppress binary output\n\ -d, --directories=ACTION how to handle directories\n\ ACTION is 'read', 'recurse', or 'skip'.\n\ -r, --recursive equivalent to --directories=recurse.\n\ + -Y, --binary-files=ACTION how to handle binary files\n\ + ACTION is 'summarize' (default), 'read', or 'skip'. + -a, --text equivalent to --binary-files=read\n\ + -I equivalent to --binary-files=skip\n\ -L, --files-without-match only print FILE names containing no match\n\ -l, --files-with-matches only print FILE names containing matches\n\ -c, --count only print a count of matching lines per FILE\n\ @@ -1276,7 +1290,7 @@ setmatcher (optarg); break; case 'a': - always_text = 1; + binaries = READ_BINARIES; break; case 'b': out_byte = 1; @@ -1326,6 +1340,9 @@ case 'h': no_filenames = 1; break; + case 'I': + binaries = SKIP_BINARIES; + break; case 'i': case 'y': /* For old-timers . . . */ match_icase = 1; @@ -1363,6 +1380,16 @@ break; case 'x': match_lines = 1; + break; + case 'Y': + if (strcmp (optarg, "summarize") == 0) + binaries = SUMMARIZE_BINARIES; + else if (strcmp (optarg, "read") == 0) + binaries = READ_BINARIES; + else if (strcmp (optarg, "skip") == 0) + binaries = SKIP_BINARIES; + else + fatal (_("unknown binary-files method"), 0); break; case 'Z': filename_mask = 0; --n8g4imXOkfNTN/H1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 5: 1:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 027741526A for ; Tue, 4 Jan 2000 05:01:20 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 125TaQ-0000mU-00 for current@freebsd.org; Tue, 4 Jan 2000 13:01:18 +0000 Date: Tue, 4 Jan 2000 14:01:17 +0100 (CET) From: Marc Schneiders To: current@freebsd.org Subject: new man pages 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 Where do I look for new man pages? I would like to read those for the new ata driver and for ntpd. They were not created during a build world some 5 days ago. And I cannot find them in /usr/src/share/man/man4, where I would expect man ata/ad in any case. TIA. -- Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 1:42pm up 4 days, 15:31, load average: 3.05 3.01 2.89 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 6:12:48 2000 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 B27151528E for ; Tue, 4 Jan 2000 06:12:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA28583 for current@FreeBSD.org; Tue, 4 Jan 2000 14:58:07 +0100 (CET) (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: Tue, 04 Jan 2000 14:58:01 +0100 From: Marcel Moolenaar Message-ID: <3871FC69.C99882E9@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Proposal: Removing doscmd from the source tree... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [sent to both -current and -arch] Hi, doscmd breaks cross-building, because it depends on X11 which obviously is not in the source tree (see below). I'm proposing to remove doscmd from the source tree and make it a port (emulators/doscmd). Your comments please. From a i386 cross-build on Alpha: cc -O -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/i386/usr/src/alpha/usr/include -o doscmd AsyncIO.o ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o xms.o -L/usr/X11R6/lib -lX11 /usr/X11R6/lib/libX11.so: file not recognized: File format not recognized *** Error code 1 Thanks, -- 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 Tue Jan 4 6:37:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AE5C31518B for ; Tue, 4 Jan 2000 06:37:47 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id BAA05933; Wed, 5 Jan 2000 01:37:32 +1100 Date: Wed, 5 Jan 2000 01:37:31 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... In-Reply-To: <3871FC69.C99882E9@scc.nl> 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, 4 Jan 2000, Marcel Moolenaar wrote: > [sent to both -current and -arch] > > Hi, > > doscmd breaks cross-building, because it depends on X11 which obviously > is not in the source tree (see below). I'm proposing to remove doscmd > from the source tree and make it a port (emulators/doscmd). But it doesn't depend on X11. It ifdefs some X11 files and only builds the X11 version if X11 seems to be present. > Your comments please. > > >From a i386 cross-build on Alpha: > > cc -O -I. -I/usr/X11R6/include -DDISASSEMBLER > -I/usr/obj/i386/usr/src/alpha/usr/include -o doscmd AsyncIO.o > ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o > debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o > int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o > mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o > xms.o -L/usr/X11R6/lib -lX11 > /usr/X11R6/lib/libX11.so: file not recognized: File format not > recognized > *** Error code 1 It uses wrong ifdefs for the X11 files :-). It should never find any X11 files for building worlds, since there are no X11 includes or libraries under ${WORLDTMP}. Adding some ${DESTDIR}'s is probably a sufficient fix. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 6:51:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B3FDA1523A for ; Tue, 4 Jan 2000 06:51:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA79395; Tue, 4 Jan 2000 15:49:33 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001041449.PAA79395@freebsd.dk> Subject: Re: new man pages In-Reply-To: from Marc Schneiders at "Jan 4, 2000 02:01:17 pm" To: marc@oldserver.demon.nl (Marc Schneiders) Date: Tue, 4 Jan 2000 15:49:33 +0100 (CET) Cc: 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 Marc Schneiders wrote: > Where do I look for new man pages? I would like to read those for the > new ata driver and for ntpd. They were not created during a build > world some 5 days ago. And I cannot find them in > /usr/src/share/man/man4, where I would expect man ata/ad in any case. There are no man pages for the ata driver (yet), for nptd I dunno... -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 Jan 4 7: 8:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id A052314E49 for ; Tue, 4 Jan 2000 07:08:39 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 125VZd-0004MW-00; Tue, 4 Jan 2000 15:08:37 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id QAA04034; Tue, 4 Jan 2000 16:08:19 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38720CE3.DDD78778@scc.nl> Date: Tue, 04 Jan 2000 16:08:19 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On Tue, 4 Jan 2000, Marcel Moolenaar wrote: > > > [sent to both -current and -arch] > > > > Hi, > > > > doscmd breaks cross-building, because it depends on X11 which obviously > > is not in the source tree (see below). I'm proposing to remove doscmd > > from the source tree and make it a port (emulators/doscmd). > > But it doesn't depend on X11. It ifdefs some X11 files and only builds > the X11 version if X11 seems to be present. X11 can be present, but it won't necessarily be a usable X11. A i386 cross-build on Alpha will use an alpha X11 to build an i386 doscmd. That's wrong. > > >From a i386 cross-build on Alpha: > > > > cc -O -I. -I/usr/X11R6/include -DDISASSEMBLER > > -I/usr/obj/i386/usr/src/alpha/usr/include -o doscmd AsyncIO.o > > ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o > > debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o > > int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o > > mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o > > xms.o -L/usr/X11R6/lib -lX11 > > /usr/X11R6/lib/libX11.so: file not recognized: File format not > > recognized > > *** Error code 1 > > It uses wrong ifdefs for the X11 files :-). It should never find any X11 > files for building worlds, since there are no X11 includes or libraries > under ${WORLDTMP}. Adding some ${DESTDIR}'s is probably a sufficient fix. Ok, but this means that we won't install doscmd with X11 support anymore. The user has to rebuild doscmd itself to have X11 support. In that case, it's better to have it in the ports collection... -- 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 Tue Jan 4 7:18:10 2000 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 3897E15223 for ; Tue, 4 Jan 2000 07:18:06 -0800 (PST) (envelope-from brdean@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 KAA08795; Tue, 4 Jan 2000 10:18:04 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA25078; Tue, 4 Jan 2000 10:17:34 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id KAA55947; Tue, 4 Jan 2000 10:17:34 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200001041517.KAA55947@dean.pc.sas.com> Subject: Re: tip features (cdelay and ldelay)? In-Reply-To: <200001022240.RAA01469@vger.foo.com> from Brian Dean at "Jan 2, 2000 05:40:36 pm" To: freebsd-current@freebsd.org Date: Tue, 4 Jan 2000 10:17:34 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, (replying to myself) Since no one seems to recall why these features were removed, and I don't see any reference to them in the CVS log, would someone please consider applying the included patch to re-enable them? This patch also includes a fix I made to correct PR bin/15847 that I opened. If you wish to submit these separately so that it makes backing out easier, just edit out the stuff related to eofchars in this included patch. I included a patch in the PR that fixes the core dump and can be applied on its own. Thanks, -Brian -- Brian Dean brdean@unx.sas.com Brian Dean wrote: > Subject: tip features (cdelay and ldelay)? > To: freebsd-current@FreeBSD.ORG > Date: Sun, 2 Jan 2000 17:40:36 -0500 (EST) > I have a couple of really dumb devices that I use 'tip' to talk to. > One is a Motorola 6811 microcontroller and the other is an old EEPROM > burner. I find that 'tip' overflows these devices when I'm sending > Motorola s-record and Intel Hex formatted files. > > It looks like tip's 'cdelay' and 'ldelay' features do just the trick. > However, they are disabled, surrounded by '#ifdef notdef' sequences. > Just to make sure, I re-enabled them locally, and re-implemented the > apparently lost 'nap()' function to make sure that these features work > for my application, and they do. > > My question is: does anyone remember why these were disabled in the > first place? Is there an equivalent replacement feature that I can > use instead to pace the outgoing characters so that I don't overrun > dumb devices with no flow control? Here's the patch: ---------------------------------------------------------------------- Index: cmds.c =================================================================== RCS file: /usr02/mirror/ncvs/src/usr.bin/tip/tip/cmds.c,v retrieving revision 1.10 diff -u -r1.10 cmds.c --- cmds.c 1999/08/28 01:06:32 1.10 +++ cmds.c 2000/01/04 15:04:31 @@ -48,6 +48,7 @@ #include #include #include +#include /* * tip @@ -513,7 +514,7 @@ out: if (lastc != '\n' && !boolean(value(RAWFTP))) send('\r'); - for (pc = eofchars; *pc; pc++) + for (pc = eofchars; pc && *pc; pc++) send(*pc); stop_t = time(0); fclose(fd); @@ -560,6 +561,24 @@ transmit(fd, "\04", line); } + +static int +nap ( int microsec ) +{ + int rc; + + rc = usleep ( microsec ); + if (rc != 0) { + fprintf ( stderr, + "warning: ldelay or cdelay interrupted, " + "delay time cut short: %s\n", + strerror(errno) ); + } + + return 0; +} + + /* * FTP - send single character * wait for echo & handle timeout @@ -573,15 +592,11 @@ cc = c; xpwrite(FD, &cc, 1); -#ifdef notdef if (number(value(CDELAY)) > 0 && c != '\r') nap(number(value(CDELAY))); -#endif if (!boolean(value(ECHOCHECK))) { -#ifdef notdef if (number(value(LDELAY)) > 0 && c == '\r') nap(number(value(LDELAY))); -#endif return; } tryagain: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 7:31:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2A78615254 for ; Tue, 4 Jan 2000 07:31:17 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA07620; Wed, 5 Jan 2000 02:31:05 +1100 Date: Wed, 5 Jan 2000 02:31:04 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... In-Reply-To: <38720CE3.DDD78778@scc.nl> 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, 4 Jan 2000, Marcel Moolenaar wrote: > Bruce Evans wrote: > > > > But it doesn't depend on X11. It ifdefs some X11 files and only builds > > the X11 version if X11 seems to be present. > > X11 can be present, but it won't necessarily be a usable X11. A i386 > cross-build on Alpha will use an alpha X11 to build an i386 doscmd. > That's wrong. An X11 for a different arch shouldn't count as being present. > > It uses wrong ifdefs for the X11 files :-). It should never find any X11 > > files for building worlds, since there are no X11 includes or libraries > > under ${WORLDTMP}. Adding some ${DESTDIR}'s is probably a sufficient fix. > > Ok, but this means that we won't install doscmd with X11 support > anymore. The user has to rebuild doscmd itself to have X11 support. In This is nothing new, I hope. The release build environment shouldn't be polluted with X11, so releases should only have non-X11 doscmds. > that case, it's better to have it in the ports collection... I think it's too system-dependent to work well as a port. You would need 2 ports, one with X11 support and one without. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 7:55:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 53C15153C9 for ; Tue, 4 Jan 2000 07:55:06 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA08308; Wed, 5 Jan 2000 02:54:52 +1100 Date: Wed, 5 Jan 2000 02:54:50 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: tip features (cdelay and ldelay)? In-Reply-To: <200001041517.KAA55947@dean.pc.sas.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, 4 Jan 2000, Brian Dean wrote: > Since no one seems to recall why these features were removed, and I > don't see any reference to them in the CVS log, would someone please The were gone in the base version (4.4Lite1). > consider applying the included patch to re-enable them? > +static int > +nap ( int microsec ) > +{ > + int rc; > + > + rc = usleep ( microsec ); > + if (rc != 0) { > + fprintf ( stderr, > + "warning: ldelay or cdelay interrupted, " > + "delay time cut short: %s\n", > + strerror(errno) ); > + } > + > + return 0; > +} usleep() has a resolution of 2/HZ seconds (normally 20msec), so the above gives very slow output (50-100 cps). Using a low baud rate (500-1000 bps) give the same result. If you want a shorter delay/faster output, then there is nothing better than a busy-wait loop for implementing nap(). Using a not so low baud rate (1200+ bps) may work better. Perhaps nap() was dropped because it can't be implemented reasonably. > /* > * FTP - send single character > * wait for echo & handle timeout > @@ -573,15 +592,11 @@ > > cc = c; > xpwrite(FD, &cc, 1); > -#ifdef notdef > if (number(value(CDELAY)) > 0 && c != '\r') > nap(number(value(CDELAY))); > -#endif > if (!boolean(value(ECHOCHECK))) { > -#ifdef notdef > if (number(value(LDELAY)) > 0 && c == '\r') > nap(number(value(LDELAY))); > -#endif > return; > } > tryagain: This seems to rely on the driver adding a suitable delay for the c == '\r' case. The tty driver has never supported delays for special characters. The necessary delays are even harder to implement in the kernel than in userland, since timeout() resolution is the same as usleep() resolution and busy waiting is not acceptable in the kernel. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 7:55:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 10FE914FF9 for ; Tue, 4 Jan 2000 07:55:39 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id AAA09704; Wed, 5 Jan 2000 00:55:29 +0900 (JST) Received: from rhea.sky.rim.or.jp by mail1.rim.or.jp (8.9.3+Sun/3.7W/) id AAA02247; Wed, 5 Jan 2000 00:55:31 +0900 (JST) (envelope-from kuriyama@sky.rim.or.jp) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id AAA29928; Wed, 5 Jan 2000 00:55:28 +0900 (JST) Date: Wed, 05 Jan 2000 00:55:26 +0900 Message-ID: <14450.6126.709759.19547O@localhost.sky.rim.or.jp> From: Jun Kuriyama To: bmilekic@dsuper.net Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c In-Reply-To: In your message of "Sat, 1 Jan 2000 23:03:39 -0500 (EST)" References: <14446.48302.292419.80479F@localhost.sky.rim.or.jp> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bosko Milekic > You don't happen to have a backtrace? I don't have it. When my box gives no reaction, I've hit some keys, keys, keys...and rebooted automatically. At that time, I could not switch to VT1 from X with [Ctrl]+[Alt]+[F1]. > Was anything particular happening at the time of the crash? Do you > have any way to not necessarily directly reproduce the panic but rather > "force" it to happen (e.g. as a consequence of execution of something or, > even as a result of some external "trigger")? I think I used XEmacs, Netscape Communicator and many console works with ssh'ed remote login. I have no idea which one made this. Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@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 Jan 4 8: 5:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 210B615355; Tue, 4 Jan 2000 08:05:11 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id LAA16719; Tue, 4 Jan 2000 11:05:03 -0500 (EST) From: "Allen Pulsifer" To: "freebsd-questions@FreeBSD. ORG" Cc: Subject: RE: console support (was RIDE for BSD) Date: Tue, 4 Jan 2000 11:05:03 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I second this. I'm not a linux user, but as a FreeBSD newbie I had a lot of trouble getting anywhere with console programs, esp. emacs and various IDE's that I tried to install. The key board mapping was difficult/impossible to figure out, and it also seemed like cons25 didn't always work correctly. The IDE's (whose names I now forget) would often draw stuff on the screen randomly offset by one line or one column, and old stuff wouldn't get erased properly. They also threw funny characters up on the screen when it looked like they were trying to produce formatting such as colored or highlighted text. This made the tools impossible to use. At the time I wasn't sure if it was me, my setup, the tools, or something in FreeBSD. I know this isn't a very good bug report, but if someone is actively working on this stuff or if there are any plans to revisit it, let me know and I'll put in better bug reports if/when I get a chance to revisit it. Allen P.S. I cc'ed this email to -current. > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jonathon > McKitrick > Sent: Tuesday, January 04, 2000 9:42 AM > To: Alexey N. Dokuchaev > Cc: Adam; freebsd-questions@FreeBSD.ORG > Subject: Re: RIDE for BSD > > > > On Tue, 4 Jan 2000, Alexey N. Dokuchaev wrote: > > >Probably improving terminal would be one of the things Fbsd might consider > >for future releases? > > > >And one more thing: until I wait for cool FreeBSD native terminal support, > >I consider copying linux-terminal descrition for my linux box termcap. Did > >anyone do anything like this before? What problems/pitfalls should I > >encounter? > > I must admit, this is one concept i do not understand. I mean, it makes > sense to leave the system freely configurable, but wouldn't it make sense > that the default config be useable? For exampl,e little things, like > linux uses bash as the default shell. It's there, it works, no questions > asked: my backspace never turns into a ^H, and arrow up is history, not > ^A]. This is one thing that makes it very frustrating for those of us who > leave Linux for something reportedly better. I agree i *do* like FreeBSD > better now, but i'm still pulling my hair out over little details that > were smooth sailing with Linux. And setting up usable color consoles > shouldn't be that difficult. But apparently for me it is. > > -=> jm <=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 8: 6: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 8507D15364 for ; Tue, 4 Jan 2000 08:05:46 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id KAA57128; Tue, 4 Jan 2000 10:04:58 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 4 Jan 2000 10:04:58 -0600 (CST) From: David Scheidt To: Soren Schmidt Cc: Marc Schneiders , current@FreeBSD.ORG Subject: Re: new man pages In-Reply-To: <200001041449.PAA79395@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 Tue, 4 Jan 2000, Soren Schmidt wrote: > It seems Marc Schneiders wrote: > > Where do I look for new man pages? I would like to read those for the > > new ata driver and for ntpd. They were not created during a build > > world some 5 days ago. And I cannot find them in > > /usr/src/share/man/man4, where I would expect man ata/ad in any case. > > There are no man pages for the ata driver (yet), for nptd I dunno... The new ntpd doesn't have any man pages. There are some html docs that come with the base distribution. I don't know if they are in the FreeBSD distribution, or where. Try looking in /usr/share. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 8: 8:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id EF55215355 for ; Tue, 4 Jan 2000 08:08:20 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 125WVI-000FXa-00; Tue, 4 Jan 2000 16:08:12 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id RAA05982; Tue, 4 Jan 2000 17:08:11 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38721AEB.68D35958@scc.nl> Date: Tue, 04 Jan 2000 17:08:11 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > > > It uses wrong ifdefs for the X11 files :-). It should never find any X11 > > > files for building worlds, since there are no X11 includes or libraries > > > under ${WORLDTMP}. Adding some ${DESTDIR}'s is probably a sufficient fix. > > > > Ok, but this means that we won't install doscmd with X11 support > > anymore. The user has to rebuild doscmd itself to have X11 support. In > > This is nothing new, I hope. The release build environment shouldn't be > polluted with X11, so releases should only have non-X11 doscmds. Duh... that's probably the case because a release is built in a chrooted environment. A buildworld/installworld will behave differently though. I don't know if there're people that depend on world to install a doscmd that has x11 support? > > that case, it's better to have it in the ports collection... > > I think it's too system-dependent to work well as a port. I think it's too system dependent to live in the source tree :-) From the manpage: -x Open an X11 window to display output. This enables a variety in- terrupts not available otherwise. Simply compiling with X support also isn't enough, because the default font (vga) is not present in a default X installation. Ergo: doscmd won't run in a X window unless you grab a compatible font from the net. > You would need 2 ports, one with X11 support and one without. But isn't that what our ports collection isn't all about. Examples: kde11 vs kde11-i18n nethack vs nethack-qt *emacs* Alternatively, the user can specify whether he/she wants X11 support by adding -DUSE_XLIB or -DNO_X or whatever. Not to forget that we can also use NetBSD's port! -- 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 Tue Jan 4 8:13:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id E1C941508D for ; Tue, 4 Jan 2000 08:13:26 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (128.83.154.129) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Tue, 4 Jan 2000 10:13:20 -0600 From: Richard Wackerbarth To: Marcel Moolenaar , Bruce Evans Subject: Re: Proposal: Removing doscmd from the source tree... Date: Tue, 4 Jan 2000 10:09:07 -0600 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain Cc: current@FreeBSD.ORG References: <38720CE3.DDD78778@scc.nl> In-Reply-To: <38720CE3.DDD78778@scc.nl> MIME-Version: 1.0 Message-Id: <0001041013180C.63343@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 04 Jan 2000, Marcel Moolenaar wrote: > Ok, but this means that we won't install doscmd with X11 support > anymore. The user has to rebuild doscmd itself to have X11 support. In > that case, it's better to have it in the ports collection... I agree. Further, if X is not found, the port can indicate that X11 support is optional and this package needs to be rebuilt after X is installed if that is what is desired. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 8:19:38 2000 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 53FBB15131 for ; Tue, 4 Jan 2000 08:19:22 -0800 (PST) (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 RAA15287; Tue, 4 Jan 2000 17:17:38 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA00602; Tue, 4 Jan 2000 17:03:24 +0100 (CET) (envelope-from wilko) Date: Tue, 4 Jan 2000 17:03:24 +0100 From: Wilko Bulte To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... Message-ID: <20000104170324.A571@yedi.iaf.nl> References: <3871FC69.C99882E9@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3871FC69.C99882E9@scc.nl>; from marcel@scc.nl on Tue, Jan 04, 2000 at 02:58:01PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 02:58:01PM +0100, Marcel Moolenaar wrote: > [sent to both -current and -arch] > > Hi, > > doscmd breaks cross-building, because it depends on X11 which obviously > is not in the source tree (see below). I'm proposing to remove doscmd > from the source tree and make it a port (emulators/doscmd). > > Your comments please. Excellent idea. doscmd on Alpha is a bit daft anyway.. W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 Tue Jan 4 8:40:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.35]) by hub.freebsd.org (Postfix) with ESMTP id 4AB9C153FF for ; Tue, 4 Jan 2000 08:40:38 -0800 (PST) (envelope-from news-list.freebsd.current@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with ESMTP id RAA17505 for ; Tue, 4 Jan 2000 17:40:32 +0100 Received: by mate.bln.innominate.de (Postfix, from userid 9) id 3AC7A2CA6C; Tue, 4 Jan 2000 17:33:55 +0100 (CET) From: news-list.freebsd.current@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.current Subject: Re: Initio SCSI driver Date: 4 Jan 2000 16:33:52 GMT Organization: innominate AG, Berlin, Germany Lines: 24 Message-ID: References: <199912071811.LAA23389@panzer.kdm.org> Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 947003632 18615 192.168.0.213 (4 Jan 2000 16:33:52 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/3.3-RELEASE (i386)) To: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > Thomas Graichen has been working on getting both > of Initio's drivers into FreeBSD. This may explain why Initio has fixed > the copyright on their Ultra-Wide driver. (Their Ultra2 driver never had a > copyright problem.) You may want to contact Thomas and see how things are > going. sorry for the delay yes i am working on it - i hope to find some time soon - you may find the current state at http://www.innominate.org/~tgr/projects/FreeBSD/iha so stay tuned t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 8:56: 0 2000 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 723FB14DF3 for ; Tue, 4 Jan 2000 08:55:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA23681; Tue, 4 Jan 2000 08:55:55 -0800 (PST) (envelope-from dillon) Date: Tue, 4 Jan 2000 08:55:55 -0800 (PST) From: Matthew Dillon Message-Id: <200001041655.IAA23681@apollo.backplane.com> To: Phil Regnauld Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS Race References: <20000104123804.23965@ns.int.ftf.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Just saw this passing on the console while compiling teTeX on an NFS :mounted dir: : :NFS append race @0:19 :NFS append race @0:135 :NFS append race @0:60 :NFS append race @0:102 :NFS append race @0:60 :NFS append race @0:12 :NFS append race @0:24 :NFS append race @0:66 :NFS append race @0:512 :NFS append race @0:958 : :What does that mean ? A few more popped up while I type this. This is catching a situation and printing a debug message for it. The problem existed previously but there was no debug message being printed for it before. It is probably harmless in the case of your compile. There were a bunch of situations that could cause this, including an append race for which the debug message was named after. The append race is now fixed but there are still a few situations that can cause this to occur. I will attempt to reproduce the problem by compiling up the teTeX port over a RW NFS mount. -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 Jan 4 8:58:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from gate.keisu.t.u-tokyo.ac.jp (ns06.t.u-tokyo.ac.jp [133.11.68.1]) by hub.freebsd.org (Postfix) with ESMTP id A1A5814E5C for ; Tue, 4 Jan 2000 08:58:44 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from sylph.sat.t.u-tokyo.ac.jp (sylph.sat.t.u-tokyo.ac.jp [10.6.1.20]) by gate.keisu.t.u-tokyo.ac.jp (Postfix) with ESMTP id 020213D2A; Wed, 5 Jan 2000 01:58:43 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by sylph.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id 840F52DAA9; Wed, 5 Jan 2000 01:58:42 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp by ett.sat.t.u-tokyo.ac.jp (8.9.3/sat-V0.6) id BAA43317; Wed, 5 Jan 2000 01:58:41 +0900 (JST) Date: Wed, 05 Jan 2000 01:58:40 +0900 Message-ID: From: Hidetoshi Shimokawa To: daeron@Wit401305.student.utwente.nl Cc: dfr@nlsystems.com, freebsd-current@FreeBSD.ORG, sanpei@jp.freebsd.org Subject: Re: NewPCM causes kernel panics ! In-Reply-To: In your message of "Tue, 4 Jan 2000 11:43:36 +0100" <20000104114336.B89670@shadowmere.student.utwente.nl> References: <20000104014046.A769@shadowmere.student.utwente.nl> <20000104114336.B89670@shadowmere.student.utwente.nl> User-Agent: Wanderlust/2.2.9 (Gonna Make You Sweat) SEMI/1.13.6 (Komatsu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX wrote: > > On Tue, Jan 04, 2000 at 09:27:54AM +0000, Doug Rabson wrote: > > On Tue, 4 Jan 2000, Pascal Hofstee wrote: > > > > > Hi, With CURRENT sources updated earlier today ... my system now > > > crash-and-burns when trying to play audio. > > > > > > i have foudn these messages in /var/log/messages: > > > > > > Jan 4 01:30:26 shadowmere /kernel: gusc0: at port > > > 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 > > > Jan 4 01:30:26 shadowmere /kernel: pcm0: on gusc0 > > > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > > > = 0xdf00 > > > Jan 4 01:30:26 shadowmere /kernel: bus_dmamap_load: Too many segs! buf_len > > > = 0xdf00 > > > > > > If any more info is needed let me know. > > > > This looks like a buffer which spans >1 non-contiguous physical ranges. > > Was the buffer allocated with contigmalloc? > > I don't know this is what came directly from the NewPCM-probe/attach code. > > -- > -------------------- > Pascal Hofstee - daeron@shadowmere.student.utwente.nl > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- > t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ > ------END GEEK CODE BLOCK------ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > I think backing out rev 1.42 of /sys/dev/sound/isa/mss.c or reducing MSS_BUFSIZE will fix the problem. DMA buffer size seems too large. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 9: 2:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id 899CD14FF9 for ; Tue, 4 Jan 2000 09:02:49 -0800 (PST) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id 3F9783D1D; Tue, 4 Jan 2000 12:02:48 -0500 (EST) Date: Tue, 4 Jan 2000 12:02:48 -0500 From: Josh Tiefenbach To: Matthew Dillon Cc: Phil Regnauld , freebsd-current@FreeBSD.ORG Subject: Re: NFS Race Message-ID: <20000104120247.A49618@snickers.org> References: <20000104123804.23965@ns.int.ftf.net> <200001041655.IAA23681@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001041655.IAA23681@apollo.backplane.com> Organization: Hah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :NFS append race @0:19 [snip] > There were a bunch of situations that could cause this, including an > append race for which the debug message was named after. The append > race is now fixed but there are still a few situations that can cause > this to occur. Just another data point. I saw this reasonably frequently when compiling world using an NFS mounted /usr/src and /usr/obj. Both server/client were -current circa Christmas. josh -- I am not a shrimp. I am a king prawn! -- Pepe the Prawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 9:29:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id BDDDB15315 for ; Tue, 4 Jan 2000 09:29:46 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup4-32.iptelecom.net.ua [212.9.226.224]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id TAA01621 for ; Tue, 4 Jan 2000 19:32:53 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id TAA69301 for ; Tue, 4 Jan 2000 19:28:41 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38722DC7.6A22FE27@altavista.net> Date: Tue, 04 Jan 2000 19:28:39 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: X-server related panic Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On post new year's -current I've observed strange panics: when I'm starting my XFree server (CT55554 SVGA) it paniced with "panic: isa_dmastart: bad bounce buffer" message. Regards, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 9:35:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102]) by hub.freebsd.org (Postfix) with ESMTP id 747D8151E4 for ; Tue, 4 Jan 2000 09:35:50 -0800 (PST) (envelope-from michael.waite@compaq.com) Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345) id C4CD22F1; Tue, 4 Jan 2000 12:35:49 -0500 (EST) Received: from exctay-gh02.tay.cpqcorp.net (exctay-gh02.tay.cpqcorp.net [16.103.129.52]) by zmamail02.zma.compaq.com (Postfix) with ESMTP id BD2E0332 for ; Tue, 4 Jan 2000 12:35:49 -0500 (EST) Received: by exctay-gh02.tay.cpqcorp.net with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jan 2000 12:35:49 -0500 Message-ID: <212CC57E84B8D111AD780000F84AA04906963D66@mroexc2.tay.dec.com> From: "Waite, Michael" To: "'freebsd-current@FreeBSD.ORG'" Subject: 4.0-20000101-CURRENT on Alpha Date: Tue, 4 Jan 2000 12:35:47 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just finished putting the latest Alpha 4.0 CURRENT up on the Internet for developers to use. The system that I have it running on is a brand new EV6.7 XP1000 running at 667MHZ with two gigs of ram. You can get your free shell account at http://www.testdrive.compaq.com This is not intended as an additional mail client. We have disabled most out-going connections for obvious reasons but you can ftp and telnet onto the system. I also have a DPW500au running an earier version of 4.0 CURRENT -----Mike Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 9:51:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id A279515258 for ; Tue, 4 Jan 2000 09:51:42 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id SAA07700 for ; Tue, 4 Jan 2000 18:51:40 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C376E.dip.t-dialin.net [62.156.55.110]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id SAA07696 for ; Tue, 4 Jan 2000 18:51:39 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (doom [172.23.7.254]) by server.rock.net (8.9.3+Sun/8.9.3) with ESMTP id SAA15951 for ; Tue, 4 Jan 2000 18:51:40 +0100 (MET) Message-ID: <387233BE.9733079A@dead-end.net> Date: Tue, 04 Jan 2000 18:54:06 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: NFS Race References: <20000104123804.23965@ns.int.ftf.net> <200001041655.IAA23681@apollo.backplane.com> <20000104120247.A49618@snickers.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josh Tiefenbach schrieb: > > > :NFS append race @0:19 > > [snip] > > > There were a bunch of situations that could cause this, including an > > append race for which the debug message was named after. The append > > race is now fixed but there are still a few situations that can cause > > this to occur. > > Just another data point. I saw this reasonably frequently when compiling world > using an NFS mounted /usr/src and /usr/obj. > > Both server/client were -current circa Christmas. Me too ;) I got almost 300 of these messages during a "make release" with the chroot dir NFS mounted. Otherwise I had no problems with such over NFS created files though. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 10:38:48 2000 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 89A4314F35 for ; Tue, 4 Jan 2000 10:38:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA37128; Tue, 4 Jan 2000 10:38:45 -0800 (PST) (envelope-from dillon) Date: Tue, 4 Jan 2000 10:38:45 -0800 (PST) From: Matthew Dillon Message-Id: <200001041838.KAA37128@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Re: NFS Race References: <20000104123804.23965@ns.int.ftf.net> <200001041655.IAA23681@apollo.backplane.com> <20000104120247.A49618@snickers.org> <387233BE.9733079A@dead-end.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Me too ;) : :I got almost 300 of these messages during a "make release" with the :chroot dir NFS mounted. Otherwise I had no problems with such over :NFS created files though. : :Daniel I think I've tracked it down. When the client close()'s an NFS filehandle it calls nfs_flush() without specifying that a commit should be done, then clears the NMODIFIED bit in np->n_flags. It is not legal to clear NMODIFIED if no commit is done. Clearing NMODIFIED prematurely causes NFS to believe that there are no dirty buffers to destroy when a new file is created with O_TRUNC or ftruncate(). This will not lead to any problems if all you are doing is appending, it will lead to problems if you seek/write around after truncating the file. I think the correct solution is simply to not clear NMODIFIED on the last close. Please try this patch to -current -Matt Matthew Dillon Index: nfs_vnops.c =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.149 diff -u -r1.149 nfs_vnops.c --- nfs_vnops.c 1999/12/15 23:02:19 1.149 +++ nfs_vnops.c 2000/01/04 18:26:50 @@ -561,10 +561,15 @@ if ((VFSTONFS(vp->v_mount)->nm_flag & NFSMNT_NQNFS) == 0 && (np->n_flag & NMODIFIED)) { if (NFS_ISV3(vp)) { + /* + * Note: Since we haven't committed the buffers we cannot + * clear the NMODIFIED np->n_flag + */ error = nfs_flush(vp, ap->a_cred, MNT_WAIT, ap->a_p, 0); - np->n_flag &= ~NMODIFIED; - } else + /* np->n_flag &= ~NMODIFIED; */ + } else { error = nfs_vinvalbuf(vp, V_SAVE, ap->a_cred, ap->a_p, 1); + } np->n_attrstamp = 0; } if (np->n_flag & NWRITEERR) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 11:10:40 2000 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 148FB14D6A for ; Tue, 4 Jan 2000 11:10:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA02671; Tue, 4 Jan 2000 12:10:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA61032; Tue, 4 Jan 2000 12:10:35 -0700 (MST) Message-Id: <200001041910.MAA61032@harmony.village.org> To: Marcel Moolenaar Subject: Re: Proposal: Removing doscmd from the source tree... Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 14:58:01 +0100." <3871FC69.C99882E9@scc.nl> References: <3871FC69.C99882E9@scc.nl> Date: Tue, 04 Jan 2000 12:10:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3871FC69.C99882E9@scc.nl> Marcel Moolenaar writes: : doscmd breaks cross-building, because it depends on X11 which obviously : is not in the source tree (see below). I'm proposing to remove doscmd : from the source tree and make it a port (emulators/doscmd). One can build it w/o X11. Doesn't sound like sufficent reason to me to remove it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 11:14:25 2000 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 C046014C59 for ; Tue, 4 Jan 2000 11:14:08 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA02688; Tue, 4 Jan 2000 12:14:04 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA61066; Tue, 4 Jan 2000 12:14:02 -0700 (MST) Message-Id: <200001041914.MAA61066@harmony.village.org> To: Marcel Moolenaar Subject: Re: Proposal: Removing doscmd from the source tree... Cc: Bruce Evans , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 17:08:11 +0100." <38721AEB.68D35958@scc.nl> References: <38721AEB.68D35958@scc.nl> Date: Tue, 04 Jan 2000 12:14:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38721AEB.68D35958@scc.nl> Marcel Moolenaar writes: : I think it's too system dependent to live in the source tree :-) I don't. It is highly dependent on kernel elements. : From the manpage: : -x Open an X11 window to display output. This enables a variety in- : terrupts not available otherwise. : : Simply compiling with X support also isn't enough, because the default : font (vga) is not present in a default X installation. Ergo: doscmd : won't run in a X window unless you grab a compatible font from the net. Don't need to run with the default font. I've done that *MANY* times. Still works, but you don't get the ibm character set encoding, which isn't that big a deal. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 11:27:56 2000 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 931CB14CCA; Tue, 4 Jan 2000 11:27:50 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA00721; Tue, 4 Jan 2000 11:27:32 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001041927.LAA00721@gndrsh.dnsmgr.net> Subject: Re: new man pages In-Reply-To: from Marc Schneiders at "Jan 4, 2000 02:01:17 pm" To: marc@oldserver.demon.nl (Marc Schneiders) Date: Tue, 4 Jan 2000 11:27:32 -0800 (PST) Cc: current@FreeBSD.ORG, phk@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 > Where do I look for new man pages? I would like to read those for the > new ata driver and for ntpd. They were not created during a build > world some 5 days ago. And I cannot find them in > /usr/src/share/man/man4, where I would expect man ata/ad in any case. Sos already answered about ata/ad, I'll add some info for ntpd. xntpd was recently renamed ntpd, but the documentation and manual pages was not. You'll find the manual page for ntpd with a ``man xntpd''. And a side note for PHK. Could you change the rm -f /usr/sbin/xntpd to instead replace /usr/sbin/xntpd with a LINK to ntpd for maximal compatibility. You should probably also do an MLINK for ntpd->xntpd man pages. -- Rod Grimes - KD7CAX @ CN85sl - (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 Tue Jan 4 11:54: 3 2000 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 AAED314FAE for ; Tue, 4 Jan 2000 11:53:55 -0800 (PST) (envelope-from brdean@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 OAA17698 for ; Tue, 4 Jan 2000 14:53:53 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA28862; Tue, 4 Jan 2000 14:53:23 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id OAA57356; Tue, 4 Jan 2000 14:53:23 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200001041953.OAA57356@dean.pc.sas.com> Subject: Re: tip features (cdelay and ldelay)? In-Reply-To: from Bruce Evans at "Jan 5, 2000 02:54:50 am" To: freebsd-current@freebsd.org Date: Tue, 4 Jan 2000 14:53:23 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > Date: Wed, 5 Jan 2000 02:54:50 +1100 (EST) > > consider applying the included patch to re-enable them? > > > +static int > > +nap ( int microsec ) > > +{ > > + int rc; > > + > > + rc = usleep ( microsec ); > > + if (rc != 0) { > > + fprintf ( stderr, > > + "warning: ldelay or cdelay interrupted, " > > + "delay time cut short: %s\n", > > + strerror(errno) ); > > + } > > + > > + return 0; > > +} > > usleep() has a resolution of 2/HZ seconds (normally 20msec), so the above > gives very slow output (50-100 cps). Using a low baud rate (500-1000 bps) > give the same result. If you want a shorter delay/faster output, then > there is nothing better than a busy-wait loop for implementing nap(). > Using a not so low baud rate (1200+ bps) may work better. Perhaps nap() > was dropped because it can't be implemented reasonably. This explains why setting cdelay below a certain value seemed to have no additional affect in my tests. I was suspicious of the microsecond resolution, though I had not verified it by code examination. I did implement nap() with nanosleep() and saw no difference in resolution so it must be based on the same underlying facilities as usleep(). For my microcontroller (9600 baud), setting cdelay=0 and ldelay=70ms while using 80 character per line S-Record files does the trick. Any lower and it overflows my device and I don't get reliable data transfer. However, I must use 'cdelay' for my EEPROM burner (fixed at 1200 baud) set set ldelay=0; I can only surmize that it does not buffer much if at all while writing the data to the chip (50 ms burn time per byte for the EEPROM chip I worked with last). Thus, for my slow EEPROM burner, enforcing a 50ms delay per character vs no other flow control means the difference between being able to use FreeBSD and tip for burning my EEPROMs (which is very convenient) or having to come up with some other alternative. Perhaps re-enabling 'cdelay' and 'ldelay' but changing 'nap()' to accept its argument in milliseconds so that it does not misrepresent itself to badly would be more reasonable? For me this change makes the difference between working acceptably well and not working at all. Would you consider committing a patch to that effect? It would save me from having to maintain local mods to my source tree, and it would probably be useful to others as well. If not, please let me know what changes you would consider taking and I'll do my best to get you patches. Here a modified patch which: 1) closes PR bin/15847 2) enables 'cdelay' and 'ldelay' 3) makes 'nap()' take milliseconds instead of microseconds so that it does not misrepresent it's resolution too badly Thanks, -Brian -- Brian Dean brdean@unx.sas.com Index: cmds.c =================================================================== RCS file: /usr00/mirror/ncvs/src/usr.bin/tip/tip/cmds.c,v retrieving revision 1.10 diff -r1.10 cmds.c 516c516 < for (pc = eofchars; *pc; pc++) --- > for (pc = eofchars; pc && *pc; pc++) 562a563,579 > static int > nap(msec) > int msec; /* msec is milliseconds */ > { > int rc; > > rc = usleep ( msec*1000 ); > if (rc != 0) { > fprintf ( stderr, > "warning: ldelay or cdelay interrupted, " > "delay time cut short: %s\n", > strerror(errno) ); > } > > return 0; > } > 576d592 < #ifdef notdef 579d594 < #endif 581d595 < #ifdef notdef 584d597 < #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 13:23:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 9718F14DD0 for ; Tue, 4 Jan 2000 13:23:40 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id D547B1E2F; Tue, 4 Jan 2000 22:23:37 +0100 (CET) Date: Tue, 4 Jan 2000 22:23:37 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: compiling libF77/libI77 Message-ID: <20000104222337.A1426@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can anyone tell me how to compile and install libF77/libI77 from /usr/src/contrib/libf2c please? Or, for that matter, the whole libf2c? I need the libraries and the ones from netlib won't compile. Is there some way to include building the libraries in a standard make buildworld? Thanks a lot, Dave Boers -- True Music was born with Johann Sebastian Bach. It died with Anton Bruckner while he was working on his nineth symphony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 13:28:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id E0A3214DF2 for ; Tue, 4 Jan 2000 13:28:31 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 349AC1E2F; Tue, 4 Jan 2000 22:28:28 +0100 (CET) Date: Tue, 4 Jan 2000 22:28:28 +0100 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: Re: compiling libF77/libI77 Message-ID: <20000104222828.B1426@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000104222337.A1426@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000104222337.A1426@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Tue, Jan 04, 2000 at 10:23:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 10:23:37PM +0100, Dave J. Boers wrote: > Can anyone tell me how to compile and install libF77/libI77 from > /usr/src/contrib/libf2c please? Or, for that matter, the whole libf2c? (reply to self...) It's funny how I tend to find things out only just _after_ I asked someone else (not that I didn't spend an hour going through /usr/src _before_ I sent in my email). Just found out that they are combined into /usr/lib/libf2c.a. So, never mind my question. Regards, Dave Boers. -- True Music was born with Johann Sebastian Bach. It died with Anton Bruckner while he was working on his nineth symphony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 13:30:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 14AAD14D60 for ; Tue, 4 Jan 2000 13:30:40 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id NAA73402; Tue, 4 Jan 2000 13:31:28 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001042131.NAA73402@troutmask.apl.washington.edu> Subject: Re: compiling libF77/libI77 In-Reply-To: <20000104222337.A1426@relativity.student.utwente.nl> from "Dave J. Boers" at "Jan 4, 2000 10:23:37 pm" To: djb@Wit389306.student.utwente.nl Date: Tue, 4 Jan 2000 13:31:28 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave J. Boers wrote: > Hi, > > Can anyone tell me how to compile and install libF77/libI77 from > /usr/src/contrib/libf2c please? Or, for that matter, the whole libf2c? > > I need the libraries and the ones from netlib won't compile. Is there some > way to include building the libraries in a standard make buildworld? > Dave, Freebsd-current comes with g77 has the Fortran compiler. Its runtime library is libg2c.a. Libg2c contains libF77/libI77 as well as libU77. If you still want to compile libF77/libI77, you can install the f2c port (ports/lang/f2c). -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 13:34: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.tyler.net (mail.tyler.net [205.218.118.185]) by hub.freebsd.org (Postfix) with ESMTP id F421214E54 for ; Tue, 4 Jan 2000 13:33:57 -0800 (PST) (envelope-from smccloud@tcainternet.com) Received: from q4h7k8 ([208.180.62.127]) by mail.tyler.net (Post.Office MTA Undefined release Undefined ID# 0-54929U30000L30000S0V35) with SMTP id net for ; Tue, 4 Jan 2000 15:32:56 -0600 Message-ID: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> From: "----" To: Subject: Opera Beta and FreeBSD Date: Tue, 4 Jan 2000 15:29:34 -0600 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.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone gotten Opera beta working under linux emulation? Thanks, Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:12:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 3461D14A08 for ; Tue, 4 Jan 2000 14:12:09 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id BA1CCDE; Tue, 4 Jan 2000 14:12:08 -0800 (PST) Date: Tue, 4 Jan 2000 14:12:08 -0800 From: Chris Piazza To: ---- Cc: freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD Message-ID: <20000104141208.B379@norn.ca.eu.org> References: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net>; from smccloud@tcainternet.com on Tue, Jan 04, 2000 at 03:29:34PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 03:29:34PM -0600, ---- wrote: > Has anyone gotten Opera beta working under linux emulation? Yes. I must warn you it's still really buggy if you intend to use it a lot. Basically all I did was grab the opera tarball, extract it and run the 'runnow' script. Screenshot here: http://www.freebsd.org/~cpiazza/sshot-opera.png The screenshot weighs in at about 130K. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:15:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from iscserv7.nepustil.net (ISCSERV7.Nepustil.NET [193.96.243.22]) by hub.freebsd.org (Postfix) with ESMTP id 0CA4114FA9 for ; Tue, 4 Jan 2000 14:15:25 -0800 (PST) (envelope-from thz@tuebingen.netsurf.de) Received: from peotl.tuebingen.netsurf.de (host-355.tuebingen.netsurf.de [195.180.140.155]) by iscserv7.nepustil.net (8.9.3/8.8.5) with ESMTP id XAA16760 for ; Tue, 4 Jan 2000 23:15:16 +0100 (CET) Received: (from thz@localhost) by peotl.tuebingen.netsurf.de (8.9.3/8.9.3) id WAA01364 for current@FreeBSD.ORG; Tue, 4 Jan 2000 22:57:41 +0100 (MET) (envelope-from thz) Date: Tue, 4 Jan 2000 22:57:41 +0100 From: Thomas Zenker To: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... Message-ID: <20000104225739.A865@peotl.tuebingen.netsurf.de> References: <3871FC69.C99882E9@scc.nl> <200001041910.MAA61032@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200001041910.MAA61032@harmony.village.org>; from Warner Losh on Tue, Jan 04, 2000 at 12:10:35PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 12:10:35PM -0700, Warner Losh wrote: > In message <3871FC69.C99882E9@scc.nl> Marcel Moolenaar writes: > : doscmd breaks cross-building, because it depends on X11 which obviously > : is not in the source tree (see below). I'm proposing to remove doscmd > : from the source tree and make it a port (emulators/doscmd). > > One can build it w/o X11. Doesn't sound like sufficent reason to me > to remove it. > Actually i never used it under X11, but it is very important for us to have it to run cross-compilers (which are only available as DOS binaries) integrated with native development environment under FreeBSD. I am not sure how many people use it this way. But if it is not build in buildworld, it will break after kernel updates and I will have strong wind blowing in my face defending our FreeBSD development environment at work. A possibility could be: 1. build it for i386 only, 2. build it via buildworld without X11, regardless if X11 exists. If I want to use it with X11, it is interactive and I can make it for X11 by hand - it will not break on compile runs at some hour at night. So, my vote against removing. Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:21:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 8AD9614A08 for ; Tue, 4 Jan 2000 14:21:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA03645; Tue, 4 Jan 2000 14:26:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001042226.OAA03645@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas Zenker Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... In-reply-to: Your message of "Tue, 04 Jan 2000 22:57:41 +0100." <20000104225739.A865@peotl.tuebingen.netsurf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 14:26:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually i never used it under X11, but it is very important for > us to have it to run cross-compilers (which are only available as > DOS binaries) integrated with native development environment under > FreeBSD. > > I am not sure how many people use it this way. But if it is not > build in buildworld, it will break after kernel updates and I will > have strong wind blowing in my face defending our FreeBSD development > environment at work. It's actually quite unlikely that this would be the case; apart from the 4.x signal changes I don't recall a single other event that would have broken doscmd's binary compatibility. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:23:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 2DAD714F9E for ; Tue, 4 Jan 2000 14:23:29 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.3) with SMTP id BAA15890 for ; Wed, 5 Jan 2000 01:23:26 +0300 (MSK) Date: Wed, 5 Jan 2000 01:23:26 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: current@freebsd.org Subject: options COMPAT_LINUX makes kernel fail to compile 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! With option COMPAT_LINUX (which present in LINT) make depend fails with: cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c ../../i386/linux/linux_genassym.c genassym -o linux_assym.h linux_genassym.o genassym:No such file or directory *** Error code 1 Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:39: 3 2000 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 1E86014C59 for ; Tue, 4 Jan 2000 14:38:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA38829; Tue, 4 Jan 2000 14:38:45 -0800 (PST) (envelope-from dillon) Date: Tue, 4 Jan 2000 14:38:45 -0800 (PST) From: Matthew Dillon Message-Id: <200001042238.OAA38829@apollo.backplane.com> To: Dmitry Valdov Cc: current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi! : :With option COMPAT_LINUX (which present in LINT) make depend fails with: :cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes :-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual :-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include :-D_KERNEL -include opt_global.h -elf -fno-builtin :-mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c :../../i386/linux/linux_genassym.c :genassym -o linux_assym.h linux_genassym.o :genassym:No such file or directory :*** Error code 1 : :Dmitry. genassym is now in /usr/src/usr.bin/genassym, compile and install that then try your make again. The one in the local compile directory is still being used for other things (and not compatible with the one in /usr/src/usr.bin/ ) -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 Jan 4 14:46:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 2713214CCE for ; Tue, 4 Jan 2000 14:46:38 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 125cip-000Mi3-00; Tue, 4 Jan 2000 22:46:35 +0000 Date: Tue, 4 Jan 2000 23:46:34 +0100 (CET) From: Marc Schneiders To: David Scheidt Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: new man pages 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 Tue, 4 Jan 2000, David Scheidt wrote: > On Tue, 4 Jan 2000, Soren Schmidt wrote: > > > It seems Marc Schneiders wrote: > > > Where do I look for new man pages? I would like to read those for the > > > new ata driver and for ntpd. They were not created during a build > > > world some 5 days ago. And I cannot find them in > > > /usr/src/share/man/man4, where I would expect man ata/ad in any case. > > > > There are no man pages for the ata driver (yet), for nptd I dunno... > > The new ntpd doesn't have any man pages. There are some html docs that come > with the base distribution. I don't know if they are in the FreeBSD > distribution, or where. Try looking in /usr/share. > Thanks for putting me on track. They are in /usr/src/contrib/ntp/html. According to /usr/src/contrib/ntp/FREEBSD-upgrade they should be installed as docs in /usr/share/doc/ntp. I haven't got them there. It is where the, now probably obsolete, port would have put them. I can't find in the src where they are supposed to be installed, but I haven't tried to read all the files in all the subdirs of both usr.sbin/ntp and contrib/ntp :-) > > David > -- Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 8:16pm up 4 days, 22:05, load average: 3.56 3.24 2.81 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:47: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id E88051522F for ; Tue, 4 Jan 2000 14:46:47 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.3) with SMTP id BAA21845; Wed, 5 Jan 2000 01:46:33 +0300 (MSK) Date: Wed, 5 Jan 2000 01:46:32 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: <200001042238.OAA38829@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 Should it be described in /usr/src/UPDATING ? On Tue, 4 Jan 2000, Matthew Dillon wrote: > Date: Tue, 4 Jan 2000 14:38:45 -0800 (PST) > From: Matthew Dillon > To: Dmitry Valdov > Cc: current@FreeBSD.ORG > Subject: Re: options COMPAT_LINUX makes kernel fail to compile > > > :Hi! > : > :With option COMPAT_LINUX (which present in LINT) make depend fails with: > :cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > :-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > :-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > :-D_KERNEL -include opt_global.h -elf -fno-builtin > :-mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c > :../../i386/linux/linux_genassym.c > :genassym -o linux_assym.h linux_genassym.o > :genassym:No such file or directory > :*** Error code 1 > : > :Dmitry. > > genassym is now in /usr/src/usr.bin/genassym, compile and install that > then try your make again. The one in the local compile directory is > still being used for other things (and not compatible with the one > in /usr/src/usr.bin/ ) > > -Matt > Matthew Dillon > > > > 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 Jan 4 14:56:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id B45E514E7E for ; Tue, 4 Jan 2000 14:56:40 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id XAA46075 for ; Tue, 4 Jan 2000 23:56:39 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E88.dip.t-dialin.net [62.158.14.136]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id XAA46071 for ; Tue, 4 Jan 2000 23:56:38 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (server [172.23.7.1]) by server.rock.net (8.9.3+Sun/8.9.3) with ESMTP id XAA02882 for ; Tue, 4 Jan 2000 23:56:36 +0100 (MET) Message-ID: <38727AA4.EFDEDEB4@dead-end.net> Date: Tue, 04 Jan 2000 23:56:36 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: FreeBSD CURRENT Mailing List Subject: Re: panic: isa_dmastart: bad bounce buffer References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > > Starting mpg123 with a random mpg3 file produces the following panic > within half a second. The kernel is current as of this morning. THe > panic is reproducable (as in, I cannot play the mpg3 file). > > kernel plus core available if needed. > > Dec 15 14:55:25 henny /kernel: ESS1879: adding io range 0x220-0x22f, > size=0x10, align=0 > Dec 15 14:55:25 henny /kernel: ESS1879: adding io range 0x388-0x38b, > size=0x4, align=0 > Dec 15 14:55:25 henny /kernel: ESS1879: adding irq mask 0x20 > Dec 15 14:55:25 henny /kernel: ESS1879: adding dma mask 0x2 > Dec 15 14:55:25 henny /kernel: ESS1879: adding dma mask 0x20 > Dec 15 14:55:25 henny /kernel: ESS1879: start dependant > Dec 15 14:55:25 henny /kernel: pnpbios: handle 1 device ID ESS1879 > (79187316) > Dec 19 17:10:48 henny /kernel: sbc0: at port > 0x220-0x22f,0x388-0x38b irq 5 drq 1,5 on isa0 > Dec 19 17:10:48 henny /kernel: pcm0: on sbc0 Same here. If I change the call to esschan_init() back to sbchan_init() [in /sys/dev/sound/isa/sb.c], these messages and the panic disappear again. (Alternatively I can turn down ESS_BUFFSIZE to 8192, larger values [tried (16384 and 32768) -256] also don't work] Sound still doesn't work yet. Just noise - probably played at a fraction of the normal speed (<5%). sbc: at port 0x220-0x22f, 0x388-0x38b, 0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 14:56:49 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 465CE15083; Tue, 4 Jan 2000 14:56:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EB3561CD40A; Tue, 4 Jan 2000 14:56:45 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 4 Jan 2000 14:56:45 -0800 (PST) From: Kris Kennaway To: Matthew Dillon Cc: Dmitry Valdov , current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: <200001042238.OAA38829@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 Tue, 4 Jan 2000, Matthew Dillon wrote: > genassym is now in /usr/src/usr.bin/genassym, compile and install that > then try your make again. The one in the local compile directory is > still being used for other things (and not compatible with the one > in /usr/src/usr.bin/ ) We seem to have re-reverted to "make world before make kernel" :-/ Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 15: 9: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C17F414E7E; Tue, 4 Jan 2000 15:08:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AF70B1CD41E for ; Tue, 4 Jan 2000 15:08:56 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 4 Jan 2000 15:08:56 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: ATA lost contact 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 One of my Western Digital Caviars doesn't work under the new ATA driver: upon trying to access the disk (via swapon or mount during boot) it gives the famous "lost contact with disk" message and falls back to PIO mode. Interestingly, my two older WDCs work fine - although I notice that ad1 and ad2 are only detected as WDMA2, when it seems (from the udma=2) that they can handle UDMA - is this a cabling issue or something (I'm not familiar with IDE cabling requirements)? Kris Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Tue Jan 4 01:44:37 PST 2000 kkenn@morden.rebel.net.au:/usr5/src2/src/sys/compile/MORDEN Calibrating clock(s) ... TSC clock: 120042068 Hz, i8254 clock: 1193601 Hz Timecounter "i8254" frequency 1193601 Hz Timecounter "TSC" frequency 120042068 Hz CPU: Pentium/P54C (120.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00325000 - 0x02feffff, 46968832 bytes (11467 pages) avail memory = 45641728 (44572K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fac90 bios32: Entry = 0xfb150 (c00fb150) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb180 pnpbios: Found PnP BIOS data at 0xc00fb9f0 pnpbios: Entry = f0000:ba18 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 02 01 48 56 00 c0 00 00 00 00 8f 56 00 c0 20 00 de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de VESA: 29 mode(s) found VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c568f (c000568f) VESA: Tseng Labs ET4000 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 155884645 bytes/sec bzero() bandwidth = 78076202 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) pcib0: on motherboard found-> vendor=0x8086, dev=0x122d, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x122e, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x1230, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00003000, size 4 found-> vendor=0x100c, dev=0x3206, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f0000000, size 24 found-> vendor=0x9004, dev=0x5078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00006000, size 8 map[14]: type 1, range 32, base f1000000, size 12 pci0: on pcib0 CPU Inactivity timer: clocks Peer Concurrency: enabled CPU-to-PCI Write Bursting: enabled PCI Streaming: enabled Bus Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 60 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: IRQ10, C: IRQ11, D: disabled MB0: disabled, MB1: disabled isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x3000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=52 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x3008 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x9 ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: irq 11 at device 18.0 on pci0 ahc0: irq 10 at device 19.0 on pci0 ahc0: No SEEPROM available. ahc0: Using left over BIOS settings ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs ahc0: Downloading Sequencer Program... 407 instructions downloaded Trying Read_Port at 203 Trying Read_Port at 243 CTL0031: start dependant CTL0031: adding irq mask 0x20 CTL0031: adding dma mask 0x2 CTL0031: adding dma mask 0x20 CTL0031: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0031: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0xca0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: end dependant CTL2011: start dependant CTL2011: adding irq mask 0x400 CTL2011: adding io range 0x168-0x16f, size=0x8, align=0x1 CTL2011: adding io range 0x36e-0x36f, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x800 CTL2011: adding io range 0x1e8-0x1ef, size=0x8, align=0x1 CTL2011: adding io range 0x3ee-0x3ef, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x9c00 CTL2011: adding io range 0x100-0x1ff, size=0x8, align=0x8 CTL2011: adding io range 0x300-0x3ff, size=0x2, align=0x2 CTL2011: start dependant CTL2011: adding irq mask 0x8000 CTL2011: adding io range 0x170-0x177, size=0x8, align=0x1 CTL2011: adding io range 0x376-0x376, size=0x1, align=0x1 CTL2011: end dependant PNPffff: adding io range 0x100-0x3f8, size=0x1, align=0x8 CTL7001: adding io range 0x200-0x207, size=0x8, align=0x1 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <12 virtual consoles, flags=0x200> sc0: fb0 kbd0 isa_probe_children: probing PnP devices sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 pcm: setmap c000, 2000; 0xc4e9a000 -> c000 pcm: setmap e000, 2000; 0xc4e9c000 -> e000 ata2: iobase=0x01e8 altiobase=0x03ee bmaddr=0x0000 ata2: mask=00 status0=ff status1=ff unknown0: at port 0x1e8-0x1ef,0x3ee-0x3ef irq 11 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 BIOS Geometries: 0:03113f3f 0..785=786 cylinders, 0..63=64 heads, 1..63=63 sectors 1:026a7f3f 0..618=619 cylinders, 0..127=128 heads, 1..63=63 sectors 2:030efe3f 0..782=783 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging bpf: ppp0 attached bpf: ppp1 attached new masks: bio 4008c040, tty 4003003a, net 4007003a bpf: lo0 attached Linux-ELF exec handler installed ata0-master: success setting up WDMA2 mode on PIIX chip ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ATA-0 disk at ata0 as master ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad0 Creating DISK wd0 ata0-slave: success setting up WDMA2 mode on PIIX chip ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 ad1: ATA-3 disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad1 Creating DISK wd1 ata1-master: success setting up WDMA2 mode on PIIX chip ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad2 Creating DISK wd2 ata1-slave: piomode=3 dmamode=0 udmamode=-1 dmaflag=1 acd0: CDROM drive at ata1 as slave acd0: read 171KB/s (689KB/s), 256KB buffer, ??? acd0: Reads: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked, lock protected Waiting 2 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. Mounting root from ufs:wd0s2a wd0s1: type 0x6, start 63, end = 1745855, size 1745793 : OK wd0s2: type 0xa5, start 1745856, end = 3173183, size 1427328 : OK start_init: trying /sbin/init wd1s1: type 0x6, start 63, end = 2048255, size 2048193 : OK wd1s2: type 0x5, start 2048256, end = 3072383, size 1024128 : OK wd1s3: type 0xa5, start 3072384, end = 4999679, size 1927296 : OK wd1s5: type 0x6, start 2048319, end = 3072383, size 1024065 : OK ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting up PIO3 mode on generic chip done ad2: ad_timeout: lost disk contact - resetting ata1-master: success setting up PIO4 mode on generic chip ad2: ad_timeout: trying fallback to PIO mode ata1: resetting devices .. ata1: mask=03 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip ata1-slave: timeout waiting for command=ef s=00 e=00 ata1-slave: failed setting up PIO3 mode on generic chip done wd2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK wd2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK wd2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK wd2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK wd2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK wd2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK wd2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK wd2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK wd2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK wd2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK wd2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK wd2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK wd2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK wd2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK wd2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 15:36:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust240.tnt3.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BE2814E0A; Tue, 4 Jan 2000 15:36:48 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 4 Jan 2000 18:36:44 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.org Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001040813.JAA84062@freebsd.dk> Message-ID: 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 On Tue, 4 Jan 2000, Soren Schmidt wrote: > The problem here is that you will then do a lot of unneeded padding > as the driver will attempt to pad to the blocksize used which is not > wanted. You HAVE to use the right blocksize especially for audio, or > you will get "silent" ie zero padded blocks on disk, and thats not > what you want is it ? I used a multiple of the blocksize, and it works fine, except for on the very last bit of data. The very last bit of data is what causes an underrun, and the code that's there for overrun/underrun is wrong right now. For underrun, it ends up writing the underlying blocksize length from the user buffer of _less_than_that_size_, then it writes (blocksize - user buffer size) _more_ zeroed data! This promptly locks up the IDE bus with my CD-R. That's what the patch was about and you didn't say anything about; yes, I know that blocksizes should be matched perfectly and padded perfectly to prevent the ATA driver from having to handle the underrun/overrun cases, but the current handling is/was still broken. > > -Søren > -- 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 Jan 4 16:11:33 2000 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 E991814C20 for ; Tue, 4 Jan 2000 16:11:29 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 6C72E1C4A; Tue, 4 Jan 2000 19:12:28 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 5DE7C3819; Tue, 4 Jan 2000 19:12:28 -0500 (EST) Date: Tue, 4 Jan 2000 19:12:28 -0500 (EST) From: Bill Fumerola To: Alex Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) In-Reply-To: <3871CBBE.496E36F1@freenet.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 On Tue, 4 Jan 2000, Alex wrote: > ....and I apologise for wrongfully accusing it. The panic is in fact > caused by newpcm (Cameron CC'd). DDB trace can be provided upon request > (is there a way to save it into a file instead of having to write it > down on a piece of paper?) Serial consoles are your friend. I recently started using them and am never going back. -- - 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 Tue Jan 4 16:31:21 2000 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 638F815198 for ; Tue, 4 Jan 2000 16:31:06 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id BAA24947 for current@FreeBSD.ORG; Wed, 5 Jan 2000 01:31:05 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 06F128863; Wed, 5 Jan 2000 00:44:24 +0100 (CET) Date: Wed, 5 Jan 2000 00:44:24 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: new man pages Message-ID: <20000105004424.A61676@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from marc@oldserver.demon.nl on Tue, Jan 04, 2000 at 11:46:34PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Marc Schneiders: > According to /usr/src/contrib/ntp/FREEBSD-upgrade they should be > installed as docs in /usr/share/doc/ntp. I haven't got them there. They will soon. > haven't tried to read all the files in all the subdirs of both > usr.sbin/ntp and contrib/ntp :-) There's nothing in the former except Makefile glue. Everything you want is in contrib/ntp. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 16:31:23 2000 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 0C26915242 for ; Tue, 4 Jan 2000 16:31:10 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id BAA24952 for current@FreeBSD.ORG; Wed, 5 Jan 2000 01:31:09 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 92F278863; Wed, 5 Jan 2000 00:51:18 +0100 (CET) Date: Wed, 5 Jan 2000 00:51:18 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: new man pages Message-ID: <20000105005118.B61676@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <200001041927.LAA00721@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001041927.LAA00721@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Tue, Jan 04, 2000 at 11:27:32AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Rodney W. Grimes: > xntpd was recently renamed ntpd, but the documentation and manual > pages was not. > You'll find the manual page for ntpd with a ``man xntpd''. Yes and no. The documentation is close for command line options but probably far behind for drivers. > And a side note for PHK. Could you change the rm -f /usr/sbin/xntpd > to instead replace /usr/sbin/xntpd with a LINK to ntpd for maximal I discussed that with Poul-Henning, Peter and David. I do not think that it is a good idea because: - there are many differences between the two. - if you don't use a refclock driver (the majority I think), there are few chances that you overwrote what's in /etc/defaults/rc.conf which means that conversion from xntpd to ntpd was immediate. - if you do have a refclock driver, you'll need to read the documentation and pointing to xntpd manpages won't help you. I prefer a clean break like we have. I only kept the old manpages (i.e. didn't delete them as I did for the binary) because we have a lack in this area. As soon as I get some time, I'll work with Sheldon who offered to merge the new documentation with the old manpages. As a stop-gap, I'll put ASCII generated versions in /usr/share/doc/ntp. > compatibility. You should probably also do an MLINK for ntpd->xntpd > man pages. I don't want to point to obsolete documentation. See above. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 16:35: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from qnx.com (qnx.com [209.226.137.1]) by hub.freebsd.org (Postfix) with ESMTP id 95CA114CFE for ; Tue, 4 Jan 2000 16:35:02 -0800 (PST) (envelope-from alain@qnx.com) Received: (from alain@localhost) by qnx.com (8.8.8/8.8.8) with UUCP id TAA21483 for freebsd-current@freebsd.org; Tue, 4 Jan 2000 19:34:54 -0500 Message-Id: <200001050034.TAA21483@qnx.com> Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? To: ru@freebsd.org (Ruslan Ermilov) Date: Tue, 4 Jan 100 19:34:53 -0500 (EST) From: "Alain Magloire" Cc: eggert@twinsun.com, obrien@nuxi.com, alainm@rcsm.ece.mcgill.ca, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-Reply-To: <20000104143320.D10970@relay.ucb.crimea.ua> from "Ruslan Ermilov" at Jan 4, 0 02:33:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > --n8g4imXOkfNTN/H1 > Content-Type: text/plain; charset=us-ascii > > On Fri, Nov 12, 1999 at 20:45:10 -0800, Paul Eggert wrote: > > > > Date: Fri, 12 Nov 1999 17:23:21 -0800 > > From: "David O'Brien" > > > > I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU > > longopt. > > > > Another possibility would be to follow the example of the existing > > --directories=ACTION option, e.g. something like this: > > > > --binary-files=ACTION how to handle binary files > > ACTION is 'read', 'skip', or 'summarize' (default) > > -I equivalent to --binary-files=skip > > -a, --text equivalent to --binary-files=read > > > Paul, could you please consider applying the following patch (it is against > virgin grep-2.4 sources). Could you please also let me know when the Alpha > with this feature will be made available, so I could import it into FreeBSD. > Or maybe tell me an address of appropriate "announce" mailing list... Bonjour I'm presently busy, with some other problems. Will commit the patch later. The alphas/betas are usually on alpha.gnu.org/gnu/grep. Do you wish to be on the beta list, to be notify ? There is no ETA for grep, the plan is to let the 2.4 propagate and wait for the reports, 2.4.1 will be release to correct any major problems, David's patch will be part of it. BTW, David can you please provide a ChangeLog entry and thanks for the patch. -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 19: 7:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id D27DC1524F for ; Tue, 4 Jan 2000 19:07:14 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 125gn2-00005q-0V; Wed, 5 Jan 2000 03:07:13 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id A6A78D913; Wed, 5 Jan 2000 03:09:26 +0000 (GMT) Message-ID: <001d01bf572a$2ec26d00$0304020a@rings> From: "Cameron Grant" To: "D. Rock" , "FreeBSD CURRENT Mailing List" References: <38727AA4.EFDEDEB4@dead-end.net> Subject: Re: panic: isa_dmastart: bad bounce buffer Date: Wed, 5 Jan 2000 03:08:47 -0000 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.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the panics should be fixed now with sb.c rev 1.47, mss.c rev 1.43. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 19:27: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id C377014D56 for ; Tue, 4 Jan 2000 19:26:54 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3a-2.cybcon.com [205.147.75.131]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id LAA16456 for ; Tue, 4 Jan 2000 11:26:15 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 04 Jan 2000 19:27:57 -0800 (PST) From: William Woods To: freebsd-current@freebsd.org Subject: A couple questions regarding pcmcia cards.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two pcmcia cards here I am wondering if the work under either -stable or -current, they are: 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT The other card is cardbus, so I doubt it but I will ask anyway.... Adaptec SlimSCSI 1480A UltraSCSI If either of these cards DO work, what would I need to get them going, I already have the 3COM PCMCIA modem here working. Thanks, ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 16:32:41 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 19:39:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id BF1E0151CF for ; Tue, 4 Jan 2000 19:39:44 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id TAA00262; Tue, 4 Jan 2000 19:39:36 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000104192028.00a97800@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 04 Jan 2000 19:39:35 -0800 To: Cameron Grant , "D. Rock" , FreeBSD CURRENT Mailing List From: Manfred Antar Subject: Re: panic: isa_dmastart: bad bounce buffer In-Reply-To: <001d01bf572a$2ec26d00$0304020a@rings> References: <38727AA4.EFDEDEB4@dead-end.net> 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:08 AM 1/5/00 +0000, Cameron Grant wrote: >the panics should be fixed now with sb.c rev 1.47, mss.c rev 1.43. > > - cameron > Cameron The panics are stopped !!!! But any sound out of speakers is truncated. If I try to play a au file it just repeats the first part of it over and over. The sound card is a built in Crystal Audio on a Intel PR440FX mother board. Here is the dmesg output: pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 bus_dmamap_load: Too many segs! buf_len = 0xdf00 bus_dmamap_load: Too many segs! buf_len = 0xdf00 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x120-0x127 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 The sound worked fine on a kernel built with sources current as of 12/28/1999 Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 20: 3:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id D0AB8151FD for ; Tue, 4 Jan 2000 20:03:54 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 125hfo-000JGn-0A; Wed, 5 Jan 2000 04:03:49 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 6CE7CD913; Wed, 5 Jan 2000 04:06:20 +0000 (GMT) Message-ID: <000901bf5732$214dee80$0304020a@rings> From: "Cameron Grant" To: "D. Rock" , "FreeBSD CURRENT Mailing List" , "Manfred Antar" References: <38727AA4.EFDEDEB4@dead-end.net> <4.2.2.20000104192028.00a97800@pozo.com> Subject: Re: panic: isa_dmastart: bad bounce buffer Date: Wed, 5 Jan 2000 04:05:40 -0000 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.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > bus_dmamap_load: Too many segs! buf_len = 0xdf00 > bus_dmamap_load: Too many segs! buf_len = 0xdf00 argh, forgot something. try mss.c rev 1.44, sb.c rev 1.48. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 20:58:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 88D61150CD for ; Tue, 4 Jan 2000 20:58:46 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id PAA17598; Wed, 5 Jan 2000 15:58:36 +1100 Date: Wed, 5 Jan 2000 15:58:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: new man pages In-Reply-To: <20000105005118.B61676@keltia.freenix.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 On Wed, 5 Jan 2000, Ollivier Robert wrote: > According to Rodney W. Grimes: > > xntpd was recently renamed ntpd, but the documentation and manual > > pages was not. > > > You'll find the manual page for ntpd with a ``man xntpd''. Those are the old man pages. You're not running -current if you have them :-). > > And a side note for PHK. Could you change the rm -f /usr/sbin/xntpd > > to instead replace /usr/sbin/xntpd with a LINK to ntpd for maximal > > I discussed that with Poul-Henning, Peter and David. I do not think that it is > a good idea because: I think it's a better idea than removing xntpd (not very good). We normally don't remove old commands when their sources go away. It clutters the makefiles and might remove a local copy of the command. It is the responsibilty of the upgrader to remove old commands and their infrastructure. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 21:12:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from soolin.barclayscapital.com (avon2.barclayscapital.com [141.228.4.193]) by hub.freebsd.org (Postfix) with SMTP id 7D24614ED8 for ; Tue, 4 Jan 2000 21:12:25 -0800 (PST) (envelope-from pierre.dampure@barclayscapital.com) Received: from jfsebastian.ldn.bzwint.com by soolin.barclayscapital.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 5 Jan 2000 05:12:25 UT Received: from barclayscapital.com (localhost.ldn.bzwint.com [127.0.0.1]) by bladerunner.ldn.bzwint.com (8.9.3/8.9.3) with ESMTP id FAA01695 for ; Wed, 5 Jan 2000 05:06:59 GMT (envelope-from pierre.dampure@barclayscapital.com) Message-ID: <3872D173.6A9EEB56@barclayscapital.com> Date: Wed, 05 Jan 2000 05:06:59 +0000 From: "Pierre Y. Dampure" Organization: Barclays Capital X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Whilst on the subject of man pages... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... it looks like only a small subset of the man pages for bind 8.2.2P5 (in /usr/src/contrib) gets installed. In particular, we are missing the man page for nsupdate. Any reasons for not installing the whole bunch, since we do install the binaries? PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:15:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 7943F14D84 for ; Tue, 4 Jan 2000 22:15:14 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id WAA09721; Tue, 4 Jan 2000 22:15:08 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000104221107.00aa8570@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 04 Jan 2000 22:15:07 -0800 To: Cameron Grant , "D. Rock" , FreeBSD CURRENT Mailing List From: Manfred Antar Subject: Re: panic: isa_dmastart: bad bounce buffer In-Reply-To: <000901bf5732$214dee80$0304020a@rings> References: <38727AA4.EFDEDEB4@dead-end.net> <4.2.2.20000104192028.00a97800@pozo.com> 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 04:05 AM 1/5/00 +0000, Cameron Grant wrote: > > bus_dmamap_load: Too many segs! buf_len = 0xdf00 > > bus_dmamap_load: Too many segs! buf_len = 0xdf00 > >argh, forgot something. try mss.c rev 1.44, sb.c rev 1.48. > > - cameron Now the au files play great !!! there is still something amiss with /usr/ports/audio/rsynth #say hello world comes out as "hel" this might be a problem with the port although it worked last week Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:17:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 7D51C14D98 for ; Tue, 4 Jan 2000 22:17:49 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id WAA39903; Tue, 4 Jan 2000 22:17:48 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id WAA05501; Tue, 4 Jan 2000 22:17:48 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001050617.WAA05501@realtime.exit.com> Subject: Re: A couple questions regarding pcmcia cards.... In-Reply-To: from William Woods at "Jan 4, 2000 07:27:57 pm" To: freebsd@cybcon.com (William Woods) Date: Tue, 4 Jan 2000 22:17:48 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG Reply-To: frank@exit.com 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 William Woods wrote: > I have two pcmcia cards here I am wondering if the work under either -stable > or -current, they are: > > 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT This is a cardbus card (I have one, too) and won't work. Many of us are eagerly awaiting Warner's new cardbus code. > The other card is cardbus, so I doubt it but I will ask anyway.... > > Adaptec SlimSCSI 1480A UltraSCSI If it's cardbus, it won't work. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:34:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 6847114CF8 for ; Tue, 4 Jan 2000 22:34:34 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (u1033.seaple.icc.ne.jp [210.170.9.33]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id PAA10796; Wed, 5 Jan 2000 15:34:22 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id PAA03950; Wed, 5 Jan 2000 15:34:22 +0900 (JST) Message-Id: <200001050634.PAA03950@lavender.yy.cs.keio.ac.jp> To: freebsd-current@FreeBSD.ORG Subject: Re: [diskless] /etc/rc.diskless1 in 3-stable is better than in 4-current In-Reply-To: Your message of "Tue, 21 Dec 1999 16:51:24 +0100 (CET)" References: <199912211551.QAA16496@info.iet.unipi.it> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Wed_Jan__5_15:34:21_2000)--" Content-Transfer-Encoding: 7bit Date: Wed, 05 Jan 2000 15:34:21 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Wed_Jan__5_15:34:21_2000)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi. First of all, I tried to take in modification of 3-stable into 4-current. And I tested with 4-current NFS server and diskless client. merge from latest 3-stable rc.diskless shell scripts: etc/rc.diskless1 1.1.2.1(for 3-stable) etc/rc.diskless2 1.2.2.1(for 3-stable) Some differences between 3-stable and below rc.diskless{1,2} files - add $FreeBSD$ tag - apply a consistent style to most of the etc scripts - don't extract inet6 address for bootp_ipa and bootp_bca. TODO list: - If files in ``/etc'' directory are symbolic linked, cp -Rp are failed. I will check it and fix. - I want to free rc.diskless1 from /usr partition. (We don't have any hint about path name of /usr directory with bootp. But we need to use ``/usr/bin/awk and /usr/bin/fgrep, /usr/bin/head'' commands to obtain IP address. So currently rc.diskless1 has hard-coded with ${nfs_root}/usr). - create or copy below files and directories (I want to compile ports collection in diskless machine) /var/db/port.mkversion /var/db/pkg --- MIHIRA Sanpei Yoshiro Yokohama, Japan. ----Next_Part(Wed_Jan__5_15:34:21_2000)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit # $FreeBSD: src/etc/rc.diskless1,v 1.4 1999/09/13 17:09:07 peter Exp $ # # /etc/rc.diskless - general BOOTP startup # # BOOTP has mounted / for us. Assume a read-only mount. We must then # - figure out where the NFS mount is coming from # - figure out our IP by querying the interface # - retarget /conf/ME softlink to proper configuration script directory # # It is expected that /etc/fstab and /etc/rc.conf.local will be # set by the system operator on the server to be softlinks to # /conf/ME/fstab and /conf/ME/rc.conf.local. The system operator may # choose to retarget other files as well. The server itself boots # properly with its default /conf/ME softlink pointing to # /conf/server.host.name. # # During a diskless boot, we retarget the /conf/ME softlink to point # to /conf/DISKLESS.CLIENT.IP.ADDRESS. Thus, various system config # files that are softlinks through /conf/ME also get retargeted. # # SEE SAMPLE FILES IN /usr/share/examples/diskless. # chkerr: # # Routine to check for error # # checks error code and drops into shell on failure. # if shell exits, terminates script as well as /etc/rc. # chkerr() { case $1 in 0) ;; *) echo "$2 failed: dropping into /bin/sh" /bin/sh # RESUME ;; esac } # DEBUGGING # # set -v # Figure out where the root mount is coming from, synthesize a mount # for /usr and mount it. # # e.g. nfs_root might wind up as "A.B.C.D:/" # # NOTE! the /usr mount is only temporary so we can access commands necessary # to retarget /conf/ME. The actual /usr mount should be part of the # retargeted /etc/fstab. See instructions in /usr/share/examples/diskless. # set `/bin/df /` nfs_root=$8 # XXX we should extract the host part from nfs_root, but we don't have # any good tool for string parsing yet. The ../ is a dirty hack. We # can add more than one. But this whole section to determine the boot # ifc etc. needs some cleanup mount_nfs -o ro ${nfs_root}/../usr /usr chkerr $? "mount of /usr" # Figure out our interface and IP. # bootp_ifc=`route -n get default | fgrep interface | awk '{ print $2; }'` bootp_ipbca=`ifconfig ${bootp_ifc} | fgrep 'inet ' | head -1 | awk '{ print $6; }'` bootp_ipa=`ifconfig ${bootp_ifc} | fgrep 'inet ' | head -1 | awk '{ print $2; }'` echo "Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipbca}" umount /usr # Files in /etc are copied to /conf/etc which is writable. Then # per-machine configs from /conf/ip.address/etc are copied onto this # directory. First choice is using the client's IP, then the client's # broadcast address, then a default configuration. # This way we have some flexibility to handle clusters of machines # on separate subnets. # # WARNING! null mounts cannot handle mmap, and since many programs # use mmap (such as 'cp'), we have to copy. # mount_mfs -s 2048 -T qp120at dummy /conf/etc cp -Rp /etc/* /conf/etc chkerr $? "MFS mount on /conf/etc" if [ -d /conf/${bootp_ipa} ] then cp -Rp /conf/${bootp_ipa}/etc/* /conf/etc elif [ -d /conf/${bootp_ipbca} ] then cp -Rp /conf/${bootp_ipbca}/etc/* /conf/etc else cp -Rp /conf/default/etc/* /conf/etc fi #mkdir /conf/ME #cp -Rp /conf/${bootp_ipa}/* /conf/ME # # Make the new directory available as /etc # mount_null /conf/etc /etc # retarget the kernel # #sysctl -w kern.bootfile=/conf/ME/kernel # Tell /etc/rc to run the specified script after # it does its mounts but before it does anything # else. # # This script is responsible for setting up the # diskless mount environment. This can be # overriden by /conf/ME/rc.conf.local if, for # example, you do not want to run the standard # system /etc/rc.diskless2 diskless_mount="/etc/rc.diskless2" ----Next_Part(Wed_Jan__5_15:34:21_2000)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit # $FreeBSD: src/etc/rc.diskless2,v 1.4 1999/09/13 17:09:07 peter Exp $ # # rc.diskless2 # # If there is a global system configuration file, suck it in. # if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi mount_mfs -s ${varsize:=65536} -T qp120at dummy /var var_dirs="run dev db msgs tmp spool spool/mqueue spool/lpd spool/output \ spool/output/lpd" for i in ${var_dirs} do mkdir /var/${i} done chmod 755 /var/run chmod 755 /var/db chmod 755 /var/spool chmod 1777 /var/tmp chown -R root.daemon /var/spool/output chgrp daemon /var/spool/lpd # # XXX make sure to create one dir for each printer as requested by lpd # if [ ! -h /tmp -a ! -h /var/tmp ]; then mount_null /var/tmp /tmp fi # extract a list of device entries, then copy them to a writable partition (cd /; find -x dev | cpio -o -H newc) > /tmp/dev.tmp mount_mfs -s 4096 -i 512 -T qp120at dummy /dev (cd /; cpio -i -H newc -d < /tmp/dev.tmp) ----Next_Part(Wed_Jan__5_15:34:21_2000)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:39: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id E553214E6C for ; Tue, 4 Jan 2000 22:39:03 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3a-2.cybcon.com [205.147.75.131]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id OAA00490; Tue, 4 Jan 2000 14:38:12 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050617.WAA05501@realtime.exit.com> Date: Tue, 04 Jan 2000 22:39:55 -0800 (PST) From: William Woods To: Frank Mayhar Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought I read in the mailing list that the 3COM did work...... On 05-Jan-00 Frank Mayhar wrote: > William Woods wrote: >> I have two pcmcia cards here I am wondering if the work under either -stable >> or -current, they are: >> >> 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT > > This is a cardbus card (I have one, too) and won't work. Many of us are > eagerly awaiting Warner's new cardbus code. > >> The other card is cardbus, so I doubt it but I will ask anyway.... >> >> Adaptec SlimSCSI 1480A UltraSCSI > > If it's cardbus, it won't work. > -- > Frank Mayhar frank@exit.com ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 22:39:17 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:42:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 7B30D14EF3 for ; Tue, 4 Jan 2000 22:42:23 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id WAA40112; Tue, 4 Jan 2000 22:42:22 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id WAA05876; Tue, 4 Jan 2000 22:42:22 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001050642.WAA05876@realtime.exit.com> Subject: Re: A couple questions regarding pcmcia cards.... In-Reply-To: from William Woods at "Jan 4, 2000 10:39:55 pm" To: freebsd@cybcon.com (William Woods) Date: Tue, 4 Jan 2000 22:42:22 -0800 (PST) Cc: frank@exit.com (Frank Mayhar), freebsd-current@FreeBSD.ORG Reply-To: frank@exit.com 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 William Woods wrote: > I thought I read in the mailing list that the 3COM did work...... Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's a bug somewhere in the driver. I have one of _those_, too, having read the same thing you did. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 22:59:49 2000 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 DF83514EF3 for ; Tue, 4 Jan 2000 22:59:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA04530; Tue, 4 Jan 2000 23:59:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA64527; Tue, 4 Jan 2000 23:59:40 -0700 (MST) Message-Id: <200001050659.XAA64527@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 19:27:57 PST." References: Date: Tue, 04 Jan 2000 23:59:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : I have two pcmcia cards here I am wondering if the work under either -stable : or -current, they are: : : 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT If this is the cardbus version, no. If it is the pccard version then yes. We've received reports of this same model number being used for both the pccard and cardbus. : The other card is cardbus, so I doubt it but I will ask anyway.... : : Adaptec SlimSCSI 1480A UltraSCSI Nope. It is waiting on cardbus support, which is waiting on cardbus bridge support of cardbus and pccard which is waiting on pccard connection to pccard bridge, which is what I'm working on right now :-) I fear it will be Feb or Mar before I get to it at this rate since I have little free time. Consulting $$$ takes precidence over freetime hacking... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 1:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 6B13414D84 for ; Tue, 4 Jan 2000 23:01:11 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA02016; Tue, 4 Jan 2000 15:00:44 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050642.WAA05876@realtime.exit.com> Date: Tue, 04 Jan 2000 23:02:47 -0800 (PST) From: William Woods To: Frank Mayhar Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Man, this is getting depressing, all these goodies for Christmass and NADA workie, well, I assume that -current they are working on the driver for the 574BT right and eventually it will work. On a side note, how does your laptop like -current? I am going to run it on a Thinkpad 770E On 05-Jan-00 Frank Mayhar wrote: > William Woods wrote: >> I thought I read in the mailing list that the 3COM did work...... > > Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's > a bug somewhere in the driver. I have one of _those_, too, having read the > same thing you did. > -- > Frank Mayhar frank@exit.com ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:00:25 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 1:55 2000 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 4C2B914BD8 for ; Tue, 4 Jan 2000 23:01:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04548; Wed, 5 Jan 2000 00:01:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64553; Wed, 5 Jan 2000 00:01:50 -0700 (MST) Message-Id: <200001050701.AAA64553@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: Frank Mayhar , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 22:39:55 PST." References: Date: Wed, 05 Jan 2000 00:01:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : I thought I read in the mailing list that the 3COM did work...... There are two different versions of the 3ccfe574. One is cardbus and one is pccard, although the pccard may be 3c574. At least that's what the conclusion was when this came up in the past. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 2:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id 6241A1531A; Tue, 4 Jan 2000 23:02:18 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from set.twinsun.com ([192.54.239.8]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id XAA12071; Tue, 4 Jan 2000 23:01:10 -0800 (PST) Received: (eggert@localhost) by set.twinsun.com (8.9.3+Sun/8.9.3) id WAA10612; Tue, 4 Jan 2000 22:59:34 -0800 (PST) Date: Tue, 4 Jan 2000 22:59:34 -0800 (PST) From: Paul Eggert Message-Id: <200001050659.WAA10612@set.twinsun.com> To: ru@freebsd.org Cc: obrien@NUXI.com, alainm@rcsm.ece.mcgill.ca, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <20000104143320.D10970@relay.ucb.crimea.ua> (ru@freebsd.org) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <20000104143320.D10970@relay.ucb.crimea.ua> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for implementing the result of our earlier discussion. I documented what you wrote, and as a result I have the following suggestions for further improvements: * The assignment to not_text should depend on out_quiet if no --binary-files option is given. * The operands of --binary-files are confusing. E.g. --binary-files=read implies that --binary-options=summarize and --binary-options=skip don't read binary files, which isn't true. And --binary-options=skip implies that binary files aren't mentioned on output, which also isn't true (a counterexample is --files-without-match --binary-options=skip). I propose that the operands be renamed from (read, skip, summarize) to (text, without-match, binary). * There's no need for a short equivalent to the --binary-files option. * Is the -I option really needed? Can't users just use --binary-files=without-match instead? I have the impression that this option won't be typed interactively much. Could you please try the patch enclosed below instead? It implements all the above suggestions. 2000-01-04 Paul Eggert Add --binary-files option. * NEWS, doc/grep.1, doc/grep.texi: Document it. * src/grep.c (BINARY_FILES_OPTION): New constant. (long_options, grep, usage, main): New --binary-files option. (binary_files): New var. * src/system.h (TYPE_SIGNED, TYPE_MINIMUM, TYPE_MAXIMUM, CHAR_MAX): New macros. (INT_MAX, UCHAR_MAX): Define in terms of TYPE_MAXIMUM. =================================================================== RCS file: doc/grep.1,v retrieving revision 2.4 retrieving revision 2.4.0.1 diff -pu -r2.4 -r2.4.0.1 --- doc/grep.1 1999/10/12 20:41:22 2.4 +++ doc/grep.1 2000/01/05 06:35:00 2.4.0.1 @@ -28,6 +28,7 @@ grep, egrep, fgrep \- print lines matchi .IR FILE ] .RB [ \-d .IR ACTION ] +.RB [ \-\^\-binary-files=\fITYPE\fP ] .RB [ \-\^\-directories=\fIACTION\fP ] .RB [ \-\^\-extended-regexp ] .RB [ \-\^\-fixed-strings ] @@ -143,6 +144,41 @@ Print the version number of to standard error. This version number should be included in all bug reports (see below). .TP +.BI \-\^\-binary-files= TYPE +If the first few bytes of a file indicate that the file contains binary +data, assume that the file is of type +.IR TYPE . +By default, +.I TYPE +is +.BR binary , +and +.B grep +normally outputs either +a one-line message saying that a binary file matches, or no message if +there is no match. +If +.I TYPE +is +.BR without-match , +.B grep +assumes that a binary file does not match. +If +.I TYPE +is +.BR text , +.B grep +processes a binary file as if it were text; this is equivalent to the +.B \-a +or +.B \-\^\-text +option. +.I Warning: +.B "grep \-\^\-binary-files=text" +might output binary garbage, +which can have nasty side effects if the output is a terminal and if the +terminal driver interprets some of it as commands. +.TP .BR \-b ", " \-\^\-byte-offset Print the byte offset within the input file before each line of output. @@ -257,15 +293,9 @@ and and should redirect output to /dev/null instead. .TP .BR \-a ", " \-\^\-text -Do not suppress output lines that contain binary data. -Normally, if the first few bytes of a file indicate that -the file contains binary data, -.B grep -outputs only a message saying that the file matches the pattern. -This option causes -.B grep -to act as if the file is a text file, -even if it would otherwise be treated as binary. +Process a binary file as if it were text; this is equivalent to the +.B \-\^\-binary-files=text +option. .TP .BR \-v ", " \-\^\-invert-match Invert the sense of matching, to select non-matching lines. @@ -323,9 +353,9 @@ system call to read input, instead of the default .BR read (2) system call. In some situations, -.B -\^-mmap +.B \-\^\-mmap yields better performance. However, -.B -\^-mmap +.B \-\^\-mmap can cause undefined behavior (including core dumps) if an input file shrinks while .B grep =================================================================== RCS file: doc/grep.texi,v retrieving revision 2.4 retrieving revision 2.4.0.1 diff -pu -r2.4 -r2.4.0.1 --- doc/grep.texi 1999/11/13 21:20:24 2.4 +++ doc/grep.texi 2000/01/05 06:35:00 2.4.0.1 @@ -275,6 +275,21 @@ This version number should be included i Print a usage message briefly summarizing these command-line options and the bug-reporting address, then exit. +@itemx --binary-files=@var{type} +@opindex --binary-files +@cindex binary files +If the first few bytes of a file indicate that the file contains binary +data, assume that the file is of type @var{type}. By default, +@var{type} is @samp{binary}, and @command{grep} normally outputs either +a one-line message saying that a binary file matches, or no message if +there is no match. If @var{type} is @samp{without-match}, +@command{grep} assumes that a binary file does not match. If @var{type} +is @samp{text}, @command{grep} processes a binary file as if it were +text; this is equivalent to the @samp{-a} or @samp{--text} option. +@emph{Warning:} @samp{--binary-files=text} might output binary garbage, +which can have nasty side effects if the output is a terminal and if the +terminal driver interprets some of it as commands. + @item -b @itemx --byte-offset @opindex -b @@ -329,16 +344,8 @@ The scanning of every file will stop on @opindex --text @cindex suppress binary data @cindex binary files -Do not suppress output lines that contain binary data. -Normally, if the first few bytes of a file indicate -that the file contains binary data, grep outputs only a -message saying that the file matches the pattern. This -option causes grep to act as if the file is a text -file, even if it would otherwise be treated as binary. -@emph{Warning:} the result might be binary garbage -printed to the terminal, which can have nasty -side-effects if the terminal driver interprets some of -it as commands. +Process a binary file as if it were text; this is equivalent to the +@samp{--binary-files=text} option. @item -w @itemx --word-regexp =================================================================== RCS file: RCS/NEWS,v retrieving revision 2.4 retrieving revision 2.4.0.1 diff -pu -r2.4 -r2.4.0.1 --- NEWS 1999/11/08 00:42:29 2.4 +++ NEWS 2000/01/05 06:35:00 2.4.0.1 @@ -1,3 +1,10 @@ + - The new option --binary-files=TYPE makes grep assume that a binary input + file is of type TYPE. + --binary-files='binary' (the default) outputs a 1-line summary of matches. + --binary-files='without-match' assumes binary files do not match. + --binary-files='text' treats binary files as text + (equivalent to -a or --text). + Version 2.4: - egrep is now equivalent to `grep -E' as required by POSIX, =================================================================== RCS file: src/grep.c,v retrieving revision 2.4 retrieving revision 2.4.0.1 diff -pu -r2.4 -r2.4.0.1 --- src/grep.c 1999/11/13 16:31:55 2.4 +++ src/grep.c 2000/01/05 06:35:00 2.4.0.1 @@ -62,12 +62,19 @@ static int mmap_option; static char const short_options[] = "0123456789A:B:C::EFGHUVX:abcd:e:f:hiLlnqrsuvwxyZz"; +/* Non-boolean long options that have no corresponding short equivalents. */ +enum +{ + BINARY_FILES_OPTION = CHAR_MAX + 1 +}; + /* Long options equivalences. */ static struct option long_options[] = { {"after-context", required_argument, NULL, 'A'}, {"basic-regexp", no_argument, NULL, 'G'}, {"before-context", required_argument, NULL, 'B'}, + {"binary-files", required_argument, NULL, BINARY_FILES_OPTION}, {"byte-offset", no_argument, NULL, 'b'}, {"context", optional_argument, NULL, 'C'}, {"count", no_argument, NULL, 'c'}, @@ -476,7 +483,12 @@ fillbuf (save, stats) } /* Flags controlling the style of output. */ -static int always_text; /* Assume the input is always text. */ +static enum + { + BINARY_BINARY_FILES, + TEXT_BINARY_FILES, + WITHOUT_MATCH_BINARY_FILES + } binary_files; /* How to handle binary files. */ static int filename_mask; /* If zero, output nulls after filenames. */ static int out_quiet; /* Suppress all normal output. */ static int out_invert; /* Print nonmatching stuff. */ @@ -729,11 +741,14 @@ grep (fd, file, stats) { if (! (is_EISDIR (errno, file) && suppress_errors)) error (filename, errno); - return nlines; + return 0; } - not_text = (! (always_text | out_quiet) + not_text = (((binary_files == BINARY_BINARY_FILES && !out_quiet) + || binary_files == WITHOUT_MATCH_BINARY_FILES) && memchr (bufbeg, eol ? '\0' : '\200', buflim - bufbeg)); + if (not_text && binary_files == WITHOUT_MATCH_BINARY_FILES) + return 0; done_on_match += not_text; out_quiet += not_text; @@ -993,7 +1008,9 @@ Output control:\n\ -H, --with-filename print the filename for each match\n\ -h, --no-filename suppress the prefixing filename on output\n\ -q, --quiet, --silent suppress all normal output\n\ - -a, --text do not suppress binary output\n\ + -a, --text equivalent to --binary-files=text\n\ + --binary-files=TYPE assume that binary files are TYPE\n\ + TYPE is 'binary', 'text', or 'without-match'.\n\ -d, --directories=ACTION how to handle directories\n\ ACTION is 'read', 'recurse', or 'skip'.\n\ -r, --recursive equivalent to --directories=recurse.\n\ @@ -1276,7 +1293,7 @@ main (argc, argv) setmatcher (optarg); break; case 'a': - always_text = 1; + binary_files = TEXT_BINARY_FILES; break; case 'b': out_byte = 1; @@ -1370,6 +1387,16 @@ main (argc, argv) case 'z': eolbyte = '\0'; break; + case BINARY_FILES_OPTION: + if (strcmp (optarg, "binary") == 0) + binary_files = BINARY_BINARY_FILES; + else if (strcmp (optarg, "text") == 0) + binary_files = TEXT_BINARY_FILES; + else if (strcmp (optarg, "without-match") == 0) + binary_files = WITHOUT_MATCH_BINARY_FILES; + else + fatal (_("unknown binary-files type"), 0); + break; case 0: /* long options */ break; =================================================================== RCS file: src/system.h,v retrieving revision 2.4 retrieving revision 2.4.0.1 diff -pu -r2.4 -r2.4.0.1 --- src/system.h 1999/10/12 20:41:25 2.4 +++ src/system.h 2000/01/05 06:35:00 2.4.0.1 @@ -127,11 +127,20 @@ void free(); #ifndef CHAR_BIT # define CHAR_BIT 8 #endif +/* The extra casts work around common compiler bugs. */ +#define TYPE_SIGNED(t) (! ((t) 0 < (t) -1)) +#define TYPE_MINIMUM(t) ((t) (TYPE_SIGNED (t) \ + ? ~ (t) 0 << (sizeof (t) * CHAR_BIT - 1) \ + : (t) 0)) +#define TYPE_MAXIMUM(t) ((t) (~ (t) 0 - TYPE_MINIMUM (t))) +#ifndef CHAR_MAX +# define CHAR_MAX TYPE_MAXIMUM (char) +#endif #ifndef INT_MAX -# define INT_MAX 2147483647 +# define INT_MAX TYPE_MAXIMUM (int) #endif #ifndef UCHAR_MAX -# define UCHAR_MAX 255 +# define UCHAR_MAX TYPE_MAXIMUM (unsigned char) #endif #if !defined(STDC_HEADERS) && defined(HAVE_STRING_H) && defined(HAVE_MEMORY_H) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 3:24 2000 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 4CC2615071 for ; Tue, 4 Jan 2000 23:03:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04564; Wed, 5 Jan 2000 00:03:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64580; Wed, 5 Jan 2000 00:03:15 -0700 (MST) Message-Id: <200001050703.AAA64580@harmony.village.org> To: frank@exit.com Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd@cybcon.com (William Woods), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 22:42:22 PST." <200001050642.WAA05876@realtime.exit.com> References: <200001050642.WAA05876@realtime.exit.com> Date: Wed, 05 Jan 2000 00:03:15 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001050642.WAA05876@realtime.exit.com> Frank Mayhar writes: : Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's : a bug somewhere in the driver. I have one of _those_, too, having read the : same thing you did. Last I heard, Matt Dodd had or was waiting for a 574BT and pccard enviornment to fix the driver. I have a 3CCFE575CT sitting here on my desk right now as a gentile reminder to work on pccard/cardbus stuff :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 4:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 2F59515387 for ; Tue, 4 Jan 2000 23:04:22 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA02239; Tue, 4 Jan 2000 15:03:53 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050659.XAA64527@harmony.village.org> Date: Tue, 04 Jan 2000 23:05:57 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT > > If this is the cardbus version, no. If it is the pccard version then > yes. We've received reports of this same model number being used for > both the pccard and cardbus. So, how do I tell if its pccard or cardbus? Got some way for me to test it? ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:04:30 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23: 9:29 2000 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 19AA814EF3 for ; Tue, 4 Jan 2000 23:09:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04614; Wed, 5 Jan 2000 00:09:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64686; Wed, 5 Jan 2000 00:09:25 -0700 (MST) Message-Id: <200001050709.AAA64686@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 23:05:57 PST." References: Date: Wed, 05 Jan 2000 00:09:25 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : So, how do I tell if its pccard or cardbus? Got some way for me to test it? Hold on. Lemme try something here.... 1) Physical inspection. The cardbus cards have a row of dots on the top side of the card right next to the connectors for the pccard/cardbus bus for better grounding and are often copper in color. 2) pccardc dumpcis This gives me one tuple that is 0xff. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:12:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 7EAEC14EF3 for ; Tue, 4 Jan 2000 23:12:42 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA02760; Tue, 4 Jan 2000 15:12:14 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050709.AAA64686@harmony.village.org> Date: Tue, 04 Jan 2000 23:14:15 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hold on. Lemme try something here.... > > 1) Physical inspection. The cardbus cards have a row of dots on the > top side of the card right next to the connectors for the > pccard/cardbus bus for better grounding and are often copper in > color. Nope, no row of dots or anything similar. ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:13:25 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:16:19 2000 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 354D515319 for ; Tue, 4 Jan 2000 23:15:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04658; Wed, 5 Jan 2000 00:15:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64806; Wed, 5 Jan 2000 00:15:51 -0700 (MST) Message-Id: <200001050715.AAA64806@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 23:14:15 PST." References: Date: Wed, 05 Jan 2000 00:15:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : > Hold on. Lemme try something here.... : > : > 1) Physical inspection. The cardbus cards have a row of dots on the : > top side of the card right next to the connectors for the : > pccard/cardbus bus for better grounding and are often copper in : > color. : : Nope, no row of dots or anything similar. Does plugging it in and doing a pccardc dumpcis reveal anything. Also if you look at the pccard/cardbus bus end, is the connector on the right look like: * ** ** or does it look like * * ** The above is a 3.3V card and generally means that it is cardbus (although there are some low voltage 3.3V pccards out there and the nomads list produced some patches for them a short time ago). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:16:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from yormungandr.demos.su (yormungandr.demos.su [194.87.5.30]) by hub.freebsd.org (Postfix) with ESMTP id 1E6F215370 for ; Tue, 4 Jan 2000 23:16:42 -0800 (PST) (envelope-from mishania@yormungandr.demos.su) Received: (from mishania@localhost) by yormungandr.demos.su (8.9.3/8.9.2) id KAA80137; Wed, 5 Jan 2000 10:15:33 +0300 (MSK) (envelope-from mishania) Date: Wed, 5 Jan 2000 10:15:33 +0300 From: "Mikhail A. Sokolov" To: Warner Losh Cc: frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG Subject: Re: A couple questions regarding pcmcia cards.... Message-ID: <20000105101533.A79948@demos.su> References: <200001050642.WAA05876@realtime.exit.com> <200001050703.AAA64580@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200001050703.AAA64580@harmony.village.org> X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And what about 3cxem556b? When somebody already asked some time ago, I looked through archives to no avail of information. It worked splendid on 2.2.7-pao ;) OpenBSD 2.6, which I have to use now isn't a solution due to it being OpenBSD. On Wed, Jan 05, 2000 at 12:03:15AM -0700, Warner Losh wrote: # In message <200001050642.WAA05876@realtime.exit.com> Frank Mayhar writes: #: Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's # : a bug somewhere in the driver. I have one of _those_, too, having read the # : same thing you did. # # Last I heard, Matt Dodd had or was waiting for a 574BT and pccard # enviornment to fix the driver. # # I have a 3CCFE575CT sitting here on my desk right now as a gentile # reminder to work on pccard/cardbus stuff :-). # # Warner -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:19:21 2000 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 0E9D01531B for ; Tue, 4 Jan 2000 23:19:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04680; Wed, 5 Jan 2000 00:19:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64861; Wed, 5 Jan 2000 00:19:13 -0700 (MST) Message-Id: <200001050719.AAA64861@harmony.village.org> To: "Mikhail A. Sokolov" Subject: Re: A couple questions regarding pcmcia cards.... Cc: frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 10:15:33 +0300." <20000105101533.A79948@demos.su> References: <20000105101533.A79948@demos.su> <200001050642.WAA05876@realtime.exit.com> <200001050703.AAA64580@harmony.village.org> Date: Wed, 05 Jan 2000 00:19:13 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105101533.A79948@demos.su> "Mikhail A. Sokolov" writes: : And what about 3cxem556b? When somebody already asked some time ago, I looked : through archives to no avail of information. It worked splendid on 2.2.7-pao ;) What's a 3cxem556b? It looks like the -current sources identify it and make efforts to support it. Looks like a combo card version of the 574 or 574B. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:22:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 1C15D152EC for ; Tue, 4 Jan 2000 23:22:40 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA03402; Tue, 4 Jan 2000 15:22:03 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050715.AAA64806@harmony.village.org> Date: Tue, 04 Jan 2000 23:23:48 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not near the laptop right now to get a dumpcis for you, but I have the card here, it doesnt look like either...it is like this ** ** ** On 05-Jan-00 Warner Losh wrote: > In message William Woods writes: >: > Hold on. Lemme try something here.... >: > >: > 1) Physical inspection. The cardbus cards have a row of dots on the >: > top side of the card right next to the connectors for the >: > pccard/cardbus bus for better grounding and are often copper in >: > color. >: >: Nope, no row of dots or anything similar. > > Does plugging it in and doing a pccardc dumpcis reveal anything. > > Also if you look at the pccard/cardbus bus end, is the connector on > the right look like: > > * > ** > ** > > or does it look like > > * > * > ** > > The above is a 3.3V card and generally means that it is cardbus > (although there are some low voltage 3.3V pccards out there and the > nomads list produced some patches for them a short time ago). > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:21:09 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:24:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from yormungandr.demos.su (yormungandr.demos.su [194.87.5.30]) by hub.freebsd.org (Postfix) with ESMTP id 853AE1531C for ; Tue, 4 Jan 2000 23:24:37 -0800 (PST) (envelope-from mishania@yormungandr.demos.su) Received: (from mishania@localhost) by yormungandr.demos.su (8.9.3/8.9.2) id KAA80356; Wed, 5 Jan 2000 10:24:24 +0300 (MSK) (envelope-from mishania) Date: Wed, 5 Jan 2000 10:24:24 +0300 From: "Mikhail A. Sokolov" To: Warner Losh Cc: "Mikhail A. Sokolov" , frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG Subject: Re: A couple questions regarding pcmcia cards.... Message-ID: <20000105102424.A80280@demos.su> References: <20000105101533.A79948@demos.su> <200001050642.WAA05876@realtime.exit.com> <200001050703.AAA64580@harmony.village.org> <20000105101533.A79948@demos.su> <200001050719.AAA64861@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200001050719.AAA64861@harmony.village.org> X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 12:19:13AM -0700, Warner Losh wrote: # In message <20000105101533.A79948@demos.su> "Mikhail A. Sokolov" writes: # : And what about 3cxem556b? When somebody already asked some time ago, I looked # : through archives to no avail of information. It worked splendid on 2.2.7-pao ;) # # What's a 3cxem556b? It looks like the -current sources identify it # and make efforts to support it. Looks like a combo card version of # the 574 or 574B. But not that my card was recongnized 2 days ago. It's 10mbit/56K, probably 574{,B}. ep0 in OpenBSD and in old PAO. # Warner -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:26:39 2000 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 3AE6F1531C for ; Tue, 4 Jan 2000 23:26:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04730; Wed, 5 Jan 2000 00:26:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64966; Wed, 5 Jan 2000 00:26:34 -0700 (MST) Message-Id: <200001050726.AAA64966@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 23:23:48 PST." References: Date: Wed, 05 Jan 2000 00:26:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : Not near the laptop right now to get a dumpcis for you, but I have the card : here, : : it doesnt look like either...it is like this : : ** : ** : ** Are you sure? Both the right and left sides have a key to prevent low voltage only cards from being plugged into a non-low voltage supporting socket. The key is divided into approx 1/3rds For a high voltage card, the bottom 1/3 is present and the top 2/3rds are missing. IF you have a known pccard around, it is easy to see the difference when held side by side. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:28:21 2000 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 A670F14D2F for ; Tue, 4 Jan 2000 23:28:19 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04743; Wed, 5 Jan 2000 00:28:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA64999; Wed, 5 Jan 2000 00:28:18 -0700 (MST) Message-Id: <200001050728.AAA64999@harmony.village.org> To: "Mikhail A. Sokolov" Subject: Re: A couple questions regarding pcmcia cards.... Cc: frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 10:24:24 +0300." <20000105102424.A80280@demos.su> References: <20000105102424.A80280@demos.su> <20000105101533.A79948@demos.su> <200001050642.WAA05876@realtime.exit.com> <200001050703.AAA64580@harmony.village.org> <20000105101533.A79948@demos.su> <200001050719.AAA64861@harmony.village.org> Date: Wed, 05 Jan 2000 00:28:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105102424.A80280@demos.su> "Mikhail A. Sokolov" writes: : But not that my card was recongnized 2 days ago. It's 10mbit/56K, : probably 574{,B}. ep0 in OpenBSD and in old PAO. Odd. Did you get the following failure: Unit failed to come ready or product ID unknown (id 0x%x)? and if so, what was the ID? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:29: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mooseriver.com (superior.mooseriver.com [209.249.56.198]) by hub.freebsd.org (Postfix) with ESMTP id 5BCDE152F2 for ; Tue, 4 Jan 2000 23:28:57 -0800 (PST) (envelope-from jgrosch@mooseriver.com) Received: (from jgrosch@localhost) by mooseriver.com (8.9.3/8.9.3) id XAA68262; Tue, 4 Jan 2000 23:21:45 -0800 (PST) (envelope-from jgrosch) Date: Tue, 4 Jan 2000 23:21:45 -0800 From: Josef Grosch To: William Woods Cc: Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: A couple questions regarding pcmcia cards.... Message-ID: <20000104232145.B68206@mooseriver.com> Reply-To: jgrosch@mooseriver.com References: <200001050659.XAA64527@harmony.village.org> 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 Tue, Jan 04, 2000 at 11:05:57PM -0800, William Woods wrote: > > >: 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT > > > > If this is the cardbus version, no. If it is the pccard version then > > yes. We've received reports of this same model number being used for > > both the pccard and cardbus. > > So, how do I tell if its pccard or cardbus? Got some way for me to test it? Look at the business end of the card. Do you see a row of bumps the card? If you do, then you are holding a CardBus. If you do not see the row of bumps then you have a pccard. Josef -- Josef Grosch | Another day closer to a | FreeBSD 3.4 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:30:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 9CE9B14D2F for ; Tue, 4 Jan 2000 23:30:51 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA03814; Tue, 4 Jan 2000 15:30:13 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050726.AAA64966@harmony.village.org> Date: Tue, 04 Jan 2000 23:32:03 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * ** is what I see On 05-Jan-00 Warner Losh wrote: > In message William Woods writes: >: Not near the laptop right now to get a dumpcis for you, but I have the card >: here, >: >: it doesnt look like either...it is like this >: >: ** >: ** >: ** > > Are you sure? Both the right and left sides have a key to prevent low > voltage only cards from being plugged into a non-low voltage > supporting socket. The key is divided into approx 1/3rds For a high > voltage card, the bottom 1/3 is present and the top 2/3rds are > missing. IF you have a known pccard around, it is easy to see the > difference when held side by side. > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:30:39 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:33:19 2000 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 0184015346 for ; Tue, 4 Jan 2000 23:33:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04777; Wed, 5 Jan 2000 00:33:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA65069; Wed, 5 Jan 2000 00:33:12 -0700 (MST) Message-Id: <200001050733.AAA65069@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 23:32:03 PST." References: Date: Wed, 05 Jan 2000 00:33:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : * : ** : : is what I see Which part is taller, the tab sticking out, or the slot sticking in? If the tab is taller, it is likely cardbus, otherwise pccard. I suspect that the slot is taller since you don't have the row of bumps on the card. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:36:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 5F91B153EB for ; Tue, 4 Jan 2000 23:35:57 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA04072; Tue, 4 Jan 2000 15:35:16 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050733.AAA65069@harmony.village.org> Date: Tue, 04 Jan 2000 23:37:02 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG slot is taller On 05-Jan-00 Warner Losh wrote: > In message William Woods writes: >: * >: ** >: >: is what I see > > Which part is taller, the tab sticking out, or the slot sticking in? > If the tab is taller, it is likely cardbus, otherwise pccard. I > suspect that the slot is taller since you don't have the row of bumps > on the card. > > Warner ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:36:39 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:36:19 2000 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 097811546D for ; Tue, 4 Jan 2000 23:36:14 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 884C52CE5F; Wed, 5 Jan 2000 09:36:10 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id AB7E373; Wed, 5 Jan 2000 09:36:11 +0200 (EET) Date: Wed, 5 Jan 2000 09:36:11 +0200 From: Vallo Kallaste To: Chris Piazza Cc: freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD Message-ID: <20000105093611.A29239@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> <20000104141208.B379@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000104141208.B379@norn.ca.eu.org>; from Chris Piazza on Tue, Jan 04, 2000 at 02:12:08PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 02:12:08PM -0800, Chris Piazza wrote: > Yes. I must warn you it's still really buggy if you intend to use > it a lot. Basically all I did was grab the opera tarball, extract > it and run the 'runnow' script. > > Screenshot here: http://www.freebsd.org/~cpiazza/sshot-opera.png What WM you are running? Is it Blackbox with KDE or..? -- 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 Tue Jan 4 23:38: 6 2000 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 E864A1532C for ; Tue, 4 Jan 2000 23:38:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04801; Wed, 5 Jan 2000 00:38:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA65201; Wed, 5 Jan 2000 00:38:01 -0700 (MST) Message-Id: <200001050738.AAA65201@harmony.village.org> To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jan 2000 23:37:02 PST." References: Date: Wed, 05 Jan 2000 00:38:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : slot is taller Then it is a pccard. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 4 23:39:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id B6EBA15395 for ; Tue, 4 Jan 2000 23:39:47 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-46.cybcon.com [205.147.75.47]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id PAA04258; Tue, 4 Jan 2000 15:39:21 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001050738.AAA65201@harmony.village.org> Date: Tue, 04 Jan 2000 23:41:25 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, now...to get it working........... ideas? On 05-Jan-00 Warner Losh wrote: > In message William Woods writes: >: slot is taller > > Then it is a pccard. > > Warner ---------------------------------- E-Mail: William Woods Date: 04-Jan-00 Time: 23:40:58 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 0:35:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DAC7715347; Wed, 5 Jan 2000 00:35:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA35344; Wed, 5 Jan 2000 09:35:11 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001050835.JAA35344@freebsd.dk> Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: from Brian Fundakowski Feldman at "Jan 4, 2000 06:36:44 pm" To: green@FreeBSD.ORG (Brian Fundakowski Feldman) Date: Wed, 5 Jan 2000 09:35:11 +0100 (CET) Cc: 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 Brian Fundakowski Feldman wrote: > > I used a multiple of the blocksize, and it works fine, except for on > the very last bit of data. The very last bit of data is what causes > an underrun, and the code that's there for overrun/underrun is > wrong right now. For underrun, it ends up writing the underlying > blocksize length from the user buffer of _less_than_that_size_, then > it writes (blocksize - user buffer size) _more_ zeroed data! This > promptly locks up the IDE bus with my CD-R. That's what the patch was > about and you didn't say anything about; yes, I know that blocksizes > should be matched perfectly and padded perfectly to prevent the ATA > driver from having to handle the underrun/overrun cases, but the > current handling is/was still broken. Try this patch instead, it should do the right thing.. Index: atapi-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/atapi-all.c,v retrieving revision 1.29 diff -u -r1.29 atapi-all.c --- atapi-all.c 2000/01/03 10:26:56 1.29 +++ atapi-all.c 2000/01/05 08:36:49 @@ -563,12 +563,15 @@ #endif for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA); + *buffer += request->bytecount; + request->bytecount = 0; } - else + else { insw(request->device->controller->ioaddr + ATA_DATA, (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + *buffer += length; + request->bytecount -= length; + } } static void @@ -585,19 +588,22 @@ request->device->devname, length, request->bytecount); #ifdef ATA_16BIT_ONLY outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int16_t)); #else outsl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int32_t)); + (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int32_t)); #endif for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA, 0); + *buffer += request->bytecount; + request->bytecount = 0; } - else + else { outsw(request->device->controller->ioaddr + ATA_DATA, (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + *buffer += length; + request->bytecount -= length; + } } static void -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 0:39:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B79EE14C38; Wed, 5 Jan 2000 00:39:09 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA36274; Wed, 5 Jan 2000 09:39:08 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001050839.JAA36274@freebsd.dk> Subject: Re: ATA lost contact In-Reply-To: from Kris Kennaway at "Jan 4, 2000 03:08:56 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Wed, 5 Jan 2000 09:39:08 +0100 (CET) Cc: 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 Kris Kennaway wrote: > One of my Western Digital Caviars doesn't work under the new ATA driver: > upon trying to access the disk (via swapon or mount during boot) it gives > the famous "lost contact with disk" message and falls back to PIO mode. > Interestingly, my two older WDCs work fine - although I notice that ad1 > and ad2 are only detected as WDMA2, when it seems (from the udma=2) that > they can handle UDMA - is this a cabling issue or something (I'm not > familiar with IDE cabling requirements)? The disk probably has problems with DMA mode (lots of older WD disks has that). You only get WDMA2 mode since you controller is an older Intel PIIX that can't do UDMA... > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 > ad0: ATA-0 disk at ata0 as master > ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, WDMA2 > ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 > ad1: ATA-3 disk at ata0 as slave > ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, WDMA2 > ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 > ad2: ATA-4 disk at ata1 as master > ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S > ad2: 16 secs/int, 1 depth queue, WDMA2 -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 0:47:20 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6F08814BD8; Wed, 5 Jan 2000 00:47:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5C5481CD61D; Wed, 5 Jan 2000 00:47:19 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 5 Jan 2000 00:47:19 -0800 (PST) From: Kris Kennaway To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA lost contact In-Reply-To: <200001050839.JAA36274@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 Wed, 5 Jan 2000, Soren Schmidt wrote: > The disk probably has problems with DMA mode (lots of older WD disks > has that). You only get WDMA2 mode since you controller is an older > Intel PIIX that can't do UDMA... Hmm..This disk was bought in about March 99..you're sure that's the reason? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 0:47:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-11.cpinternet.com [208.149.16.11]) by hub.freebsd.org (Postfix) with ESMTP id 6A14314D0D for ; Wed, 5 Jan 2000 00:47:15 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id CAA00439; Wed, 5 Jan 2000 02:29:51 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 Jan 2000 02:29:51 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: newpcm problems X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14451.149.716785.925686@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With yesterday's current I get bounce buffer panics in isa_dmastart doing cat foo.pcm >/dev/dsp. The same thing happens with mss.c v1.42 modified to reduce MSS_BUFSIZE by 48k. The card is ESS1869 in this case: Jan 5 02:16:55 avalon /kernel: unknown0: at port 0x800-0x807 on isa0 Jan 5 02:16:55 avalon /kernel: sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 Jan 5 02:16:55 avalon /kernel: pcm0: on sbc0 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: joy1: at port 0x200 on isa0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 0:47:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-11.cpinternet.com [208.149.16.11]) by hub.freebsd.org (Postfix) with ESMTP id BC7D614A27 for ; Wed, 5 Jan 2000 00:47:26 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id CAA00481; Wed, 5 Jan 2000 02:43:24 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 5 Jan 2000 02:43:24 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: portmap problems X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14451.257.54511.497159@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently I've noticed that it takes a long time for portmap to settle well enough so that mountd and nfsd can register. Jan 5 02:16:56 avalon mountd[97]: can't register mount Jan 5 02:16:56 avalon nfsd:[99]: can't register with udp portmap Very strange. Strange enough so that perhaps it might catch someone else's interest. Someone who might actually do something about it, maybe even. portmap was pid 92 this time. Killing and restarting mountd and nfsd works: % rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100005 3 udp 1011 mountd 100005 3 tcp 1020 mountd 100005 1 udp 1011 mountd 100005 1 tcp 1020 mountd 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs Which suggests to me -- perhaps portmap and mountd should be allowed to take a -u argument as well, to reduce port consumption? If so, I imagine the patch would be something like this: diff -u sbin/mountd/mountd.c.orig sbin/mountd/mountd.c.new --- sbin/mountd/mountd.c.orig Wed Jan 5 02:36:27 2000 +++ sbin/mountd/mountd.c.new Wed Jan 5 02:38:22 2000 @@ -229,6 +229,8 @@ int debug = 0; #endif +int udponly = 0; + /* * Mountd server for NFS mount protocol as described in: * NFS: Network File System Protocol Specification, RFC1094, Appendix A @@ -255,7 +257,7 @@ if (error) errx(1, "NFS support is not available in the running kernel"); - while ((c = getopt(argc, argv, "2dlnr")) != -1) + while ((c = getopt(argc, argv, "2dlnru")) != -1) switch (c) { case '2': force_v2 = 1; @@ -272,6 +274,9 @@ case 'l': log = 1; break; + case 'u': + udponly = 1; + break; default: usage(); }; @@ -317,7 +322,7 @@ } } if ((udptransp = svcudp_create(RPC_ANYSOCK)) == NULL || - (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL) { + (!udponly && (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL)) { syslog(LOG_ERR, "can't create socket"); exit(1); } @@ -325,12 +330,12 @@ pmap_unset(RPCPROG_MNT, 3); if (!force_v2) if (!svc_register(udptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_UDP) || - !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_TCP)) { + (!udponly && !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_TCP))) { syslog(LOG_ERR, "can't register mount"); exit(1); } if (!svc_register(udptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_UDP) || - !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_TCP)) { + (!udponly && !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_TCP))) { syslog(LOG_ERR, "can't register mount"); exit(1); } diff -u usr.sbin/portmap/portmap.c.orig usr.sbin/portmap/portmap.c.new --- usr.sbin/portmap/portmap.c.orig Wed Jan 5 02:33:53 2000 +++ usr.sbin/portmap/portmap.c.new Wed Jan 5 02:36:03 2000 @@ -109,6 +109,7 @@ struct pmaplist *pmaplist; int debugging = 0; +int udponly = 0; int main(argc, argv) @@ -121,7 +122,7 @@ int len = sizeof(struct sockaddr_in); register struct pmaplist *pml; - while ((c = getopt(argc, argv, "dv")) != -1) { + while ((c = getopt(argc, argv, "duv")) != -1) { switch (c) { case 'd': @@ -132,6 +133,10 @@ verboselog = 1; break; + case 'u': + udponly = 1; + break; + default: usage(); } @@ -169,29 +174,32 @@ pml->pml_map.pm_port = PMAPPORT; pmaplist = pml; - if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) { + if (!udponly) { + + if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) { syslog(LOG_ERR, "cannot create tcp socket: %m"); exit(1); - } - if (bind(sock, (struct sockaddr *)&addr, len) != 0) { + } + if (bind(sock, (struct sockaddr *)&addr, len) != 0) { syslog(LOG_ERR, "cannot bind tcp: %m"); exit(1); - } - if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE)) - == (SVCXPRT *)NULL) { + } + if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE)) + == (SVCXPRT *)NULL) { syslog(LOG_ERR, "couldn't do tcp_create"); exit(1); + } + /* make an entry for ourself */ + pml = (struct pmaplist *)malloc((u_int)sizeof(struct pmaplist)); + pml->pml_map.pm_prog = PMAPPROG; + pml->pml_map.pm_vers = PMAPVERS; + pml->pml_map.pm_prot = IPPROTO_TCP; + pml->pml_map.pm_port = PMAPPORT; + pml->pml_next = pmaplist; + pmaplist = pml; + + (void)svc_register(xprt, PMAPPROG, PMAPVERS, reg_service, FALSE); } - /* make an entry for ourself */ - pml = (struct pmaplist *)malloc((u_int)sizeof(struct pmaplist)); - pml->pml_map.pm_prog = PMAPPROG; - pml->pml_map.pm_vers = PMAPVERS; - pml->pml_map.pm_prot = IPPROTO_TCP; - pml->pml_map.pm_port = PMAPPORT; - pml->pml_next = pmaplist; - pmaplist = pml; - - (void)svc_register(xprt, PMAPPROG, PMAPVERS, reg_service, FALSE); /* additional initializations */ check_startup(); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 1: 2:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E855414E3C; Wed, 5 Jan 2000 01:02:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA41882; Wed, 5 Jan 2000 10:02:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001050902.KAA41882@freebsd.dk> Subject: Re: ATA lost contact In-Reply-To: from Kris Kennaway at "Jan 5, 2000 00:47:19 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Wed, 5 Jan 2000 10:02:53 +0100 (CET) Cc: 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 Kris Kennaway wrote: > On Wed, 5 Jan 2000, Soren Schmidt wrote: > > > The disk probably has problems with DMA mode (lots of older WD disks > > has that). You only get WDMA2 mode since you controller is an older > > Intel PIIX that can't do UDMA... > > Hmm..This disk was bought in about March 99..you're sure that's the > reason? No, but I've had my share of bad experiences with WD disks in that regard, I'll have to look up the modelnumber to be sure... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 1:22:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id 74BF214E49 for ; Wed, 5 Jan 2000 01:22:48 -0800 (PST) (envelope-from jyoung@accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Wed, 5 Jan 2000 03:22:43 -0600 Message-ID: From: Jason Young To: "'frank@exit.com'" , freebsd@cybcon.com Cc: freebsd-current@FreeBSD.ORG Subject: RE: A couple questions regarding pcmcia cards.... Date: Wed, 5 Jan 2000 03:22:42 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The card is also available in a 16-bit version (it has a PC Card logo on the back, I don't know if the Cardbus one does or not). It's important to note that the 575 (not the 574) is CardBus. I used to have one, but semi-thankfully, it got blown up by lightning and the replacement was 16-bit and thus usuable with FreeBSD. If you actually have the 16-bit pccard version, then you need to patch your driver. I sent in patches that got committed to 4.0, but were basically replaced a month later by Matt Jacob's massive rework of the entire ep driver and not MFC'd. You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c And it will drop directly into your tree in /sys/i386/isa. Make sure you have 1.23.2.1 or later of if_epreg.h. The only major change of the patch is to hit the card with an offset command if the no-offset commands don't work. I have no idea what its significance is other than it's required to make my card work. I can't remember where I got the basic idea from, it was from PAO I think. > -----Original Message----- > From: Frank Mayhar [mailto:frank@exit.com] > Sent: Wednesday, January 05, 2000 12:18 AM > To: freebsd@cybcon.com > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: A couple questions regarding pcmcia cards.... > > > William Woods wrote: > > I have two pcmcia cards here I am wondering if the work > under either -stable > > or -current, they are: > > > > 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT > > This is a cardbus card (I have one, too) and won't work. > Many of us are > eagerly awaiting Warner's new cardbus code. > > > The other card is cardbus, so I doubt it but I will ask anyway.... > > > > Adaptec SlimSCSI 1480A UltraSCSI > > If it's cardbus, it won't work. > -- > Frank Mayhar frank@exit.com > > > 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 Wed Jan 5 1:27:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id 835A41534B for ; Wed, 5 Jan 2000 01:27:16 -0800 (PST) (envelope-from jyoung@accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Wed, 5 Jan 2000 03:27:15 -0600 Message-ID: From: Jason Young To: "'frank@exit.com'" , freebsd@cybcon.com Cc: freebsd-current@FreeBSD.ORG Subject: RE: A couple questions regarding pcmcia cards.... Date: Wed, 5 Jan 2000 03:27:15 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c > > And it will drop directly into your tree in /sys/i386/isa. > Make sure you > have 1.23.2.1 or later of if_epreg.h. Argh, I thought I was talking on the freebsd-stable list. You're going to have to talk to Matt about this card in -current, since he's the maintainer of the driver now. I might look into it later, but I stopped cvsupping my laptop when the ep driver upheavals began for fear of losing connectivity totally (never have gotten the modem to work). The instructions I gave -will- get a 3.X box working, however > The only major change of the patch is to hit the card with an > offset command > if the no-offset commands don't work. I have no idea what its > significance > is other than it's required to make my card work. I can't > remember where I > got the basic idea from, it was from PAO I think. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 1:53:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 9DBBF1535D for ; Wed, 5 Jan 2000 01:53:29 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup2-50.iptelecom.net.ua [212.9.226.114]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA29463; Wed, 5 Jan 2000 11:56:22 +0200 (EET) Message-ID: <387314A9.16B024BD@altavista.net> Date: Wed, 05 Jan 2000 11:53:46 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: vallo@matti.ee Cc: freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD References: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> <20000104141208.B379@norn.ca.eu.org> <20000105093611.A29239@myhakas.matti.ee> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste wrote: > On Tue, Jan 04, 2000 at 02:12:08PM -0800, Chris Piazza wrote: > > > Yes. I must warn you it's still really buggy if you intend to use > > it a lot. Basically all I did was grab the opera tarball, extract > > it and run the 'runnow' script. > > > > Screenshot here: http://www.freebsd.org/~cpiazza/sshot-opera.png > > What WM you are running? Is it Blackbox with KDE or..? Looks like it is KWM with KDE ;). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 2:22: 7 2000 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 2B69515319 for ; Wed, 5 Jan 2000 02:22:03 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id ABD322CE5B; Wed, 5 Jan 2000 12:21:57 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id EA0767D; Wed, 5 Jan 2000 12:21:59 +0200 (EET) Date: Wed, 5 Jan 2000 12:21:59 +0200 From: Vallo Kallaste To: Maxim Sobolev Cc: freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD Message-ID: <20000105122159.A36129@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> <20000104141208.B379@norn.ca.eu.org> <20000105093611.A29239@myhakas.matti.ee> <387314A9.16B024BD@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <387314A9.16B024BD@altavista.net>; from Maxim Sobolev on Wed, Jan 05, 2000 at 11:53:46AM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 11:53:46AM +0200, Maxim Sobolev wrote: > > What WM you are running? Is it Blackbox with KDE or..? > > Looks like it is KWM with KDE ;). Ok, ok :) I did run Blackbox some time ago w.o. KDE and now I saw the nice taskbar with gradient, so.. hehe I thought it has something to do with Blackbox. Forgot themes completely. Can Opera run NS plugins, example Shockwave plugin for Linux? Shockwave enabled, err.. restricted site count seems to increase rapidly nowadays :-| -- 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 Wed Jan 5 2:38:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 4091814D84 for ; Wed, 5 Jan 2000 02:38:58 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id E98301F3C; Wed, 5 Jan 2000 11:38:56 +0100 (CET) Date: Wed, 5 Jan 2000 11:38:56 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: kvm-troubles Message-ID: <20000105113856.A739@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG with a buildworld of sources fetched about 6-8 hours ago ... I get a whole lot of trouble with anything that tries to use kvm. Ending up with loads of the following error: link_elf_lookup_symbol: corrupt symbol table bash-2.03$ vmstat -i vmstat: undefined symbols: _cp_time _cnt _boottime _hz _stathz _nchstats _intrnames _eintrnames _intrcnt _eintrcnt _kmemstatistics _bucket _zlist bash-2.03$ top top: nlist failed I get the feeling it's still trying to use /var/db/kvm_kernel.db which hasn't been updated since (iirc) the kernel should directly acuire these symbols from the running kernel itself. (around Dec. 25th 1999) -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 4: 5:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id BE9B814C59 for ; Wed, 5 Jan 2000 04:05:42 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA15950; Wed, 5 Jan 2000 13:05:19 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001050659.XAA64527@harmony.village.org> References: <200001050659.XAA64527@harmony.village.org> Date: Wed, 5 Jan 2000 12:40:31 +0100 To: Warner Losh , William Woods From: Brad Knowles Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-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 11:59 PM -0700 2000/1/4, Warner Losh wrote: > I fear it will be Feb or Mar before I get to it at this rate > since I have little free time. Consulting $$$ takes precidence over > freetime hacking... I'm not one of the affected, but is there any chance a collection could be taken up to help fund this effort at a higher priority? It seems to me that this is precisely the sort of thing that people might be willing pay some money for, and it wouldn't take too much money from too many people before this might start becoming potentially interesting. On a related note, perhaps it might be interesting to start a list of FreeBSD projects that might affect relatively large numbers of people, but which are languishing due to lack of funds on the part of the people who are involved in the implementation process? I don't have any money to just donate to causes like this [0], but I suspect that this is one of those things where we could allow people to contribute in a material fashion, other than either hacking on code or volunteering to be a guinea-pig and testing out code that had been hacked by someone else. It would also allow people to get collections together for those things where a lot of people who would be materially impacted could get small-scale donations together and potentially have a large impact. In fact, you could even get into corporate sponsors & paid support contracts, and potentially start generating some serious money that could be put to good uses. Sorry if I'm re-opening any old wounds, or if this is something that's already being done. However, if that's the case, I'd appreciate pointers to information on this. [0] It's not like I'm a multi-millionaire who got lots of money from a company I founded being bought out from underneath me or going IPO, and then spending all my free time working on FreeBSD kernel issues -- unlike certain other people I could mention. ;-) -- 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 Wed Jan 5 4:29:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id A1F2B14C97 for ; Wed, 5 Jan 2000 04:29:14 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id HAA07699; Wed, 5 Jan 2000 07:29:08 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001051229.HAA07699@blackhelicopters.org> Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: from Dmitry Valdov at "Jan 5, 2000 1:23:26 am" To: dv@dv.ru (Dmitry Valdov) Date: Wed, 5 Jan 2000 07:29:08 -0500 (EST) Cc: 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 Hello, Not that this is an actual fix to the problem, but: The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At least, when I wrote an article on this, it wasn't.) You can probably remove COMPAT_LINUX entirely. (If only the rest of the problems were this easy. :) ==ml > Hi! > > With option COMPAT_LINUX (which present in LINT) make depend fails with: > cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > -D_KERNEL -include opt_global.h -elf -fno-builtin > -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c > ../../i386/linux/linux_genassym.c > genassym -o linux_assym.h linux_genassym.o > genassym:No such file or directory > *** Error code 1 > > Dmitry. > > > > 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 Wed Jan 5 4:37: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from colin.muc.de (colin.muc.de [193.149.48.1]) by hub.freebsd.org (Postfix) with SMTP id ECEF615383 for ; Wed, 5 Jan 2000 04:36:53 -0800 (PST) (envelope-from lutz@tavari.de) Received: from tavari.muc.de ([193.149.49.22]) by colin.muc.de with SMTP id <140591-1>; Wed, 5 Jan 2000 13:36:43 +0100 Received: (from uucp@localhost) by tavari.muc.de (8.8.8/8.8.7) id MAA03905; Wed, 5 Jan 2000 12:31:53 +0100 (CET) Received: from ripley.tavari.muc.de(192.168.42.202), claiming to be "192.168.42.202" via SMTP by smptd, id smtpdGt3903; Wed Jan 5 12:31:47 2000 From: Lutz Albers To: ---- , freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD Message-ID: <2182701833.947075506@[192.168.42.202]> In-Reply-To: <000d01bf56fa$cc7510a0$7f3eb4d0@tcac.net> X-Mailer: Mulberry (Win32) [2.0.0b7, s/n U-301229] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Date: Wed, 5 Jan 2000 13:36:43 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If memory serves me right, ---- said on 2000-01-04 15:29 -0600: > Has anyone gotten Opera beta working under linux emulation? Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as it is linked against these. Keep in mind that this is no beta, but a 'technical preview', many functions are still missing. -- Lutz Albers, lutz@tavari.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 4:42:43 2000 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 AD4FC15366 for ; Wed, 5 Jan 2000 04:42:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id NAA62422 for current@FreeBSD.org; Wed, 5 Jan 2000 13:29:45 +0100 (CET) (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: Wed, 05 Jan 2000 13:29:41 +0100 From: Marcel Moolenaar Message-ID: <38733935.C8691F71@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <3871FC69.C99882E9@scc.nl>, <20000104225739.A865@peotl.tuebingen.netsurf.de> Subject: Re: Proposal: Removing doscmd from the source tree... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Zenker wrote: > > A possibility could be: 1. build it for i386 only, 2. build it via > buildworld without X11, regardless if X11 exists. If I want to use it > with X11, it is interactive and I can make it for X11 by hand - it will > not break on compile runs at some hour at night. I'll commit a fix that will prevent including X when DESTDIR has been set. In practice this means that doscmd will never include X, unless you compile it by hand. This of course implies that you have to compile doscmd by hand every time you do an installworld, given that you want X. I still think doscmd should and can be a port, but I think it helps my argument if I have the port ready to be committed and downloadable for testing. It helps undermine the general objection that doscmd is very dependent on the kernel, which I doubt... If not, it will at least show me that I'm wrong :-) -- 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 Wed Jan 5 4:45:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B126F153A7 for ; Wed, 5 Jan 2000 04:45:29 -0800 (PST) (envelope-from taavi@uninet.ee) Received: by ns.uninet.ee (Postfix, from userid 1001) id D419E25842; Wed, 5 Jan 2000 14:45:24 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by ns.uninet.ee (Postfix) with SMTP id CEE7E14A13; Wed, 5 Jan 2000 14:45:24 +0200 (EET) Date: Wed, 5 Jan 2000 14:45:24 +0200 (EET) From: Taavi Talvik To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: Proposal: Removing doscmd from the source tree... In-Reply-To: <38733935.C8691F71@scc.nl> 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, 5 Jan 2000, Marcel Moolenaar wrote: > Thomas Zenker wrote: > > > > A possibility could be: 1. build it for i386 only, 2. build it via > > buildworld without X11, regardless if X11 exists. If I want to use it > > with X11, it is interactive and I can make it for X11 by hand - it will > > not break on compile runs at some hour at night. > > I'll commit a fix that will prevent including X when DESTDIR has been > set. In practice this means that doscmd will never include X, unless you > compile it by hand. This of course implies that you have to compile > doscmd by hand every time you do an installworld, given that you want X. Maybe knob in /etc/make.conf instead to force compiling with X? best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee Unineti Andmeside AS | phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 4:58:17 2000 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 852A2153A4 for ; Wed, 5 Jan 2000 04:58:15 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 990251C2B; Wed, 5 Jan 2000 07:59:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 942933819; Wed, 5 Jan 2000 07:59:14 -0500 (EST) Date: Wed, 5 Jan 2000 07:59:14 -0500 (EST) From: Bill Fumerola To: Lutz Albers Cc: ---- , freebsd-current@FreeBSD.ORG Subject: Re: Opera Beta and FreeBSD In-Reply-To: <2182701833.947075506@[192.168.42.202]> 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, 5 Jan 2000, Lutz Albers wrote: > Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as > it is linked against these. > > Keep in mind that this is no beta, but a 'technical preview', many > functions are still missing. FWIW, the linux_base port in http://www.FreeBSD.org/~marcel/ works fine, and probably should be committed. I'm running Nutscrape on that port on several different machines and they're all just fine. -- - 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 Wed Jan 5 4:59: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust15.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 128451537E; Wed, 5 Jan 2000 04:59:06 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Wed, 5 Jan 2000 07:59:03 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001050835.JAA35344@freebsd.dk> Message-ID: 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 On Wed, 5 Jan 2000, Soren Schmidt wrote: > Try this patch instead, it should do the right thing.. Since they're functionally the same, sure, I wouldn't mind either way :) > > -Søren > -- 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 Wed Jan 5 5: 1:32 2000 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 E993115332 for ; Wed, 5 Jan 2000 05:01:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id FAA44691; Wed, 5 Jan 2000 05:01:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id FAA28529; Wed, 5 Jan 2000 05:01:26 -0800 (PST) (envelope-from obrien) Date: Wed, 5 Jan 2000 05:01:25 -0800 From: "David O'Brien" To: "Dave J. Boers" Cc: freebsd-current@freebsd.org Subject: Re: compiling libF77/libI77 Message-ID: <20000105050125.A19772@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000104222337.A1426@relativity.student.utwente.nl> <20000104222828.B1426@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000104222828.B1426@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Tue, Jan 04, 2000 at 10:28:28PM +0100 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 Tue, Jan 04, 2000 at 10:28:28PM +0100, Dave J. Boers wrote: > It's funny how I tend to find things out only just _after_ I asked someone If you still need the shared libf2c.so.2 for older binaries, install the latest compat3x distribution. -- -- 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 Jan 5 5: 3:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id D4BCD14E6C for ; Wed, 5 Jan 2000 05:03:44 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA07866; Wed, 5 Jan 2000 08:03:18 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001051303.IAA07866@blackhelicopters.org> Subject: Re: Proposal: Removing doscmd from the source tree... In-Reply-To: from Taavi Talvik at "Jan 5, 2000 2:45:24 pm" To: taavi@uninet.ee (Taavi Talvik) Date: Wed, 5 Jan 2000 08:03:18 -0500 (EST) Cc: marcel@scc.nl, 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 > > > A possibility could be: 1. build it for i386 only, 2. build it via > > > buildworld without X11, regardless if X11 exists. If I want to use it > > > with X11, it is interactive and I can make it for X11 by hand - it will > > > not break on compile runs at some hour at night. > > > > I'll commit a fix that will prevent including X when DESTDIR has been > > set. In practice this means that doscmd will never include X, unless you > > compile it by hand. This of course implies that you have to compile > > doscmd by hand every time you do an installworld, given that you want X. > > Maybe knob in /etc/make.conf instead to force compiling with X? > > best regards, > taavi Actually, several ports give you the option of building with or without X support (i.e., SSH). It would be nice to have a USE_X11 option in /etc/make.conf for doscmd as well as these ports, so you don't have to specify it on the command line while building. Of course, I'd like a pony too. And a pink bike shed. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 5:11:41 2000 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 659421537C for ; Wed, 5 Jan 2000 05:11:26 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id IAA50722; Wed, 5 Jan 2000 08:11:10 -0500 (EST) Date: Wed, 5 Jan 2000 08:11:09 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG Subject: Re: A couple questions regarding pcmcia cards.... In-Reply-To: <200001050703.AAA64580@harmony.village.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 Wed, 5 Jan 2000, Warner Losh wrote: > Last I heard, Matt Dodd had or was waiting for a 574BT and pccard > enviornment to fix the driver. I've got both a 574 and a 575. I'm waiting on my PCIC ISA bridgeboard. :/ Anyone know of a PCI Cardbus bridgeboard? I'd rather not have to get a laptop just so I can play with cardbus. -- | 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 Wed Jan 5 5:11:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 9B9D4153D6 for ; Wed, 5 Jan 2000 05:11:54 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 125qE9-00069M-00; Wed, 5 Jan 2000 13:11:50 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id OAA47568; Wed, 5 Jan 2000 14:11:47 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38734313.2F43D385@scc.nl> Date: Wed, 05 Jan 2000 14:11:47 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Taavi Talvik Cc: current@FreeBSD.org Subject: Re: Proposal: Removing doscmd from the source tree... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Taavi Talvik wrote: > > Maybe knob in /etc/make.conf instead to force compiling with X? > Nah, we don't need to. doscmd doesn't have X support by default (now that I've committed the fix). Recompiling doscmd to get X (given X is installed on the machine of course) is broken but simple enough. If you don't want X, don't recompile doscmd or don't install X. Any other change only adds to the argument of making doscmd a port (or two), IMO. -- 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 Wed Jan 5 5:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 94B53153A4 for ; Wed, 5 Jan 2000 05:24:00 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id LAA76593 for ; Wed, 5 Jan 2000 11:29:38 +0200 (EET) Date: Wed, 5 Jan 2000 11:29:38 +0200 (EET) From: Alexandr Listopad To: freebsd-current@freebsd.org Subject: making release 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. I want to make a release of 4.0-CUR in 3.4-ST. Will it nice idea? Now I cvsuping sources of 4.0. Is there any troubles? And another one question: I don't cvsup "cvs-crypto". Will my release maked? Thanks. ..and sorry for my bad English. ;| P.S. pls reply to me, i'm not currently subscribed. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 5:36: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id CA62A14FF8 for ; Wed, 5 Jan 2000 05:36:02 -0800 (PST) (envelope-from oschonef@TechFak.Uni-Bielefeld.DE) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id OAA01099 for ; Wed, 5 Jan 2000 14:36:01 +0100 (MET) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id OAA10021; Wed, 5 Jan 2000 14:36:00 +0100 Message-Id: <200001051336.OAA10021@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: ifq_maxlen in vx-driver To: freebsd-current@freebsd.org Date: Wed, 5 Jan 2000 14:36:00 +0100 (MET) X-Mailer: ELM [version 2.5 PL2] 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 *! i am using the vx driver in for my two 3c397 boards. when booting i get the following message: vx0 XXX: driver didn't set ifq_maxlen obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the driver. actually, to set this, would be one line in the driver, but unfrotunatly i am not that familiar with the hardware, and do not know, which value this parameter shoul have. maybe, someone knows ... cheers, oliver -- -------------------------------------------------------- And remember: "Life sucks and then you die!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 5:42:44 2000 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 D37C414D6B for ; Wed, 5 Jan 2000 05:42:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA74413 for current@FreeBSD.org; Wed, 5 Jan 2000 14:18:35 +0100 (CET) (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: Wed, 05 Jan 2000 14:18:31 +0100 From: Marcel Moolenaar Message-ID: <387344A7.8122BDB3@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <200001051229.HAA07699@blackhelicopters.org> Subject: Re: options COMPAT_LINUX makes kernel fail to compile Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > least, when I wrote an article on this, it wasn't.) You can probably > remove COMPAT_LINUX entirely. Assuming that you want to use the module of course... -- 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 Wed Jan 5 6: 7: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 3386C1539A for ; Wed, 5 Jan 2000 06:06:58 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 125r5U-0003Dy-00; Wed, 5 Jan 2000 14:06:56 +0000 Date: Wed, 5 Jan 2000 15:06:55 +0100 (CET) From: Marc Schneiders To: Bruce Evans Cc: Ollivier Robert , current@freebsd.org Subject: Re: new man pages 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, 5 Jan 2000, Bruce Evans wrote: > On Wed, 5 Jan 2000, Ollivier Robert wrote: > > > According to Rodney W. Grimes: > > > xntpd was recently renamed ntpd, but the documentation and manual > > > pages was not. > > > > > You'll find the manual page for ntpd with a ``man xntpd''. > > Those are the old man pages. You're not running -current if you have > them :-). > As far as I can see only the command is removed, the xntpd man page is left alone. I still have it. This is current of December 31. [...] -- Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 3:02pm up 5 days, 16:51, load average: 2.18 2.09 2.05 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 6:18:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 4141C14DEA for ; Wed, 5 Jan 2000 06:18:22 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id D72F11F28; Wed, 5 Jan 2000 15:18:15 +0100 (CET) Date: Wed, 5 Jan 2000 15:18:15 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Re: kvm-troubles Message-ID: <20000105151815.A438@shadowmere.student.utwente.nl> References: <20000105113856.A739@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105113856.A739@shadowmere.student.utwente.nl>; from daeron@shadowmere.student.utwente.nl on Wed, Jan 05, 2000 at 11:38:56AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 11:38:56AM +0100, Pascal Hofstee wrote: > with a buildworld of sources fetched about 6-8 hours ago ... I get a whole > lot of trouble with anything that tries to use kvm. > > Ending up with loads of the following error: > link_elf_lookup_symbol: corrupt symbol table > > bash-2.03$ vmstat -i > vmstat: undefined symbols: > _cp_time _cnt _boottime _hz _stathz _nchstats _intrnames _eintrnames > _intrcnt _eintrcnt _kmemstatistics _bucket _zlist > > > bash-2.03$ top > top: nlist failed > > > I get the feeling it's still trying to use /var/db/kvm_kernel.db which > hasn't been updated since (iirc) the kernel should directly acuire these > symbols from the running kernel itself. (around Dec. 25th 1999) Ok ... either this problem has been solved in the source-code already. Or i just had to do a config -r on my kernel configuration first. Either way ... it's working again. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 7: 0:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 75F7D153E6 for ; Wed, 5 Jan 2000 07:00:53 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id HAA45320; Wed, 5 Jan 2000 07:00:52 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id HAA12904; Wed, 5 Jan 2000 07:00:51 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001051500.HAA12904@realtime.exit.com> Subject: Re: A couple questions regarding pcmcia cards.... In-Reply-To: <200001050703.AAA64580@harmony.village.org> from Warner Losh at "Jan 5, 2000 00:03:15 am" To: imp@village.org (Warner Losh) Date: Wed, 5 Jan 2000 07:00:51 -0800 (PST) Cc: frank@exit.com, freebsd@cybcon.com (William Woods), freebsd-current@FreeBSD.ORG Reply-To: frank@exit.com 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 Warner Losh wrote: > In message <200001050642.WAA05876@realtime.exit.com> Frank Mayhar writes: > : Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's > : a bug somewhere in the driver. I have one of _those_, too, having read the > : same thing you did. > > Last I heard, Matt Dodd had or was waiting for a 574BT and pccard > enviornment to fix the driver. He's got both the card and the documentation, courtesy of Terry Murphy at 3Com and my efforts to that end. > I have a 3CCFE575CT sitting here on my desk right now as a gentile > reminder to work on pccard/cardbus stuff :-). Is that one that Matt sent you? If so, that's the result of the same effort. Else Matt has one, too. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 7: 1:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 23DB9153DF; Wed, 5 Jan 2000 07:00:23 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id QAA33046; Wed, 5 Jan 2000 16:57:58 +0200 (EET) Date: Wed, 5 Jan 2000 16:57:58 +0200 (EET) From: Alexandr Listopad To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: making release 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... marc.s>Have a look at : marc.s> marc.s>http://www.external.org/freebsd/current.html marc.s> marc.s>Worked fine for me. ...but it not what do I mean... I need to make RELEASE (ftp-like). I know that I need a FULL CVS tree as handbook wrote: --- Second, you have to have the whole CVS repository at hand. To get this ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ you can use CVSUP but in your supfile set the release name to cvs and remove any tag or date fields: --- but it is so difficult for me (14.4Kbit/s - our I-net... ;/) Did there anybody who can help me? I have full src-es, cvsuped today. My configs is: ==== *default host=cvsup2.ua.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_3 *default delete use-rel-suffix doc-all src-base src-bin src-contrib src-etc src-gnu src-include src-lib src-libexec src-release src-sbin src-share src-sys src-usrbin src-usrsbin ==== As you can see I have not all sources... Did it wrong for making release? Did I certainly need src-all src-secure src-eBones for making release? Can I make my custom release? Is there another way for making release? Because a "have to have the whole CVS repository at hand" VERY difficult for me. Please... help me! Thanks. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 7:12:52 2000 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 72B25154B2 for ; Wed, 5 Jan 2000 07:12:42 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id QAA03014 for current@FreeBSD.org; Wed, 5 Jan 2000 16:12:19 +0100 (CET) (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: Wed, 05 Jan 2000 16:12:11 +0100 From: Marcel Moolenaar Message-ID: <38735F4B.D6CDDFF6@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: HEADS UP: Crossbuilding world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After a couple of weeks (or is it months already) of reorganizing the build process, I've come to the point where I can say that I'm ready -- well, sort of. I'm cross-building with two patches that are in the pipeline of being committed. I've made the patches available for those who can't or won't wait for the patches (or equivalent fixes) to be committed: http://www.freebsd.org/~marcel/crossbuild.diff NOTE: gnu/usr.bin/cc/cc_tools/Makefile also needs to be fixed. It creates the wrong dependencies which breaks a buildworld with -DNOCLEAN at the moment. The workaround is to remove the '.depend' file in the object directory before starting the buildworld. Of course this doesn't mean that when that is fixed, I'm finished. At least the following tasks still need to be done: o Finish cross-building kernels. o Fix installworld so that it doesn't execute any of the binaries previously installed. This solves the upgrade problem in which the kernel isn't capable (yet) of running the binaries. o Create a 'kernel' target to make kernels. This target is to be used by the upgrade process. o Redefine the current 'upgrade' target to make world and kernel, followed by an install for world and kernel. It ends with a reboot. This roughly describes what I'm going to do next wrt to the build process. If you think I should be doing things differently, this is the time to speak up... preferably with diffs :-) \begin{talking to myself} I have to finish those linux ports and PRs as well. Not to forget mumble mumble, especially mumble mumble mumble... \end{mumble mumble} -- 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 Wed Jan 5 7:12:56 2000 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 5060C1545D for ; Wed, 5 Jan 2000 07:12:46 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id KAA51743; Wed, 5 Jan 2000 10:12:43 -0500 (EST) Date: Wed, 5 Jan 2000 10:12:43 -0500 (EST) From: "Matthew N. Dodd" To: Oliver Schonefeld Cc: freebsd-current@FreeBSD.ORG Subject: Re: ifq_maxlen in vx-driver In-Reply-To: <200001051336.OAA10021@frizzantino.TechFak.Uni-Bielefeld.DE> 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, 5 Jan 2000, Oliver Schonefeld wrote: > i am using the vx driver in for my two 3c397 boards. > when booting i get the following message: > > vx0 XXX: driver didn't set ifq_maxlen > > obviosly the ifq_maxlen is not set in the eisa nor in the pci version > in the driver. actually, to set this, would be one line in the driver, > but unfrotunatly i am not that familiar with the hardware, and do not > know, which value this parameter shoul have. maybe, someone knows ... This is just a warning message; it doesn't hurt anything. I'll deal with if_vx at some point; it will get fixed with if_ed and if_vx get collided at high speed. -- | 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 Wed Jan 5 7:13:48 2000 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 A186914BF1 for ; Wed, 5 Jan 2000 07:13:45 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id KAA51760; Wed, 5 Jan 2000 10:13:38 -0500 (EST) Date: Wed, 5 Jan 2000 10:13:37 -0500 (EST) From: "Matthew N. Dodd" To: Frank Mayhar Cc: Warner Losh , William Woods , freebsd-current@FreeBSD.ORG Subject: Re: A couple questions regarding pcmcia cards.... In-Reply-To: <200001051500.HAA12904@realtime.exit.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 Wed, 5 Jan 2000, Frank Mayhar wrote: > > I have a 3CCFE575CT sitting here on my desk right now as a gentile > > reminder to work on pccard/cardbus stuff :-). > > Is that one that Matt sent you? If so, that's the result of the same > effort. Else Matt has one, too. I offered him mine but he said he already had one. -- | 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 Wed Jan 5 7:25: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (dialfwn11.fwn.rug.nl [129.125.32.161]) by hub.freebsd.org (Postfix) with ESMTP id 191C6153EE for ; Wed, 5 Jan 2000 07:24:56 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id MAA02123; Tue, 4 Jan 2000 12:11:16 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 4 Jan 2000 12:11:16 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Vallo Kallaste Cc: Alex , freebsd-current@FreeBSD.ORG Subject: Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA)) In-Reply-To: <20000104124628.A40560@myhakas.matti.ee> 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 > > ....and I apologise for wrongfully accusing it. The panic is in fact > > caused by newpcm (Cameron CC'd). DDB trace can be provided upon request > > (is there a way to save it into a file instead of having to write it > > down on a piece of paper?) > > Sure. Hook up serial console or some terminal program to appropriate > serial port using null-modem cable, then rebuild your kernel and boot > with right flag. Look at sys/i386/LINT, man sio(4) and man boot(8). Or, if the panic happens after rc.conf has been run / you can log in, set the dump device to something sensible. From DDB type panic. When the system boots up again, you type savecore /some/dir and possibly copy the debugging kernel from /sys/compile/KERNELNAME to /some/dir/kernel.0 as well. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 7:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id F236315366 for ; Wed, 5 Jan 2000 07:49:29 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA29555; Wed, 5 Jan 2000 10:49:03 -0500 (EST) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA13088; Wed, 5 Jan 2000 10:49:06 -0500 (EST) Received: from localhost (culverk@localhost) by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA13081; Wed, 5 Jan 2000 10:49:05 -0500 (EST) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Wed, 5 Jan 2000 10:49:05 -0500 (EST) From: Kenneth Wayne Culver To: Michael Lucas Cc: Dmitry Valdov , current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: <200001051229.HAA07699@blackhelicopters.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 Well, just make sure that you load the linux compatibility kernel module though. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 5 Jan 2000, Michael Lucas wrote: > Hello, > > Not that this is an actual fix to the problem, but: > > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > least, when I wrote an article on this, it wasn't.) You can probably > remove COMPAT_LINUX entirely. > > (If only the rest of the problems were this easy. :) > > ==ml > > > Hi! > > > > With option COMPAT_LINUX (which present in LINT) make depend fails with: > > cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > > -D_KERNEL -include opt_global.h -elf -fno-builtin > > -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c > > ../../i386/linux/linux_genassym.c > > genassym -o linux_assym.h linux_genassym.o > > genassym:No such file or directory > > *** Error code 1 > > > > Dmitry. > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 7:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 8EF8E15409 for ; Wed, 5 Jan 2000 07:52:56 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA77344; Wed, 5 Jan 2000 09:52:43 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 5 Jan 2000 09:52:43 -0600 (CST) From: David Scheidt To: Michael Lucas Cc: Dmitry Valdov , current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: <200001051229.HAA07699@blackhelicopters.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 Wed, 5 Jan 2000, Michael Lucas wrote: > Hello, > > Not that this is an actual fix to the problem, but: > > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > least, when I wrote an article on this, it wasn't.) You can probably > remove COMPAT_LINUX entirely. I use COMPAT_LINUX because I make kernels more frequently then I make world or modules. I get fewer panics that way. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 8:39:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 26A5E1517E for ; Wed, 5 Jan 2000 08:39:56 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id LAA00472; Wed, 5 Jan 2000 11:38:38 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 05 Jan 2000 11:38:38 -0500 (EST) From: will andrews To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-00 William Woods wrote: > ok, now...to get it working........... > > ideas? I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is 4.0-CURRENT as of September 29, right before Matt Dodd's if_ep.c commit that moved towards newcard implementation. You will not be able to use it on any later version of 4.0-CURRENT as far as I know. And I know it does not work with 3.3-RELEASE. You may have better luck with 3.4-RELEASE, but I wouldn't know. /me waits for Matt to fix if_ep *patiently* ;-) I know it's coming soon. *twiddle thumbs* -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 8:40:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 6CE961540E for ; Wed, 5 Jan 2000 08:40:40 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id LAA00472; Wed, 5 Jan 2000 11:38:38 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 05 Jan 2000 11:38:38 -0500 (EST) From: will andrews To: William Woods Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG, Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-00 William Woods wrote: > ok, now...to get it working........... > > ideas? I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is 4.0-CURRENT as of September 29, right before Matt Dodd's if_ep.c commit that moved towards newcard implementation. You will not be able to use it on any later version of 4.0-CURRENT as far as I know. And I know it does not work with 3.3-RELEASE. You may have better luck with 3.4-RELEASE, but I wouldn't know. /me waits for Matt to fix if_ep *patiently* ;-) I know it's coming soon. *twiddle thumbs* -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 8:50:46 2000 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 BFFB51517E for ; Wed, 5 Jan 2000 08:50:43 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id RAA36735; Wed, 5 Jan 2000 17:50:40 +0100 (CET) (envelope-from olli) Date: Wed, 5 Jan 2000 17:50:40 +0100 (CET) Message-Id: <200001051650.RAA36735@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... X-Newsgroups: list.freebsd-current In-Reply-To: <84vfjb$18nn$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Michael Lucas wrote in list.freebsd-current: > Actually, several ports give you the option of building with or > without X support (i.e., SSH). It would be nice to have a USE_X11 > option in /etc/make.conf for doscmd as well as these ports, so you > don't have to specify it on the command line while building. > > Of course, I'd like a pony too. And a pink bike shed. Me too! :) I'm currently trying to fix the POV-Ray port. It could be built with and without X11 support, too, and it would be very useful to have a way to let the user choose. A USE_X11 knob in make.conf would be great. 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 Wed Jan 5 9: 6:59 2000 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 A870B1517E for ; Wed, 5 Jan 2000 09:06:56 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA06678; Wed, 5 Jan 2000 10:06:54 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA68226; Wed, 5 Jan 2000 10:06:54 -0700 (MST) Message-Id: <200001051706.KAA68226@harmony.village.org> To: frank@exit.com Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd@cybcon.com (William Woods), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 07:00:51 PST." <200001051500.HAA12904@realtime.exit.com> References: <200001051500.HAA12904@realtime.exit.com> Date: Wed, 05 Jan 2000 10:06:54 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051500.HAA12904@realtime.exit.com> Frank Mayhar writes: : He's got both the card and the documentation, courtesy of Terry Murphy at : 3Com and my efforts to that end. Cool. : > I have a 3CCFE575CT sitting here on my desk right now as a gentile : > reminder to work on pccard/cardbus stuff :-). : : Is that one that Matt sent you? If so, that's the result of the same effort. : Else Matt has one, too. No. FreeBSD Inc and/or Walnut creek bought mine. I'll keep your name in mind if I need any docs for it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 9:22:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7475D15326 for ; Wed, 5 Jan 2000 09:21:50 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA20036; Wed, 5 Jan 2000 18:21:57 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001051721.SAA20036@info.iet.unipi.it> Subject: rlogin from 3.X to 4.0 problem... To: current@freebsd.org Date: Wed, 5 Jan 2000 18:21:56 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: > rlogin bsd4 assword:hey this is great! why is the initial 'P' missing, and the password echoed ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 9:33:50 2000 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 98A4915420 for ; Wed, 5 Jan 2000 09:33:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA26381; Wed, 5 Jan 2000 18:33:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: rlogin from 3.X to 4.0 problem... In-reply-to: Your message of "Wed, 05 Jan 2000 18:21:56 +0100." <200001051721.SAA20036@info.iet.unipi.it> Date: Wed, 05 Jan 2000 18:33:40 +0100 Message-ID: <26379.947093620@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051721.SAA20036@info.iet.unipi.it>, Luigi Rizzo writes: >With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: > > > rlogin bsd4 > assword:hey this is great! > >why is the initial 'P' missing, and the password echoed ? Bug in /etc/pam.conf I belive markm is on the case. -- 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 Jan 5 10:14: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 00B2915433 for ; Wed, 5 Jan 2000 10:13:58 -0800 (PST) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.9.3/8.9.3) with ESMTP id TAA07600; Wed, 5 Jan 2000 19:13:55 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id TAA18503; Wed, 5 Jan 2000 19:13:54 +0100 (MET) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.10 ]) with ESMTP id TAA16707; Wed, 5 Jan 2000 19:13:54 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id SAA37971; Wed, 5 Jan 2000 18:13:53 GMT (envelope-from ust) Date: Wed, 5 Jan 2000 19:13:53 +0100 From: Udo Schweigert To: Mark Murray Cc: Luoqi Chen , freebsd-current@FreeBSD.ORG Subject: Re: Problem with rlogin and /etc/pam.conf Message-ID: <20000105191353.A37946@alaska.cert.siemens.de> Mail-Followup-To: Mark Murray , Luoqi Chen , freebsd-current@FreeBSD.ORG References: <200001040557.AAA07921@lor.watermarkgroup.com> <200001040610.e046APw12146@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001040610.e046APw12146@gratis.grondar.za>; from mark@grondar.za on Tue, Jan 04, 2000 at 08:10:24AM +0200 X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 04, 2000 at 08:10:24 +0200, Mark Murray wrote: > > My work around to this problem is to add the following line to /etc/pam.conf, > > rshd auth sufficient pam_deny.so > > What timing! I just committed something that looks identical! > Great. That fixed it for me. Also I think this should be considered for MFC since the /etc/pam.conf from -current works for me under -stable and makes XFree86 with PAM support working. Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 41166 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:17:58 2000 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 5F5DE1545A for ; Wed, 5 Jan 2000 10:17:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA06971; Wed, 5 Jan 2000 11:17:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA68678; Wed, 5 Jan 2000 11:17:43 -0700 (MST) Message-Id: <200001051817.LAA68678@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: A couple questions regarding pcmcia cards.... Cc: frank@exit.com, William Woods , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 08:11:09 EST." References: Date: Wed, 05 Jan 2000 11:17:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Anyone know of a PCI Cardbus bridgeboard? I'd rather not have to get a : laptop just so I can play with cardbus. I've seen two, both of which seem to be unavailable. One is at a URL that I've lost and the other was made by compaq and was available for their desktop machines. CDW used to carry this, but it is unavailable now as well. I'll have to dig up the URL that I've lost (it is in my netscape history file, I'm sure) since they talked about availablities after the first of the year which is why I blew them off before (it was in October or so I was looking). I'll send you something if I can find it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:18: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 2D5421543A for ; Wed, 5 Jan 2000 10:18:00 -0800 (PST) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id TAA10471; Wed, 5 Jan 2000 19:17:53 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id TAA15234; Wed, 5 Jan 2000 19:17:53 +0100 (MET) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.10 ]) with ESMTP id TAA16721; Wed, 5 Jan 2000 19:17:53 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id SAA38012; Wed, 5 Jan 2000 18:17:52 GMT (envelope-from ust) Date: Wed, 5 Jan 2000 19:17:52 +0100 From: Udo Schweigert To: Poul-Henning Kamp Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: rlogin from 3.X to 4.0 problem... Message-ID: <20000105191752.B37946@alaska.cert.siemens.de> References: <200001051721.SAA20036@info.iet.unipi.it> <26379.947093620@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <26379.947093620@critter.freebsd.dk>; from phk@critter.freebsd.dk on Wed, Jan 05, 2000 at 06:33:40PM +0100 X-Operating-System: FreeBSD 3.4-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 18:33:40 +0100, Poul-Henning Kamp wrote: > In message <200001051721.SAA20036@info.iet.unipi.it>, Luigi Rizzo writes: > >With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: > > > > > rlogin bsd4 > > assword:hey this is great! > > > >why is the initial 'P' missing, and the password echoed ? > > Bug in /etc/pam.conf > Fixed with pam.conf version 1.4. Regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 41166 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:18:33 2000 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 C7C7015492 for ; Wed, 5 Jan 2000 10:18:29 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DCF741CA0; Tue, 5 Jan 1999 15:22:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: David Scheidt Cc: Michael Lucas , Dmitry Valdov , current@FreeBSD.ORG Subject: Re: options COMPAT_LINUX makes kernel fail to compile In-Reply-To: Message from David Scheidt of "Wed, 05 Jan 2000 09:52:43 CST." Date: Tue, 05 Jan 1999 15:22:10 +0800 From: Peter Wemm Message-Id: <19990105072210.DCF741CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > On Wed, 5 Jan 2000, Michael Lucas wrote: > > > Hello, > > > > Not that this is an actual fix to the problem, but: > > > > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > > least, when I wrote an article on this, it wasn't.) You can probably > > remove COMPAT_LINUX entirely. > > I use COMPAT_LINUX because I make kernels more frequently then I make world > or modules. I get fewer panics that way. > > David Scheidt You should definately use a static kernel without modules if you are tracking -current and rebuilding regularly. It is too easy to shoot yourself in the foot by getting /modules and the kernel out of sync while the internal interfaces are still changing. Using kld's to develop drivers is different. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:19:41 2000 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 47ECA15433 for ; Wed, 5 Jan 2000 10:19:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA06986; Wed, 5 Jan 2000 11:19:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA68704; Wed, 5 Jan 2000 11:19:32 -0700 (MST) Message-Id: <200001051819.LAA68704@harmony.village.org> To: will andrews Subject: Re: A couple questions regarding pcmcia cards.... Cc: William Woods , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 11:38:38 EST." References: Date: Wed, 05 Jan 2000 11:19:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message will andrews writes: : I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is What does your pccard.conf entry look like for it? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:22:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id A459415033 for ; Wed, 5 Jan 2000 10:22:29 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3b-38.cybcon.com [205.147.75.103]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id KAA04369; Wed, 5 Jan 2000 10:22:06 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001051819.LAA68704@harmony.village.org> Date: Wed, 05 Jan 2000 10:24:04 -0800 (PST) From: William Woods To: Warner Losh Subject: Re: A couple questions regarding pcmcia cards.... Cc: freebsd-current@FreeBSD.ORG, will andrews Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the pccard.conf entry: # 3Com Fast Etherlink 3C574TX card "3Com" "Megahertz 574B" config 0x1 "ep0" ? 0x1 insert echo 3Com Fast Etherlink 3C574B inserted insert /etc/pccard_ether ep0 remove echo 3Com Fast Etherlink This is on a 3.4 -stable system On 05-Jan-00 Warner Losh wrote: > In message will andrews > writes: >: I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that >: is > > What does your pccard.conf entry look like for it? > > Warner ---------------------------------- E-Mail: William Woods Date: 05-Jan-00 Time: 10:23:02 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id EED2E153FB for ; Wed, 5 Jan 2000 10:24:25 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA22026 for freebsd-current@freebsd.org; Wed, 5 Jan 2000 10:11:24 -0800 (PST) From: Archie Cobbs Message-Id: <200001051811.KAA22026@bubba.whistle.com> Subject: Boot serial console all blanks To: freebsd-current@freebsd.org Date: Wed, 5 Jan 2000 10:11:23 -0800 (PST) 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 Has anyone else seen this problem? The 2nd and 3rd stage boot loader output to the serial port is all blanks. That is, every character is output as a blank -- you can see them printing, and see the 10 second autoboot messages, but they're all space characters. Thanks for any insights. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 1169415762 for ; Wed, 5 Jan 2000 10:36:20 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id KAA25549 for freebsd-current@freebsd.org; Wed, 5 Jan 2000 10:32:12 -0800 (PST) Date: Wed, 5 Jan 2000 10:32:12 -0800 (PST) From: Jim Shankland Message-Id: <200001051832.KAA25549@biggusdiskus.flyingfox.com> To: freebsd-current@freebsd.org Subject: Re: Boot serial console all blanks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > The 2nd and 3rd stage boot loader output to the serial port > is all blanks. That is, every character is output as a > blank -- you can see them printing, and see the 10 second > autoboot messages, but they're all space characters. Sorry, I'm drawing a blank. (Carry on; moment of weakness.) Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 10:46:41 2000 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 ED4141543C for ; Wed, 5 Jan 2000 10:46:29 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA07145; Wed, 5 Jan 2000 11:46:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA69034; Wed, 5 Jan 2000 11:46:25 -0700 (MST) Message-Id: <200001051846.LAA69034@harmony.village.org> To: Archie Cobbs Subject: Re: Boot serial console all blanks Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 10:11:23 PST." <200001051811.KAA22026@bubba.whistle.com> References: <200001051811.KAA22026@bubba.whistle.com> Date: Wed, 05 Jan 2000 11:46:25 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051811.KAA22026@bubba.whistle.com> Archie Cobbs writes: : The 2nd and 3rd stage boot loader output to the serial port is all : blanks. That is, every character is output as a blank -- you can : see them printing, and see the 10 second autoboot messages, but : they're all space characters. I have seen this when I've had the baud rate wrong. On my development box that has a serial console, I seem to recall that I needed to build special bootblocks to run at 115200. Try connecting a serial line analyser to the line if you have it. Or a oscope will do in a pinch. Or try the default baud rate of 9600. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 11: 8: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id E5AC515469 for ; Wed, 5 Jan 2000 11:08:00 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA22300; Wed, 5 Jan 2000 11:07:57 -0800 (PST) From: Archie Cobbs Message-Id: <200001051907.LAA22300@bubba.whistle.com> Subject: Re: Boot serial console all blanks In-Reply-To: <200001051846.LAA69034@harmony.village.org> from Warner Losh at "Jan 5, 2000 11:46:25 am" To: imp@village.org (Warner Losh) Date: Wed, 5 Jan 2000 11:07:57 -0800 (PST) Cc: 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 Warner Losh writes: > : The 2nd and 3rd stage boot loader output to the serial port is all > : blanks. That is, every character is output as a blank -- you can > : see them printing, and see the 10 second autoboot messages, but > : they're all space characters. > > I have seen this when I've had the baud rate wrong. On my development > box that has a serial console, I seem to recall that I needed to build > special bootblocks to run at 115200. > > Try connecting a serial line analyser to the line if you have it. Or > a oscope will do in a pinch. Or try the default baud rate of 9600. I am doing 9600 baud.. also, this is a slightly abnormal setup, using the old boot0/boot1 bootblocks (because it's an InterJet) with /kernel hardlinked to 3.4-REL /boot/loader (so I can boot an ELF kernel). The old bootblocks print normally, then /boot/loader prints all spaces, then when the kernel itself boots it prints normally again. Everything seems to be printing at the same baud rate (9600). Maybe the old boot blocks are confusing the loader in the way they are configuring the serial port.. ? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 11:11:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 494E31541E; Wed, 5 Jan 2000 11:11:18 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas4-46-6.dial.proxad.net [212.27.46.6]) by postfix2.free.fr (Postfix) with ESMTP id 3F72A7450A; Wed, 5 Jan 2000 20:11:16 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id VAA00866; Tue, 4 Jan 2000 21:00:15 +0100 (CET) (envelope-from nsouch) Message-ID: <20000104210015.63255@breizh.free.fr> Date: Tue, 4 Jan 2000 21:00:15 +0100 From: Nicolas Souchu To: Maxim Sobolev Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3870F784.2B1E8126@altavista.net>; from Maxim Sobolev on Mon, Jan 03, 2000 at 09:24:52PM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: > >Nicolas Souchu wrote: > >> Hi there! >> >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current >> >> A major ppbus(4) release is available for beta-testing. > >Good work! Now plip, which has been broken for ages, works perfectly - no more >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X >and NFS working over plip line, things which was impossible with oldppbus. Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) in you MACHINE config file would have done the job. > >Count on my vote to commit it before branch split because IMHO it should be >considered as a bugfix rather that a new feature. > >-Maxim > Nicholas -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Wed Jan 5 11:44:17 2000 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 D3C6315459; Wed, 5 Jan 2000 11:44:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA28156; Wed, 5 Jan 2000 11:44:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: committers@freebsd.org Cc: current@freebsd.org Reply-To: committers@freebsd.org Subject: 4.0 code freeze scheduled for Jan 15th Date: Wed, 05 Jan 2000 11:44:06 -0800 Message-ID: <28153.947101446@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And given that we've already slipped from December 15th, I think you can treat this as a pretty hard deadline, to be further slipped only grudgingly and in response to clear and dire need. 10 days, folks! Make 'em count.. :) The code freeze will last for 15 days, during which time the 4.0 snapshot server (current.freebsd.org) will be cranking out its daily snapshots (and, in the last half of the release cycle, ISO images as well). There will be an additional 10 days following 4.0-RELEASE before the final CD images are made, it being our goal to get the bugs worked out of the net release before the CDs are made in the future. This will result in some additional lag to CD customers, but they'll also get a product with the sharp edges filed off in return for the delay and I think it's worth-while since CDs are a lot harder to update than FTP sites. :-) If someone would care to volunteer an Alpha which has good network connectivity and enough "oomph" to create a full release every night, I'd also be happy to drag the Alpha architecture into this process of doing some actual release QA by porting my snapshot building scripts over and starting them up. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 11:50: 9 2000 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 B25DB14CA5; Wed, 5 Jan 2000 11:50:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA48762; Wed, 5 Jan 2000 11:50:03 -0800 (PST) (envelope-from dillon) Date: Wed, 5 Jan 2000 11:50:03 -0800 (PST) From: Matthew Dillon Message-Id: <200001051950.LAA48762@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hallelujah! Guys, lets try to make this the most stable .0 release ever! -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 Wed Jan 5 12:26:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id D81BC1519F; Wed, 5 Jan 2000 12:26:04 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id PAA61728; Wed, 5 Jan 2000 15:26:00 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001052026.PAA61728@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: committers@FreeBSD.ORG Cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> In-reply-to: Your message of "Wed, 05 Jan 2000 11:44:06 PST." <28153.947101446@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jan 2000 15:26:00 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will we try to include the remaining KAME IPv6 integration into 4.0 before the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and some applications. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 12:35:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id EC8CC1549C; Wed, 5 Jan 2000 12:35:10 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id PAA23426; Wed, 5 Jan 2000 15:34:57 -0500 (EST) Date: Wed, 5 Jan 2000 15:34:57 -0500 From: Christian Kuhtz To: "Louis A. Mamakos" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000105153457.H22835@ns1.arch.bellsouth.net> References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <200001052026.PAA61728@whizzo.transsys.com>; from Louis A. Mamakos on Wed, Jan 05, 2000 at 03:26:00PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 03:26:00PM -0500, Louis A. Mamakos wrote: > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > some applications. I second that desire. Cheers, Chris -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 12:40:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from abc.123.org (123.org [195.244.241.123]) by hub.freebsd.org (Postfix) with ESMTP id F27831551D; Wed, 5 Jan 2000 12:39:56 -0800 (PST) (envelope-from k@abc.123.org) Received: (from k@localhost) by abc.123.org (8.9.3/8.9.3) id VAA02110; Wed, 5 Jan 2000 21:39:31 +0100 (CET) (envelope-from k) Date: Wed, 5 Jan 2000 21:39:30 +0100 From: Kai Voigt To: "Louis A. Mamakos" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000105213930.C751@abc.123.org> References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001052026.PAA61728@whizzo.transsys.com> Organization: 123.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > some applications. IPv6 is a very complex area and I believe that a -RELEASE should come with both a clean IPv6 stack and working userland tools. When looking at Linux and Solaris, they also lack a usable IPv6 support when it comes to userland tools. A lot of things need to be modified: ifconfig, route, ipfw, tcpd, ... and all the client/server tools you can find in /etc/inetd.conf I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it will be a major item for this year. Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 12:50:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-107.rp-plus.de [149.221.237.107]) by hub.freebsd.org (Postfix) with ESMTP id 3D05D15467 for ; Wed, 5 Jan 2000 12:50:22 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id D97FDAB8D; Wed, 5 Jan 2000 21:50:25 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id VAA05633; Wed, 5 Jan 2000 21:51:23 +0100 (CET) (envelope-from alex) Date: Wed, 5 Jan 2000 21:51:23 +0100 From: Alexander Langer To: Brian Somers Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: date(1) and -v-1m Message-ID: <20000105215123.F4563@cichlids.cichlids.com> Mail-Followup-To: Brian Somers , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org References: <200001040150.BAA03280@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001040150.BAA03280@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Tue, Jan 04, 2000 at 01:50:12AM +0000 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Brian Somers (brian@Awfulhak.org): > > Do we want an additional option? (I want :-)) > I certainly wouldn't object to -V doing the same as -v but rounding > down.... this could also decide how to behave when a -v adjusts the > time onto a non-existent time (say 1:30 when the clocks go forward). Ok. I start work :-) Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 12:50:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 0CF4315717; Wed, 5 Jan 2000 12:50:53 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA66416; Wed, 5 Jan 2000 15:50:46 -0500 (EST) Date: Wed, 5 Jan 2000 15:50:46 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: committers@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <28153.947101446@zippy.cdrom.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 Wed, 5 Jan 2000, Jordan K. Hubbard wrote: > And given that we've already slipped from December 15th, I think you > can treat this as a pretty hard deadline, to be further slipped only > grudgingly and in response to clear and dire need. > > 10 days, folks! Make 'em count.. :) > I don't suppose there is any chance that kern/15251 might be closed before then. It adds unsigned support to sysctl(8) so it doesn't report bogus numbers. It's just a minor detail, but it wouldn't take but a moment to fix. I'de commit it myself, but... ;) Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 12:52:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 217E5158D9; Wed, 5 Jan 2000 12:52:39 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id PAA23691; Wed, 5 Jan 2000 15:52:09 -0500 (EST) Date: Wed, 5 Jan 2000 15:52:09 -0500 From: Christian Kuhtz To: Kai Voigt Cc: "Louis A. Mamakos" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000105155209.J22835@ns1.arch.bellsouth.net> References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> <20000105213930.C751@abc.123.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <20000105213930.C751@abc.123.org>; from Kai Voigt on Wed, Jan 05, 2000 at 09:39:30PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 09:39:30PM +0100, Kai Voigt wrote: > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > > some applications. > > IPv6 is a very complex area and I believe that a -RELEASE should come with > both a clean IPv6 stack and working userland tools. When looking at > Linux and Solaris, they also lack a usable IPv6 support when it comes > to userland tools. Really. IPv6 code is in the 2.2 release & 2.3 development kernels (albeit flagged as experimental). And works quite well, and is being used on the 6bone and other IPv6 testbeds. So, what exactly do you mean with your statement? Would you care to qualify your remark? I don't consider it fair to throw Solaris into the mix isn't fair because it's a different beast considering the availability and maintenance of the source. You're comparing apples with oranges here. Nobody expects IPv6 to be particularly pretty, but it needs to make it into the regular tree. Why not for the 4.0 release. For example, Cisco's IPv6 IOS train isn't pretty, but it works. And has been brought up to their most current code train almost a year ago, if I recall correctly. If it doesn't get in now, it will be a very long time before a major release will come about. And it's not going to get any prettier if nobody has exposure to it. > I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it > will be a major item for this year. I think that's not good enough. Nobody says it has to be turned on by default, but it needs to make it into the train as a regular component to allow it to get more exposure. Cheers, Chris -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 13:16:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102]) by hub.freebsd.org (Postfix) with ESMTP id D32E315078; Wed, 5 Jan 2000 13:16:09 -0800 (PST) (envelope-from michael.waite@compaq.com) Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345) id C0E4114D; Wed, 5 Jan 2000 16:16:07 -0500 (EST) Received: from exctay-gh02.tay.cpqcorp.net (exctay-gh02.tay.cpqcorp.net [16.103.129.52]) by zmamail02.zma.compaq.com (Postfix) with ESMTP id B5EF53BB; Wed, 5 Jan 2000 16:16:07 -0500 (EST) Received: by exctay-gh02.tay.cpqcorp.net with Internet Mail Service (5.5.2650.21) id ; Wed, 5 Jan 2000 16:16:06 -0500 Message-ID: <212CC57E84B8D111AD780000F84AA04906963DD8@mroexc2.tay.dec.com> From: "Waite, Michael" To: "'jkh@zippy.cdrom.com'" Cc: current@freebsd.org, "'committers@freebsd.org'" Subject: RE: 4.0 code freeze scheduled for Jan 15th Date: Wed, 5 Jan 2000 16:16:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What kind of an Alpha would you like? ----Mike Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com > ---------- > From: Jordan K. Hubbard[SMTP:jkh@zippy.cdrom.com] > Reply To: committers@freebsd.org > Sent: Wednesday, January 05, 2000 2:44 PM > To: committers@freebsd.org > Cc: current@freebsd.org > Subject: 4.0 code freeze scheduled for Jan 15th > > And given that we've already slipped from December 15th, I think you > can treat this as a pretty hard deadline, to be further slipped only > grudgingly and in response to clear and dire need. > > 10 days, folks! Make 'em count.. :) > > The code freeze will last for 15 days, during which time the 4.0 > snapshot server (current.freebsd.org) will be cranking out its daily > snapshots (and, in the last half of the release cycle, ISO images as > well). There will be an additional 10 days following 4.0-RELEASE > before the final CD images are made, it being our goal to get the bugs > worked out of the net release before the CDs are made in the future. > This will result in some additional lag to CD customers, but they'll > also get a product with the sharp edges filed off in return for the > delay and I think it's worth-while since CDs are a lot harder to > update than FTP sites. :-) > > If someone would care to volunteer an Alpha which has good network > connectivity and enough "oomph" to create a full release every night, > I'd also be happy to drag the Alpha architecture into this process of > doing some actual release QA by porting my snapshot building scripts > over and starting them 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 Wed Jan 5 13:38:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from fep04-svc.mail.telepac.pt (fep04-svc.mail.telepac.pt [194.65.5.203]) by hub.freebsd.org (Postfix) with ESMTP id 1EDE615365 for ; Wed, 5 Jan 2000 13:38:11 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([194.65.204.111]) by fep04-svc.mail.telepac.pt (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000105214030.ZOOB9384.fep04-svc.mail.telepac.pt@manecao.tafkap.priv> for ; Wed, 5 Jan 2000 21:40:30 +0000 Content-Length: 1299 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Date: Wed, 05 Jan 2000 21:37:40 -0000 (GMT) From: Joao Pedras To: freebsd-current@freebsd.org Subject: upgrade 3.3REL -> 4.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all! On the 2nd on January I made a fresh install of a 3.3-REL. On that same day I updated its /usr/src to 4.0-CURRENT. I went through a process(almost trivial to me, trivial for you guys) that took sometime. On the 3rd the machine was fully running -CURRENT. I made this rehearsal because I have a dozen must-be-online that in due time, will be running 4.0. I remember last years 'version-rush', scripts and whatever, to upgrade everyone to 3.0. Some made it with success, some not. Thanks to the great job FreeBSD's team has been doing, more and more people are running FreeBSD on very serious environments/bussinesses and gladly, not everyone needs to be a 15 year-old Unix hacker to command the troops. What are your plans regarding the upgrading procedure this year ? Will it be easy to upgrade to the 4.0-REL from 3.4(5) with scripts ? Joao ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- This sentence contradicts itself -- no actually it doesn't. -- Hofstadter ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 14:15:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 123E914D44 for ; Wed, 5 Jan 2000 14:13:57 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.9.3/8.9.3) with UUCP id AAA24801 for current@FreeBSD.org; Thu, 6 Jan 2000 00:21:21 +0300 (MSK) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id AAA12208; Thu, 6 Jan 2000 00:06:15 +0300 (MSK) Date: Thu, 6 Jan 2000 00:06:15 +0300 From: Alexey Zelkin To: current@FreeBSD.org Subject: unknown*:* Message-ID: <20000106000615.A12191@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I just updated my -CURRENT, compiled kernel with PNPBIOS and found a lot of unknown items in dmesg output. Should I submit my PNP devices IDs ? And who is PNP related part maintainer ? PS: Also I got strange error about `device slot allocation' for acd0. What the trouble I got ? As I understand it's something related to DEVFS. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #3: Mon Jan 3 11:36:10 MSK 2000 phantom@spider.scorpion.crimea.ua:/usr/src/HEAD/src/sys/compile/SPIDER Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 67108864 (65536K bytes) avail memory = 61665280 (60220K bytes) Preloaded elf kernel "kernel" at 0xc0339000. DEVFS: ready for devices VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (c0000e38) VESA: S3 Incorporated Trio3D. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 chip1: at device 7.3 on pci0 ed0: irq 12 at device 9.0 on pci0 ed0: supplying EUI64: 00:00:21:ff:fe:c7:5b:a7 ed0: address 00:00:21:c7:5b:a7, type NE2000 (16 bit) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A unknown: can't assign resources unknown0: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0xf0-0xff irq 13 on isa0 unknown4: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x3ffffff on isa0 unknown5: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0 unknown6: at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0 unknown7: at port 0x208-0x20f on isa0 unknown: can't assign resources unknown: can't assign resources unknown8: at port 0x378-0x37f irq 7 on isa0 unknown: can't assign resources pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 unknown9: at port 0x201 on isa0 unknown10: at port 0x100-0x107 on isa0 unknown11: at port 0x1e0-0x1e7,0x3e6 irq 11 on isa0 DEVFS: ready to run ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Device acd0a: name slot allocation failed (Errno=17) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Device acd0c: name slot allocation failed (Errno=17) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ acd0: <24X CD-ROM/VER 1.0E> CDROM drive at ata0 as slave acd0: read 687KB/s (3093KB/s), 128KB buffer, UDMA33 acd0: Reads: CD-DA stream acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked Mounting root from ufs:/dev/wd0s1a ed0: starting DAD for fe80:0001::0200:21ff:fec7:5ba7 ed0: DAD complete for fe80:0001::0200:21ff:fec7:5ba7 - no duplicates found -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 14:34:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 68CDD15560 for ; Wed, 5 Jan 2000 14:34:10 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 19149373 invoked from network); 5 Jan 2000 22:34:25 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2000 22:34:25 -0000 Message-ID: <3873C717.350B6983@cybercable.fr> Date: Wed, 05 Jan 2000 23:35:03 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: error messages while loading the kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just remade the world and a new kernel with sources supped around 21h00 GMT today, and I've got error messages in the kernel loading phase (on an SMP machine : bi-celeron BP6) link_elf: symbol zfree undefined link_elf: symbol zfree undefined FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Jan 5 23:15:23 CET 2000 thierry.herbelot@multi.herbelot.nom:/usr/src/sys/compile/multi i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 14:44: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 07A2E154AD for ; Wed, 5 Jan 2000 14:44:00 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 7885517 invoked from network); 5 Jan 2000 22:43:58 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2000 22:43:58 -0000 Message-ID: <3873C95C.EE021541@cybercable.fr> Date: Wed, 05 Jan 2000 23:44:44 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: unwanted Vinum partition fsck'ing when booting Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On my SMP box, I've set up a striped Vinum partition. Not wanting to mount it each time I boot, I've included a "placeholder" in fstab to get it known, but without it getting mounted at boot-up. /dev/vinum/initial /files1 ufs rw,noauto 2 2 herbie2:/files2 /files2 nfs rw /dev/ad4s2e /files3 ufs rw,noauto 2 2 /dev/ad4s1b /usr/obj mfs rw 0 0 This evening, with freshly supped sources (got around 21h00 GMT, followed by a "make world"), my new kernel insists it wants to fsck the /files1 partition, even if it is not to be mounted. I then have to comment out the /files1 line in /etc/fstab while in single-user mode : no joy the /files3 has absolutely no trouble, it stays un-mounted and un-fsck'ed TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 14:45:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A89F14D04; Wed, 5 Jan 2000 14:45:07 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-19.iptelecom.net.ua [212.9.226.19]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id AAA29920; Thu, 6 Jan 2000 00:48:16 +0200 (EET) Message-ID: <3873C990.70D294F7@altavista.net> Date: Thu, 06 Jan 2000 00:45:36 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Nicolas Souchu Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> <20000104210015.63255@breizh.free.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: > > > >Nicolas Souchu wrote: > > > >> Hi there! > >> > >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current > >> > >> A major ppbus(4) release is available for beta-testing. > > > >Good work! Now plip, which has been broken for ages, works perfectly - no more > >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X > >and NFS working over plip line, things which was impossible with oldppbus. > > Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) > in you MACHINE config file would have done the job. Unfortunately it is not a solution because net,tty and bio keywords went away from config(8) long time ago... I've only received `syntax error' message. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 14:49:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.2hip.net (gizmo.2hip.net [208.241.12.2]) by hub.freebsd.org (Postfix) with ESMTP id 5245A14DB5 for ; Wed, 5 Jan 2000 14:49:56 -0800 (PST) (envelope-from rnoland@gizmo.2hip.net) Received: (from rnoland@localhost) by gizmo.2hip.net (8.9.3/8.9.3) id RAA78369; Wed, 5 Jan 2000 17:49:44 -0500 (EST) (envelope-from rnoland) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14451.51848.416138.262888@gizmo.2hip.net> Date: Wed, 5 Jan 2000 17:49:44 -0500 (EST) From: "Robert C. Noland III" To: Thierry Herbelot Cc: current@FreeBSD.ORG Subject: error messages while loading the kernel In-Reply-To: <3873C717.350B6983@cybercable.fr> References: <3873C717.350B6983@cybercable.fr> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen that as well... It seems to be caused by svr4_enable="YES" in rc.conf. or rather the specified module. robert. Thierry Herbelot writes: >I've just remade the world and a new kernel with sources supped around >21h00 GMT today, and I've got error messages in the kernel loading phase >(on an SMP machine : bi-celeron BP6) > >link_elf: symbol zfree undefined >link_elf: symbol zfree undefined > > > >FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: >Wed Jan 5 23:15:23 CET 2000 >thierry.herbelot@multi.herbelot.nom:/usr/src/sys/compile/multi i386 > > >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 Wed Jan 5 15: 2:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id A96CD14F29 for ; Wed, 5 Jan 2000 15:02:16 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 1214830 invoked from network); 5 Jan 2000 23:05:48 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2000 23:05:48 -0000 Message-ID: <3873CD96.2E27D6EC@cybercable.fr> Date: Thu, 06 Jan 2000 00:02:46 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Robert C. Noland III" Cc: current@FreeBSD.ORG Subject: Re: error messages while loading the kernel References: <3873C717.350B6983@cybercable.fr> <14451.51848.416138.262888@gizmo.2hip.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Robert C. Noland III" wrote: > > I have seen that as well... It seems to be caused by svr4_enable="YES" > in rc.conf. or rather the specified module. > I'd say any module : multi% kldstat Id Refs Address Size Name 1 2 0xc0100000 1c4b58 kernel 4 1 0xc1155000 2000 blank_saver.ko multi% I don't use the svr4 emulation TfH > robert. > > Thierry Herbelot writes: > >I've just remade the world and a new kernel with sources supped around > >21h00 GMT today, and I've got error messages in the kernel loading phase > >(on an SMP machine : bi-celeron BP6) > > > >link_elf: symbol zfree undefined > >link_elf: symbol zfree undefined > > > > > > > >FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: > >Wed Jan 5 23:15:23 CET 2000 > >thierry.herbelot@multi.herbelot.nom:/usr/src/sys/compile/multi i386 > > > > > >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 Wed Jan 5 15: 6:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BD1A81548E for ; Wed, 5 Jan 2000 15:06:35 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA32825; Thu, 6 Jan 2000 09:35:31 +1030 (CST) (envelope-from newton) Date: Thu, 6 Jan 2000 09:35:31 +1030 From: Mark Newton To: "Robert C. Noland III" Cc: Thierry Herbelot , current@FreeBSD.ORG Subject: Re: error messages while loading the kernel Message-ID: <20000106093531.A32775@internode.com.au> References: <3873C717.350B6983@cybercable.fr> <14451.51848.416138.262888@gizmo.2hip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <14451.51848.416138.262888@gizmo.2hip.net> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote: > I have seen that as well... It seems to be caused by svr4_enable="YES" > in rc.conf. or rather the specified module. FWIW, this was fixed in rev 1.10 of svr4_sysvec.c - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 15: 8:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 9AC5F15488 for ; Wed, 5 Jan 2000 15:08:28 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA32862; Thu, 6 Jan 2000 09:37:49 +1030 (CST) (envelope-from newton) Date: Thu, 6 Jan 2000 09:37:49 +1030 From: Mark Newton To: Thierry Herbelot Cc: current@FreeBSD.ORG Subject: Re: unwanted Vinum partition fsck'ing when booting Message-ID: <20000106093749.B32775@internode.com.au> References: <3873C95C.EE021541@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3873C95C.EE021541@cybercable.fr> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 11:44:44PM +0100, Thierry Herbelot wrote: > On my SMP box, I've set up a striped Vinum partition. Not wanting to > mount it each time I boot, I've included a "placeholder" in fstab to get > it known, but without it getting mounted at boot-up. Uh huh -- But you've specified a non-zero fsck pass number in the fstab entry. Change this: > /dev/vinum/initial /files1 ufs rw,noauto 2 2 to this: /dev/vinum/initial /files1 ufs rw,noauto 2 0 - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 15:16: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.2hip.net (gizmo.2hip.net [208.241.12.2]) by hub.freebsd.org (Postfix) with ESMTP id 140B914EA5 for ; Wed, 5 Jan 2000 15:16:04 -0800 (PST) (envelope-from rnoland@gizmo.2hip.net) Received: (from rnoland@localhost) by gizmo.2hip.net (8.9.3/8.9.3) id SAA79041; Wed, 5 Jan 2000 18:15:42 -0500 (EST) (envelope-from rnoland) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14451.53406.554333.176629@gizmo.2hip.net> Date: Wed, 5 Jan 2000 18:15:42 -0500 (EST) From: "Robert C. Noland III" To: Mark Newton Cc: "Robert C. Noland III" , Thierry Herbelot , current@FreeBSD.ORG Subject: Re: error messages while loading the kernel In-Reply-To: <20000106093531.A32775@internode.com.au> References: <3873C717.350B6983@cybercable.fr> <14451.51848.416138.262888@gizmo.2hip.net> <20000106093531.A32775@internode.com.au> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So it was, it now shows up in: vinum/vinum.ko U zfree BTW, this seems to be the only module referencing this symbol at the moment. robert. Mark Newton writes: >On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote: > > > I have seen that as well... It seems to be caused by svr4_enable="YES" > > in rc.conf. or rather the specified module. > >FWIW, this was fixed in rev 1.10 of svr4_sysvec.c > > - mark > >-- >Mark Newton Email: newton@internode.com.au (W) >Network Engineer Email: newton@atdot.dotat.org (H) >Internode Systems Pty Ltd Desk: +61-8-82232999 >"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-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 Wed Jan 5 15:37:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 7104E154D8 for ; Wed, 5 Jan 2000 15:37:06 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 7914043 invoked from network); 5 Jan 2000 23:36:21 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2000 23:36:21 -0000 Message-ID: <3873D5A4.E97CC1E4@cybercable.fr> Date: Thu, 06 Jan 2000 00:37:08 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton Cc: current@FreeBSD.ORG Subject: Re: unwanted Vinum partition fsck'ing when booting References: <3873C95C.EE021541@cybercable.fr> <20000106093749.B32775@internode.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton wrote: > > On Wed, Jan 05, 2000 at 11:44:44PM +0100, Thierry Herbelot wrote: > > > On my SMP box, I've set up a striped Vinum partition. Not wanting to > > mount it each time I boot, I've included a "placeholder" in fstab to get > > it known, but without it getting mounted at boot-up. > > Uh huh -- But you've specified a non-zero fsck pass number in the fstab > entry. Change this: > > > /dev/vinum/initial /files1 ufs rw,noauto 2 2 > > to this: > > /dev/vinum/initial /files1 ufs rw,noauto 2 0 done ! (and it now works "as advertised") (but my /files3 line was identical and /ad4s2e was not fsck'ed) /dev/ad4s2e /files3 ufs rw,noauto 2 2 Strange TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 15:39:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BDD7B15481 for ; Wed, 5 Jan 2000 15:39:17 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Thu, 6 Jan 2000 10:31:45 +1100 Content-return: prohibited From: Peter Jeremy Subject: ATA driver problems To: freebsd-current@FreeBSD.ORG Message-Id: <00Jan6.103145est.40326@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Thu, 6 Jan 2000 10:31:43 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I updated from a pre-signal-change -current to something closer to the present (cvs-cur 5961 - about last Monday, to be precise). Every night, I run "dd if=/dev/rwdXc of=/dev/null bs=64k" on both of my disks (I trim the output and merge it with a number of other systems). I forgot to update the wd to ad and last night it reported errors. I was expecting: gsmx07:wd0:91746+1 records in gsmx07:wd0:91746+1 records out gsmx07:wd0:6012679680 bytes transferred gsmx07:wd2:19561+1 records in gsmx07:wd2:19561+1 records out gsmx07:wd2:1281950208 bytes transferred But instead I got: gsmx07:wd0:dd: /dev/rwd0c: Invalid argument gsmx07:wd0:91747+0 records in gsmx07:wd0:91747+0 records out gsmx07:wd0:6012731392 bytes transferred gsmx07:wd2:dd: /dev/rwd2c: Input/output error gsmx07:wd2:19561+0 records in gsmx07:wd2:19561+0 records out gsmx07:wd2:1281949696 bytes transferred At about the same time, the following message appeared in /var/log/messages: /kernel: ad2: HARD READ ERROR blk# 2503871 /kernel: ad2: HARD READ ERROR blk# 2503871 status=59 error=10 /kernel: ad2: DMA problem encountered, fallback to PIO mode I just tried repeating it with ad0 instead of wd0 and got the same thing. I don't want to repeat it with ad2 since there doesn't appear to be any way to re-enable DMA short of rebooting [or maybe that patch hasn't arrived here yet]. This suggests that there are two separate problems: 1) An I/O request for a block that entends beyond the end of the physical slice will abort with EINVAL, rather than returning a partial block. 2) There seems to be an off-by-1 error in the size reported by my Fireball (or maybe in the request handling), causing it to report an I/O error on the last sector. The first problem would seem to be a bug in the ata driver, since the behaviour on other Unices is to return a partial block. (And this might be related to the difficulties Brian Feldman is reporting). I'm not sure about the second problem - all I can say if that the wd driver saw the same number of sectors and the bytes read from the disk matches the number of sectors in the slices. Does anyone have any ideas? The disk-related probe messages are: ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 ... ad0: ATA-3 disk at ata0 as master ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-0 disk at ata1 as master ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata0 as slave acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ad0 has two active slices, the FreeBSD one is the second and is 11743515 sectors. ad2 is dedicated (not dangerously) to FreeBSD and the slice is 2503809 sectors. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 15:51:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust140.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A677F151F4; Wed, 5 Jan 2000 15:51:49 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Wed, 5 Jan 2000 18:50:45 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001050835.JAA35344@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 How about this? It's mostly the changes in your patch, but it also takes into account non-int{8,16}_t-sizing/alignment. It also takes care of the truncation problem when you use outsl and insl, as part of that. Please review it, as I think it should be the right thing to do. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' Index: atapi-all.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-all.c,v retrieving revision 1.29 diff -u -r1.29 atapi-all.c --- atapi-all.c 2000/01/03 10:26:56 1.29 +++ atapi-all.c 2000/01/05 23:37:27 @@ -552,23 +552,39 @@ *buffer = (int8_t *)&request->sense; if (request->bytecount < length) { - printf("%s: read data overrun %d/%d\n", + printf("%s: read data buffer too small (bs %d > buflen %d)\n", request->device->devname, length, request->bytecount); #ifdef ATA_16BIT_ONLY insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)*buffer, request->bytecount / sizeof(int16_t)); #else insl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int32_t)); + (void *)*buffer, request->bytecount / sizeof(int32_t)); + if (request->bytecount & sizeof(int16_t)) { + *(int16_t *)(*buffer + request->bytecount - + (sizeof(int16_t) + (request->bytecount & sizeof(int8_t)))) = + inw(request->device->controller->ioaddr + ATA_DATA); + length -= sizeof(int16_t); + } #endif - for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA); + if (request->bytecount & sizeof(int8_t)) { + (*buffer)[request->bytecount - sizeof(int8_t)] = + inb(request->device->controller->ioaddr + ATA_DATA); + (void)inb(request->device->controller->ioaddr + ATA_DATA); + length -= sizeof(int8_t); + } + resid = request->bytecount & ~(sizeof(int16_t) | sizeof(int8_t)); + for (; resid < length; resid += sizeof(int16_t)) + (void)inw(request->device->controller->ioaddr + ATA_DATA); + *buffer += request->bytecount; + request->bytecount = 0; } - else + else { insw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + (void *)*buffer, length / sizeof(int16_t)); + *buffer += length; + request->bytecount -= length; + } } static void @@ -581,23 +597,38 @@ *buffer = (int8_t *)&request->sense; if (request->bytecount < length) { - printf("%s: write data underrun %d/%d\n", - request->device->devname, length, request->bytecount); + printf("%s: write data underrun (buflen %d < bs %d), padding written\n", + request->device->devname, request->bytecount, length); #ifdef ATA_16BIT_ONLY outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); + (void *)*buffer, request->bytecount / sizeof(int16_t)); #else outsl(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int32_t)); + (void *)*buffer, request->bytecount / sizeof(int32_t)); + if (request->bytecount & sizeof(int16_t)) { + outw(request->device->controller->ioaddr + ATA_DATA, + *(int16_t *)(*buffer + request->bytecount - + (sizeof(int16_t) + (request->bytecount & sizeof(int8_t))))); + length -= sizeof(int16_t); + } #endif - for (resid=request->bytecount; residbytecount & sizeof(int8_t)) { + outb(request->device->controller->ioaddr + ATA_DATA, + (*buffer)[request->bytecount]); + length -= sizeof(int8_t); + } + resid = request->bytecount & ~(sizeof(int16_t) | sizeof(int8_t)); + for (; resid < length; resid += sizeof(int16_t)) outw(request->device->controller->ioaddr + ATA_DATA, 0); + *buffer += request->bytecount; + request->bytecount = 0; } - else + else { outsw(request->device->controller->ioaddr + ATA_DATA, - (void *)((uintptr_t)*buffer), length / sizeof(int16_t)); - request->bytecount -= length; - *buffer += length; + (void *)*buffer, length / sizeof(int16_t)); + *buffer += length; + request->bytecount -= length; + } } static void To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 16:22:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6105815479; Wed, 5 Jan 2000 16:22:28 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id TAA63109; Wed, 5 Jan 2000 19:21:17 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001060021.TAA63109@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kai Voigt Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> <20000105213930.C751@abc.123.org> In-reply-to: Your message of "Wed, 05 Jan 2000 21:39:30 +0100." <20000105213930.C751@abc.123.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jan 2000 19:21:17 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Louis A. Mamakos wrote: > > > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > > some applications. > > IPv6 is a very complex area and I believe that a -RELEASE should come with > both a clean IPv6 stack and working userland tools. When looking at > Linux and Solaris, they also lack a usable IPv6 support when it comes > to userland tools. > > A lot of things need to be modified: ifconfig, route, ipfw, tcpd, ... > and all the client/server tools you can find in /etc/inetd.conf > > I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it > will be a major item for this year. A large part of the integration has already been done. The KAME IPv6 and IPSEC code has been available for 3.2 and 3.3 for a while, and seems to be pretty stable based on the testing I did a few weeks ago. While there's been a bunch of changes in the 4.0 kernel, I think adapted to the differences between 3.x and 4.x is the major challange rather than the IPSEC and IPv6 features and functionality. All the changes you mentioned (and more) already exist as patches to 3.3 from KAME. Of course, I'm not doing the work, so my opinion on the difficulty doesn't carry much authority.. louie . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 16:28:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0D02B154C1 for ; Wed, 5 Jan 2000 16:28:12 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 1260ly-0001kZ-00 for freebsd-current@freebsd.org; Wed, 05 Jan 2000 16:27:26 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: make.conf NO_SENDMAIL=true blown Message-Id: Date: Wed, 05 Jan 2000 16:27:26 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my /etc/make.conf has NO_SENDMAIL=true but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq, etc. all about /usr/sbin/mailwrapper. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 16:38:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 2C7DB14E94; Wed, 5 Jan 2000 16:38:06 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id QAA86457; Wed, 5 Jan 2000 16:37:00 -0800 (PST) X-Authentication-Warning: btw.plaintalk.bellevue.wa.us: Host fwiw.plaintalk.bellevue.wa.us [206.129.5.157] claimed to be software-munitions.com Message-ID: <3873E3AC.62A76BC5@software-munitions.com> Date: Wed, 05 Jan 2000 16:37:00 -0800 From: Dennis Glatting X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms7B55930FA2AAFE9EE4D45CA1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms7B55930FA2AAFE9EE4D45CA1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stupid question: will the latest PAO stuff be integrated with 4.0? -dpg --------------ms7B55930FA2AAFE9EE4D45CA1 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B7owggSEMIID7aADAgECAhAV4oOYVg1pE0gVFzzXJ4WbMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDMyMTAwMDAw MFoXDTAwMDMyMDIzNTk1OVowggEoMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0Rlbm5pcyBHbGF0dGluZzE1MDMGCSqG SIb3DQEJARYmZGVubmlzLmdsYXR0aW5nQHNvZnR3YXJlLW11bml0aW9ucy5jb20wgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAKSBSrAz19P5zPsu3odv359aq1FIuU7RXSXlVga0DqpE ST8T6/e3wtn1f8NnfnytpCWP4r2FgO51Z2Q8o5fy99Gajtlm5tYDBEm09HGWoxAYfEJE8oVI lMCDRQazW5WFiY8WkoNl36eoVl0Oa5rsaSMnk5u45R7Mu3wyLRBooXfnAgMBAAGjggEGMIIB AjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUF BwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVy aVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2Ug bGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCww KjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0B AQQFAAOBgQAlb2LpvHzHBF/o/uILYbM2MGnIkf4y7PN+XQnMAXpk1mIFeVtIH+kquwCo93ra 9h1wdohBxmPt4Sw/EHG4WNr8PnYXuo7kFOBokqSTOYQTr/6zbSKnjXhO3N4qWKoS0dK0G8GO QTKulULvZBkmbnHJ1YIvES2KH7hC2Uzs1K7SDDCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKo JV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2ln biwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9u IEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHMMRcwFQYDVQQK Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GN ADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFLuUgT Vi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMC AQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNp Z24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0G CSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVq D7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9d WBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICPDCCAjgCAQEwgeEwgcwx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEBXig5hWDWkTSBUX PNcnhZswCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3 DQEJBTEPFw0wMDAxMDYwMDM3MDBaMCMGCSqGSIb3DQEJBDEWBBTkxiwUZhp3nkH4IQ68e3dS bh10MzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUr DgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgE3C dAJtyb81/ZddzFFgqEx7Bcx3wxEM6QSi/HSyknjvAT2P2yDuDIPyXt+ipGF2stDJN243g/Ig vxF4rVyc03AxbdNeVLZztS6yjjDuGZtMdslbhlgqv10CYJYIO8ZnzIY8YlcpP00t/a0FrQ9U w3aiFAtD69PcZF7Sz6R8m6E5 --------------ms7B55930FA2AAFE9EE4D45CA1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 16:54:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 52235154FF; Wed, 5 Jan 2000 16:54:05 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id JAA14563; Thu, 6 Jan 2000 09:52:40 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id JAA15829; Thu, 6 Jan 2000 09:52:40 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id JAA11396; Thu, 6 Jan 2000 09:52:39 +0900 (JST) To: louie@TransSys.COM Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001052026.PAA61728@whizzo.transsys.com> References: <28153.947101446@zippy.cdrom.com> <200001052026.PAA61728@whizzo.transsys.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000106095316M.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Jan 2000 09:53:16 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Will we try to include the remaining KAME IPv6 integration into 4.0 before > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > some applications. > > louie As an information from a person doing merging work, -Kernel part is almost done(tcp patch is under review and testing). -IPsec userland tools patch is also under review. -some more tcp and udp userland tools need to be added but I think it can be done including review time before 15th. Then I think 4.0 will have some enough degree of IPv6 and IPsec functionalities. Some items won't make it until 15th, -IPv6 multicast routing -many IPv6 ports But after 4.0 is released, KAME package for 4.0 release will be also made, and I think it can provide those part and other update for users who needs more intensive support for IPv6 and IPsec. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 16:58:23 2000 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 B0EC91502D; Wed, 5 Jan 2000 16:58:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA08562; Wed, 5 Jan 2000 17:58:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA71675; Wed, 5 Jan 2000 17:58:10 -0700 (MST) Message-Id: <200001060058.RAA71675@harmony.village.org> To: Dennis Glatting Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: committers@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Wed, 05 Jan 2000 16:37:00 PST." <3873E3AC.62A76BC5@software-munitions.com> References: <3873E3AC.62A76BC5@software-munitions.com> <28153.947101446@zippy.cdrom.com> Date: Wed, 05 Jan 2000 17:58:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3873E3AC.62A76BC5@software-munitions.com> Dennis Glatting writes: : Stupid question: will the latest PAO stuff be integrated with 4.0? Not as such no. Like 3.x before, most of the PAO bits have been merged, but much still remains in PAO that hasn't been integrated. There will likely be a PAO4 while we trnasition to the new pccard system. At least that's my sense of things. I'm not part of the PAO team, so they may deside to do something different. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 17: 5:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 93247154E9 for ; Wed, 5 Jan 2000 17:05:23 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 79FA61EA; Wed, 5 Jan 2000 17:03:24 -0800 (PST) Date: Wed, 5 Jan 2000 17:03:24 -0800 From: Chris Piazza To: Randy Bush Cc: FreeBSD Current Subject: Re: make.conf NO_SENDMAIL=true blown Message-ID: <20000105170324.A1526@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from randy@psg.com on Wed, Jan 05, 2000 at 04:27:26PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 04:27:26PM -0800, Randy Bush wrote: > my /etc/make.conf has NO_SENDMAIL=true > > but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq, > etc. all about /usr/sbin/mailwrapper. Yeah, that bit me too but I forgot to post a message here. I'm using postfix and I just changed /etc/mail/mailer.conf to this: sendmail /usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail It was still really annoying, though, and at least UPDATING could have had an entry for it. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 17:14:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id AE69714CB7 for ; Wed, 5 Jan 2000 17:14:27 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 1261Rb-00021o-00; Wed, 05 Jan 2000 17:10:27 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chris Piazza Cc: FreeBSD Current Subject: Re: make.conf NO_SENDMAIL=true blown References: <20000105170324.A1526@norn.ca.eu.org> Message-Id: Date: Wed, 05 Jan 2000 17:10:27 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq, >> etc. all about /usr/sbin/mailwrapper. > Yeah, that bit me too but I forgot to post a message here. I'm using > postfix and I just changed /etc/mail/mailer.conf to this: > > sendmail /usr/local/sbin/sendmail > send-mail /usr/local/sbin/sendmail > mailq /usr/local/sbin/sendmail > newaliases /usr/local/sbin/sendmail similarly, but i am an exim bigot. > It was still really annoying, though thousands of people were denied the wisdom of my words for hours until i noticed it. :-) > and at least UPDATING could have had an entry for it. yup^2 randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 17:15:15 2000 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 3225D15055 for ; Wed, 5 Jan 2000 17:14:50 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA67771; Thu, 6 Jan 2000 11:41:05 +1030 (CST) Date: Thu, 6 Jan 2000 11:41:05 +1030 From: Greg Lehey To: Thierry Herbelot Cc: current@FreeBSD.ORG Subject: Re: error messages while loading the kernel Message-ID: <20000106114104.J30038@freebie.lemis.com> References: <3873C717.350B6983@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <3873C717.350B6983@cybercable.fr> 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 Wednesday, 5 January 2000 at 23:35:03 +0100, Thierry Herbelot wrote: > I've just remade the world and a new kernel with sources supped around > 21h00 GMT today, and I've got error messages in the kernel loading phase > (on an SMP machine : bi-celeron BP6) > > link_elf: symbol zfree undefined > link_elf: symbol zfree undefined > > > > FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: > Wed Jan 5 23:15:23 CET 2000 > thierry.herbelot@multi.herbelot.nom:/usr/src/sys/compile/multi i386 One possibility is that you're including Vinum in the kernel, as not recommended. There was a problem between commits 1.48 and 1.49 of vinumio.c, about 18 hours. If you have Vinum in the kernel, just re-CVSup. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 17:20:36 2000 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 EEBBA14E55 for ; Wed, 5 Jan 2000 17:20:27 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA67801; Thu, 6 Jan 2000 11:44:49 +1030 (CST) Date: Thu, 6 Jan 2000 11:44:49 +1030 From: Greg Lehey To: "Robert C. Noland III" Cc: Mark Newton , Thierry Herbelot , current@FreeBSD.ORG Subject: Re: error messages while loading the kernel Message-ID: <20000106114449.K30038@freebie.lemis.com> References: <3873C717.350B6983@cybercable.fr> <14451.51848.416138.262888@gizmo.2hip.net> <20000106093531.A32775@internode.com.au> <14451.53406.554333.176629@gizmo.2hip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <14451.53406.554333.176629@gizmo.2hip.net> 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 Wednesday, 5 January 2000 at 18:15:42 -0500, Robert C. Noland III wrote: > Mark Newton writes: >> On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote: >> >>> I have seen that as well... It seems to be caused by svr4_enable="YES" >>> in rc.conf. or rather the specified module. >> >> FWIW, this was fixed in rev 1.10 of svr4_sysvec.c > > So it was, it now shows up in: > > vinum/vinum.ko > U zfree > > BTW, this seems to be the only module referencing this symbol at the > moment. It's all a consspiracy of the South Australian committers to break the kernel build. You'll notice that Peter Wemm (just West of South Australia) didn't blow our cover :-) Seriously, it's an inline function. If you don't include vm/vm_zone.h in the source file, it will become an undefined reference. As I said in an earlier message, it's fixed in Vinum now. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 20:21:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 802321552B for ; Wed, 5 Jan 2000 20:21:36 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Thu, 6 Jan 2000 15:13:59 +1100 Content-return: prohibited From: Peter Jeremy Subject: Mounting CD-ROM with ATA driver hangs system To: freebsd-current@FreeBSD.ORG Message-Id: <00Jan6.151359est.40327@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Thu, 6 Jan 2000 15:13:59 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just discovered that my ATAPI CD-ROM is no longer usable - when I try to mount it, my maching hangs (hard). I'm running -current from cvs-cur 5961 (Monday about 0000UTC). The symptoms are: Run "mount -r /dev/acd0c /cdrom" The CD-ROM activity light flashes briefly and the CD-ROM spins up. The activity light then goes hard on for something like 20 seconds. The kernel then prints: acd0: atapi_timeout: cmd=READ_BIG - resetting ata0: resetting devices .. _ The cursor remains at the end of the line ("_" above). The CD-ROM spins up and down. The HDD light stays hard on. At this point, the system will not respond to the keyboard. I didn't have any problems with the WD driver, so I don't think it's hardware. Any ideas? Dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #15: Thu Jan 6 08:02:56 EST 2000 root@gsmx07.alcatel.com.au:/3.0/cvs/src/sys/compile/gsmx Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 267310659 Hz CPU: Pentium II (267.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 67108864 (65536K bytes) avail memory = 61980672 (60528K bytes) Preloaded elf kernel "kernel" at 0xc0301000. VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc02b1e22 (1000022) VESA: Matrox Graphics Inc. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: at device 7.3 on pci0 vga-pci0: irq 10 at device 9.0 on pci0 tx0: irq 9 at device 10.0 on pci0 tx0: address 00:e0:29:24:34:1f, type SMC9432TX, Auto-Neg 100Mbps ed0 at port 0x300-0x31f iomem 0xcc000-0xcffff irq 7 on isa0 ed0: address 00:00:c0:57:99:47, type WD8013EPC (16 bit) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: not probed (disabled) sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A pca0 at port 0x40 on isa0 pca0: PC speaker audio driver isa_compat: didn't get irq for ppc ppc0 at port 0x378-0x37f irq 7 on isa0 isa_compat: didn't get irq for ppc ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pps0: on ppbus 0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 sbc0: setting card to irq 5, drq 1, 3 pcm0: on sbc0 joy0: at port 0x201 on isa0 ad0: ATA-3 disk at ata0 as master ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-0 disk at ata1 as master ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata0 as slave acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 20:51:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from public.xfree86.org (xf86.isc.org [204.152.184.37]) by hub.freebsd.org (Postfix) with ESMTP id 6372614F7B for ; Wed, 5 Jan 2000 20:51:08 -0800 (PST) (envelope-from dawes@public.xfree86.org) Received: (from dawes@localhost) by public.xfree86.org (8.9.1/8.9.1) id UAA20844; Wed, 5 Jan 2000 20:47:08 -0800 (PST) Date: Wed, 5 Jan 2000 20:47:07 -0800 From: David Dawes To: devel@xfree86.org Cc: current@freebsd.org Subject: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current Message-ID: <20000105204707.A14003@xfree86.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just been doing a build test of the pre-3.3.6 version of XFree86 on a recent FreeBSD 4.0-current, and I've noticed that /usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake uses /usr/libexec/cpp. Is it intentional that /usr/libexec/cpp not predefine any symbols like this? I've changed imake to use /usr/bin/cpp instead, and it seems to work on 3.4 and 4.0. Should this be OK on all FreeBSD versions? --- imakemdep.h 1999/07/29 09:22:27 3.24.2.14 +++ xc/config/imake/imakemdep.h 2000/01/06 04:39:59 @@ -265,8 +265,11 @@ #ifdef _CRAY #define DEFAULT_CPP "/lib/pcpp" #endif -#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || defined(__FreeBSD__) +#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) #define DEFAULT_CPP "/usr/libexec/cpp" +#endif +#if defined(__FreeBSD__) +#define DEFAULT_CPP "/usr/bin/cpp" #endif #if defined(__sgi) && defined(__ANSI_CPP__) #define USE_CC_E David -- David Dawes Email: dawes@XFree86.org Co-founder/President, The XFree86 Project, Inc Phone: +1 570 775 9502 http://www.xfree86.org/ Fax: +61 2 9897 3755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 20:55:24 2000 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 5ED9415575; Wed, 5 Jan 2000 20:55:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA54137; Wed, 5 Jan 2000 20:54:00 -0800 (PST) (envelope-from dillon) Date: Wed, 5 Jan 2000 20:54:00 -0800 (PST) From: Matthew Dillon Message-Id: <200001060454.UAA54137@apollo.backplane.com> To: Dennis Glatting Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> <3873E3AC.62A76BC5@software-munitions.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This is a cryptographically signed message in MIME format. : :--------------ms7B55930FA2AAFE9EE4D45CA1 :Content-Type: text/plain; charset=us-ascii :Content-Transfer-Encoding: 7bit : : :Stupid question: will the latest PAO stuff be integrated with 4.0? : : :-dpg :--------------ms7B55930FA2AAFE9EE4D45CA1 :Content-Type: application/x-pkcs7-signature; name="smime.p7s" :Content-Transfer-Encoding: base64 :Content-Disposition: attachment; filename="smime.p7s" :Content-Description: S/MIME Cryptographic Signature : :MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC :B7owggSEMIID7aADAgECAhAV4oOYVg1pE0gVFzzXJ4WbMA0GCSqGSIb3DQEBBAUAMIHMMRcw :FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y :... :... lots of junk removed :... What is all ^^^^^^^^^^^ this junk? Can you post without adding all of this? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 20:58:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from public.xfree86.org (xf86.isc.org [204.152.184.37]) by hub.freebsd.org (Postfix) with ESMTP id 9D73B15561 for ; Wed, 5 Jan 2000 20:58:27 -0800 (PST) (envelope-from dawes@public.xfree86.org) Received: (from dawes@localhost) by public.xfree86.org (8.9.1/8.9.1) id UAA21333; Wed, 5 Jan 2000 20:54:29 -0800 (PST) Date: Wed, 5 Jan 2000 20:54:29 -0800 From: David Dawes To: devel@XFree86.Org Cc: current@freebsd.org Subject: Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current Message-ID: <20000105205429.B14003@xfree86.org> References: <20000105204707.A14003@XFree86.Org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000105204707.A14003@XFree86.Org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote: >I've just been doing a build test of the pre-3.3.6 version of >XFree86 on a recent FreeBSD 4.0-current, and I've noticed that >/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake >uses /usr/libexec/cpp. Is it intentional that /usr/libexec/cpp >not predefine any symbols like this? I've changed imake to use >/usr/bin/cpp instead, and it seems to work on 3.4 and 4.0. Should >this be OK on all FreeBSD versions? I posted too soon. This is already dealt with in the pre-4.0 XFree86 code by using 'cc -E'. I'll fold that change in for 3.3.6. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 21:15:12 2000 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 BD0DE1555C for ; Wed, 5 Jan 2000 21:15:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA49110; Wed, 5 Jan 2000 21:15:08 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA03666; Wed, 5 Jan 2000 21:15:07 -0800 (PST) (envelope-from obrien) Date: Wed, 5 Jan 2000 21:15:07 -0800 From: "David O'Brien" To: devel@xfree86.org, current@freebsd.org Subject: Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current Message-ID: <20000105211507.B3568@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000105204707.A14003@xfree86.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105204707.A14003@xfree86.org>; from dawes@xfree86.org on Wed, Jan 05, 2000 at 08:47:07PM -0800 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 Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote: > I've just been doing a build test of the pre-3.3.6 version of > XFree86 on a recent FreeBSD 4.0-current, and I've noticed that > /usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. Correct. The change is due to philosophical changes by the GCC development team. GCC 2.95.2's cpp built from cccp.c is now a pure preprocessor and knows much less about the world than it previously did. In 2.95.2 there is now an additional cpp that is build using gcc.c and is a driver for the cccp.c cpp. -- -- 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 Jan 5 21:22: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id DF81115526; Wed, 5 Jan 2000 21:21:52 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id PAA34817; Thu, 6 Jan 2000 15:51:46 +1030 (CST) (envelope-from newton) Date: Thu, 6 Jan 2000 15:51:46 +1030 From: Mark Newton To: "David O'Brien" Cc: devel@xfree86.org, current@FreeBSD.ORG Subject: Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current Message-ID: <20000106155146.H33799@internode.com.au> References: <20000105204707.A14003@xfree86.org> <20000105211507.B3568@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000105211507.B3568@dragon.nuxi.com> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 09:15:07PM -0800, David O'Brien wrote: > Correct. The change is due to philosophical changes by the GCC > development team. GCC 2.95.2's cpp built from cccp.c is now a pure > preprocessor and knows much less about the world than it previously did. > In 2.95.2 there is now an additional cpp that is build using gcc.c and is > a driver for the cccp.c cpp. I dare you to try saying that again with a mouth full of peanuts! - mark :-) -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 22:27:32 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 689A614FC9; Wed, 5 Jan 2000 22:27:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 563131CD810 for ; Wed, 5 Jan 2000 22:27:31 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 5 Jan 2000 22:27:31 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Advance notice: Removing SHA1 passwords 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 Tomorrow I plan to remove the support for SHA1 passwords from libcrypt: this was (re-)added silently by Mark Murray a few months ago as part of a cleanup/re-merging of the libcrypt code, and he's already okayed the re-removal. The reason I want to remove this is because I intend to reimplement libcrypt in a more extensible way sometime over the next few months (assuming I can get over/around/under a final hurdle), and I'd prefer not to have any more compatability warts than necessary (if this were to make it into a release we'd have to support it forever). There's no real advantage to using SHA1 passwords anyway, since they're an algorithmically identical format to the default MD5 system, and there's nothing inherently insecure about that one. If anyone has been using SHA1 passwords, now's the time to regenerate them :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 23:44:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8FE5D15406 for ; Wed, 5 Jan 2000 23:44:45 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA71954; Thu, 6 Jan 2000 08:43:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001060743.IAA71954@freebsd.dk> Subject: Re: Mounting CD-ROM with ATA driver hangs system In-Reply-To: <00Jan6.151359est.40327@border.alcanet.com.au> from Peter Jeremy at "Jan 6, 2000 03:13:59 pm" To: peter.jeremy@alcatel.com.au (Peter Jeremy) Date: Thu, 6 Jan 2000 08:43:35 +0100 (CET) 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 Peter Jeremy wrote: > I just discovered that my ATAPI CD-ROM is no longer usable - when I > try to mount it, my maching hangs (hard). > > I'm running -current from cvs-cur 5961 (Monday about 0000UTC). > > The symptoms are: > > Run "mount -r /dev/acd0c /cdrom" > The CD-ROM activity light flashes briefly and the CD-ROM spins up. > The activity light then goes hard on for something like 20 seconds. > The kernel then prints: > acd0: atapi_timeout: cmd=READ_BIG - resetting > ata0: resetting devices .. _ > The cursor remains at the end of the line ("_" above). The CD-ROM > spins up and down. The HDD light stays hard on. > acd0: CDROM drive at ata0 as slave > acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA ^^^ You have enabled ATAPI DMA in your kernel config, dont, your drive apparently doesn't support it. DMA on ATAPI devices is disabled as default because _lots_ and I mean _lots_ of ATAPI devices claim to do DMA, but they actually dont :( -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 5 23:50:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DDAAB14F85; Wed, 5 Jan 2000 23:50:13 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA73510; Thu, 6 Jan 2000 08:50:07 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001060750.IAA73510@freebsd.dk> Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: from Brian Fundakowski Feldman at "Jan 5, 2000 06:50:45 pm" To: green@FreeBSD.org (Brian Fundakowski Feldman) Date: Thu, 6 Jan 2000 08:50:07 +0100 (CET) Cc: 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 Brian Fundakowski Feldman wrote: > How about this? It's mostly the changes in your patch, but it also takes > into account non-int{8,16}_t-sizing/alignment. It also takes care of the > truncation problem when you use outsl and insl, as part of that. Please > review it, as I think it should be the right thing to do. Hmm, sortof. In the real world we should newer ever see partial transfers, they should always be of N * DEV_BSIZE, so this is a bitt overkill. However some of the internal ATAPI handling use odd sizes for modes etc, but they are all at least 16 bit aligned, so 8 bit alignment is not needed, I'll have to check if we need 16 bit alignment, I can't remember ofhand... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 0:24:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 47859155A2 for ; Thu, 6 Jan 2000 00:24:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA01045; Thu, 6 Jan 2000 00:30:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001060830.AAA01045@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Archie Cobbs Cc: freebsd-current@freebsd.org Subject: Re: Boot serial console all blanks In-reply-to: Your message of "Wed, 05 Jan 2000 10:11:23 PST." <200001051811.KAA22026@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 00:30:32 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone else seen this problem? > > The 2nd and 3rd stage boot loader output to the serial port is all > blanks. That is, every character is output as a blank -- you can > see them printing, and see the 10 second autoboot messages, but > they're all space characters. Nope. In your case, you're using a 'classic' boot2, correct? I'd be wondering if it wasn't a BIOS issue, since both boot2 and the loader use the BIOS for serial output. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 0:42:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust206.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4A83F155D5; Thu, 6 Jan 2000 00:42:41 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Thu, 6 Jan 2000 03:42:25 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: current@FreeBSD.org Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: <200001060750.IAA73510@freebsd.dk> Message-ID: 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 On Thu, 6 Jan 2000, Soren Schmidt wrote: > It seems Brian Fundakowski Feldman wrote: > > How about this? It's mostly the changes in your patch, but it also takes > > into account non-int{8,16}_t-sizing/alignment. It also takes care of the > > truncation problem when you use outsl and insl, as part of that. Please > > review it, as I think it should be the right thing to do. > > Hmm, sortof. In the real world we should newer ever see partial > transfers, they should always be of N * DEV_BSIZE, so this is > a bitt overkill. However some of the internal ATAPI handling > use odd sizes for modes etc, but they are all at least 16 bit > aligned, so 8 bit alignment is not needed, I'll have to check > if we need 16 bit alignment, I can't remember ofhand... It's just as well. It's almost 4 AM and I've just about given up on getting this all working. Anyway, if everything has to be DEV_BSIZE, then I guess that would simplify things, except when I try, say, writing 4697 bytes as an audio blocksize (2 * 2352 - 7), it goes all the way through the acdstrategy as 4697... I don't know why DEV_BSIZE isn't respected, then, but I suppose Poul might be able to help here? Anyway, for now, I'd just be satisfied with having atapi-all.c corrected WRT the request->bytecount and length mixup. I've been working on this for four hours, have no clue what I'm doing wrong, and have school tomorrow. > > -Søren > -- 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 Thu Jan 6 1: 4:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8565E155DE; Thu, 6 Jan 2000 01:04:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA90935; Thu, 6 Jan 2000 10:04:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001060904.KAA90935@freebsd.dk> Subject: Re: ATA atapi-all.c problems/fixes/cleanups In-Reply-To: from Brian Fundakowski Feldman at "Jan 6, 2000 03:42:25 am" To: green@FreeBSD.ORG (Brian Fundakowski Feldman) Date: Thu, 6 Jan 2000 10:04:21 +0100 (CET) Cc: 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 Brian Fundakowski Feldman wrote: > > It's just as well. It's almost 4 AM and I've just about given up on getting > this all working. Anyway, if everything has to be DEV_BSIZE, then I guess > that would simplify things, except when I try, say, writing 4697 bytes > as an audio blocksize (2 * 2352 - 7), it goes all the way through the > acdstrategy as 4697... I don't know why DEV_BSIZE isn't respected, then, > but I suppose Poul might be able to help here? You should respect the blocksize when talking to a device with a fixed blocklength, dont write ! % blocksize blocks to the device.. Anyhow I've done a replacement for wormcontrol and have cleaned up the interface to the driver, I hope to have it tested for commit soon, this will solve the problem once and for all.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 1:28: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id C9B18155F9; Thu, 6 Jan 2000 01:27:55 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id JAA27482; Thu, 6 Jan 2000 09:27:49 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma027480; Thu, 6 Jan 00 09:27:23 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id UAA03779; Thu, 6 Jan 2000 20:27:21 +1100 (EST) From: Darren Reed Message-Id: <200001060927.UAA03779@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue) Date: Thu, 6 Jan 100 20:27:21 +1100 (EST) Cc: louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <20000106095316M.shin@nd.net.fujitsu.co.jp> from "Yoshinobu Inoue" at Jan 6, 0 09:53:16 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Yoshinobu Inoue, sie wrote: > > > Will we try to include the remaining KAME IPv6 integration into 4.0 before > > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and > > some applications. > > > > louie > > As an information from a person doing merging work, > -Kernel part is almost done(tcp patch is under review and testing). > -IPsec userland tools patch is also under review. > -some more tcp and udp userland tools need to be added but I think > it can be done including review time before 15th. > Then I think 4.0 will have some enough degree of IPv6 and > IPsec functionalities. > > Some items won't make it until 15th, > -IPv6 multicast routing > -many IPv6 ports > But after 4.0 is released, KAME package for 4.0 release will > be also made, and I think it can provide those part and other > update for users who needs more intensive support for IPv6 and > IPsec. For what it's worth, I think releasing 4.0 *without* IPv6 support is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be released *with* IPv6 support (I'd count IPv6 as being a big enough change to signify a major release number change). If that doesn't happen, then FreeBSD is chasing the wrong goals, IMHO. Personally, I think the timeline laid down - 25(?) days from now until 4.0 release is too aggressive. Given that the announcement (to me) seemed to be rather autocratic and possibly driven by marketting factors ("we need 4.0 out now regardless" ?) than by the general stability and maturity of -current. Well, that's the impression I get from an announcement encouraging people to do heavy testing in the next 10 days. I would encourage Jordan and others to have a rethink about the timeframe for 4.0 and what plans they have for it feature wise. To give you some idea, Solaris8 will have been in *beta* for ~9 months when it is released and will support IPv6 (telnet, inetd services, NFS) and IPSec when it is released around March. FreeBSD is no less an OS than Solaris is, when it comes to completeness. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 1:41:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id A844714E94; Thu, 6 Jan 2000 01:41:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA01480; Thu, 6 Jan 2000 01:47:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001060947.BAA01480@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Darren Reed Cc: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 0100 20:27:21 +1100." <200001060927.UAA03779@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 01:47:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Personally, I think the timeline laid down - 25(?) days from now > until 4.0 release is too aggressive. Given that the announcement > (to me) seemed to be rather autocratic and possibly driven by > marketting factors ("we need 4.0 out now regardless" ?) than by > the general stability and maturity of -current. Well, that's the > impression I get from an announcement encouraging people to do > heavy testing in the next 10 days. I would encourage Jordan and > others to have a rethink about the timeframe for 4.0 and what plans > they have for it feature wise. The 4.0 release has been scheduled for Q1 2000 since at least June last year. This has been a generally known fact since then. The feature freeze was announced for Dec 15th (but was largely suspended in order to accomodate new work and reality in general). Unfortunately, the 3.0 release made it very clear that simply sliding the release date indefinitely for "technical" reasons results in the release never happening. The alternative is this - people that for whatever reason haven't noticed that the release has been looming ever closer suddenly realise that it's right over their shoulder and burst out in surprise. > To give you some idea, Solaris8 will have been in *beta* for ~9 months > when it is released and will support IPv6 (telnet, inetd services, NFS) > and IPSec when it is released around March. FreeBSD is no less an OS > than Solaris is, when it comes to completeness. I'd love to have Sun's resources, not to mention their mechanisms for motivating their developers. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2: 6:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 7566915452 for ; Thu, 6 Jan 2000 02:06:48 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id UAA13642; Thu, 6 Jan 2000 20:06:33 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd013639; Thu Jan 6 20:06:29 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA11215 for ; Thu, 6 Jan 2000 20:06:06 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id UAA22210 for ; Thu, 6 Jan 2000 20:06:05 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id UAA21698; Thu, 6 Jan 2000 20:06:04 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200001061006.UAA21698@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Small fix to netstat argument processing Date: Thu, 06 Jan 2000 20:06:04 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got very used to an alias ns='netstat -f inet' which lets me do all the things I like to do without annoying me with stuff I don't want to see. All the options that don't care about the address family just ignore that option. Or, used to. Recently that changed, and "netstat -f inet -i" in particular changed to give the -f flag priority over the -i flag. This makes no sense to me, so I intend to commit this patch: --- netstat/main.c.old Tue Jan 4 16:14:46 2000 +++ netstat/main.c Thu Jan 6 18:19:24 2000 @@ -460,9 +460,6 @@ */ #endif if (iflag) { - if (af != AF_UNSPEC) - goto protostat; - kread(0, 0, 0); intpr(interval, nl[N_IFNET].n_value, NULL); exit(0); @@ -501,7 +498,6 @@ exit(0); } - protostat: kread(0, 0, 0); if (af == AF_INET || af == AF_UNSPEC) for (tp = protox; tp->pr_name; tp++) It removes the special case that specifically makes "netstat -f inet -i" act the opposite to the way it used to (and the way I expect). Any problems, folks? Is there some bizarre IPv6 impact I've not seen? Hmm, I've just noticed some small misalignment of column headings in the default output. I'll fix that too. Stephen. PS Roll on 4.0-RELEASE! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2: 7:54 2000 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 21BF814F28 for ; Thu, 6 Jan 2000 02:07:49 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e06A5ew24353; Thu, 6 Jan 2000 12:05:40 +0200 (SAST) Message-Id: <200001061005.e06A5ew24353@gratis.grondar.za> To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: rlogin from 3.X to 4.0 problem... References: <200001051721.SAA20036@info.iet.unipi.it> In-Reply-To: <200001051721.SAA20036@info.iet.unipi.it> ; from Luigi Rizzo "Wed, 05 Jan 2000 18:21:56 +0100." Date: Thu, 06 Jan 2000 12:05:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: > > > rlogin bsd4 > assword:hey this is great! > > why is the initial 'P' missing, and the password echoed ? MFC of etc/pam.conf coming to fix this... 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 Jan 6 2:14:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.01019freenet.de (mout0.01019freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id 5C3021547D; Thu, 6 Jan 2000 02:14:47 -0800 (PST) (envelope-from julian@elischer.org) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout0.01019freenet.de with esmtp (Exim 3.12 #2) id 1269vv-000456-00; Thu, 06 Jan 2000 11:14:19 +0100 Received: from [212.81.229.62] (helo=jules.elischer.org) by mx1.01019freenet.de with smtp (Exim 3.12 #2) id 1269vu-0003ji-00; Thu, 06 Jan 2000 11:14:18 +0100 Message-ID: <38746AEC.167EB0E7@elischer.org> Date: Thu, 06 Jan 2000 02:14:04 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Darren Reed Cc: Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001060927.UAA03779@avalon.reed.wattle.id.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darren Reed wrote: > > > For what it's worth, I think releasing 4.0 *without* IPv6 support > is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be > released *with* IPv6 support (I'd count IPv6 as being a big enough > change to signify a major release number change). If that doesn't > happen, then FreeBSD is chasing the wrong goals, IMHO. > > Personally, I think the timeline laid down - 25(?) days from now > until 4.0 release is too aggressive. Given that the announcement > (to me) seemed to be rather autocratic and possibly driven by > marketting factors ("we need 4.0 out now regardless" ?) than by > the general stability and maturity of -current. Well, that's the > impression I get from an announcement encouraging people to do > heavy testing in the next 10 days. I would encourage Jordan and > others to have a rethink about the timeframe for 4.0 and what plans > they have for it feature wise. I agree with this.. I think that 4.0 is clsoe but it's just not there yet. I think it needs IPV6 to have reached a better milestone, and certainly the stuff that warner is doing (and others) needs to be a little further down the track. I think the release needs to be made at a 'knee in the curve' of change and I think that the slope after the suggested date will be identical to that before it, which to me indicates that there is no real rason or axcuse to make that the release. I think we should layout a plan of everything that everyone is working on and try find a natural inflection point. I reallu thing that IPV6 is too important to make a release with it "half" implemented. > > To give you some idea, Solaris8 will have been in *beta* for ~9 months > when it is released and will support IPv6 (telnet, inetd services, NFS) > and IPSec when it is released around March. FreeBSD is no less an OS > than Solaris is, when it comes to completeness. > > Darren -- +------------------------------------+ | __--_|\ Julian Elischer | | / \ julian@elischer.org +------Near Koln/Duseldorf | ( OZ ) World tour 2000 +- X_.---._/ presently in: Germany v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2:26: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id E002D154D8 for ; Thu, 6 Jan 2000 02:25:59 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 7957 invoked from network); 6 Jan 2000 10:25:59 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 6 Jan 2000 10:25:59 -0000 Date: Thu, 6 Jan 2000 05:25:27 -0500 (EST) From: Donn Miller To: Julian Elischer Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <38746AEC.167EB0E7@elischer.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 Thu, 6 Jan 2000, Julian Elischer wrote: > I agree with this.. > I think that 4.0 is clsoe but it's just not there yet. > I think it needs IPV6 to have reached a better milestone, and certainly > the stuff that warner is doing (and others) needs to be a little > further down the track. I agree. Why rush 4.0-RELEASE out the door if it's "not there yet"? One possibility is to make our 4.0-current something like 3.9-RELEASE, and when everything has been added, release 4.0-RELEASE. 3.9-RELEASE would be a lot like 4.0-REL, only with some missing parts (such as IPV6 you just mentioned). That way, 3.9-REL would bear all the shortcomings of a release ending in 0, and when 4.0-REL comes out, it would be less buggy than most *.0 releases. (It would really be at the level of a *.1 release then.) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2:29:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 5FD1915456 for ; Thu, 6 Jan 2000 02:29:22 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id TAA16274; Thu, 6 Jan 2000 19:29:15 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id TAA02894; Thu, 6 Jan 2000 19:29:14 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id TAA09511; Thu, 6 Jan 2000 19:29:13 +0900 (JST) To: syssgm@detir.qld.gov.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: Small fix to netstat argument processing In-Reply-To: <200001061006.UAA21698@nymph.detir.qld.gov.au> References: <200001061006.UAA21698@nymph.detir.qld.gov.au> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000106192950T.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Jan 2000 19:29:50 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Recently that changed, and "netstat -f inet -i" in particular changed to > give the -f flag priority over the -i flag. This makes no sense to me, > so I intend to commit this patch: Could this be left with adding sflag check? Because now there is interface statistics display mode, when, e.g. netstat -s -I bar0 -f inet6 is specified. (though this is inet6 only now.) If it is confusing, I'll think of adding new option flag for it. --- netstat/main.c.old Tue Jan 4 16:14:46 2000 +++ netstat/main.c Thu Jan 6 18:19:24 2000 @@ -460,9 +460,6 @@ */ #endif if (iflag) { - if (af != AF_UNSPEC) + if (sflag && af != AF_UNSPEC) goto protostat; kread(0, 0, 0); intpr(interval, nl[N_IFNET].n_value, NULL); exit(0); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2:32:59 2000 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 8FA2F14EFC for ; Thu, 6 Jan 2000 02:32:58 -0800 (PST) (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.9.3) with ESMTP id CAA39454; Thu, 6 Jan 2000 02:32:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001061032.CAA39454@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 02:14:04 PST." <38746AEC.167EB0E7@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 02:32:47 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Curious , what is elischer.org ? 8) -- 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 Jan 6 2:44:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 0159015517 for ; Thu, 6 Jan 2000 02:44:26 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id TAA02883; Thu, 6 Jan 2000 19:44:24 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id TAA13827; Thu, 6 Jan 2000 19:44:23 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id TAA09945; Thu, 6 Jan 2000 19:44:23 +0900 (JST) To: syssgm@detir.qld.gov.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: Small fix to netstat argument processing In-Reply-To: <20000106192950T.shin@nd.net.fujitsu.co.jp> References: <200001061006.UAA21698@nymph.detir.qld.gov.au> <20000106192950T.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000106194459M.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Jan 2000 19:44:59 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think my last description was poor. > Could this be left with adding sflag check? > Because now there is interface statistics display mode, when, e.g. Maybe improved one is, Because now there is a mode where protocol specific statistics over each interface is displayed. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 2:45:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 2CCC714BF9 for ; Thu, 6 Jan 2000 02:45:39 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA74802; Thu, 6 Jan 2000 12:44:13 +0200 (EET) (envelope-from ru) Date: Thu, 6 Jan 2000 12:44:13 +0200 From: Ruslan Ermilov To: Amancio Hasty Cc: Julian Elischer , current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106124413.I31198@relay.ucb.crimea.ua> Mail-Followup-To: Amancio Hasty , Julian Elischer , current@FreeBSD.org References: <38746AEC.167EB0E7@elischer.org> <200001061032.CAA39454@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <200001061032.CAA39454@rah.star-gate.com>; from Amancio Hasty on Thu, Jan 06, 2000 at 02:32:47AM -0800 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 02:32:47AM -0800, Amancio Hasty wrote: > > Curious , what is elischer.org ? 8) > According to www.elischer.org, this is the temporary home page for the Elischer family's internet enterprises and Family stuff. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 3: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 1D3D714C05 for ; Thu, 6 Jan 2000 03:05:11 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id CBF761F8B; Thu, 6 Jan 2000 12:05:06 +0100 (CET) Date: Thu, 6 Jan 2000 12:05:06 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: GDB Problems ! Message-ID: <20000106120506.A31489@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I think i already mentioned the following issue several months ago ... but just noticed this again. And considering 4.0 is coming up soon, I really think this ought to be fixed. see the following testcase: #include int main(int argc, char **argv) { int i = 0; for (i = 0; i < 10; i++) fprintf(stderr, "i = %d\n", i); return 0; } Compiling this program with -ggdb will give normal results (a list of i = 0, upto i = 9). However when running the program through gdb Every Value you can print is completely Bogus, which makes debugging impossible. Things like the following will happen: (gdb) break main Breakpoint 1 at 0x804841e: file gdbtest.c, line 6. (gdb) run Starting program: /home/daeron/./gdbtest Breakpoint 1, main (argc=-1077937360, argv=0x2805e100) at gdbtest.c:6 6 int i = 0; (gdb) (gdb) next 8 for (i = 0; i < 10; i++) (gdb) 9 fprintf(stderr, "i = %d\n", i); (gdb) print i $1 = -1077937368 Notice the completely bogus value of argc, and the same goes for i. the program still outputs the correct values, just requesting them from gdb is broken. Fortunately you can compile it with -g only and GDB Will work properly ... but -ggdb is a flag i encounter quite often for debugging purposes. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 3:12:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C5D9514A05 for ; Thu, 6 Jan 2000 03:12:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA21167 for current@freebsd.org; Thu, 6 Jan 2000 12:12:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001061112.MAA21167@freebsd.dk> Subject: wormcontrol replacement coming! To: current@freebsd.org Date: Thu, 6 Jan 2000 12:12:23 +0100 (CET) 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 I've just done a replacement for wormcontrol that allows burning CDR/CDRW with just one command. Its simpleminded but it works. Just a FYI as I know several people have said they where thinking about doing such a thingy. The API to the kernel has changed too, finally I got around to cleaning up the interface.. I'll commit it later when I have tested all combinations and written a man page... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 3:23: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id AF9CD15588; Thu, 6 Jan 2000 03:22:59 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id MAA27428; Thu, 6 Jan 2000 12:22:57 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA28368; Thu, 6 Jan 2000 12:22:56 +0100 (MET) Date: Thu, 6 Jan 2000 12:22:56 +0100 From: Eivind Eklund To: Julian Elischer Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106122256.B13922@bitbox.follo.net> References: <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38746AEC.167EB0E7@elischer.org>; from julian@elischer.org on Thu, Jan 06, 2000 at 02:14:04AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 02:14:04AM -0800, Julian Elischer wrote: > Darren Reed wrote: > > > > > > > For what it's worth, I think releasing 4.0 *without* IPv6 support > > is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be > > released *with* IPv6 support (I'd count IPv6 as being a big enough > > change to signify a major release number change). If that doesn't > > happen, then FreeBSD is chasing the wrong goals, IMHO. > > > > Personally, I think the timeline laid down - 25(?) days from now > > until 4.0 release is too aggressive. Given that the announcement > > (to me) seemed to be rather autocratic and possibly driven by > > marketting factors ("we need 4.0 out now regardless" ?) than by > > the general stability and maturity of -current. Well, that's the > > impression I get from an announcement encouraging people to do > > heavy testing in the next 10 days. I would encourage Jordan and > > others to have a rethink about the timeframe for 4.0 and what plans > > they have for it feature wise. > > I agree with this.. > I think that 4.0 is clsoe but it's just not there yet. > I think it needs IPV6 to have reached a better milestone, and certainly > the stuff that warner is doing (and others) needs to be a little > further down the track. In my opinion, whether the present plans for 4.0-RELEASE is appropriate or not somewhat depends on what the further plans are for the release engineering. I believe putting down RELENG_4 without having a finished IPv6 and functional laptop support (I'm not sure what state this is in right now) would be a bad idea. > I think we should layout a plan of everything that everyone is > working on and try find a natural inflection point. I reallu thing > that IPV6 is too important to make a release with it "half" > implemented. If somebody is up to organizing it, it would be nice to have an overview of what everybody would like to put in before we decide to put down a branch. However, given how much variance most of us has in how much effort (or at least results) we're able to push into FreeBSD, it is somewhat hard to create clear lines for things, so we might have to be satisfied with lining up some of the most important things. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 4: 0:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id E8D7F155F7; Thu, 6 Jan 2000 04:00:38 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA06884; Thu, 6 Jan 2000 13:00:18 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be (Unverified) Message-Id: In-Reply-To: References: Date: Thu, 6 Jan 2000 12:55:06 +0100 To: Donn Miller , Julian Elischer From: Brad Knowles Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, 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 5:25 AM -0500 2000/1/6, Donn Miller wrote: > I agree. Why rush 4.0-RELEASE out the door if it's "not there yet"? One > possibility is to make our 4.0-current something like 3.9-RELEASE, and > when everything has been added, release 4.0-RELEASE. No, I disagree. There's too much in 4.0-CURRENT that has changed from 3.x-STABLE, and there needs to be a major version bump. I'd prefer to release 4.0-CURRENT sooner, and then perhaps follow-up with a 4.1-CURRENT soon thereafter to pick up IPv6 and all the other things that we had hoped to put into 4.0-CURRENT, but just couldn't make it in time. More releases more often are better than indefinitely holding up releases waiting for just that one last thing to be finished. -- 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 Jan 6 4: 2:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id EA78014F87 for ; Thu, 6 Jan 2000 04:02:21 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id VAA27046; Thu, 6 Jan 2000 21:02:20 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id VAA05191; Thu, 6 Jan 2000 21:02:19 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id VAA12430; Thu, 6 Jan 2000 21:02:19 +0900 (JST) To: syssgm@detir.qld.gov.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: Small fix to netstat argument processing In-Reply-To: <200001061006.UAA21698@nymph.detir.qld.gov.au> References: <200001061006.UAA21698@nymph.detir.qld.gov.au> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000106210255C.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Jan 2000 21:02:55 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 101 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, I've just noticed some small misalignment of column headings in the > default output. I'll fix that too. > > Stephen. I also noticed that my another IPv6 related change is one of main cause of the misalignment. So I also tried to make patches for it, including "netstat -f inet -i" issue. Does these patches fix your problem, or should another better fix is desired? Please give me any opinions. Yoshinobu Inoue Index: inet.c =================================================================== RCS file: /home/ncvs/src/usr.bin/netstat/inet.c,v retrieving revision 1.36 diff -u -r1.36 inet.c --- inet.c 1999/12/13 20:08:43 1.36 +++ inet.c 2000/01/06 11:57:57 @@ -219,7 +219,7 @@ if (Aflag) printf("%-8.8s ", "Socket"); if (Lflag) - printf("%-14.14s %-21.21s\n", + printf("%-14.14s %-22.22s\n", "Listen", "Local Address"); else printf(Aflag ? @@ -245,15 +245,22 @@ printf("%-14.14s ", buf); } else continue; - else - printf("%-3.3s%s%s %6ld %6ld ", name, - (inp->inp_vflag & INP_IPV4) ? "4" : "", + else { + const u_char *vchar; + #ifdef INET6 - (inp->inp_vflag & INP_IPV6) ? "6" : + if ((inp->inp_vflag & INP_IPV6) != 0) + vchar = ((inp->inp_vflag & INP_IPV4) != 0) + ? "46" : "6 "; + else #endif - "", + vchar = ((inp->inp_vflag & INP_IPV4) != 0) + ? "4 " : " "; + + printf("%-3.3s%-2.2s %6ld %6ld ", name, vchar, so->so_rcv.sb_cc, so->so_snd.sb_cc); + } if (nflag) { if (inp->inp_vflag & INP_IPV4) { inetprint(&inp->inp_laddr, (int)inp->inp_lport, @@ -801,7 +808,7 @@ else sprintf(cp, "%d", ntohs((u_short)port)); width = Aflag ? 18 : 22; - printf(" %-*.*s", width, width, line); + printf("%-*.*s ", width, width, line); } /* Index: inet6.c =================================================================== RCS file: /home/ncvs/src/usr.bin/netstat/inet6.c,v retrieving revision 1.2 diff -u -r1.2 inet6.c --- inet6.c 1999/12/28 02:37:01 1.2 +++ inet6.c 2000/01/06 11:57:57 @@ -904,7 +904,7 @@ else sprintf(cp, "%d", ntohs((u_short)port)); width = lflag ? 45 : Aflag ? 18 : 22; - printf(" %-*.*s", width, width, line); + printf("%-*.*s ", width, width, line); } /* Index: main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/netstat/main.c,v retrieving revision 1.31 diff -u -r1.31 main.c --- main.c 1999/12/28 02:37:01 1.31 +++ main.c 2000/01/06 11:57:57 @@ -460,7 +460,7 @@ */ #endif if (iflag) { - if (af != AF_UNSPEC) + if (sflag && af != AF_UNSPEC) goto protostat; kread(0, 0, 0); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 4:31:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.hk.linkage.net (smtp01.hk.linkage.net [210.184.16.66]) by hub.freebsd.org (Postfix) with ESMTP id 83511154EC for ; Thu, 6 Jan 2000 04:31:21 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by smtp01.hk.linkage.net (8.8.8/8.8.8) with SMTP id UAA21991 for ; Thu, 6 Jan 2000 20:25:31 +0800 (HKT) Received: (qmail 17964 invoked from network); 6 Jan 2000 12:56:43 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.223) by mail.spnetctg.com with SMTP; 6 Jan 2000 12:56:43 -0000 Message-ID: <3874899F.D61A9110@spnetctg.com> Date: Thu, 06 Jan 2000 18:25:03 +0600 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Installation problem 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 new in FreeBSD. Today i install FreeBSD3.3 sucessfully. I have 2 harddrive both 6.4GB. In one harddisk I have Redhat and another one i install FreeBSD 3.3 now. I install Freebsd boot manager but i don't find it. but when i add Freebsd in Lilo (edit /etc/lilo.conf file) it shows : hdb1 = device not configured. what i will do ? when i cut linux plug from linux harddrive, and reboot with single Freebsd harddrive ,freebsd shows : F1 FreeBSD. what's problem . please help anybody. satyajit NB: sorry to mail this mailing list, i'm not subscribe freebsd-question , later i will do it. now pls help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 4:36:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id E724F14F87; Thu, 6 Jan 2000 04:36:29 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p70.rlz.netvision.net.il [62.0.168.72]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id OAA25655; Thu, 6 Jan 2000 14:36:26 +0200 (IST) Message-ID: <38748CE5.AD1AD786@freenet.co.uk> Date: Thu, 06 Jan 2000 12:39:01 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Eivind Eklund Cc: Julian Elischer , Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, freebsd-committers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > If somebody is up to organizing it, it would be nice to have an > overview of what everybody would like to put in before we decide to > put down a branch. However, given how much variance most of us has in > how much effort (or at least results) we're able to push into FreeBSD, > it is somewhat hard to create clear lines for things, so we might have > to be satisfied with lining up some of the most important things. I vote for: - IPv6 and the tools to go with it (Yoshinobu Inoue) - Better laptop (PC card) support, possibly Cardbus (Warner Losh) - Improved soundcard support: right now newpcm is broken in a number of ways (Cameron Grant), possibly new MIDI (Seigo Tanimura) - Reorganised source tree (e.g. filesystems must go into /sys/fs, etc.) Realistically though, IPv6 is the most important issue here; people can continue to use the old pccard system while Warner is working on the new one, and the old sound driver until newpcm is fixed and new MIDI integrated. Anything will go as long as we don't lose any existing features. People tend to get very disappointed when they find that something that used to work with an earlier release has been replaced by something that doesn't (yet). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 5:13:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2D7A51563A; Thu, 6 Jan 2000 05:13:24 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id IAA27072; Thu, 6 Jan 2000 08:12:49 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Thu, 6 Jan 2000 08:12:49 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Darren Reed Cc: Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001060927.UAA03779@avalon.reed.wattle.id.au> 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, 6 Jan 100, Darren Reed wrote: > For what it's worth, I think releasing 4.0 *without* IPv6 support > is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be > released *with* IPv6 support (I'd count IPv6 as being a big enough > change to signify a major release number change). If that doesn't > happen, then FreeBSD is chasing the wrong goals, IMHO. I agree entirely -- releasing without IPv6 and IPsec would be a great mistake. At least in the research community, I know of a lot of people relying on FreeBSD 4.0 to be the answer to their problem of locating an open source freely licensable next generation networking platform. Both at TIS and on CAIRN, the DARPA test network, the assumption is that we will jump to FreeBSD 4.0 for experimental networking work as soon as it is released--people are sick of patching Kame on top of FreeBSD, and want it integrated so that they can concentrate on their own experiments (i.e., multicast work, new routing protocols, ad hoc networks, queueing techniques, wireless network technologies, extremely high bandwidth, etc). I can tell you right not that announcing that we don't have decent (i.e., largely complete) out of the box support for IPsec and IPv6 would result in serious disillusionment :-). And as out-there as the research stuff may seem, it's not bad to have on our platform. I'd really hate to see CAIRN switch to Linux as it's backbone router platform :-). CAIRN is a primary testbed spot for a number of new networking technologies that presumably will be quite popular in the near future--by having FreeBSD be the platform of choice for CAIRN, we guarantee those technologies will be available for FreeBSD, helping to maintain our technological lead. The big question at December IETF at the FreeBSD dinner was "When will IPv6 and IPsec be in the tree--we need them". And I think there's a difference between holding up the release indefinitely, and saying "we're waiting on IPv6 and IPsec, and will release once it is ready" -- it's not a plethora of features, rather, two very specific features from a stable source base (Kame) that is well tested, and with developers clearly interested in a timely and successful integration. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 5:28:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by hub.freebsd.org (Postfix) with ESMTP id 7DC7E15628; Thu, 6 Jan 2000 05:28:53 -0800 (PST) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id IAA11896; Thu, 6 Jan 2000 08:28:32 -0500 (EST) Message-Id: <200001061328.IAA11896@chai.torrentnet.com> To: Julian Elischer Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 02:14:04 PST." <38746AEC.167EB0E7@elischer.org> Date: Thu, 06 Jan 2000 08:28:32 -0500 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think we should layout a plan of everything that everyone is working > on > and try find a natural inflection point. I reallu thing that IPV6 is too > important to make a release with it "half" implemented. What would be nice is a table of features versus release in which they appear. Something like 3.3 3.4 3.x? 4.0 4.1 5.0 hood ornaments x x tailights p x x hubcaps x bigger trunk x sound system 8 track x cassette x fairings Where x == full support, p == partial support. More complex features get broken into featurelets. Adjust and publish the table every few weeks/months to reflect reality -- generally that means turning an x into p or moving it to the next column! Separately you lay down a tentative schedule so people know when to expect what feature + developers have a target to shoot for and last minute surprises are fewer. Given the volunteer nature of the project the schedule will be much more tentative but it is useful nonetheless. Having said all that, IMHO a 4.0 release with partial IPv6 support would be useful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 5:59: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id ECC8914FDE for ; Thu, 6 Jan 2000 05:59:02 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 834C3137F6C for ; Thu, 6 Jan 2000 08:58:57 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id IAA26624; Thu, 6 Jan 2000 08:58:57 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14452.40864.973241.492117@trooper.velocet.net> Date: Thu, 6 Jan 2000 08:58:56 -0500 (EST) To: freebsd-current@freebsd.org Subject: BOOTP and IPFIREWALL X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG options BOOTP and options IPFIREWALL appear to be incompatible in -CURRENT. I havn't tried -STABLE. While the kernel compiles fine, the BOOTP code fails to send the discover packet and panic()'s. While it might not be immediately obvious that you'd want IPFIREWALL in a BOOTP-loaded machine, there are good reasons for it... 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 Thu Jan 6 6:50:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id D9852155F8; Thu, 6 Jan 2000 06:50:07 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id JAA65028; Thu, 6 Jan 2000 09:45:11 -0500 (EST) (envelope-from steve) Date: Thu, 6 Jan 2000 09:45:11 -0500 From: Steve Ames To: Donn Miller Cc: Julian Elischer , Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106094511.A30328@virtual-voodoo.com> References: <38746AEC.167EB0E7@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Donn Miller on Thu, Jan 06, 2000 at 05:25:27AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree. Why rush 4.0-RELEASE out the door if it's "not there yet"? One > possibility is to make our 4.0-current something like 3.9-RELEASE, and > when everything has been added, release 4.0-RELEASE. 3.9-RELEASE would be > a lot like 4.0-REL, only with some missing parts (such as IPV6 you just > mentioned). That way, 3.9-REL would bear all the shortcomings of a > release ending in 0, and when 4.0-REL comes out, it would be less buggy > than most *.0 releases. (It would really be at the level of a *.1 release > then.) I don't think anything is being rushed out the door. _FEATURE_ freeze is January 15th. That means that any new features to be added to 4.0 have to be in the source repository by January 15th... now once a feature is in, I'm sure _AMPLE_ time will be given to get every 4.0 feature working completely before 4.0 becomes -RELEASE. My question is how much time are developers/testers being given between feature freeze (9 days from now) and release to get all code working and stable? FWIW, I'd call IPv6 a feature... releasing half a feature looks pretty rushed. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 6:50:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A698815618; Thu, 6 Jan 2000 06:50:10 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id PAA04595; Thu, 6 Jan 2000 15:50:04 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id PAA06428; Thu, 6 Jan 2000 15:49:45 +0100 (CET) (envelope-from andreas) Date: Thu, 6 Jan 2000 15:49:45 +0100 From: Andreas Klemm To: Brad Knowles Cc: Donn Miller , Julian Elischer , Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106154945.A5887@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Thu, Jan 06, 2000 at 12:55:06PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: > More releases more often are better than indefinitely holding up > releases waiting for just that one last thing to be finished. Second that. And to follow on that... FreeBSD 4.0 will become the new STABLE. So 4.0 should become as stable as possible. I think there are certainly many people running on FreeBSD 2.x and 3.x who wait for something like 4.0 to become a new stable release. So we should get them the new STABLE toy ! In that short timeframe this can only be achieved by not including too much new technology into it. Otherwise we label something as STABLE which is in fact something like a -current with respect to IP V6 and IPSec. Additionally it gives developers and customers time to breath. IP V6 and IPSec should be integrated into the new 5.0(?)-current. With FreeBSD-4.0-RELEASE we will get a rapidly growing user base for 4.0 and we'll certainly have enough to do to make it really stable for everybody. In the meantime people have their new testbed in 5.0-current. If the dust has setteled in -current, I'd vote to merge IP V6 and IPsec with as much client tools as possible into something like 4.1-RELEASE. 4.0-STABLE I'd personally not touch with any brand new network code. So people have a chance to remain some time on 4.0-RELEASE or 4.0-STABLE. Another possibility would be to wait until the dust settles after merging IP V6 and IPsec into -current and release FreeBSD 4.0 complete with that features at a later time (+1-2 months). But that's probably not wanted... What do you think of that ?! Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 6:54:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id C08B115676; Thu, 6 Jan 2000 06:54:50 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id JAA72606; Thu, 6 Jan 2000 09:47:56 -0500 (EST) (envelope-from steve) Date: Thu, 6 Jan 2000 09:47:56 -0500 From: Steve Ames To: Brad Knowles Cc: Donn Miller , Julian Elischer , Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106094756.B30328@virtual-voodoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Brad Knowles on Thu, Jan 06, 2000 at 12:55:06PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > More releases more often are better than indefinitely holding up > releases waiting for just that one last thing to be finished. I think a recent thread on -STABLE indicates that the majority of end users seem to believe that -RELEASE means STABLE and should be fully operational not a wide-beta under a release name. I also thing that an extremely complete and stable .0 release would be good for the FreeBSD release image. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 7:15:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id E27AB14FB0; Thu, 6 Jan 2000 07:15:41 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id PAA02122; Thu, 6 Jan 2000 15:15:30 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000106154945.A5887@titan.klemm.gtn.com> Date: Thu, 06 Jan 2000 15:15:30 -0000 (GMT) From: "Steve O'Hara-Smith" To: Andreas Klemm Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: current@FreeBSD.org, committers@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jan-00 Andreas Klemm wrote: > On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: >> More releases more often are better than indefinitely holding up >> releases waiting for just that one last thing to be finished. > > Second that. And to follow on that... > FreeBSD 4.0 will become the new STABLE. Are you sure about that 3-stable did not start until well after 3.0-RELEASE. I would expect the same thing with 4.0. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 7:40:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 3EB8615629 for ; Thu, 6 Jan 2000 07:40:20 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id CAA29380 for ; Fri, 7 Jan 2000 02:40:16 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Fri, 7 Jan 2000 02:40:16 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: freebsd-current@FreeBSD.ORG Subject: mergemaster(8) busted 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 cvsup'ing, a -current system based on userland/kernel dated 31-dec-1999, 'mergemaster -sv' is failing with mknod errors. cd src/sbin/mknod ; make all install ; make clean fixes it. -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 7:50:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-045.rp-plus.de [149.221.237.45]) by hub.freebsd.org (Postfix) with ESMTP id 969B71560D for ; Thu, 6 Jan 2000 07:50:33 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 8B3BBAB91 for ; Thu, 6 Jan 2000 16:45:16 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id QAA03242 for freebsd-current@FreeBSD.ORG; Fri, 31 Dec 1999 16:45:58 +0100 (CET) (envelope-from alex) Date: Fri, 31 Dec 1999 16:45:58 +0100 From: Alexander Langer To: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 Message-ID: <19991231164557.G1327@cichlids.cichlids.com> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199912190443.VAA00923@harmony.village.org> <199912190845.AAA01286@mass.cdrom.com> <19991219143433.A336@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xJK8B5Wah2CMJs8h" X-Mailer: Mutt 1.0i In-Reply-To: <19991219143433.A336@cichlids.cichlids.com>; from alex@big.endian.de on Sun, Dec 19, 1999 at 02:34:33PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --xJK8B5Wah2CMJs8h Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Thus spake Alexander Langer (alex@big.endian.de): > Here are the messages regarding ata and hdd's: >=20 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > ... > ad0: ATA-3 disk at ata0 as master > ad0: 6197 MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 After I have now posted the boot-messages. Can you see any reason for it? Alex --=20 I doubt, therefore I might be.=20 --xJK8B5Wah2CMJs8h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iQEVAwUBOGzPtLRIIUSeqRcRAQH7rQf+Jt/wUXDydetHIp8ZC1/+YxAUDRNmpNHI 9G9NvQEcqgAoDceNwvTnUUvyq/FZhkt19oSxRZJiXqfiXidfVl65OahTtUsEoo3D JlN/VB3Duqn8TJH2vhVxpzXDvQDGELBVCJRvEq/UAd8xF0daHatq6PsNVJonAXnT yrX66uy7Zqxi/kVYgtkjPJ36jA4EjzPTjQ5Ykr0LOgesP4AfbAdF7OculdmTVolR o6nzQhFUFXkG6g1qpOJdMA/LX9kpg386LqHRRMbOSw+bWh1+Qg+EwK7uKMrJBuIF HdFRkpCOur5q3DoEESLJxvHWJ7Cul1uWsPUINhQYuY52i/soeoyUyA== =MdV5 -----END PGP SIGNATURE----- --xJK8B5Wah2CMJs8h-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8: 1:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from cloudbase.sixforty.co.uk (cloudbase.sixforty.co.uk [194.207.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C3561560D for ; Thu, 6 Jan 2000 08:01:28 -0800 (PST) (envelope-from l.farr@epcdirect.co.uk) Received: from monkey (pepe.sixforty.co.uk [194.207.180.202]) by cloudbase.sixforty.co.uk (8.9.3/8.8.7) with SMTP id PAA24067 for ; Thu, 6 Jan 2000 15:41:18 GMT Reply-To: From: "Lawrence Farr" To: Subject: Booting with a Mylex-DAC960PL Installed Date: Thu, 6 Jan 2000 16:01:23 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I downloaded Jan 2nd Current, made the floppies, and tried to boot a box with a DAC-960PL installed. The system hung as soon as it started to read from floppy. Rebooted, turned off the BIOS on the Mylex, system booted OK. Installed directly to the Mylex, and it all came to a halt with "Tried to write beyond end of drive" errors, which I am assuming is a geometry issue. Any ideas, short of booting from a separate disk? PS - The BIOS on the Mylex is Current. Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8: 9:28 2000 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 8DC8B1560D; Thu, 6 Jan 2000 08:09:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA11687; Thu, 6 Jan 2000 09:09:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA77304; Thu, 6 Jan 2000 09:09:23 -0700 (MST) Message-Id: <200001061609.JAA77304@harmony.village.org> To: Eivind Eklund Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: committers@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Thu, 06 Jan 2000 12:22:56 +0100." <20000106122256.B13922@bitbox.follo.net> References: <20000106122256.B13922@bitbox.follo.net> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> Date: Thu, 06 Jan 2000 09:09:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106122256.B13922@bitbox.follo.net> Eivind Eklund writes: : I believe putting down RELENG_4 without having a finished IPv6 and : functional laptop support (I'm not sure what state this is in right : now) would be a bad idea. The laptop support is approx that of 3.x. The fe device is no longer supported as a pccard. The sn device has been added. The YE_DATA floppy device isn't supported, but could be if some is motivated to fix it. There may be a few lingering hot plug issues in the old code's migration to newbus. The newcard stuff as I've been calling it won't be stable in time, but might be functional. I'd always counted on Q1 2000 being late march rather than february. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8:26:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 81BC114E58; Thu, 6 Jan 2000 08:26:07 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id RAA02771; Thu, 6 Jan 2000 17:26:05 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA30958; Thu, 6 Jan 2000 17:26:04 +0100 (MET) Date: Thu, 6 Jan 2000 17:26:04 +0100 From: Eivind Eklund To: Warner Losh Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106172604.T13922@bitbox.follo.net> References: <20000106122256.B13922@bitbox.follo.net> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> <200001061609.JAA77304@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001061609.JAA77304@harmony.village.org>; from imp@village.org on Thu, Jan 06, 2000 at 09:09:22AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: > In message <20000106122256.B13922@bitbox.follo.net> Eivind Eklund writes: > : I believe putting down RELENG_4 without having a finished IPv6 and > : functional laptop support (I'm not sure what state this is in right > : now) would be a bad idea. > > The laptop support is approx that of 3.x. The fe device is no longer > supported as a pccard. The sn device has been added. The YE_DATA > floppy device isn't supported, but could be if some is motivated to > fix it. There may be a few lingering hot plug issues in the old > code's migration to newbus. How much benefit would you be getting by having 4.0 ship with newcard instead of what's there now? E.g, by having 4.0-PAO relate to newcard rather than what's in presently? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8:32:12 2000 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 38728157C1; Thu, 6 Jan 2000 08:32:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA11780; Thu, 6 Jan 2000 09:32:04 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA77504; Thu, 6 Jan 2000 09:32:04 -0700 (MST) Message-Id: <200001061632.JAA77504@harmony.village.org> To: Eivind Eklund Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: committers@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Thu, 06 Jan 2000 17:26:04 +0100." <20000106172604.T13922@bitbox.follo.net> References: <20000106172604.T13922@bitbox.follo.net> <20000106122256.B13922@bitbox.follo.net> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> <200001061609.JAA77304@harmony.village.org> Date: Thu, 06 Jan 2000 09:32:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106172604.T13922@bitbox.follo.net> Eivind Eklund writes: : On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: : > The laptop support is approx that of 3.x. The fe device is no longer : > supported as a pccard. The sn device has been added. The YE_DATA : > floppy device isn't supported, but could be if some is motivated to : > fix it. There may be a few lingering hot plug issues in the old : > code's migration to newbus. There's also preliminary support for ata flash and ata cdroms that is new, as well as linksys support (although I think the linksys stuff is in 3.x now). I have hardware for fdc and fe changes, but not the time right now. Xircom has preliminary support as well, but that is broken at the moment. : How much benefit would you be getting by having 4.0 ship with newcard : instead of what's there now? E.g, by having 4.0-PAO relate to newcard : rather than what's in presently? I'm not sure that there is a huge advantage to having 4.0 ship with a fully functional newcard. As it stands now, there will likely be a PAO 4.0 release which brings forward much of the PAO3 functionality that hasn't yet been merged. In the 4.1 timeframe I think we'll see a more agressive move to newcard and by 4.2 see the differences between regular FreeBSD and PAO diminish quite a bit. However, that's just a guess. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8:53:32 2000 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 5F51815385; Thu, 6 Jan 2000 08:53:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA52106; Thu, 6 Jan 2000 08:53:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA57538; Thu, 6 Jan 2000 08:53:26 -0800 (PST) (envelope-from obrien) Date: Thu, 6 Jan 2000 08:53:26 -0800 From: "David O'Brien" To: Warner Losh Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106085326.B1417@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000106122256.B13922@bitbox.follo.net> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> <200001061609.JAA77304@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001061609.JAA77304@harmony.village.org>; from imp@village.org on Thu, Jan 06, 2000 at 09:09:22AM -0700 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 Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: > : I believe putting down RELENG_4 without having a finished IPv6 and > : functional laptop support (I'm not sure what state this is in right > : now) would be a bad idea. > > The laptop support is approx that of 3.x. The fe device is no longer > supported as a pccard. `ep' is also broken for what is becoming a very popular Ethernet 10/100Mbit card -- the 3Com 3c574TX (and rebadged versions). `ep' is seriously wounded for some with 3c589d cards as it isn't getting interrupts and only works via the watchdog timer. `xe' is also broken in 4.0-C, awaiting new functions for getting CIS information. -- -- 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 Thu Jan 6 8:54:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 4C756156B6 for ; Thu, 6 Jan 2000 08:54:42 -0800 (PST) (envelope-from mw@theatre.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id RAA19464; Thu, 6 Jan 2000 17:54:36 +0100 (CET) Received: by theatre.sax.de (8.9.3/8.6.12-s1) id RAA97479; Thu, 6 Jan 2000 17:43:57 +0100 (CET) Date: Thu, 6 Jan 2000 17:43:57 +0100 From: Martin Welk To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: BOOTP and IPFIREWALL Message-ID: <20000106174356.D96748@theatre.sax.de> References: <14452.40864.973241.492117@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14452.40864.973241.492117@trooper.velocet.net>; from dgilbert@velocet.ca on Thu, Jan 06, 2000 at 08:58:56AM -0500 Organization: Private UUCP/Usenet site. X-Operating-System: FreeBSD http://www.freebsd.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 08:58:56AM -0500, David Gilbert wrote: > options BOOTP and options IPFIREWALL appear to be incompatible in > -CURRENT. I havn't tried -STABLE. While the kernel compiles fine, > the BOOTP code fails to send the discover packet and panic()'s. > > While it might not be immediately obvious that you'd want IPFIREWALL > in a BOOTP-loaded machine, there are good reasons for it... Can you explain that more? Did you have your IPFIREWALL to default to accept? (Otherwise, it's obvious that you have really serious trouble, because the kernel will load, decide not to allow any further network traffic and this will cause the kernel not to be able to get any data via NFS any more.) Regards, Martin -- /| /| | /| / ,,You know, there's a lot of opportunities, / |/ | artin |/ |/ elk if you're knowing to take them, you know, there's a lot of opportunities, Freiberg/Saxony, Germany if there aren't you can make them, mw@sax.de / mw@theatre.sax.de make or break them!'' (Tennant/Lowe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 8:58:24 2000 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 4AB7914A1A; Thu, 6 Jan 2000 08:58:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA52131; Thu, 6 Jan 2000 08:58:21 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA57558; Thu, 6 Jan 2000 08:58:21 -0800 (PST) (envelope-from obrien) Date: Thu, 6 Jan 2000 08:58:21 -0800 From: "David O'Brien" To: Alex Cc: Eivind Eklund , freebsd-committers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106085821.C1417@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> <38748CE5.AD1AD786@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38748CE5.AD1AD786@freenet.co.uk>; from ak@freenet.co.uk on Thu, Jan 06, 2000 at 12:39:01PM +0000 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 Thu, Jan 06, 2000 at 12:39:01PM +0000, Alex wrote: > I vote for: > > - IPv6 and the tools to go with it (Yoshinobu Inoue) > - Better laptop (PC card) support, possibly Cardbus (Warner Losh) > - Improved soundcard support: right now newpcm is broken in a number of > ways (Cameron Grant), possibly new MIDI (Seigo Tanimura) > - Reorganised source tree (e.g. filesystems must go into /sys/fs, etc.) *BUT* we have no commitment on how much time the volunteer developers of these items can give in the next X days. With out time estimates, how long do we wait?? It is simply a fact of live in a volunteer project such as FreeBSD the scheduling that many of us are used to does not work. Holding up 4.0-R in face if this, just isn't useful. -- -- 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 Thu Jan 6 8:59:49 2000 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 F2D4E14A1A; Thu, 6 Jan 2000 08:59:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA52151; Thu, 6 Jan 2000 08:59:44 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA57575; Thu, 6 Jan 2000 08:59:44 -0800 (PST) (envelope-from obrien) Date: Thu, 6 Jan 2000 08:59:44 -0800 From: "David O'Brien" To: Steve Ames Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106085944.D1417@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <38746AEC.167EB0E7@elischer.org> <20000106094511.A30328@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000106094511.A30328@virtual-voodoo.com>; from steve@virtual-voodoo.com on Thu, Jan 06, 2000 at 09:45:11AM -0500 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 Thu, Jan 06, 2000 at 09:45:11AM -0500, Steve Ames wrote: > > My question is how much time are developers/testers being given between > feature freeze (9 days from now) and release to get all code working > and stable? My question is not how much time the developers are being given -- the *real* question is how much time the developers will give. -- -- 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 Thu Jan 6 9:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from zot.ems.mindspring.net (zot.ems.mindspring.net [209.86.81.153]) by hub.freebsd.org (Postfix) with ESMTP id CAA1114DA7 for ; Thu, 6 Jan 2000 09:14:05 -0800 (PST) (envelope-from robgar@zot.ems.mindspring.net) Received: (from robgar@localhost) by zot.ems.mindspring.net (8.9.3/8.9.3) id MAA36156; Thu, 6 Jan 2000 12:14:10 -0500 (EST) (envelope-from robgar) Date: Thu, 6 Jan 2000 12:14:09 -0500 From: robgar To: Andreas Klemm Cc: current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106121409.A36123@zot.ems.mindspring.net> References: <20000106154945.A5887@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000106154945.A5887@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Thu, Jan 06, 2000 at 03:49:45PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 03:49:45PM +0100, Andreas Klemm wrote: > On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: > > More releases more often are better than indefinitely holding up > > releases waiting for just that one last thing to be finished. > > Second that. And to follow on that... > FreeBSD 4.0 will become the new STABLE. > So 4.0 should become as stable as possible. > I think there are certainly many people running on FreeBSD 2.x and > 3.x who wait for something like 4.0 to become a new stable release. > So we should get them the new STABLE toy ! > > In that short timeframe this can only be achieved by > not including too much new technology into it. > Otherwise we label something as STABLE which is in fact > something like a -current with respect to IP V6 and IPSec. > > Additionally it gives developers and customers time to breath. > > IP V6 and IPSec should be integrated into the new 5.0(?)-current. > > With FreeBSD-4.0-RELEASE we will get a rapidly growing user > base for 4.0 and we'll certainly have enough to do to make > it really stable for everybody. > > In the meantime people have their new testbed in 5.0-current. > If the dust has setteled in -current, I'd vote to merge > IP V6 and IPsec with as much client tools as possible into > something like 4.1-RELEASE. > > 4.0-STABLE I'd personally not touch with any brand new network > code. So people have a chance to remain some time on 4.0-RELEASE > or 4.0-STABLE. > > Another possibility would be to wait until the dust settles > after merging IP V6 and IPsec into -current and release > FreeBSD 4.0 complete with that features at a later time (+1-2 months). > But that's probably not wanted... > > What do you think of that ?! > > Andreas /// There are many people who use freebsd in the real world that have been counting on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would be willing to wait an additional couple of months for this functionality, please don't make us wait another year or so for this functionality Robert Garrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:20: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 0DA9614E65 for ; Thu, 6 Jan 2000 09:19:58 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 49496 invoked from network); 6 Jan 2000 17:19:56 -0000 Received: from dhcp-mtl-200.local.mindstep.com (HELO patrak) (192.168.10.200) by jacuzzi.local.mindstep.com with SMTP; 6 Jan 2000 17:19:56 -0000 Message-ID: <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Robert Watson" Cc: References: <200001060927.UAA03779@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th Date: Thu, 6 Jan 2000 12:19:38 -0500 Organization: MindStep Corporation 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 Hi, Maybe I am wrong, but it seems to me that there is already quite a bit of IPv6 and IPSec stuff in the tree. Most of the kernel stuff is there (albeit seriously lacking documentation). To me this is not *too* critical right now. I see the point for the research community though. Also, regarding what makes a *.0 release, I would say stability is the main thing. More complete features will come with the .1 .2 etc. releases. Look at the 3.x history: we just got some major features in the late 3.x (netgraph in 3.4) this does not mean that 3.0 was a bad release. If I can be sure that the IPSec and IPv6 userland stuff and documentation will be in 4.1 for sure, I would advocate for the feature freeze now. There are quite a few things that are good in 4.0 and that I really want to use in my production boxes (the new ata driver for example). To me getting what is already there in a *blessed* form is what is important. Rather than a full, complete IPv6 feature in 4.0, I would rather see that the 4.x-STABLE branch keeps track of the Kame mods in it by default and soon so that when 4.1-RELEASE is around IPv6 is in. Does that make sense ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:23: 7 2000 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 7128014E08; Thu, 6 Jan 2000 09:23:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA12036; Thu, 6 Jan 2000 10:22:58 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA77976; Thu, 6 Jan 2000 10:22:57 -0700 (MST) Message-Id: <200001061722.KAA77976@harmony.village.org> To: Alex Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: freebsd-committers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jan 2000 12:39:01 GMT." <38748CE5.AD1AD786@freenet.co.uk> References: <38748CE5.AD1AD786@freenet.co.uk> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> Date: Thu, 06 Jan 2000 10:22:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38748CE5.AD1AD786@freenet.co.uk> Alex writes: : - Better laptop (PC card) support, possibly Cardbus (Warner Losh) Won't happen by Jan 15th unless someone my boss comes into my office today and tells me to work on nothing else except pccard/cardbus for the next 9 days. The old pccard code will be it. There are a number of bugs in the old pccard support right now: o xe broken and waiting for some minor hacking on sys/pccard files. o ep relying on its timeout routine o ep broken for newer cards o fdc support for ye_data not there o fe not working due to no conversion to newbus o ISDN support for pccard unknown status o aic pccard support from 2.x not present afaik. o sio eject while active may result in hangs. Not sure if this is still true. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:24:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7A71414DCE for ; Thu, 6 Jan 2000 09:24:10 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA11762; Thu, 6 Jan 2000 18:23:54 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001061723.SAA11762@freebsd.dk> Subject: Re: wormcontrol replacement coming! In-Reply-To: <200001061702.SAA00661@info.iet.unipi.it> from Luigi Rizzo at "Jan 6, 2000 06:02:24 pm" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Thu, 6 Jan 2000 18:23:54 +0100 (CET) Cc: 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 Luigi Rizzo wrote: > [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW > > with just one command. Its simpleminded but it works. > > > > Just a FYI as I know several people have said they where thinking > > about doing such a thingy. > > this would save me the porting of my wormcontrol changes (similar ideas) Yes. > to -current. Is your command also intended for the 3.x branch ? No. This only works with the new ATA driver. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:25:24 2000 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 B060C14DCE for ; Thu, 6 Jan 2000 09:25:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA12052; Thu, 6 Jan 2000 10:25:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA78014; Thu, 6 Jan 2000 10:25:14 -0700 (MST) Message-Id: <200001061725.KAA78014@harmony.village.org> To: "Patrick Bihan-Faou" Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: "Robert Watson" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jan 2000 12:19:38 EST." <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> References: <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> <200001060927.UAA03779@avalon.reed.wattle.id.au> Date: Thu, 06 Jan 2000 10:25:14 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> "Patrick Bihan-Faou" writes: : Look at the 3.x history: we just got some major features in the late 3.x : (netgraph in 3.4) this does not mean that 3.0 was a bad release. Actually, 3.0 was a bad release, support for which was dropped before support for 2.2.x. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:29:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7450714C80 for ; Thu, 6 Jan 2000 09:28:38 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA01007; Thu, 6 Jan 2000 18:29:05 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001061729.SAA01007@info.iet.unipi.it> Subject: Re: wormcontrol replacement coming! In-Reply-To: <200001061723.SAA11762@freebsd.dk> from Soren Schmidt at "Jan 6, 2000 06:23:54 pm" To: Soren Schmidt Date: Thu, 6 Jan 2000 18:29:04 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW > > > with just one command. Its simpleminded but it works. btw for the records -- on 2.2.x i noticed i needed some wait between the transfer of data to CDR, and the "fixate" command (in other words, the fixation would often immediately fail if done within the same wormcontrol instance in charge of the data transfer.) I got lazy and instead of investigating the problem i realised that issuing the "wormcontrol fixate data" manually after the previous one was done did fix things, so i have no idea if it was related with my port of the worm support to 2.2.x, with the possible absence of closing and reopening the device, or with just the delay between the commands. Any idea ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:39:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 9A42514DA7 for ; Thu, 6 Jan 2000 09:39:15 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA00661; Thu, 6 Jan 2000 18:02:24 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001061702.SAA00661@info.iet.unipi.it> Subject: Re: wormcontrol replacement coming! In-Reply-To: <200001061112.MAA21167@freebsd.dk> from Soren Schmidt at "Jan 6, 2000 12:12:23 pm" To: Soren Schmidt Date: Thu, 6 Jan 2000 18:02:24 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW > with just one command. Its simpleminded but it works. > > Just a FYI as I know several people have said they where thinking > about doing such a thingy. this would save me the porting of my wormcontrol changes (similar ideas) to -current. Is your command also intended for the 3.x branch ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 9:51:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 2F529156BB for ; Thu, 6 Jan 2000 09:51:23 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id LAA00157 for freebsd-current@freebsd.org; Thu, 6 Jan 2000 11:51:21 -0600 (CST) From: Mohit Aron Message-Id: <200001061751.LAA00157@cs.rice.edu> Subject: patches for SMP To: freebsd-current@freebsd.org Date: Thu, 6 Jan 2000 11:51:20 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am using the FreeBSD-4.0 snapshot from 3rd January 2000. This version used to panic when configured as an SMP but with less CPUs than there are actually in the machine (I had 4 processors but only wanted to use 1). Someone mailed me patches for fixing this problem (attached below). If these haven't been applied already, can someone please apply them so that the FreeBSD-4.0 release scheduled for January 15th has this bug removed. - Mohit Index: i386/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.112 diff -u -r1.112 mp_machdep.c --- i386/mp_machdep.c 1999/11/27 12:32:20 1.112 +++ i386/mp_machdep.c 2000/01/05 08:28:40 @@ -1097,7 +1097,7 @@ processor_entry(proc_entry_ptr entry, int cpu) { /* check for usability */ - if ((cpu >= NCPU) || !(entry->cpu_flags & PROCENTRY_FLAG_EN)) + if (!(entry->cpu_flags & PROCENTRY_FLAG_EN)) return 0; /* check for BSP flag */ @@ -1109,11 +1109,13 @@ } /* add another AP to list, if less than max number of CPUs */ - else { + else if (cpu < NCPU) { CPU_TO_ID(cpu) = entry->apic_id; ID_TO_CPU(entry->apic_id) = cpu; return 1; } + + return 0; } Index: include/mpapic.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/mpapic.h,v retrieving revision 1.12 diff -u -r1.12 mpapic.h --- include/mpapic.h 1999/08/28 00:44:19 1.12 +++ include/mpapic.h 2000/01/05 08:24:58 @@ -98,6 +98,8 @@ static __inline int all_but_self_ipi(int vector) { + if (mp_ncpus <= 1) + return 0; return apic_ipi(APIC_DEST_ALLESELF, vector, APIC_DELMODE_FIXED); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 10: 0:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3CA1414D77 for ; Thu, 6 Jan 2000 10:00:20 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA20492; Thu, 6 Jan 2000 19:00:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001061800.TAA20492@freebsd.dk> Subject: Re: wormcontrol replacement coming! In-Reply-To: <200001061729.SAA01007@info.iet.unipi.it> from Luigi Rizzo at "Jan 6, 2000 06:29:04 pm" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Thu, 6 Jan 2000 19:00:16 +0100 (CET) Cc: 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 Luigi Rizzo wrote: > > > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW > > > > with just one command. Its simpleminded but it works. > > btw for the records -- on 2.2.x i noticed i needed some wait between > the transfer of data to CDR, and the "fixate" command (in other words, > the fixation would often immediately fail if done within the same wormcontrol > instance in charge of the data transfer.) > > I got lazy and instead of investigating the problem i realised that issuing > the "wormcontrol fixate data" manually after the previous one was done did > fix things, so i have no idea if it was related with my port of the worm > support to 2.2.x, with the possible absence of closing and reopening the device, or with just the delay between the commands. Any idea ? I've not seen the fixate fail, but I've seen the second write to a multitrack disk fail if the device is not closed inbetween. The problem was that the b_offset that is used to calculate the LBA to write to, is not reset between the writes, so the address doesn't corresspond with the address found with the next_writeable function. This is fixed now... I've also investigated using the READCD cmd instead of READ_BIG to read the CD, this allows one to read _any_ data in _any_ format off the CD, thereby eliminating the need for rippers, you just dd the audio CD into a file, handy :). It seems to work pretty well, so I might commit that too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 10:21:41 2000 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 8ED6D15037; Thu, 6 Jan 2000 10:21:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01348; Thu, 6 Jan 2000 10:21:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@freebsd.org Cc: Steve Ames , committers@freebsd.org, current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 08:59:44 PST." <20000106085944.D1417@dragon.nuxi.com> Date: Thu, 06 Jan 2000 10:21:40 -0800 Message-ID: <1346.947182900@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My question is not how much time the developers are being given -- the > *real* question is how much time the developers will give. Thank you for saying this. If developers were constant-output devices, we wouldn't need code freezes to motivate them into moving at all. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 10:24:30 2000 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 67DDA14C0C for ; Thu, 6 Jan 2000 10:24:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01377; Thu, 6 Jan 2000 10:24:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: robgar Cc: Andreas Klemm , current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 12:14:09 EST." <20000106121409.A36123@zot.ems.mindspring.net> Date: Thu, 06 Jan 2000 10:24:21 -0800 Message-ID: <1375.947183061@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are many people who use freebsd in the real world that have been counti ng > on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would > be willing to wait an additional couple of months for this functionality, ple Sadly, you've picked a particular bit of technology that we've been waiting more than a year for. If I had any assurance that a couple of months would make a difference for KAME, I might even contemplate that as a strong option, but they don't work to those kinds of schedules. Based on past experience, it could easily be another year before the KAME group is ready with everything you're asking for. Should we wait a year? Clearly not, and we have to make our schedules independently of the long-term project groups or we'll never release anything. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 10:55:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from zot.ems.mindspring.net (zot.ems.mindspring.net [209.86.81.153]) by hub.freebsd.org (Postfix) with ESMTP id ACB7F155FB for ; Thu, 6 Jan 2000 10:55:48 -0800 (PST) (envelope-from robgar@zot.ems.mindspring.net) Received: (from robgar@localhost) by zot.ems.mindspring.net (8.9.3/8.9.3) id NAA36655; Thu, 6 Jan 2000 13:55:52 -0500 (EST) (envelope-from robgar) Date: Thu, 6 Jan 2000 13:55:52 -0500 From: robgar To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106135552.A36638@zot.ems.mindspring.net> References: <20000106121409.A36123@zot.ems.mindspring.net> <1375.947183061@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1375.947183061@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 10:24:21AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 10:24:21AM -0800, Jordan K. Hubbard wrote: > > There are many people who use freebsd in the real world that have been counti > ng > > on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would > > be willing to wait an additional couple of months for this functionality, ple > > Sadly, you've picked a particular bit of technology that we've been > waiting more than a year for. If I had any assurance that a couple of > months would make a difference for KAME, I might even contemplate that > as a strong option, but they don't work to those kinds of schedules. > Based on past experience, it could easily be another year before the > KAME group is ready with everything you're asking for. Should we wait > a year? Clearly not, and we have to make our schedules independently > of the long-term project groups or we'll never release anything. > > - Jordan That is true, and has always been true. Things get done when people are ready to get them done and not before. Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 11: 8: 0 2000 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 A8AB41560A for ; Thu, 6 Jan 2000 11:07:57 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA70479; Thu, 6 Jan 2000 11:07:56 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id LAA38192; Thu, 6 Jan 2000 11:07:14 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200001061907.LAA38192@whistle.com> Subject: Re: BOOTP and IPFIREWALL In-Reply-To: <14452.40864.973241.492117@trooper.velocet.net> from David Gilbert at "Jan 6, 2000 08:58:56 am" To: David Gilbert Date: Thu, 6 Jan 2000 11:07:14 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert writes: | options BOOTP and options IPFIREWALL appear to be incompatible in | -CURRENT. I havn't tried -STABLE. While the kernel compiles fine, | the BOOTP code fails to send the discover packet and panic()'s. | | While it might not be immediately obvious that you'd want IPFIREWALL | in a BOOTP-loaded machine, there are good reasons for it... They are not really incompatible just your use is :-) Add options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default to your kernel. IPFW stuff is blocking any network traffic. So add this to your kernel and you firewall will default to open so BOOT etc will work (including nfs mounting of root & swap), then during the boot use the rc.firewall stuff to setup the firewall correct and then remove the default open rule. This is what I've done when playing with natd on a netbooted machine. (natd require ipfw & divert). If this fails it's news to me. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 11:19:48 2000 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 D4251156BF for ; Thu, 6 Jan 2000 11:19:37 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA18421; Thu, 6 Jan 2000 14:19:30 -0500 (EST) (envelope-from luoqi) Date: Thu, 6 Jan 2000 14:19:30 -0500 (EST) From: Luoqi Chen Message-Id: <200001061919.OAA18421@lor.watermarkgroup.com> To: aron@cs.rice.edu, freebsd-current@FreeBSD.ORG Subject: Re: patches for SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I am using the FreeBSD-4.0 snapshot from 3rd January 2000. This version > used to panic when configured as an SMP but with less CPUs than there are > actually in the machine (I had 4 processors but only wanted to use 1). Someone > mailed me patches for fixing this problem (attached below). If these haven't > been applied already, can someone please apply them so that the FreeBSD-4.0 > release scheduled for January 15th has this bug removed. > > > > - Mohit > That "someone" was me :-) I'll commit it before the deadline. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 11:25:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 1BCD1156BA for ; Thu, 6 Jan 2000 11:25:11 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id NAA03268; Thu, 6 Jan 2000 13:24:58 -0600 (CST) From: Mohit Aron Message-Id: <200001061924.NAA03268@cs.rice.edu> Subject: Re: patches for SMP To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Thu, 6 Jan 2000 13:24:58 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <200001061919.OAA18421@lor.watermarkgroup.com> from "Luoqi Chen" at Jan 6, 2000 02:19:30 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That "someone" was me :-) I'll commit it before the deadline. > Thanks. Sorry, for not mentioning your name but I had already stripped off the mail headers from the patch that you sent to me. The patch works great. Please do commit it for the release. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 12: 3: 2 2000 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 28C08155A4; Thu, 6 Jan 2000 12:02:57 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA70527; Thu, 6 Jan 2000 15:02:33 -0500 (EST) Date: Thu, 6 Jan 2000 15:02:32 -0500 (EST) From: To: Darren Reed Cc: Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001060927.UAA03779@avalon.reed.wattle.id.au> 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, 6 Jan 100, Darren Reed wrote: > For what it's worth, I think releasing 4.0 *without* IPv6 support > is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be > released *with* IPv6 support (I'd count IPv6 as being a big enough > change to signify a major release number change). If that doesn't > happen, then FreeBSD is chasing the wrong goals, IMHO. I would like to agree with darren on this one. And think IPv6 should go into 4.0 even if the date needs to be pushed back. It is a major release and adding v6 is a major change. Thats just my 2 cents anyway. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 12:12:16 2000 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 26C2515737; Thu, 6 Jan 2000 12:12:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA61710; Thu, 6 Jan 2000 12:12:01 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 12:12:01 -0800 (PST) From: Matthew Dillon Message-Id: <200001062012.MAA61710@apollo.backplane.com> To: Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> For what it's worth, I think releasing 4.0 *without* IPv6 support :> is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be :> released *with* IPv6 support (I'd count IPv6 as being a big enough :> change to signify a major release number change). If that doesn't :> happen, then FreeBSD is chasing the wrong goals, IMHO. : :I would like to agree with darren on this one. And think IPv6 should go :into 4.0 even if the date needs to be pushed back. It is a major release :and adding v6 is a major change. Thats just my 2 cents anyway. : :Chris We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, but not important enough to delay the already-delayed 4.0 release. 4.1 is not too late for these babies. On the other hand, there are *plenty* of things already in 4.0 that really need to get out there and get a workout by a larger audience. Delaying *them* is a big mistake. -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 Jan 6 12:21: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 67B55157B4; Thu, 6 Jan 2000 12:20:50 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id PAA11576; Thu, 6 Jan 2000 15:20:26 -0500 (EST) (envelope-from steve) Date: Thu, 6 Jan 2000 15:20:26 -0500 From: Steve Ames To: Matthew Dillon Cc: scanner@jurai.net, Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106152026.A98222@virtual-voodoo.com> References: <200001062012.MAA61710@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200001062012.MAA61710@apollo.backplane.com>; from Matthew Dillon on Thu, Jan 06, 2000 at 12:12:01PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, > but not important enough to delay the already-delayed 4.0 release. 4.1 > is not too late for these babies. True... 4.1 is not too late. However a good part of IPv6 and IPSEC are already present and the primary committer has already expressed his opinion on what can and can't be done by 1/15. > On the other hand, there are *plenty* of things already in 4.0 that really > need to get out there and get a workout by a larger audience. > Delaying *them* is a big mistake. *shudder* I really, really dislike the idea of -RELEASE actually being a wide beta so that some code can get a workout. LAbel it beta and more people will use it than currently do anyway. Any reason not to release and ship a 4.0-beta? -CURRENT = development which scares people. Beta means most bugs already ironed out and looking for test by larger audience. -RELEASE should not be a beta, ever. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 12:39:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id D7A18156FD for ; Thu, 6 Jan 2000 12:39:08 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id MAA01354 for ; Thu, 6 Jan 2000 12:39:06 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id MAA02514 for current@freebsd.org; Thu, 6 Jan 2000 12:39:06 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001062039.MAA02514@realtime.exit.com> Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001062012.MAA61710@apollo.backplane.com> from Matthew Dillon at "Jan 6, 2000 12:12:01 pm" To: current@freebsd.org Date: Thu, 6 Jan 2000 12:39:06 -0800 (PST) Reply-To: frank@exit.com 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 (Note: trimmed to just the -current list.) Matthew Dillon wrote: > On the other hand, there are *plenty* of things already in 4.0 that really > need to get out there and get a workout by a larger audience. > Delaying *them* is a big mistake. On the _other_ other hand (:-), having pccard ep0 broken in 4.0-RELEASE is a mistake, IMHO. At the very _least_, the 589D's should work, and it would be Really Nice if the 574BTs worked, too. Of course, no one should expect full cardbus support until 4.1 or 4.2, given Warner's work situation. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 12:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id C20E815730; Thu, 6 Jan 2000 12:42:13 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id UAA00997; Thu, 6 Jan 2000 20:42:09 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma000995; Thu, 6 Jan 00 20:41:41 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id HAA04552; Fri, 7 Jan 2000 07:41:41 +1100 (EST) From: Darren Reed Message-Id: <200001062041.HAA04552@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: steve@virtual-voodoo.com (Steve Ames) Date: Fri, 7 Jan 100 07:41:40 +1100 (EST) Cc: committers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <20000106152026.A98222@virtual-voodoo.com> from "Steve Ames" at Jan 6, 0 03:20:26 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Steve Ames, sie wrote: > > *shudder* I really, really dislike the idea of -RELEASE actually being a > wide beta so that some code can get a workout. LAbel it beta and more people > will use it than currently do anyway. Any reason not to release and ship a > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs > already ironed out and looking for test by larger audience. -RELEASE should > not be a beta, ever. What do you think 3.0-RELEASE was ? This seems to be how FreeBSD works now. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 12:52: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 57607156F3; Thu, 6 Jan 2000 12:51:55 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id PAA17903; Thu, 6 Jan 2000 15:49:15 -0500 (EST) Date: Thu, 6 Jan 2000 15:49:15 -0500 (EST) From: "Mr. K." To: Darren Reed Cc: Steve Ames , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001062041.HAA04552@avalon.reed.wattle.id.au> 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 Fri, 7 Jan 100, Darren Reed wrote: > In some email I received from Steve Ames, sie wrote: > > > > *shudder* I really, really dislike the idea of -RELEASE actually being a > > wide beta so that some code can get a workout. LAbel it beta and more people > > will use it than currently do anyway. Any reason not to release and ship a > > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs > > already ironed out and looking for test by larger audience. -RELEASE should > > not be a beta, ever. > > What do you think 3.0-RELEASE was ? > This seems to be how FreeBSD works now. > There really isn't an alternative. If there were thousands of people begging for beta code to test and we decided to just call it a release, that would be a different story, but there aren't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 13: 1:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 9E3BF15749; Thu, 6 Jan 2000 13:01:15 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id VAA01057; Thu, 6 Jan 2000 21:01:11 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma001055; Thu, 6 Jan 00 21:00:48 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id IAA04692; Fri, 7 Jan 2000 08:00:47 +1100 (EST) From: Darren Reed Message-Id: <200001062100.IAA04692@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 7 Jan 100 08:00:46 +1100 (EST) Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <200001062012.MAA61710@apollo.backplane.com> from "Matthew Dillon" at Jan 6, 0 12:12:01 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Matthew Dillon, sie wrote: [...] > We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, > but not important enough to delay the already-delayed 4.0 release. 4.1 > is not too late for these babies. [...] Well, let me put it this way. 4.0-RELEASE sounds like it will start becoming available at about the same time as other OS's make new releases *with* IPv6/IPSec. You work it out whether or not FreeBSD will win or lose from those two being there or not there. btw, I completely agree with the need to have good pccard/pcmcia support. For the first time there was a real reason for me to ditch FreeBSD on an Intel platform box (my laptop) and go with NetBSD where my 3c589d works just fine. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 13:15:35 2000 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 D74D614D94; Thu, 6 Jan 2000 13:15:28 -0800 (PST) (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.9.3) with ESMTP id NAA44066; Thu, 6 Jan 2000 13:14:56 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001062114.NAA44066@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Darren Reed Cc: dillon@apollo.backplane.com (Matthew Dillon), committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Fri, 07 Jan 0100 08:00:46 +1100." <200001062100.IAA04692@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 13:14:56 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In some email I received from Matthew Dillon, sie wrote: > [...] > > We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, > > but not important enough to delay the already-delayed 4.0 release. 4.1 > > is not too late for these babies. > [...] > > Well, let me put it this way. > > 4.0-RELEASE sounds like it will start becoming available at about the same > time as other OS's make new releases *with* IPv6/IPSec. You work it out > whether or not FreeBSD will win or lose from those two being there or not > there. For the short term the impact will be nill , zero , nada... Is not like companies get hold of a new technology and instantly start deploying it -- it will take some time ;specially, nowdays after a lot of companies are getting somewhat of a relief from Y2K work or scare .... With respect to FreeBSD people can always get an upgrade or cvsup . They want more ? Talk to JKH I am sure is willing to strike a sweet deal 8) -- 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 Jan 6 13:20:31 2000 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 893AA15733; Thu, 6 Jan 2000 13:19:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA00672; Thu, 6 Jan 2000 22:14:19 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Steve Ames Cc: Matthew Dillon , scanner@jurai.net, Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 15:20:26 EST." <20000106152026.A98222@virtual-voodoo.com> Date: Thu, 06 Jan 2000 22:14:19 +0100 Message-ID: <670.947193259@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106152026.A98222@virtual-voodoo.com>, Steve Ames writes: >> On the other hand, there are *plenty* of things already in 4.0 that really >> need to get out there and get a workout by a larger audience. >> Delaying *them* is a big mistake. > >*shudder* I really, really dislike the idea of -RELEASE actually being a >wide beta so that some code can get a workout. Who said anything about -RELEASE being a beta ? Some parts of a release will always be new, but the majority of it is the same code we released as 3.X, 2.X and even 1.X. We need for people to stop thinking of FreeBSD as commercial software which comes in "natural number" style enumerable packets. FreeBSD style is "real number", it is a continuously evolving quantity which every now and then passes a natural number on the way to infinity. We can now spot a milestone called 4.0 and that's very nice, but we are not going to stop, because the road goes on past 4.0. I'm sorry you you can't have ${insert pet feature here} in 4.0 if it is not ready yet. That's too bad, check in later. In the meantime please enjoy: NTFS filesytem Netware support Jail facility Tons of new device drivers Netgraph etc, etc Isn't that just that very incomplete list worth a release ? FreeBSD-4.0 because now the time is right! 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 Thu Jan 6 13:20:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 36566157DE for ; Thu, 6 Jan 2000 13:20:37 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id A631B191; Thu, 6 Jan 2000 13:20:33 -0800 (PST) Date: Thu, 6 Jan 2000 13:20:33 -0800 From: Chris Piazza To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: mergemaster(8) busted Message-ID: <20000106132033.B1526@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Fri, Jan 07, 2000 at 02:40:16AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 02:40:16AM +1100, Andy Farkas wrote: > > After cvsup'ing, a -current system based on userland/kernel dated > 31-dec-1999, 'mergemaster -sv' is failing with mknod errors. > > cd src/sbin/mknod ; make all install ; make clean > fixes it. Uh, yeah? MAKEDEV uses mknod arguments instead of chown to change ownership of device nodes now. You should probably build world before you sync /etc, anyway. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 13:21:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id E308F15749; Thu, 6 Jan 2000 13:21:05 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA15994; Thu, 6 Jan 2000 21:20:50 GMT (envelope-from joe) Date: Thu, 6 Jan 2000 21:20:50 +0000 From: Josef Karthauser To: Darren Reed Cc: Matthew Dillon , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106212050.D95011@florence.pavilion.net> References: <200001062012.MAA61710@apollo.backplane.com> <200001062100.IAA04692@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001062100.IAA04692@avalon.reed.wattle.id.au> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote: > > btw, I completely agree with the need to have good pccard/pcmcia support. > For the first time there was a real reason for me to ditch FreeBSD on an > Intel platform box (my laptop) and go with NetBSD where my 3c589d works > just fine. > My 3c589d works just fine now, along with suspend/resume :) (under 4.0). Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 13:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F75714D52; Thu, 6 Jan 2000 13:32:16 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id QAA00481; Thu, 6 Jan 2000 16:30:24 -0500 (EST) Date: Thu, 6 Jan 2000 16:30:24 -0500 From: Christian Kuhtz To: Poul-Henning Kamp Cc: Steve Ames , Matthew Dillon , scanner@jurai.net, Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106163024.G26743@ns1.arch.bellsouth.net> References: <20000106152026.A98222@virtual-voodoo.com> <670.947193259@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <670.947193259@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Jan 06, 2000 at 10:14:19PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 10:14:19PM +0100, Poul-Henning Kamp wrote: [..] > FreeBSD-4.0 because now the time is right! What's the rush? If we believe that IPv6 is a noteable milestone, then what better time to introduce it and get a "splash" with it than the ".0" major release. Do you really think people will notice much when you introduce new protocol stacks in minor releases (.1, .2, etc)? If you dispute that, perhaps you're due for a routine reality check. Cheers, Chris -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 13:39: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 187ED15718; Thu, 6 Jan 2000 13:38:54 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id NAA03318; Thu, 6 Jan 2000 13:38:23 -0800 (PST) Date: Thu, 6 Jan 2000 13:38:31 -0800 (PST) From: Tom Bartol To: Josef Karthauser Cc: Darren Reed , Matthew Dillon , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <20000106212050.D95011@florence.pavilion.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, 6 Jan 2000, Josef Karthauser wrote: > On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote: > > > > btw, I completely agree with the need to have good pccard/pcmcia support. > > For the first time there was a real reason for me to ditch FreeBSD on an > > Intel platform box (my laptop) and go with NetBSD where my 3c589d works > > just fine. > > > > My 3c589d works just fine now, along with suspend/resume :) (under 4.0). > And these are also working perfectly for me as well under -current on a ThinkPad 770. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 14: 5:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9EACC15753; Thu, 6 Jan 2000 14:05:44 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA08491; Thu, 6 Jan 2000 16:05:37 -0600 (CST) From: Mohit Aron Message-Id: <200001062205.QAA08491@cs.rice.edu> Subject: rlogind message in /var/log/messages To: freebsd-bugs@freebsd.org Date: Thu, 6 Jan 2000 16:05:37 -0600 (CST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I upgraded FreeBSD-3.3 to FreeBSD-current (snapshot from Jan 3) recently. I'm getting error messages of the form: Jan 6 10:56:17 idli rlogind[1806]: no modules loaded for `rshd' service Jan 6 10:56:17 idli rlogind[1806]: auth_pam: Permission denied Jan 6 10:56:17 idli rlogind[1806]: PAM authentication failed in /var/log/messages each time I do a remote login (using rsh or rlogin). Can this problem be fixed for the FreeBSD-4.0 release if possible. Thanks, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 14:16:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id C98D215755 for ; Thu, 6 Jan 2000 14:16:15 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id OAA10093; Thu, 6 Jan 2000 14:15:19 -0800 (PST) X-Authentication-Warning: btw.plaintalk.bellevue.wa.us: Host fwiw.plaintalk.bellevue.wa.us [206.129.5.157] claimed to be software-munitions.com Message-ID: <387513F7.73F33939@software-munitions.com> Date: Thu, 06 Jan 2000 14:15:19 -0800 From: Dennis Glatting X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Patrick Bihan-Faou , freebsd-current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001060927.UAA03779@avalon.reed.wattle.id.au> <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Bihan-Faou wrote: > Maybe I am wrong, but it seems to me that there is already quite a bit of > IPv6 and IPSec stuff in the tree. Most of the kernel stuff is there (albeit > seriously lacking documentation). To me this is not *too* critical right > now. I see the point for the research community though. > Speaking with my Infrastructure Services hat on, if 4.0 supported IPsec on IPv4 I would deploy FreeBSD more widely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 14:35:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 0637414E5E; Thu, 6 Jan 2000 14:35:23 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 126LUu-0007OO-00; Thu, 6 Jan 2000 22:35:12 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id XAA29436; Thu, 6 Jan 2000 23:35:08 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3875189C.371A46DA@scc.nl> Date: Thu, 06 Jan 2000 23:35:08 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: committers@freebsd.org Cc: current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <28153.947101446@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > 10 days, folks! Make 'em count.. :) > If people would stop sending this to -committers, I will actually have some time left in which to do some work :-) Better still, stop it completely. thanks, -- 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 Thu Jan 6 14:38:22 2000 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 8692914CC8 for ; Thu, 6 Jan 2000 14:38:19 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 923B93E36; Thu, 6 Jan 2000 23:38:08 +0100 (CET) Date: Thu, 6 Jan 2000 23:38:08 +0100 From: Jesper Skriver To: current@freebsd.org Subject: PCCARD - after installing a snapshot, no pccard support Message-ID: <20000106233808.A62429@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed the jan 5th 4.0-CURRENT snapshot on my brand new IBM 600E laptop, using the pccard floppies, it found my 3c589c just fine, and the installation was without any problems, but after booting the installed system, there was no pccard support, and the ep0 device wasn't found, wouldn't it be smart to install a kernel with support for pccard, when installing from the pccard floppies ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) 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 Thu Jan 6 14:44:22 2000 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 13B0B14DA7 for ; Thu, 6 Jan 2000 14:44:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA13197; Thu, 6 Jan 2000 15:44:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA80272; Thu, 6 Jan 2000 15:44:14 -0700 (MST) Message-Id: <200001062244.PAA80272@harmony.village.org> To: frank@exit.com Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jan 2000 12:39:06 PST." <200001062039.MAA02514@realtime.exit.com> References: <200001062039.MAA02514@realtime.exit.com> Date: Thu, 06 Jan 2000 15:44:14 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001062039.MAA02514@realtime.exit.com> Frank Mayhar writes: : On the _other_ other hand (:-), having pccard ep0 broken in 4.0-RELEASE is a : mistake, IMHO. At the very _least_, the 589D's should work, and it would be : Really Nice if the 574BTs worked, too. Of course, no one should expect full : cardbus support until 4.1 or 4.2, given Warner's work situation. I think that Matt Dodd will be working on this. We's waiting for hardware that is on order before he can complete fixing this. I strongly suspect that he'll be able to fix it within a few hours of the arrival of the hardware. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 14:44:56 2000 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 871D614DA7 for ; Thu, 6 Jan 2000 14:44:50 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 56C603E37; Thu, 6 Jan 2000 23:44:46 +0100 (CET) Date: Thu, 6 Jan 2000 23:44:46 +0100 From: Jesper Skriver To: current@freebsd.org Subject: Re: PCCARD - after installing a snapshot, no pccard support Message-ID: <20000106234446.A62477@skriver.dk> References: <20000106233808.A62429@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000106233808.A62429@skriver.dk>; from jesper@skriver.dk on Thu, Jan 06, 2000 at 11:38:08PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 11:38:08PM +0100, Jesper Skriver wrote: > Hi, > > I just installed the jan 5th 4.0-CURRENT snapshot on my brand new IBM > 600E laptop, using the pccard floppies, it found my 3c589c just fine, > and the installation was without any problems, but after booting the > installed system, there was no pccard support, and the ep0 device wasn't > found, wouldn't it be smart to install a kernel with support for pccard, > when installing from the pccard floppies ? Forgot the obvious, after building a new kernel, ep0 works again, but this could a show-stopper for many users, and with 4.0 soon to become a -RELEASE, this could hit quite a few unexperienced users. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) 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 Thu Jan 6 14:46:38 2000 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 7C4FE157F6; Thu, 6 Jan 2000 14:46:28 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA13217; Thu, 6 Jan 2000 15:46:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA80310; Thu, 6 Jan 2000 15:46:22 -0700 (MST) Message-Id: <200001062246.PAA80310@harmony.village.org> To: Josef Karthauser Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: Darren Reed , Matthew Dillon , committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jan 2000 21:20:50 GMT." <20000106212050.D95011@florence.pavilion.net> References: <20000106212050.D95011@florence.pavilion.net> <200001062012.MAA61710@apollo.backplane.com> <200001062100.IAA04692@avalon.reed.wattle.id.au> Date: Thu, 06 Jan 2000 15:46:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106212050.D95011@florence.pavilion.net> Josef Karthauser writes: : My 3c589d works just fine now, along with suspend/resume :) (under 4.0). The issue with the 3c589d is with its speed. It is falling back to the timeout routine to send data rather than getting an interrupt when the tx has happened (or something like this, I'm reporting second hand stuff). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 14:49: 6 2000 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 E8AF114EFF; Thu, 6 Jan 2000 14:49:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA54133; Thu, 6 Jan 2000 14:48:57 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA58719; Thu, 6 Jan 2000 14:48:56 -0800 (PST) (envelope-from obrien) Date: Thu, 6 Jan 2000 14:48:56 -0800 From: "David O'Brien" To: scanner@jurai.net Cc: Darren Reed , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106144856.F1417@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <200001060927.UAA03779@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from scanner@jurai.net on Thu, Jan 06, 2000 at 03:02:32PM -0500 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 Thu, Jan 06, 2000 at 03:02:32PM -0500, scanner@jurai.net wrote: > > I would like to agree with darren on this one. And think IPv6 should go > into 4.0 even if the date needs to be pushed back. It is a major release > and adding v6 is a major change. Thats just my 2 cents anyway. And when will IPv6 fully be in 4-CURRENT? Besides offering two cents what else can you offer to make this happen? Time? More money? People here aren't backing their opinions by tell us *how* their to make their opinions happen. -- -- 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 Thu Jan 6 15: 8:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4C19D14FF4 for ; Thu, 6 Jan 2000 15:08:33 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id AAA97334 for current@freebsd.org; Fri, 7 Jan 2000 00:08:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001062308.AAA97334@freebsd.dk> Subject: HEADS UP! wormcontrol and sys/dvdio.h users To: current@freebsd.org Date: Fri, 7 Jan 2000 00:08:16 +0100 (CET) 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 I've just committed burncd the wormcontrol replacement. The ATAPI burner API has changed, so wormcontrol does no longer work, use burncd instead (see burncd.8) The DVD ioctl's has changed numbers, so those using that should recompile thier apps. Wormcontrol and related files will be removed soon. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15: 8:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id A308515797 for ; Thu, 6 Jan 2000 15:08:52 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 7 Jan 2000 10:01:19 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: ATA driver problems In-reply-to: <20000106103851.A620@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Thu, Jan 06, 2000 at 10:38:51AM +1100 To: freebsd-current@FreeBSD.ORG Message-Id: <00Jan7.100119est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000106103851.A620@gsmx07.alcatel.com.au> Date: Fri, 7 Jan 2000 10:01:19 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-06 10:38:51 +1100, I wrote: ["dd if=/dev/rad0c of=/dev/null bs=64k" dies with an error] I did some poking around and found that there are two bugs which conspire together to cause this: 1) diskstrategy() does not detect dscheck() returning EOF, instead passing a zero-length request to the underlying driver. 2) The ata-disk driver doesn't check for (and ignore) zero-length requests, instead passing them onto the disk. See kern/15956 for details and patches. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:20:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id A8C3815741; Thu, 6 Jan 2000 15:20:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA00710; Thu, 6 Jan 2000 15:25:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001062325.PAA00710@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Darren Reed Cc: steve@virtual-voodoo.com (Steve Ames), committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Fri, 07 Jan 0100 07:41:40 +1100." <200001062041.HAA04552@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 15:25:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In some email I received from Steve Ames, sie wrote: > > > > *shudder* I really, really dislike the idea of -RELEASE actually being a > > wide beta so that some code can get a workout. LAbel it beta and more people > > will use it than currently do anyway. Any reason not to release and ship a > > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs > > already ironed out and looking for test by larger audience. -RELEASE should > > not be a beta, ever. > > What do you think 3.0-RELEASE was ? > This seems to be how FreeBSD works now. It's how FreeBSD's users seem to want it to work, since they have utterly refused to cooperate with any other arrangement. Those of us behind the release-engineering effort have tried everything realistic that's been suggested (and a great many other things); history speaks for itself as to the results. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:21:46 2000 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 65E38156BC for ; Thu, 6 Jan 2000 15:21:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA13369; Thu, 6 Jan 2000 16:20:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA80710; Thu, 6 Jan 2000 16:20:21 -0700 (MST) Message-Id: <200001062320.QAA80710@harmony.village.org> To: Jesper Skriver Subject: Re: PCCARD - after installing a snapshot, no pccard support Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jan 2000 23:44:46 +0100." <20000106234446.A62477@skriver.dk> References: <20000106234446.A62477@skriver.dk> <20000106233808.A62429@skriver.dk> Date: Thu, 06 Jan 2000 16:20:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106234446.A62477@skriver.dk> Jesper Skriver writes: : Forgot the obvious, after building a new kernel, ep0 works again, but : this could a show-stopper for many users, and with 4.0 soon to become a : -RELEASE, this could hit quite a few unexperienced users. I'll finish my PCCARD -> GENERIC merge tonight and see if it breaks anybody. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:23:23 2000 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 C86671576A; Thu, 6 Jan 2000 15:22:54 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id AAA41804; Fri, 7 Jan 2000 00:21:18 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id AAA01966; Fri, 7 Jan 2000 00:19:48 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Fri, 7 Jan 2000 00:19:48 +0100 (CET) From: Michael Reifenberger To: FreeBSD-SCSI Cc: FreeBSD-Current Subject: Problem exposed with sym driver Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1845788462-947200788=:1789" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, after enabling the sym-driver I get drive-lockups after some time of accessing the disks hanging on the sym-driver. It seems that at least on disk hangs up (steady disk light) until a bus-reset "(noperiph:sym0:0:-1:-1): SCSI BUS reset detected" occurs. A difference between ncr and sym-driver is that the sym-driver probes the disks as (excerpt from dmesg_sym.txt): da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) whereas the ncr-driver probes as (excerpt from dmesg_ncr.txt): da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) Usually the IBM-FAQ suspects a cabling/termination Problem if one has a Problem at 40MHZ. But I have the 4 disks in a external case from kingston with a proper kable and terminator and furthermore LVD-drives should have a better signal quality. Furthermore I have zero problems at 20MHZ. You can see in neg_before.txt the output of a 'camcontrol neg' which look right, in neg_after.txt the output of the same command after the disk hang up and the bus reseted. neg_ncr.txt contains the output using the ncr-driver. BTW: I have the same problems with the ncr-driver when using the kernel-config parameter: SCSI_NCR_DFLT_SYNC=10 And now the question: Whats going wrong? If it is the HW, how can it be proven? Are it the IBM-disks? Kabel?... Is it the Software? If I want to live with 40MB/s is there a knob to pre-set the speed in the kernel-config or at boot-time? Any clues? Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg_ncr.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg_ncr.txt" ZyA9IDINCiAgRmVhdHVyZXM9MHgzODNmYmZmPEZQVSxWTUUsREUsUFNFLFRT QyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQR0UsTUNBLENNT1Ys UEFULFBTRTM2LE1NWCxGWFNSLFhNTT4NCnJlYWwgbWVtb3J5ICA9IDI2ODQy MzE2OCAoMjYyMTMySyBieXRlcykNCmNvbmZpZz4gI2ZsYWdzIHdkYzAgMHhh MGZmYTBmZg0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8n IGZvciBoZWxwLg0KY29uZmlnPiAjZmxhZ3Mgd2RjMSAweGEwZmZhMGZmDQpJ bnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4LiAgVHlwZSBgPycgZm9yIGhlbHAu DQpjb25maWc+ICNpcnEgaXNpYzAgMTANCkludmFsaWQgY29tbWFuZCBvciBz eW50YXguICBUeXBlIGA/JyBmb3IgaGVscC4NCmNvbmZpZz4gI3BucCAxIDAg YmlvcyBlbmFibGUgcG9ydDAgMHgyMjAgaXJxMCA1IGRycTAgMSBkcnExIDMN CkludmFsaWQgY29tbWFuZCBvciBzeW50YXguICBUeXBlIGA/JyBmb3IgaGVs cC4NCmNvbmZpZz4gI3BucCAxIDAgYmlvcyBlbmFibGUgcG9ydDAgMHhkODAg aXJxMCAxMQ0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8n IGZvciBoZWxwLg0KY29uZmlnPiBwbnAgMSAxIG9zIGVuYWJsZSBpcnEwIDUg ZHJxMCAxIHBvcnQwIDB4MjIwDQpJbnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4 LiAgVHlwZSBgPycgZm9yIGhlbHAuDQpjb25maWc+ICNpb3NpeiBucHgwIDI2 MjE0NA0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8nIGZv ciBoZWxwLg0KY29uZmlnPiBxdWl0DQphdmFpbCBtZW1vcnkgPSAyNTY3MTI3 MDQgKDI1MDY5NksgYnl0ZXMpDQpQcm9ncmFtbWluZyAyNCBwaW5zIGluIElP QVBJQyAjMA0KSU9BUElDICMwIGludHBpbiAyIC0+IGlycSAwDQpGcmVlQlNE L1NNUDogTXVsdGlwcm9jZXNzb3IgbW90aGVyYm9hcmQNCiBjcHUwIChCU1Ap OiBhcGljIGlkOiAgMSwgdmVyc2lvbjogMHgwMDA0MDAxMSwgYXQgMHhmZWUw MDAwMA0KIGNwdTEgKEFQKTogIGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAw MDQwMDExLCBhdCAweGZlZTAwMDAwDQogaW8wIChBUElDKTogYXBpYyBpZDog IDIsIHZlcnNpb246IDB4MDAxNzAwMTEsIGF0IDB4ZmVjMDAwMDANClByZWxv YWRlZCBlbGYga2VybmVsICJrZXJuZWwiIGF0IDB4YzAzNjIwMDAuDQpQcmVs b2FkZWQgdXNlcmNvbmZpZ19zY3JpcHQgIi9ib290L2tlcm5lbC5jb25mIiBh dCAweGMwMzYyMDljLg0KUHJlbG9hZGVkIGVsZiBtb2R1bGUgImJrdHIua28i IGF0IDB4YzAzNjIwZWMuDQpWRVNBOiB2Mi4wLCA4MTkyayBtZW1vcnksIGZs YWdzOjB4MSwgbW9kZSB0YWJsZToweGMwMmY1YjQyICgxMDAwMDIyKQ0KVkVT QTogTWF0cm94IEdyYXBoaWNzIEluYy4NClBlbnRpdW0gUHJvIE1UUlIgc3Vw cG9ydCBlbmFibGVkDQpucHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9uIG1vdGhl cmJvYXJkDQpucHgwOiBJTlQgMTYgaW50ZXJmYWNlDQpwY2liMDogPEludGVs IDgyNDQzQlggKDQ0MCBCWCkgaG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3Ro ZXJib2FyZA0KcGNpMDogPFBDSSBidXM+IG9uIHBjaWIwDQpwY2liMTogPElu dGVsIDgyNDQzQlggKDQ0MCBCWCkgUENJLVBDSSAoQUdQKSBicmlkZ2U+IGF0 IGRldmljZSAxLjAgb24gcGNpMA0KcGNpMTogPFBDSSBidXM+IG9uIHBjaWIx DQp2Z2EtcGNpMDogPE1hdHJveCBtb2RlbCAwNTIxIGdyYXBoaWNzIGFjY2Vs ZXJhdG9yPiBpcnEgMTYgYXQgZGV2aWNlIDAuMCBvbiBwY2kxDQppc2FiMDog PEludGVsIDgyMzcxQUIgUENJIHRvIElTQSBicmlkZ2U+IGF0IGRldmljZSA0 LjAgb24gcGNpMA0KaXNhMDogPElTQSBidXM+IG9uIGlzYWIwDQpwY2kwOiBJ bnRlbCBQSUlYNCBBVEEgY29udHJvbGxlciAodmVuZG9yPTB4ODA4NiwgZGV2 PTB4NzExMSkgYXQgNC4xDQp1aGNpMDogPEludGVsIDgyMzcxQUIvRUIgKFBJ SVg0KSBVU0IgY29udHJvbGxlcj4gaXJxIDE5IGF0IGRldmljZSA0LjIgb24g cGNpMA0KdXNiMDogPEludGVsIDgyMzcxQUIvRUIgKFBJSVg0KSBVU0IgY29u dHJvbGxlcj4gb24gdWhjaTANCnVzYjA6IFVTQiByZXZpc2lvbiAxLjANCnVo dWIwOiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAw LzEuMDAsIGFkZHIgMQ0KdWh1YjA6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJs ZSwgc2VsZiBwb3dlcmVkDQppbnRwbTA6IDxJbnRlbCA4MjM3MUFCIFBvd2Vy IG1hbmFnZW1lbnQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDQuMyBvbiBwY2kw DQppbnRwbTA6IEkvTyBtYXBwZWQgZTgwMA0KaW50cG0wOiBpbnRyIElSUSA5 IGVuYWJsZWQgcmV2aXNpb24gMA0Kc21idXMwOiA8U3lzdGVtIE1hbmFnZW1l bnQgQnVzPiBvbiBpbnRzbWIwDQpzbWIwOiA8U01CdXMgZ2VuZXJhbCBwdXJw b3NlIEkvTz4gb24gc21idXMwDQppbnRwbTA6IFBNIEkvTyBtYXBwZWQgZTQw MCANCmFoYzA6IDxBZGFwdGVjIGFpYzc4OTAvOTEgVWx0cmEyIFNDU0kgYWRh cHRlcj4gaXJxIDE5IGF0IGRldmljZSA2LjAgb24gcGNpMA0KYWhjMDogYWlj Nzg5MC85MSBXaWRlIENoYW5uZWwgQSwgU0NTSSBJZD03LCAxNi8yNTUgU0NC cw0KcGNpMDogdW5rbm93biBjYXJkICh2ZW5kb3I9MHgxMGI3LCBkZXY9MHg5 MDU1KSBhdCA5LjAgaXJxIDE5DQpia3RyMDogPEJyb29rVHJlZSA4Nzg+IGly cSAxOCBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQpia3RyMDogSGF1cHBhdWdl IE1vZGVsIDYxMzQ0IEQxMjENCmJrdHIwOiBEZXRlY3RlZCBhIE1TUDM0MTBE LUI0IGF0IDB4ODANCkhhdXBwYXVnZSBXaW5DYXN0L1RWLCBQaGlsaXBzIEZS MTIxNiBQQUwgRk0gdHVuZXIsIG1zcDM0MDBjIHN0ZXJlbywgcmVtb3RlIGNv bnRyb2wuDQpwY2kwOiB1bmtub3duIGNhcmQgKHZlbmRvcj0weDEwOWUsIGRl dj0weDA4NzgpIGF0IDEwLjEgaXJxIDE4DQpuY3IwOiA8bmNyIDUzYzg5NSBm YXN0NDAgd2lkZSBzY3NpPiBpcnEgMTcgYXQgZGV2aWNlIDExLjAgb24gcGNp MA0KaXNpYzA6IDxFTFNBIE1pY3JvTGluayBJU0ROL1BDST4gaXJxIDE2IGF0 IGRldmljZSAxMi4wIG9uIHBjaTANCmlzaWMwOiBFcnJvciwgSVBBQyB2ZXJz aW9uIDIgdW5rbm93biENCmRldmljZV9wcm9iZV9hbmRfYXR0YWNoOiBpc2lj MCBhdHRhY2ggcmV0dXJuZWQgNg0KaXNhMDogdG9vIG1hbnkgbWVtb3J5IHJh bmdlc2ZkYzA6IDxORUMgNzIwNjVCIG9yIGNsb25lPiBhdCBwb3J0IDB4M2Yw LTB4M2Y3IGlycSA2IGRycSAyIG9uIGlzYTANCmZkYzA6IEZJRk8gZW5hYmxl ZCwgOCBieXRlcyB0aHJlc2hvbGQNCmZkMDogPDE0NDAtS0IgMy41IiBkcml2 ZT4gb24gZmRjMCBkcml2ZSAwDQphdGtiZGMwOiA8a2V5Ym9hcmQgY29udHJv bGxlciAoaTgwNDIpPiBhdCBwb3J0IDB4NjAtMHg2ZiBvbiBpc2EwDQphdGti ZDA6IDxBVCBLZXlib2FyZD4gaXJxIDEgb24gYXRrYmRjMA0KdmdhMDogPEdl bmVyaWMgSVNBIFZHQT4gYXQgcG9ydCAweDNiMC0weDNkZiBpb21lbSAweGEw MDAwLTB4YmZmZmYgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9u IGlzYTANCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0w eDIwMD4NCnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAw eDEwIG9uIGlzYTANCnNpbzA6IHR5cGUgMTY1NTBBDQpzaW8xIGF0IHBvcnQg MHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0Kc2lvMTogdHlwZSAxNjU1MEEN CnNpbzI6IGNvbmZpZ3VyZWQgaXJxIDE5IG5vdCBpbiBiaXRtYXAgb2YgcHJv YmVkIGlycXMgMA0Kc2lvMzogY29uZmlndXJlZCBpcnEgMTkgbm90IGluIGJp dG1hcCBvZiBwcm9iZWQgaXJxcyAwDQpwcGMwIGF0IHBvcnQgMHgzNzgtMHgz N2YgaXJxIDcgZmxhZ3MgMHg0MCBvbiBpc2EwDQpwcGMwOiBTTUMtbGlrZSBj aGlwc2V0IChFQ1AvRVBQL1BTMi9OSUJCTEUpIGluIENPTVBBVElCTEUgbW9k ZQ0KcHBjMDogRklGTyB3aXRoIDE2LzE2LzkgYnl0ZXMgdGhyZXNob2xkDQps cHQwOiA8Z2VuZXJpYyBwcmludGVyPiBvbiBwcGJ1cyAwDQpscHQwOiBJbnRl cnJ1cHQtZHJpdmVuIHBvcnQNCnBwaTA6IDxnZW5lcmljIHBhcmFsbGVsIGkv bz4gb24gcHBidXMgMA0KdW5rbm93bjA6IDxFU1MgRVMxODY4IFBsdWcgYW5k IFBsYXkgQXVkaW9Ecml2ZT4gYXQgcG9ydCAweDgwMC0weDgwNyBvbiBpc2Ew DQpzYmMwOiA8RVNTIEVTMTg2OD4gYXQgcG9ydCAweDIyMC0weDIyZiwweDM4 OC0weDM4YiwweDMzMC0weDMzMSBpcnEgNSBkcnEgMSwwIG9uIGlzYTANCnBj bTA6IDxTQiBEU1AgMy4wMSAoRVNTIG1vZGUpPiBvbiBzYmMwDQp1bmtub3du MTogPEVTUyBFUzE4NjggUGx1ZyBhbmQgUGxheSBBdWRpb0RyaXZlPiBhdCBw b3J0IDB4MjAxIG9uIGlzYTANCnVua25vd24yOiA8RVNTIEVTMTg2OCBQbHVn IGFuZCBQbGF5IEF1ZGlvRHJpdmU+IGF0IHBvcnQgMHgxNjgtMHgxNmYsMHgz NmUtMHgzNmYgaXJxIDEyIG9uIGlzYTANCnVua25vd246IDxQTlAwNDAxPiBj YW4ndCBhc3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDUwMT4gY2Fu J3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjogPFBOUDA1MDE+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNzAwPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQp1bmtub3duMzogPFBOUDBjMDE+IGF0IGlvbWVt IDAtMHg5ZmZmZiwweDEwMDAwMC0weGZmZmZmZmYsMHhlODAwMC0weGVmZmZm LDB4ZjAwMDAtMHhmM2ZmZiwweGY0MDAwLTB4ZjdmZmYsMHhmODAwMC0weGZm ZmZmLDB4ZDM4MDAtMHhkM2ZmZiwweGZlYzAwMDAwLTB4ZmVjMDBmZmYgb24g aXNhMA0KdW5rbm93bjogPFBOUDAwMDA+IGNhbid0IGFzc2lnbiByZXNvdXJj ZXMNCnVua25vd240OiA8UE5QMDEwMD4gYXQgcG9ydCAweDQwLTB4NDMgaXJx IDAgb24gaXNhMA0KdW5rbm93bjU6IDxQTlAwYjAwPiBhdCBwb3J0IDB4NzAt MHg3MSBpcnEgOCBvbiBpc2EwDQp1bmtub3duOiA8UE5QMDMwMz4gY2FuJ3Qg YXNzaWduIHJlc291cmNlcw0KdW5rbm93bjY6IDxQTlAwYzA0PiBhdCBwb3J0 IDB4ZjAgaXJxIDEzIG9uIGlzYTANCnVua25vd243OiA8UE5QMDIwMD4gYXQg cG9ydCAwLTB4ZiwweDgwLTB4OTAsMHg5NC0weDlmLDB4YzAtMHhkZSBkcnEg NCBvbiBpc2EwDQp1bmtub3duOiA8UE5QMDgwMD4gY2FuJ3QgYXNzaWduIHJl c291cmNlcw0KdW5rbm93bjg6IDxQTlAwYTAzPiBhdCBwb3J0IDB4Y2Y4LTB4 Y2ZmIG9uIGlzYTANCnVua25vd246IDxQTlAwYzAyPiBjYW4ndCBhc3NpZ24g cmVzb3VyY2VzDQpBUElDX0lPOiBUZXN0aW5nIDgyNTQgaW50ZXJydXB0IGRl bGl2ZXJ5DQpBUElDX0lPOiByb3V0aW5nIDgyNTQgdmlhIElPQVBJQyAjMCBp bnRwaW4gMg0KaTRidHJjOiA0IElTRE4gdHJhY2UgZGV2aWNlKHMpIGF0dGFj aGVkDQppNGJyYmNoOiA0IHJhdyBCIGNoYW5uZWwgYWNjZXNzIGRldmljZShz KSBhdHRhY2hlZA0KaTRidGVsOiAyIElTRE4gdGVsZXBob255IGludGVyZmFj ZSBkZXZpY2UocykgYXR0YWNoZWQNCmk0YmlwcjogNCBJUCBvdmVyIHJhdyBI RExDIElTRE4gZGV2aWNlKHMpIGF0dGFjaGVkDQppNGJjdGw6IElTRE4gc3lz dGVtIGNvbnRyb2wgcG9ydCBhdHRhY2hlZA0KaTRiaXNwcHA6IDQgSVNETiBT eW5jUFBQIGRldmljZShzKSBhdHRhY2hlZA0KaTRiOiBJU0ROIGNhbGwgY29u dHJvbCBkZXZpY2UgYXR0YWNoZWQNCklQIHBhY2tldCBmaWx0ZXJpbmcgaW5p dGlhbGl6ZWQsIGRpdmVydCBlbmFibGVkLCBydWxlLWJhc2VkIGZvcndhcmRp bmcgZGlzYWJsZWQsIGxvZ2dpbmcgbGltaXRlZCB0byAxMDAgcGFja2V0cy9l bnRyeSBieSBkZWZhdWx0DQpXYWl0aW5nIDIgc2Vjb25kcyBmb3IgU0NTSSBk ZXZpY2VzIHRvIHNldHRsZQ0KU01QOiBBUCBDUFUgIzEgTGF1bmNoZWQhDQpN b3VudGluZyByb290IGZyb20gdWZzOi9kZXYvZGEwczFhDQpkYTMgYXQgbmNy MCBidXMgMCB0YXJnZXQgMyBsdW4gMA0KZGEzOiA8SUJNIEREUlMtMzkxMzBE IERDMUI+IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCmRh MzogNDAuMDAwTUIvcyB0cmFuc2ZlcnMgKDIwLjAwME1Ieiwgb2Zmc2V0IDE1 LCAxNmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpkYTM6IDg3MTVN QiAoMTc4NTAwMDAgNTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2M1MvVCAxMTEx QykNCmRhNCBhdCBuY3IwIGJ1cyAwIHRhcmdldCA0IGx1biAwDQpkYTQ6IDxJ Qk0gRERSUy0zOTEzMEQgREMxQj4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJ LTIgZGV2aWNlIA0KZGE0OiA0MC4wMDBNQi9zIHRyYW5zZmVycyAoMjAuMDAw TUh6LCBvZmZzZXQgMTUsIDE2Yml0KSwgVGFnZ2VkIFF1ZXVlaW5nIEVuYWJs ZWQNCmRhNDogODcxNU1CICgxNzg1MDAwMCA1MTIgYnl0ZSBzZWN0b3JzOiAy NTVIIDYzUy9UIDExMTFDKQ0KZGExIGF0IG5jcjAgYnVzIDAgdGFyZ2V0IDEg bHVuIDANCmRhMTogPElCTSBERFJTLTM5MTMwRCBEQzFCPiBGaXhlZCBEaXJl Y3QgQWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpkYTE6IDQwLjAwME1CL3MgdHJh bnNmZXJzICgyMC4wMDBNSHosIG9mZnNldCAxNSwgMTZiaXQpLCBUYWdnZWQg UXVldWVpbmcgRW5hYmxlZA0KZGExOiA4NzE1TUIgKDE3ODUwMDAwIDUxMiBi eXRlIHNlY3RvcnM6IDI1NUggNjNTL1QgMTExMUMpDQpkYTAgYXQgYWhjMCBi dXMgMCB0YXJnZXQgMCBsdW4gMA0KZGEwOiA8SUJNIEREUlMtMzQ1NjBEIERD MUI+IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCmRhMDog ODAuMDAwTUIvcyB0cmFuc2ZlcnMgKDQwLjAwME1Ieiwgb2Zmc2V0IDE1LCAx NmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpkYTA6IDQzNTdNQiAo ODkyNTAwMCA1MTIgYnl0ZSBzZWN0b3JzOiAyNTVIIDYzUy9UIDU1NUMpDQpk YTIgYXQgbmNyMCBidXMgMCB0YXJnZXQgMiBsdW4gMA0KZGEyOiA8SUJNIERE UlMtMzkxMzBEIERDMUI+IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRl dmljZSANCmRhMjogNDAuMDAwTUIvcyB0cmFuc2ZlcnMgKDIwLjAwME1Ieiwg b2Zmc2V0IDE1LCAxNmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpk YTI6IDg3MTVNQiAoMTc4NTAwMDAgNTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2 M1MvVCAxMTExQykNCnZpbnVtOiBsb2FkZWQNCnZpbnVtOiByZWFkaW5nIGNv bmZpZ3VyYXRpb24gZnJvbSAvZGV2L2RhMXMxZA0KdmludW06IHVwZGF0aW5n IGNvbmZpZ3VyYXRpb24gZnJvbSAvZGV2L2RhMnMxZA0KdmludW06IHVwZGF0 aW5nIGNvbmZpZ3VyYXRpb24gZnJvbSAvZGV2L2RhM3MxZA0KdmludW06IHVw ZGF0aW5nIGNvbmZpZ3VyYXRpb24gZnJvbSAvZGV2L2RhNHMxZA0KdmludW1p b2N0bDogaW52YWxpZCBpb2N0bCBmcm9tIHByb2Nlc3MgMTYgKHZpbnVtKTog YzBiODQ2NDMNCnBjaTA6IEludGVsIFBJSVg0IEFUQSBjb250cm9sbGVyICh2 ZW5kb3I9MHg4MDg2LCBkZXY9MHg3MTExKSBhdCA0LjENCnhsMDogPDNDb20g M2M5MDVCLVRYIEZhc3QgRXRoZXJsaW5rIFhMPiBpcnEgMTkgYXQgZGV2aWNl IDkuMCBvbiBwY2kwDQp4bDA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOjEwOjVh OmQ1OjliOjQzDQpwY2kwOiB1bmtub3duIGNhcmQgKHZlbmRvcj0weDEwOWUs IGRldj0weDA4NzgpIGF0IDEwLjEgaXJxIDE4DQppc2ljMDogPEVMU0EgTWlj cm9MaW5rIElTRE4vUENJPiBpcnEgMTYgYXQgZGV2aWNlIDEyLjAgb24gcGNp MA0KaXNpYzA6IEVycm9yLCBJUEFDIHZlcnNpb24gMiB1bmtub3duIQ0KZGV2 aWNlX3Byb2JlX2FuZF9hdHRhY2g6IGlzaWMwIGF0dGFjaCByZXR1cm5lZCA2 DQptaWlidXMwOiA8TUlJIGJ1cz4gb24geGwwDQp4bHBoeTA6IDwzQ29tIGlu dGVybmFsIG1lZGlhIGludGVyZmFjZT4gb24gbWlpYnVzMA0KeGxwaHkwOiAg MTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFzZVRYLUZE WCwgYXV0bw0KY2QwIGF0IGFoYzAgYnVzIDAgdGFyZ2V0IDQgbHVuIDANCmNk MDogPFBMRVhUT1IgQ0QtUk9NIFBYLTQwVFMgMS4wMD4gUmVtb3ZhYmxlIENE LVJPTSBTQ1NJLTIgZGV2aWNlIA0KY2QwOiAyMC4wMDBNQi9zIHRyYW5zZmVy cyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUpDQpjZDA6IGNkIHByZXNlbnQgWzMy NzY4OSB4IDIwNDggYnl0ZSByZWNvcmRzXQ0KY2QxIGF0IGFoYzAgYnVzIDAg dGFyZ2V0IDYgbHVuIDANCmNkMTogPFlBTUFIQSBDUlc2NDE2UyAxLjBjPiBS ZW1vdmFibGUgQ0QtUk9NIFNDU0ktMiBkZXZpY2UgDQpjZDE6IDEwLjAwME1C L3MgdHJhbnNmZXJzICgxMC4wMDBNSHosIG9mZnNldCAxNSkNCmNkMTogQXR0 ZW1wdCB0byBxdWVyeSBkZXZpY2Ugc2l6ZSBmYWlsZWQ6IE5PVCBSRUFEWSwg TWVkaXVtIG5vdCBwcmVzZW50IC0gdHJheSBjbG9zZWQNCg== --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg_sym.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg_sym.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk4MiwgMTk4NiwgMTk4OSwgMTk5MSwgMTk5Mw0K CVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEu IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMC1DVVJSRU5UICM0 OiBUaHUgSmFuICA2IDIwOjQ1OjQ1IENFVCAyMDAwDQogICAgcm9vdEBudWxs dW0ucGxhdXQuZGU6L3Vzci9zcmMvc3lzL2NvbXBpbGUvbnVsbHVtDQpUaW1l Y291bnRlciAiaTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KQ1BVOiBQ ZW50aXVtIElJSS9YZW9uICg0NTEuMDItTUh6IDY4Ni1jbGFzcyBDUFUpDQog IE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4NjcyICBTdGVwcGlu ZyA9IDINCiAgRmVhdHVyZXM9MHgzODNmYmZmPEZQVSxWTUUsREUsUFNFLFRT QyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQR0UsTUNBLENNT1Ys UEFULFBTRTM2LE1NWCxGWFNSLFhNTT4NCnJlYWwgbWVtb3J5ICA9IDI2ODQy MzE2OCAoMjYyMTMySyBieXRlcykNCmNvbmZpZz4gI2ZsYWdzIHdkYzAgMHhh MGZmYTBmZg0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8n IGZvciBoZWxwLg0KY29uZmlnPiAjZmxhZ3Mgd2RjMSAweGEwZmZhMGZmDQpJ bnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4LiAgVHlwZSBgPycgZm9yIGhlbHAu DQpjb25maWc+ICNpcnEgaXNpYzAgMTANCkludmFsaWQgY29tbWFuZCBvciBz eW50YXguICBUeXBlIGA/JyBmb3IgaGVscC4NCmNvbmZpZz4gI3BucCAxIDAg YmlvcyBlbmFibGUgcG9ydDAgMHgyMjAgaXJxMCA1IGRycTAgMSBkcnExIDMN CkludmFsaWQgY29tbWFuZCBvciBzeW50YXguICBUeXBlIGA/JyBmb3IgaGVs cC4NCmNvbmZpZz4gI3BucCAxIDAgYmlvcyBlbmFibGUgcG9ydDAgMHhkODAg aXJxMCAxMQ0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8n IGZvciBoZWxwLg0KY29uZmlnPiBwbnAgMSAxIG9zIGVuYWJsZSBpcnEwIDUg ZHJxMCAxIHBvcnQwIDB4MjIwDQpJbnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4 LiAgVHlwZSBgPycgZm9yIGhlbHAuDQpjb25maWc+ICNpb3NpeiBucHgwIDI2 MjE0NA0KSW52YWxpZCBjb21tYW5kIG9yIHN5bnRheC4gIFR5cGUgYD8nIGZv ciBoZWxwLg0KY29uZmlnPiBxdWl0DQphdmFpbCBtZW1vcnkgPSAyNTY2Njc2 NDggKDI1MDY1MksgYnl0ZXMpDQpQcm9ncmFtbWluZyAyNCBwaW5zIGluIElP QVBJQyAjMA0KSU9BUElDICMwIGludHBpbiAyIC0+IGlycSAwDQpGcmVlQlNE L1NNUDogTXVsdGlwcm9jZXNzb3IgbW90aGVyYm9hcmQNCiBjcHUwIChCU1Ap OiBhcGljIGlkOiAgMSwgdmVyc2lvbjogMHgwMDA0MDAxMSwgYXQgMHhmZWUw MDAwMA0KIGNwdTEgKEFQKTogIGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAw MDQwMDExLCBhdCAweGZlZTAwMDAwDQogaW8wIChBUElDKTogYXBpYyBpZDog IDIsIHZlcnNpb246IDB4MDAxNzAwMTEsIGF0IDB4ZmVjMDAwMDANClByZWxv YWRlZCBlbGYga2VybmVsICJrZXJuZWwueHh4IiBhdCAweGMwMzZkMDAwLg0K UHJlbG9hZGVkIHVzZXJjb25maWdfc2NyaXB0ICIvYm9vdC9rZXJuZWwuY29u ZiIgYXQgMHhjMDM2ZDBhYy4NClByZWxvYWRlZCBlbGYgbW9kdWxlICJia3Ry LmtvIiBhdCAweGMwMzZkMGZjLg0KVkVTQTogdjIuMCwgODE5MmsgbWVtb3J5 LCBmbGFnczoweDEsIG1vZGUgdGFibGU6MHhjMDJmZjNjMiAoMTAwMDAyMikN ClZFU0E6IE1hdHJveCBHcmFwaGljcyBJbmMuDQpQZW50aXVtIFBybyBNVFJS IHN1cHBvcnQgZW5hYmxlZA0KbnB4MDogPG1hdGggcHJvY2Vzc29yPiBvbiBt b3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVyZmFjZQ0KcGNpYjA6IDxJ bnRlbCA4MjQ0M0JYICg0NDAgQlgpIGhvc3QgdG8gUENJIGJyaWRnZT4gb24g bW90aGVyYm9hcmQNCnBjaTA6IDxQQ0kgYnVzPiBvbiBwY2liMA0KcGNpYjE6 IDxJbnRlbCA4MjQ0M0JYICg0NDAgQlgpIFBDSS1QQ0kgKEFHUCkgYnJpZGdl PiBhdCBkZXZpY2UgMS4wIG9uIHBjaTANCnBjaTE6IDxQQ0kgYnVzPiBvbiBw Y2liMQ0KdmdhLXBjaTA6IDxNYXRyb3ggbW9kZWwgMDUyMSBncmFwaGljcyBh Y2NlbGVyYXRvcj4gaXJxIDE2IGF0IGRldmljZSAwLjAgb24gcGNpMQ0KaXNh YjA6IDxJbnRlbCA4MjM3MUFCIFBDSSB0byBJU0EgYnJpZGdlPiBhdCBkZXZp Y2UgNC4wIG9uIHBjaTANCmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KcGNp MDogSW50ZWwgUElJWDQgQVRBIGNvbnRyb2xsZXIgKHZlbmRvcj0weDgwODYs IGRldj0weDcxMTEpIGF0IDQuMQ0KdWhjaTA6IDxJbnRlbCA4MjM3MUFCL0VC IChQSUlYNCkgVVNCIGNvbnRyb2xsZXI+IGlycSAxOSBhdCBkZXZpY2UgNC4y IG9uIHBjaTANCnVzYjA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkgVVNC IGNvbnRyb2xsZXI+IG9uIHVoY2kwDQp1c2IwOiBVU0IgcmV2aXNpb24gMS4w DQp1aHViMDogSW50ZWwgVUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYg MS4wMC8xLjAwLCBhZGRyIDENCnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1v dmFibGUsIHNlbGYgcG93ZXJlZA0KaW50cG0wOiA8SW50ZWwgODIzNzFBQiBQ b3dlciBtYW5hZ2VtZW50IGNvbnRyb2xsZXI+IGF0IGRldmljZSA0LjMgb24g cGNpMA0KaW50cG0wOiBJL08gbWFwcGVkIGU4MDANCmludHBtMDogaW50ciBJ UlEgOSBlbmFibGVkIHJldmlzaW9uIDANCnNtYnVzMDogPFN5c3RlbSBNYW5h Z2VtZW50IEJ1cz4gb24gaW50c21iMA0Kc21iMDogPFNNQnVzIGdlbmVyYWwg cHVycG9zZSBJL08+IG9uIHNtYnVzMA0KaW50cG0wOiBQTSBJL08gbWFwcGVk IGU0MDAgDQphaGMwOiA8QWRhcHRlYyBhaWM3ODkwLzkxIFVsdHJhMiBTQ1NJ IGFkYXB0ZXI+IGlycSAxOSBhdCBkZXZpY2UgNi4wIG9uIHBjaTANCmFoYzA6 IGFpYzc4OTAvOTEgV2lkZSBDaGFubmVsIEEsIFNDU0kgSWQ9NywgMTYvMjU1 IFNDQnMNCnBjaTA6IHVua25vd24gY2FyZCAodmVuZG9yPTB4MTBiNywgZGV2 PTB4OTA1NSkgYXQgOS4wIGlycSAxOQ0KYmt0cjA6IDxCcm9va1RyZWUgODc4 PiBpcnEgMTggYXQgZGV2aWNlIDEwLjAgb24gcGNpMA0KYmt0cjA6IEhhdXBw YXVnZSBNb2RlbCA2MTM0NCBEMTIxDQpia3RyMDogRGV0ZWN0ZWQgYSBNU1Az NDEwRC1CNCBhdCAweDgwDQpIYXVwcGF1Z2UgV2luQ2FzdC9UViwgUGhpbGlw cyBGUjEyMTYgUEFMIEZNIHR1bmVyLCBtc3AzNDAwYyBzdGVyZW8sIHJlbW90 ZSBjb250cm9sLg0KcGNpMDogdW5rbm93biBjYXJkICh2ZW5kb3I9MHgxMDll LCBkZXY9MHgwODc4KSBhdCAxMC4xIGlycSAxOA0Kc3ltMDogPDg5NT4gaXJx IDE3IGF0IGRldmljZSAxMS4wIG9uIHBjaTANCnN5bTA6IFN5bWJpb3MgTlZS QU0sIElEIDcsIEZhc3QtNDAsIExWRCwgcGFyaXR5IGNoZWNraW5nDQpzeW0w OiBvcGVuIGRyYWluIElSUSBsaW5lIGRyaXZlciwgdXNpbmcgb24tY2hpcCBT UkFNDQppc2ljMDogPEVMU0EgTWljcm9MaW5rIElTRE4vUENJPiBpcnEgMTYg YXQgZGV2aWNlIDEyLjAgb24gcGNpMA0KaXNpYzA6IEVycm9yLCBJUEFDIHZl cnNpb24gMiB1bmtub3duIQ0KZGV2aWNlX3Byb2JlX2FuZF9hdHRhY2g6IGlz aWMwIGF0dGFjaCByZXR1cm5lZCA2DQppc2EwOiB0b28gbWFueSBtZW1vcnkg cmFuZ2VzZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgz ZjAtMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMA0KZmRjMDogRklGTyBlbmFi bGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0KZmQwOiA8MTQ0MC1LQiAzLjUiIGRy aXZlPiBvbiBmZGMwIGRyaXZlIDANCmF0a2JkYzA6IDxrZXlib2FyZCBjb250 cm9sbGVyIChpODA0Mik+IGF0IHBvcnQgMHg2MC0weDZmIG9uIGlzYTANCmF0 a2JkMDogPEFUIEtleWJvYXJkPiBpcnEgMSBvbiBhdGtiZGMwDQp2Z2EwOiA8 R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2IwLTB4M2RmIGlvbWVtIDB4 YTAwMDAtMHhiZmZmZiBvbiBpc2EwDQpzYzA6IDxTeXN0ZW0gY29uc29sZT4g b24gaXNhMA0Kc2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdz PTB4MjAwPg0Kc2lvMCBhdCBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdz IDB4MTAgb24gaXNhMA0Kc2lvMDogdHlwZSAxNjU1MEENCnNpbzEgYXQgcG9y dCAweDJmOC0weDJmZiBpcnEgMyBvbiBpc2EwDQpzaW8xOiB0eXBlIDE2NTUw QQ0Kc2lvMjogY29uZmlndXJlZCBpcnEgMTkgbm90IGluIGJpdG1hcCBvZiBw cm9iZWQgaXJxcyAwDQpzaW8zOiBjb25maWd1cmVkIGlycSAxOSBub3QgaW4g Yml0bWFwIG9mIHByb2JlZCBpcnFzIDANCnBwYzAgYXQgcG9ydCAweDM3OC0w eDM3ZiBpcnEgNyBmbGFncyAweDQwIG9uIGlzYTANCnBwYzA6IFNNQy1saWtl IGNoaXBzZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBt b2RlDQpwcGMwOiBGSUZPIHdpdGggMTYvMTYvOSBieXRlcyB0aHJlc2hvbGQN CmxwdDA6IDxnZW5lcmljIHByaW50ZXI+IG9uIHBwYnVzIDANCmxwdDA6IElu dGVycnVwdC1kcml2ZW4gcG9ydA0KcHBpMDogPGdlbmVyaWMgcGFyYWxsZWwg aS9vPiBvbiBwcGJ1cyAwDQp1bmtub3duMDogPEVTUyBFUzE4NjggUGx1ZyBh bmQgUGxheSBBdWRpb0RyaXZlPiBhdCBwb3J0IDB4ODAwLTB4ODA3IG9uIGlz YTANCnNiYzA6IDxFU1MgRVMxODY4PiBhdCBwb3J0IDB4MjIwLTB4MjJmLDB4 Mzg4LTB4MzhiLDB4MzMwLTB4MzMxIGlycSA1IGRycSAxLDAgb24gaXNhMA0K cGNtMDogPFNCIERTUCAzLjAxIChFU1MgbW9kZSk+IG9uIHNiYzANCnVua25v d24xOiA8RVNTIEVTMTg2OCBQbHVnIGFuZCBQbGF5IEF1ZGlvRHJpdmU+IGF0 IHBvcnQgMHgyMDEgb24gaXNhMA0KdW5rbm93bjI6IDxFU1MgRVMxODY4IFBs dWcgYW5kIFBsYXkgQXVkaW9Ecml2ZT4gYXQgcG9ydCAweDE2OC0weDE2Ziww eDM2ZS0weDM2ZiBpcnEgMTIgb24gaXNhMA0KdW5rbm93bjogPFBOUDA0MDE+ IGNhbid0IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNTAxPiBj YW4ndCBhc3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDUwMT4gY2Fu J3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjogPFBOUDA3MDA+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd24zOiA8UE5QMGMwMT4gYXQgaW9t ZW0gMC0weDlmZmZmLDB4MTAwMDAwLTB4ZmZmZmZmZiwweGU4MDAwLTB4ZWZm ZmYsMHhmMDAwMC0weGYzZmZmLDB4ZjQwMDAtMHhmN2ZmZiwweGY4MDAwLTB4 ZmZmZmYsMHhkMzgwMC0weGQzZmZmLDB4ZmVjMDAwMDAtMHhmZWMwMGZmZiBv biBpc2EwDQp1bmtub3duOiA8UE5QMDAwMD4gY2FuJ3QgYXNzaWduIHJlc291 cmNlcw0KdW5rbm93bjQ6IDxQTlAwMTAwPiBhdCBwb3J0IDB4NDAtMHg0MyBp cnEgMCBvbiBpc2EwDQp1bmtub3duNTogPFBOUDBiMDA+IGF0IHBvcnQgMHg3 MC0weDcxIGlycSA4IG9uIGlzYTANCnVua25vd246IDxQTlAwMzAzPiBjYW4n dCBhc3NpZ24gcmVzb3VyY2VzDQp1bmtub3duNjogPFBOUDBjMDQ+IGF0IHBv cnQgMHhmMCBpcnEgMTMgb24gaXNhMA0KdW5rbm93bjc6IDxQTlAwMjAwPiBh dCBwb3J0IDAtMHhmLDB4ODAtMHg5MCwweDk0LTB4OWYsMHhjMC0weGRlIGRy cSA0IG9uIGlzYTANCnVua25vd246IDxQTlAwODAwPiBjYW4ndCBhc3NpZ24g cmVzb3VyY2VzDQp1bmtub3duODogPFBOUDBhMDM+IGF0IHBvcnQgMHhjZjgt MHhjZmYgb24gaXNhMA0KdW5rbm93bjogPFBOUDBjMDI+IGNhbid0IGFzc2ln biByZXNvdXJjZXMNCkFQSUNfSU86IFRlc3RpbmcgODI1NCBpbnRlcnJ1cHQg ZGVsaXZlcnkNCkFQSUNfSU86IHJvdXRpbmcgODI1NCB2aWEgSU9BUElDICMw IGludHBpbiAyDQppNGJ0cmM6IDQgSVNETiB0cmFjZSBkZXZpY2UocykgYXR0 YWNoZWQNCmk0YnJiY2g6IDQgcmF3IEIgY2hhbm5lbCBhY2Nlc3MgZGV2aWNl KHMpIGF0dGFjaGVkDQppNGJ0ZWw6IDIgSVNETiB0ZWxlcGhvbnkgaW50ZXJm YWNlIGRldmljZShzKSBhdHRhY2hlZA0KaTRiaXByOiA0IElQIG92ZXIgcmF3 IEhETEMgSVNETiBkZXZpY2UocykgYXR0YWNoZWQNCmk0YmN0bDogSVNETiBz eXN0ZW0gY29udHJvbCBwb3J0IGF0dGFjaGVkDQppNGJpc3BwcDogNCBJU0RO IFN5bmNQUFAgZGV2aWNlKHMpIGF0dGFjaGVkDQppNGI6IElTRE4gY2FsbCBj b250cm9sIGRldmljZSBhdHRhY2hlZA0KSVAgcGFja2V0IGZpbHRlcmluZyBp bml0aWFsaXplZCwgZGl2ZXJ0IGVuYWJsZWQsIHJ1bGUtYmFzZWQgZm9yd2Fy ZGluZyBkaXNhYmxlZCwgbG9nZ2luZyBsaW1pdGVkIHRvIDEwMCBwYWNrZXRz L2VudHJ5IGJ5IGRlZmF1bHQNCldhaXRpbmcgMiBzZWNvbmRzIGZvciBTQ1NJ IGRldmljZXMgdG8gc2V0dGxlDQoobm9wZXJpcGg6c3ltMDowOi0xOi0xKTog U0NTSSBCVVMgcmVzZXQgZGVsaXZlcmVkLg0KU01QOiBBUCBDUFUgIzEgTGF1 bmNoZWQhDQpNb3VudGluZyByb290IGZyb20gdWZzOi9kZXYvZGEwczFhDQpk YTEgYXQgc3ltMCBidXMgMCB0YXJnZXQgMSBsdW4gMA0KZGExOiA8SUJNIERE UlMtMzkxMzBEIERDMUI+IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRl dmljZSANCmRhMTogODAuMDAwTUIvcyB0cmFuc2ZlcnMgKDQwLjAwME1Ieiwg b2Zmc2V0IDE1LCAxNmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpk YTE6IDg3MTVNQiAoMTc4NTAwMDAgNTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2 M1MvVCAxMTExQykNCmRhMCBhdCBhaGMwIGJ1cyAwIHRhcmdldCAwIGx1biAw DQpkYTA6IDxJQk0gRERSUy0zNDU2MEQgREMxQj4gRml4ZWQgRGlyZWN0IEFj Y2VzcyBTQ1NJLTIgZGV2aWNlIA0KZGEwOiA4MC4wMDBNQi9zIHRyYW5zZmVy cyAoNDAuMDAwTUh6LCBvZmZzZXQgMTUsIDE2Yml0KSwgVGFnZ2VkIFF1ZXVl aW5nIEVuYWJsZWQNCmRhMDogNDM1N01CICg4OTI1MDAwIDUxMiBieXRlIHNl Y3RvcnM6IDI1NUggNjNTL1QgNTU1QykNCmRhMiBhdCBzeW0wIGJ1cyAwIHRh cmdldCAyIGx1biAwDQpkYTI6IDxJQk0gRERSUy0zOTEzMEQgREMxQj4gRml4 ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0KZGEyOiA4MC4wMDBN Qi9zIHRyYW5zZmVycyAoNDAuMDAwTUh6LCBvZmZzZXQgMTUsIDE2Yml0KSwg VGFnZ2VkIFF1ZXVlaW5nIEVuYWJsZWQNCmRhMjogODcxNU1CICgxNzg1MDAw MCA1MTIgYnl0ZSBzZWN0b3JzOiAyNTVIIDYzUy9UIDExMTFDKQ0KZGEzIGF0 IHN5bTAgYnVzIDAgdGFyZ2V0IDMgbHVuIDANCmRhMzogPElCTSBERFJTLTM5 MTMwRCBEQzFCPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZpY2Ug DQpkYTM6IDgwLjAwME1CL3MgdHJhbnNmZXJzICg0MC4wMDBNSHosIG9mZnNl dCAxNSwgMTZiaXQpLCBUYWdnZWQgUXVldWVpbmcgRW5hYmxlZA0KZGEzOiA4 NzE1TUIgKDE3ODUwMDAwIDUxMiBieXRlIHNlY3RvcnM6IDI1NUggNjNTL1Qg MTExMUMpDQpkYTQgYXQgc3ltMCBidXMgMCB0YXJnZXQgNCBsdW4gMA0KZGE0 OiA8SUJNIEREUlMtMzkxMzBEIERDMUI+IEZpeGVkIERpcmVjdCBBY2Nlc3Mg U0NTSS0yIGRldmljZSANCmRhNDogODAuMDAwTUIvcyB0cmFuc2ZlcnMgKDQw LjAwME1Ieiwgb2Zmc2V0IDE1LCAxNmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBF bmFibGVkDQpkYTQ6IDg3MTVNQiAoMTc4NTAwMDAgNTEyIGJ5dGUgc2VjdG9y czogMjU1SCA2M1MvVCAxMTExQykNCmNkMCBhdCBhaGMwIGJ1cyAwIHRhcmdl dCA0IGx1biAwDQpjZDA6IDxQTEVYVE9SIENELVJPTSBQWC00MFRTIDEuMDA+ IFJlbW92YWJsZSBDRC1ST00gU0NTSS0yIGRldmljZSANCmNkMDogMjAuMDAw TUIvcyB0cmFuc2ZlcnMgKDIwLjAwME1Ieiwgb2Zmc2V0IDE1KQ0KY2QwOiBj ZCBwcmVzZW50IFszMjc2ODkgeCAyMDQ4IGJ5dGUgcmVjb3Jkc10NCnZpbnVt OiBsb2FkZWQNCnZpbnVtOiByZWFkaW5nIGNvbmZpZ3VyYXRpb24gZnJvbSAv ZGV2L2RhNHMxZA0KdmludW06IHVwZGF0aW5nIGNvbmZpZ3VyYXRpb24gZnJv bSAvZGV2L2RhMXMxZA0KdmludW06IHVwZGF0aW5nIGNvbmZpZ3VyYXRpb24g ZnJvbSAvZGV2L2RhMnMxZA0KdmludW06IHVwZGF0aW5nIGNvbmZpZ3VyYXRp b24gZnJvbSAvZGV2L2RhM3MxZA0KY2QxIGF0IGFoYzAgYnVzIDAgdGFyZ2V0 IDYgbHVuIDANCmNkMTogPFlBTUFIQSBDUlc2NDE2UyAxLjBjPiBSZW1vdmFi bGUgQ0QtUk9NIFNDU0ktMiBkZXZpY2UgDQpjZDE6IDEwLjAwME1CL3MgdHJh bnNmZXJzICgxMC4wMDBNSHosIG9mZnNldCAxNSkNCmNkMTogQXR0ZW1wdCB0 byBxdWVyeSBkZXZpY2Ugc2l6ZSBmYWlsZWQ6IE5PVCBSRUFEWSwgTWVkaXVt IG5vdCBwcmVzZW50IC0gdHJheSBjbG9zZWQNCg== --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="neg_before.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="neg_before.txt" Q3VycmVudCBQYXJhbWV0ZXJzOg0KKHBhc3M2OnN5bTA6MDo0OjApOiBzeW5j IHBhcmFtZXRlcjogMTANCihwYXNzNjpzeW0wOjA6NDowKTogZnJlcXVlbmNl eTogNDAuMDAwTUh6DQoocGFzczY6c3ltMDowOjQ6MCk6IG9mZnNldDogMTUN CihwYXNzNjpzeW0wOjA6NDowKTogYnVzIHdpZHRoOiAxNiBiaXRzDQoocGFz czY6c3ltMDowOjQ6MCk6IGRpc2Nvbm5lY3Rpb24gaXMgZW5hYmxlZA0KKHBh c3M2OnN5bTA6MDo0OjApOiB0YWdnZWQgcXVldWVpbmcgaXMgZW5hYmxlZA0K --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="neg_after.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="neg_after.txt" Q3VycmVudCBQYXJhbWV0ZXJzOg0KKHBhc3MzOnN5bTA6MDoxOjApOiBzeW5j IHBhcmFtZXRlcjogMA0KKHBhc3MzOnN5bTA6MDoxOjApOiBvZmZzZXQ6IDAN CihwYXNzMzpzeW0wOjA6MTowKTogYnVzIHdpZHRoOiA4IGJpdHMNCihwYXNz MzpzeW0wOjA6MTowKTogZGlzY29ubmVjdGlvbiBpcyBlbmFibGVkDQoocGFz czM6c3ltMDowOjE6MCk6IHRhZ2dlZCBxdWV1ZWluZyBpcyBlbmFibGVkDQo= --0-1845788462-947200788=:1789 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="neg_ncr.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="neg_ncr.txt" Q3VycmVudCBQYXJhbWV0ZXJzOg0KKHBhc3MzOm5jcjA6MDoxOjApOiBzeW5j IHBhcmFtZXRlcjogMTINCihwYXNzMzpuY3IwOjA6MTowKTogZnJlcXVlbmNl eTogMjAuMDAwTUh6DQoocGFzczM6bmNyMDowOjE6MCk6IG9mZnNldDogMTUN CihwYXNzMzpuY3IwOjA6MTowKTogYnVzIHdpZHRoOiAxNiBiaXRzDQoocGFz czM6bmNyMDowOjE6MCk6IGRpc2Nvbm5lY3Rpb24gaXMgZW5hYmxlZA0KKHBh c3MzOm5jcjA6MDoxOjApOiB0YWdnZWQgcXVldWVpbmcgaXMgZW5hYmxlZA0K --0-1845788462-947200788=:1789-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 24C2B1578E for ; Thu, 6 Jan 2000 15:24:14 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 7 Jan 2000 10:16:28 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: <20000106094511.A30328@virtual-voodoo.com>; from steve@virtual-voodoo.com on Fri, Jan 07, 2000 at 01:43:09AM +1100 To: Steve Ames Cc: current@FreeBSD.ORG Message-Id: <00Jan7.101628est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <38746AEC.167EB0E7@elischer.org> <20000106094511.A30328@virtual-voodoo.com> Date: Fri, 7 Jan 2000 10:16:25 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-07 01:43:09 +1100, Steve Ames wrote: > _FEATURE_ freeze is January 15th. Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:). Maybe I misunderstood Jordan's original announcement, but this was also a surprise for me. Jordan originally stated that there'd be a feature freeze from 15th December 1999. I got the impression that this was going to be in effect for several months and would allow any code updates, but prevent the introduction of new features. This would then be followed by a _CODE_ freeze sometime in 2000Q1, leading to 4.0-RELEASE late in 2000Q1. (My understanding of the difference is that during the code freeze, only changes that demonstrably fix known bugs, without deleterious side effects, are allowed). A few weeks ago, I saw comments that it had slipped a month, followed a few days ago by Jordan's announcement of a code freeze. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:26:37 2000 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 A298B14CCD; Thu, 6 Jan 2000 15:26:30 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA73169; Thu, 6 Jan 2000 18:26:16 -0500 (EST) Date: Thu, 6 Jan 2000 18:26:16 -0500 (EST) From: To: "David O'Brien" Cc: Darren Reed , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <20000106144856.F1417@dragon.nuxi.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, 6 Jan 2000, David O'Brien wrote: > And when will IPv6 fully be in 4-CURRENT? > Besides offering two cents what else can you offer to make this happen? > Time? More money? > > People here aren't backing their opinions by tell us *how* their to make > their opinions happen. I cant do anything about time. Im not the one setting a deadline for FreeBSD releases. So thats moot. The point im trying to make is regardless of the state IPv6 is in, leaving it out of a major release is a no no IMO. Looking at the 4.4BSD Design and Implementation book you can see that on all major releases NEW items were added, TCP/IP, VM, etc.. Now everyone is perfectly aware of the fact that -core tries to keep releases and FreeBSD in general as stable as possible. And ultimely it's up to david and the rest what is going in and what is not. No one is going to argue with that. All I am saying and I think other's as well is that leaving v6 OUT of 4.0 would possibly be a negative move for the OS. It's not like were moving from v4 to v6. Were just asking that it be included in the OS. It should be available to researchers using 4.0-RELEASE. That's all im saying. There is no reason to ask for resources or anything else to make it happen. It's simply, include it even though it's buggy or dont. Thats how I see it anyway. There are people who are speaking up saying "Yes I want to see v6 in 4.0". I personally can live with it being in 4.1 or later. But if it's going to hurt FreeBSD in research labs, and universities who move to Linux instead or Solaris because they have a shipping v6 release regardless of how well it works that will hurt FreeBSD. That's all i'm saying take it for what its worth. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:29: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as4-032.rp-plus.de [149.221.238.96]) by hub.freebsd.org (Postfix) with ESMTP id 83C02157F8 for ; Thu, 6 Jan 2000 15:28:53 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 1EE94AB92; Fri, 7 Jan 2000 00:28:20 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id AAA41294; Fri, 7 Jan 2000 00:28:20 +0100 (CET) (envelope-from alex) Date: Fri, 7 Jan 2000 00:28:20 +0100 From: Alexander Langer To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: HEADS UP! wormcontrol and sys/dvdio.h users Message-ID: <20000107002820.A34994@cichlids.cichlids.com> Mail-Followup-To: Soren Schmidt , current@FreeBSD.ORG References: <200001062308.AAA97334@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001062308.AAA97334@freebsd.dk>; from sos@freebsd.dk on Fri, Jan 07, 2000 at 12:08:16AM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Soren Schmidt (sos@freebsd.dk): > The DVD ioctl's has changed numbers, so those using that > should recompile thier apps. > Wormcontrol and related files will be removed soon. I saw changes for the ioctl for the ata*, but not for the wd* stuff. Could wormcontrol at least stay as the wd* drivers stay? ata* doesn't work for me at the moment, thus I'm using the wd drivers. Or am I wrong? Can I use burncd with the wd drivers? Thank you. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:41:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 3F5271570E for ; Thu, 6 Jan 2000 15:41:42 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 126MWe-000AcI-00; Thu, 06 Jan 2000 15:41:04 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Darren Reed Cc: FreeBSD Current Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-Id: Date: Thu, 06 Jan 2000 15:41:04 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 4.0-RELEASE sounds like it will start becoming available at about the same > time as other OS's make new releases *with* IPv6/IPSec. You work it out > whether or not FreeBSD will win or lose from those two being there or not > there. what if the choice is o release at the same time with lots-o-features but not all of v6 o release _considerably later_ with all of v6, well most of it? where's your competitive advanatge in the latter? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 16AC1158EB; Thu, 6 Jan 2000 15:43:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01121; Thu, 6 Jan 2000 15:48:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001062348.PAA01121@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: scanner@jurai.net Cc: "David O'Brien" , Darren Reed , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 18:26:16 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 15:48:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD releases. So thats moot. The point im trying to make is regardless > of the state IPv6 is in, leaving it out of a major release is a no no IMO. If you believe this is really an issue, then you should be scolding the KAME folks and not the rest of us. They knew when the deadlines were, just like the rest of you. And in fact, if you cared at all about it, rather than waiting until _now_ and whining about it, you could have noticed that they were falling behind and offered to _help_ them with their work in order to make the deadling. > Now everyone is perfectly aware of the fact that -core tries to keep > releases and FreeBSD in general as stable as possible. Actually, -core don't do this at all. It's the responsibility of the entire developer team to do it, and it's one that many of you seem to enjoy shirking. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:51: 0 2000 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 40D94157A5; Thu, 6 Jan 2000 15:49:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA05512; Thu, 6 Jan 2000 15:47:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Cc: phk@freebsd.org, gibbs@freebsd.org Subject: So, tell me again why we can't read audio CDs in SCSI drives? Date: Thu, 06 Jan 2000 15:47:31 -0800 Message-ID: <5510.947202451@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive and try to read data off of it, I get the following behavior: root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null dd: /dev/rcd0c: Invalid argument 0+0 records in 0+0 records out (cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0 (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0 (cd0:ahc0:0:4:0): Illegal mode for this track (cd0:ahc0:0:4:0): cddone: got error 0x16 back dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048) and I've gotten this behavior for quite some time. I didn't *use* to have this behavior, as my mpeg backups of various CDs done on this same machine can demonstrate, but if we can't even read data off an audio CD with dd then you can rest assured that utilities like tosha aren't going to be able to read data either, and that really sucks. Drive information: cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [227322 x 2048 byte records] Controller information: ahc0: irq 10 at device 4.0 on pci2 ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs [This is a BIOS-less Advansys controller, used exclusively for the CD drive. The machine also has dual on-board 7895 wide controllers which are used just for disk in order to avoid mixing wide and narrow devices in (what I consider) less-than-elegant fashion] I also say "tell me again" because this issue isn't new and I brought it up back when this first broke. Justin said it clearly wasn't his code, SCSI device or no, and phk intimated that maybe it had something to do with the blockdev stuff and then handed me several patches which didn't have any effect on the problem. All I know is that my FreeBSD-current box has lost a powerful and popular capability and I'm more than willing to test patches or work with someone in fixing it. This area of the kernel isn't my forte', but my love of mp3s may send me in there at some point if this is still broken as we get close to code freeze. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 15:52:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C173B14CC8 for ; Thu, 6 Jan 2000 15:52:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA19535; Thu, 6 Jan 2000 15:50:31 -0800 Date: Thu, 6 Jan 2000 15:50:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Jeremy , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <00Jan7.101628est.40323@border.alcanet.com.au> 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, this is a very good point. Jordan, which is it? On Fri, 7 Jan 2000, Peter Jeremy wrote: > On 2000-Jan-07 01:43:09 +1100, Steve Ames wrote: > > _FEATURE_ freeze is January 15th. > > Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:). > > Maybe I misunderstood Jordan's original announcement, but this was > also a surprise for me. Jordan originally stated that there'd be a > feature freeze from 15th December 1999. I got the impression that > this was going to be in effect for several months and would allow any > code updates, but prevent the introduction of new features. This > would then be followed by a _CODE_ freeze sometime in 2000Q1, leading > to 4.0-RELEASE late in 2000Q1. (My understanding of the difference is > that during the code freeze, only changes that demonstrably fix known > bugs, without deleterious side effects, are allowed). > > A few weeks ago, I saw comments that it had slipped a month, followed > a few days ago by Jordan's announcement of a code freeze. > > Peter > > > 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 Thu Jan 6 16: 3:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 89BEB15798; Thu, 6 Jan 2000 16:03:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA19619; Thu, 6 Jan 2000 16:02:16 -0800 Date: Thu, 6 Jan 2000 16:02:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-Reply-To: <5510.947202451@zippy.cdrom.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 Hmm! Better hold the 4.0 Code Freeze until this sorts out! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16: 4:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 5489B14CC8; Thu, 6 Jan 2000 16:04:25 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id TAA02768; Thu, 6 Jan 2000 19:04:16 -0500 (EST) Date: Thu, 6 Jan 2000 19:04:16 -0500 From: Christian Kuhtz To: current@freebsd.org, committers@freebsd.org Subject: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000106190416.E1293@ns1.arch.bellsouth.net> References: <20000106144856.F1417@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from scanner@jurai.net on Thu, Jan 06, 2000 at 06:26:16PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 06:26:16PM -0500, scanner@jurai.net wrote: > with it being in 4.1 or later. But if it's going to hurt FreeBSD in > research labs, and universities who move to Linux instead or Solaris > because they have a shipping v6 release regardless of how well it works > that will hurt FreeBSD. For what it's worth, this isn't just about research in my particular case, as I'm not part of an R&D organization or educational space but in a commercial environment. Will you guys please wake up and realize that things like the IPv6forum (http://www.ipv6forum.org) aren't just somebody's science project? Look at the list of founding members on that page. There's serious demand for this stuff! And we got code that's been in the works for a long time, so, lets take a step and merge it. I have a preference to use FreeBSD for this work. However, right now it is more practical to go with a different OS (yes, merging external code with a a given code tree is a significant issue). And the longer this goes on, the less likely it will be that FreeBSD will be reintroduced. That's just a fact of life. Projects move forward with the exposure being given to one piece and not another. Result is, you've got to have really good reasons to switch later, and most times once you set the track it's a done deal. Or, it's actually more the one of a missed window and opportunity. And I'm sure I'm not the only one in this situation. Get IPv6 into the tree. Now. Thank you. Cheers, Chris -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16: 8:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.01019freenet.de (mout0.01019freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id 5759415698; Thu, 6 Jan 2000 16:08:09 -0800 (PST) (envelope-from julian@elischer.org) Received: from [62.104.201.6] (helo=mx0.01019freenet.de) by mout0.01019freenet.de with esmtp (Exim 3.12 #2) id 126MvB-0003PA-00; Fri, 07 Jan 2000 01:06:25 +0100 Received: from [213.6.103.193] (helo=jules.elischer.org) by mx0.01019freenet.de with smtp (Exim 3.12 #2) id 126MvA-0007kO-00; Fri, 07 Jan 2000 01:06:25 +0100 Message-ID: <38752DF1.794BDF32@elischer.org> Date: Thu, 06 Jan 2000 16:06:09 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Bakul Shah Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001061328.IAA11896@chai.torrentnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bakul Shah wrote: > > fairings > I almost fell off my chair laughing.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16: 9:26 2000 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 9B3D615090 for ; Thu, 6 Jan 2000 16:09:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05685; Thu, 6 Jan 2000 16:08:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 15:50:29 PST." Date: Thu, 06 Jan 2000 16:08:13 -0800 Message-ID: <5683.947203693@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's a feature freeze, sorry. I still expect the loose-ends that are in place as of that date to be tied up afterwards. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:15:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 78D4514CED for ; Thu, 6 Jan 2000 16:15:12 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 126N36-000AoN-00; Thu, 06 Jan 2000 16:14:36 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Christian Kuhtz Cc: FreeBSD Current Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <20000106190528.F1293@ns1.arch.bellsouth.net> Message-Id: Date: Thu, 06 Jan 2000 16:14:36 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> time as other OS's make new releases *with* IPv6/IPSec. You work it out >>> whether or not FreeBSD will win or lose from those two being there or not >>> there. >> what if the choice is >> o release at the same time with lots-o-features but not all of v6 >> o release _considerably later_ with all of v6, well most of it? >> where's your competitive advanatge in the latter? > Give me a break. > Take a look at http://www.ipv6forum.org and ask yourself whether this is > just somebody's science project. give whom a break? take a look at , and you will see that i am the ietf area director for ngtrans, i.e. one of those responsible for the ipv6 transition. now read my question again. there will always be new releases of freebsd, we hope. if v6 is not completely ready for this one, then delaying for any considerable time will not help you compete today in the ipv6 game. my point is that we can only wait politely and appreciatively for the kame folk to continue their work to a point where it is more fully rounded. until then, we should not forget that other features are also driving the 4.0 release train. now laptoy support on the other hand .... randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:16: 1 2000 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 DEC7A15708 for ; Thu, 6 Jan 2000 16:15:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05750; Thu, 6 Jan 2000 16:15:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: scanner@jurai.net Cc: "David O'Brien" , Darren Reed , current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Thu, 06 Jan 2000 18:26:16 EST." Date: Thu, 06 Jan 2000 16:15:08 -0800 Message-ID: <5748.947204108@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Moved to just -current; this doesn't need to keep getting cross-posted] > It's not like were moving from v4 to v6. Were just asking that it > be included in the OS. It should be available to researchers using > 4.0-RELEASE. That's all im saying. There is no reason to ask for resources > or anything else to make it happen. It's simply, include it even though > it's buggy or dont. Well, all I can say is that this represents one of the most bizarre and frankly unrealistic perspectives I've seen for a long, long time (well, maybe not that long - Karl's message was pretty recent, wasn't it?). How do you think things "get included" in the OS? Do you think one just moves the KAME bits into a directory next to /usr/src, goes away for 24 hours to let them bits do their thing, and then comes back to find that nature has done the rest of the work? Sorry, it might work that way for hamsters but it doesn't work that way for code! Somebody has to DO the integration and then be willing to stand behind it while 10,000 people start screaming how broken it is and how it needs to be fixed in the following 4,891 ways. That requires resources, resources which even the KAME folk (who certainly know this code better than anyone else) have been hard-pressed to provide or the IPv6/IPSec support would already BE in FreeBSD today! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:17:27 2000 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 AAC8415169; Thu, 6 Jan 2000 16:17:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05765; Thu, 6 Jan 2000 16:16:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 16:02:14 PST." Date: Thu, 06 Jan 2000 16:16:38 -0800 Message-ID: <5763.947204198@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm! Better hold the 4.0 Code Freeze until this sorts out! No, just better sort it out more quickly than usual. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:18:27 2000 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 74CF015776; Thu, 6 Jan 2000 16:18:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05777; Thu, 6 Jan 2000 16:17:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Christian Kuhtz Cc: current@FreeBSD.org, committers@FreeBSD.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-reply-to: Your message of "Thu, 06 Jan 2000 19:04:16 EST." <20000106190416.E1293@ns1.arch.bellsouth.net> Date: Thu, 06 Jan 2000 16:17:52 -0800 Message-ID: <5775.947204272@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Get IPv6 into the tree. Now. Thank you. Start helping and stop asking. Now. Thank you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:29:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CEDE214D91 for ; Thu, 6 Jan 2000 16:29:19 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Fri, 7 Jan 2000 11:17:14 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: Mounting CD-ROM with ATA driver hangs system In-reply-to: <200001060743.IAA71954@freebsd.dk>; from sos@freebsd.dk on Thu, Jan 06, 2000 at 06:38:08PM +1100 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Jan7.111714est.40330@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <00Jan6.151359est.40327@border.alcanet.com.au> <200001060743.IAA71954@freebsd.dk> Date: Fri, 7 Jan 2000 11:17:13 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-06 18:38:08 +1100, Soren Schmidt wrote: >It seems Peter Jeremy wrote: >> I just discovered that my ATAPI CD-ROM is no longer usable - when I >> try to mount it, my maching hangs (hard). ... >> acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA > ^^^ >You have enabled ATAPI DMA in your kernel config, dont, your >drive apparently doesn't support it. Oops. It looks like I didn't read the caveats carefully enough when I copied the options from LINT and GENERIC to my config file :-(. Sorry for the false alarm. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:29:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 37A8114D70; Thu, 6 Jan 2000 16:29:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01812; Thu, 6 Jan 2000 16:32:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001070032.QAA01812@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Christian Kuhtz Cc: current@freebsd.org, committers@freebsd.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-reply-to: Your message of "Thu, 06 Jan 2000 19:04:16 EST." <20000106190416.E1293@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 16:32:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Get IPv6 into the tree. Now. Thank you. I don't know quite what makes you think that we came down in the last shower of rain, but has it ever occurred to you that we're not _completely_ stupid? Do you _always_ assume that anyone other than yourself is a complete moron? What makes you think that we don't want this code integrated, or that we don't care about it? Have you bothered to actually read those sides of this discussion that have come from the release engineering team? Wouldn't it be much more sensible of you to assume that there are good and valid reasons for things being the way they are? Wouldn't it be much more sensible of you to enquire as to what these reasons are, or perhaps to even have paid attention to all the discussions and progress that have gone on over the last few months (or even just stayed up to date in the last week, where the whole matter has been discussed)? Or are you just too lazy? Too lazy to pay attention? Too lazy to actually participate in this process? Too lazy to do anything other than to wait until it's too late to do anything, and then randomly sling blame around? What _do_ you think you achieve with this? How do you think that insulting the people that are actually trying to do the work while you sit on the sidelines is going to help the process? It's been said before, and I'm sure it'll be said again; if you can't or won't offer support or assistance, the very least you can do is avoid being actively destructive. Take a few moments to think about what it is that you and we want to achieve, and how best to get there. And take a hint; insulting us is not how to go about it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:30:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 9FF211590C for ; Thu, 6 Jan 2000 16:30:19 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-252.ix.netcom.com [209.109.235.252]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id QAA28663; Thu, 6 Jan 2000 16:27:35 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id QAA49556; Thu, 6 Jan 2000 16:27:30 -0800 (PST) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <5748.947204108@zippy.cdrom.com> From: asami@FreeBSD.ORG (fifi - the hamster - asami) Date: 06 Jan 2000 16:27:27 -0800 In-Reply-To: "Jordan K. Hubbard"'s message of "Thu, 06 Jan 2000 16:15:08 -0800" Message-ID: Lines: 22 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * How do you think things "get included" in the OS? Do you think one * just moves the KAME bits into a directory next to /usr/src, goes away * for 24 hours to let them bits do their thing, and then comes back to * find that nature has done the rest of the work? Sorry, it might work * that way for hamsters but it doesn't work that way for code! Somebody dear mr. hubbard, please do not insult hamsters. it doesn't work that way for hamsters either. we are fully aware of our surroundings and plan our lives accordingly. in fact, satoshi is out picking oranges now so i have full access to his computer. (ooohh nude hamster pics....) that said, i don't think you need to push back the release date. sincerely, fifi p.s. pardon the lack of capital letters but my paws can't quite reach the shift key and the alphabet keys at the same time.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:31:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9ED2515754; Thu, 6 Jan 2000 16:31:16 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA39453; Thu, 6 Jan 2000 17:30:35 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 17:30:35 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106173035.A39324@panzer.kdm.org> References: <5510.947202451@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5510.947202451@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 03:47:31PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 15:47:31 -0800, Jordan K. Hubbard wrote: > If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive > and try to read data off of it, I get the following behavior: > > root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null > dd: /dev/rcd0c: Invalid argument > 0+0 records in > 0+0 records out > > (cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0 > (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0 > (cd0:ahc0:0:4:0): Illegal mode for this track > (cd0:ahc0:0:4:0): cddone: got error 0x16 back > dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048) > > and I've gotten this behavior for quite some time. I didn't *use* to > have this behavior, as my mpeg backups of various CDs done on this > same machine can demonstrate, but if we can't even read data off an > audio CD with dd then you can rest assured that utilities like tosha > aren't going to be able to read data either, and that really sucks. Some drives need a special mode select command before they'll let you read off audio blocks. Some drives use special read CDBs for reading CDDA. Toshiba drives, in particular, need a special mode select command before you can read audio blocks. After that, they use a standard read command. In any case, the point is, reading raw audio data off a CDROM drive is not standard across drives. So I'm surprised that you could ever read audio tracks off your CDROM drive using dd, or anything else that accesses the raw/block devices. tosha and cdda2wav should work, however, since they know about many different kinds of drives and access methods. They may need tweaking to recognize the specific vendor name there, but they should work. (tosha at least has a nice rc file that you can use to tweak this kind of thing) One way that this *might* have worked is if you were using some utility on your CDROM drive that did the special mode select stuff, and didn't reset the mode to 'normal' before you did the dd. That could cause problems with reading normal data CDs, however. > Drive information: > > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: cd present [227322 x 2048 byte records] > > Controller information: > > ahc0: irq 10 at device 4.0 on pci2 > ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs > > [This is a BIOS-less Advansys controller, used exclusively for the CD > drive. The machine also has dual on-board 7895 wide controllers > which are used just for disk in order to avoid mixing wide and narrow > devices in (what I consider) less-than-elegant fashion] You mean an Adaptec controller, right? > I also say "tell me again" because this issue isn't new and I brought > it up back when this first broke. Justin said it clearly wasn't his > code, SCSI device or no, and phk intimated that maybe it had something > to do with the blockdev stuff and then handed me several patches which > didn't have any effect on the problem. All I know is that my FreeBSD-current > box has lost a powerful and popular capability and I'm more than willing > to test patches or work with someone in fixing it. This area of the > kernel isn't my forte', but my love of mp3s may send me in there at > some point if this is still broken as we get close to code freeze. :-) Like I said, I'm not sure how this ever worked properly. Try tosha or cdda2wav and report back on whether or not it works. dd has never been a supported way to read audio tracks, for the reasons outlined above. It may be possible in some situations, but it was probably just a fluke. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:34:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 74DFE14D10; Thu, 6 Jan 2000 16:34:42 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id TAA03275; Thu, 6 Jan 2000 19:32:59 -0500 (EST) Date: Thu, 6 Jan 2000 19:32:59 -0500 From: Christian Kuhtz To: "Jordan K. Hubbard" Cc: Christian Kuhtz , current@FreeBSD.org, committers@FreeBSD.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000106193259.K1293@ns1.arch.bellsouth.net> References: <20000106190416.E1293@ns1.arch.bellsouth.net> <5775.947204272@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <5775.947204272@zippy.cdrom.com>; from Jordan K. Hubbard on Thu, Jan 06, 2000 at 04:17:52PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 04:17:52PM -0800, Jordan K. Hubbard wrote: > > Get IPv6 into the tree. Now. Thank you. > > Start helping and stop asking. Now. Thank you. State specifically what is needed. Now. Thank you. Part of the lack of help may be the result of people clueless as to where to start. -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:39:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.arch.bellsouth.net (ns1.arch.bellsouth.net [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 1F0BD14C24; Thu, 6 Jan 2000 16:39:18 -0800 (PST) (envelope-from ck@ns1.arch.bellsouth.net) Received: (from ck@localhost) by ns1.arch.bellsouth.net (8.9.1a/goaway) id TAA03353; Thu, 6 Jan 2000 19:37:59 -0500 (EST) Date: Thu, 6 Jan 2000 19:37:59 -0500 From: Christian Kuhtz To: Mike Smith Cc: Christian Kuhtz , current@freebsd.org, committers@freebsd.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000106193759.L1293@ns1.arch.bellsouth.net> References: <20000106190416.E1293@ns1.arch.bellsouth.net> <200001070032.QAA01812@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <200001070032.QAA01812@mass.cdrom.com>; from Mike Smith on Thu, Jan 06, 2000 at 04:32:21PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 04:32:21PM -0800, Mike Smith wrote: > > Get IPv6 into the tree. Now. Thank you. > > I don't know quite what makes you think that we came down in the last > shower of rain, but has it ever occurred to you that we're not > _completely_ stupid? Sure it has. I think I'm not assuming that everyone's completely stupid. So, that said, stick your flame thrower where it came from and assume for one second that I'm not completely stupid and follow your own proposed lead. > Do you _always_ assume that anyone other than yourself is a complete > moron? Where did this and all that other stuff come from? > What makes you think that we don't want this code integrated, or > that we don't care about it? Have you bothered to actually read those > sides of this discussion that have come from the release engineering team? Yes. As a matter of fact, I have. So, where is the email which specifically states the reasons why it will not be integrated? I apparently missed something in this flurry of email. Nobody is trying to insult anyone here. Quit taking things personal. Just because people are lurking doesn't mean they're not paying attention. Cheers, Chris -- Christian Kuhtz Architecture, BellSouth.net -wk, -hm Atlanta, GA "Speaking for myself only." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:42:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4ECF6156EC; Thu, 6 Jan 2000 16:42:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02011; Thu, 6 Jan 2000 16:46:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001070046.QAA02011@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Christian Kuhtz Cc: "Jordan K. Hubbard" , current@FreeBSD.org, committers@FreeBSD.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-reply-to: Your message of "Thu, 06 Jan 2000 19:32:59 EST." <20000106193259.K1293@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 16:46:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Jan 06, 2000 at 04:17:52PM -0800, Jordan K. Hubbard wrote: > > > Get IPv6 into the tree. Now. Thank you. > > > > Start helping and stop asking. Now. Thank you. > > State specifically what is needed. Now. Thank you. > > Part of the lack of help may be the result of people clueless as to where to > start. First, you need a time machine. Second, you should go back to when the KAME folks started talking about their integration work (that's about eight or ten months now). Third, you should start working with them on the integration process. Fourth, and this is probably more important since the first three are probably beyond your reach right now - start paying attention. If you hadn't been asleep at the wheel, you'd already know all this, and the entire issue would be moot because you'd be helping already. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:49:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id DF9BF14C4B for ; Thu, 6 Jan 2000 16:49:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02144; Thu, 6 Jan 2000 16:53:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001070053.QAA02144@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Christian Kuhtz Cc: current@freebsd.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-reply-to: Your message of "Thu, 06 Jan 2000 19:37:59 EST." <20000106193759.L1293@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 16:53:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you _always_ assume that anyone other than yourself is a complete > > moron? > > Where did this and all that other stuff come from? You have to ask this? > > What makes you think that we don't want this code integrated, or > > that we don't care about it? Have you bothered to actually read those > > sides of this discussion that have come from the release engineering team? > > Yes. As a matter of fact, I have. Then I'm puzzled as to which parts you haven't understood. > So, where is the email which specifically states the reasons why it will not > be integrated? I apparently missed something in this flurry of email. I'm sorry. I thought you'd been keeping up to date. There's a perfectly good mail archive provided by the Project for your use; I suggest that you'd be best served by using it to locate all the mail that you've read and forgotten or otherwise misunderstood. Discussion on the state of the KAME integration has been going on for over a year now, and the work itself for well over six months. I'm not about to do your research for you; I have other work to do in order to avoid being randomly flamed by someone else like yourself. > Nobody is trying to insult anyone here. Quit taking things personal. Just > because people are lurking doesn't mean they're not paying attention. In your case, you're not lurking and still not paying attention. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 16:50:15 2000 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 6BB6B1567D for ; Thu, 6 Jan 2000 16:50:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA54710; Thu, 6 Jan 2000 16:47:58 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA59182; Thu, 6 Jan 2000 16:47:57 -0800 (PST) (envelope-from obrien) Date: Thu, 6 Jan 2000 16:47:57 -0800 From: "David O'Brien" To: Christian Kuhtz Cc: current@freebsd.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000106164757.A59158@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000106144856.F1417@dragon.nuxi.com> <20000106190416.E1293@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000106190416.E1293@ns1.arch.bellsouth.net>; from ck@arch.bellsouth.net on Thu, Jan 06, 2000 at 07:04:16PM -0500 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 Thu, Jan 06, 2000 at 07:04:16PM -0500, Christian Kuhtz wrote: > -wk, -hm ^^^^^^^ Damnit! I've asked for some features in GCC, GNU grep, and GNU diff. I want them *NOW* in time for 4.0-RELEASE. So where the fsck are they??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 17:12:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 9114315753; Thu, 6 Jan 2000 17:12:25 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA38222; Fri, 7 Jan 2000 11:40:33 +1030 (CST) (envelope-from newton) Date: Fri, 7 Jan 2000 11:40:33 +1030 From: Mark Newton To: fifi - the hamster - asami Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000107114033.B37571@internode.com.au> References: <5748.947204108@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 04:27:27PM -0800, fifi - the hamster - asami wrote: > dear mr. hubbard, > please do not insult hamsters. it doesn't work that way for hamsters > either. we are fully aware of our surroundings and plan our lives > accordingly. in fact, satoshi is out picking oranges now so i have > full access to his computer. (ooohh nude hamster pics....) http://www.realhamster.com - mark :-) -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 17:12:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from acutiator.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id 7E29C15753; Thu, 6 Jan 2000 17:12:33 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: by acutiator.nacamar.de (Postfix, from userid 499) id F212D5F4B; Fri, 7 Jan 2000 02:03:29 +0100 (CET) Date: Fri, 7 Jan 2000 02:03:29 +0100 From: "Karsten W. Rohrbach" To: "Jordan K. Hubbard" Cc: current@freebsd.org, phk@freebsd.org, gibbs@freebsd.org Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000107020327.B68369@nacamar.net> Reply-To: rohrbach@nacamar.net References: <5510.947202451@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <5510.947202451@zippy.cdrom.com>; from Jordan K. Hubbard on Thu, Jan 06, 2000 at 03:47:31PM -0800 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG reading raw audio data off a cd with dd did never work for me... anyway, it would be a good thing(TM) if there was a tool such as cdparanoia under l*n*x that has all that fancy jitter and scratch detection and removal (real goodd error correction) and this ones also really fast (10x speed) when youre reading on a plextor drive (such as my pxw4220t) or something else that has a native mode for extracting audio. i think, theres a port of tosha available, but the last time i tried this one it wouldnt work for me so i used the l*n*x box next to my workstation... /k Jordan K. Hubbard (jkh@zippy.cdrom.com) @ Thu, Jan 06, 2000 at 03:47:31PM -0800: > If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive > and try to read data off of it, I get the following behavior: > > root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null > dd: /dev/rcd0c: Invalid argument > 0+0 records in > 0+0 records out > > (cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0 > (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0 > (cd0:ahc0:0:4:0): Illegal mode for this track > (cd0:ahc0:0:4:0): cddone: got error 0x16 back > dscheck(#cd/2): b_bcount 512 is not on a sector boundary (ssize 2048) > > and I've gotten this behavior for quite some time. I didn't *use* to > have this behavior, as my mpeg backups of various CDs done on this > same machine can demonstrate, but if we can't even read data off an > audio CD with dd then you can rest assured that utilities like tosha > aren't going to be able to read data either, and that really sucks. > > Drive information: > > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: cd present [227322 x 2048 byte records] > > Controller information: > > ahc0: irq 10 at device 4.0 on pci2 > ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs > > [This is a BIOS-less Advansys controller, used exclusively for the CD > drive. The machine also has dual on-board 7895 wide controllers > which are used just for disk in order to avoid mixing wide and narrow > devices in (what I consider) less-than-elegant fashion] > > I also say "tell me again" because this issue isn't new and I brought > it up back when this first broke. Justin said it clearly wasn't his > code, SCSI device or no, and phk intimated that maybe it had something > to do with the blockdev stuff and then handed me several patches which > didn't have any effect on the problem. All I know is that my FreeBSD-current > box has lost a powerful and popular capability and I'm more than willing > to test patches or work with someone in fixing it. This area of the > kernel isn't my forte', but my love of mp3s may send me in there at > some point if this is still broken as we get close to code freeze. :-) > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- > Hackers know all the right MOVs. http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net KR433/KR11-RIPE - PGP-KFP = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 17:49: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mickey.atarde.com.br (mickey.atarde.com.br [200.223.87.5]) by hub.freebsd.org (Postfix) with SMTP id 076FC150C6 for ; Thu, 6 Jan 2000 17:48:25 -0800 (PST) (envelope-from boozy@rabelo.eti.br) Received: (qmail 27364 invoked from network); 7 Jan 2000 01:48:38 -0000 Received: from cartoon117.atarde.com.br (HELO robusto) (200.223.87.117) by mickey.atarde.com.br with SMTP; 7 Jan 2000 01:48:38 -0000 Message-Id: X-Sender: boozy%rabelo.eti.br@mickey.atarde.com.br X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Thu, 06 Jan 2000 23:34:11 -0200 To: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org From: Boozy Subject: -current or 3.4 with KAME ??? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Lists again :))), I'm sorry but when I sent this message I wasn't subscribe here. So I am puting this message again and I'd be happy if somebody reply me. ----- How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it stable? What is better: use FreeBSD 3.4 with Kame or FreeBSD 4.0? ----- Thanks, Luciano Rabelo Salvador - Bahia - Brazil ******************************** * Luciano Rabelo * * Analista de Sistemas * * Salvador - Bahia - Brasil * * http://www.rabelo.eti.br/ * * lrcp@rabelo.eti.br * * UIN - 8642704 * ******************************** /"\ \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 17:57:22 2000 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 1116B158BA for ; Thu, 6 Jan 2000 17:56:58 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id CAA45762; Fri, 7 Jan 2000 02:27:17 +0100 (CET) (envelope-from olli) Date: Fri, 7 Jan 2000 02:27:17 +0100 (CET) Message-Id: <200001070127.CAA45762@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@freebsd.org Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? X-Newsgroups: list.freebsd-current In-Reply-To: <853eri$rr4$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Karsten W. Rohrbach wrote in list.freebsd-current: > reading raw audio data off a cd with dd did never work for me... > anyway, it would be a good thing(TM) if there was a tool such as > cdparanoia under l*n*x that has all that fancy jitter and scratch > detection and removal (real goodd error correction) and this ones also > really fast (10x speed) when youre reading on a plextor drive (such as > my pxw4220t) or something else that has a native mode for extracting > audio. > > i think, theres a port of tosha available, but the last time i tried > this one it wouldnt work for me so i used the l*n*x box next to my > workstation... "Port of tosha"? Tosha is a native FreeBSD program. :-) BTW, it reads audio tracks off my Plextor drive at 20x - 24x speed. 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 Jan 6 17:59:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6D5CB15765; Thu, 6 Jan 2000 17:59:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA40001; Thu, 6 Jan 2000 18:44:24 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 18:44:24 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106184424.A39865@panzer.kdm.org> References: <20000106173035.A39324@panzer.kdm.org> <6143.947208503@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6143.947208503@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 05:28:23PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 17:28:23 -0800, Jordan K. Hubbard wrote: > > You mean an Adaptec controller, right? > > Yes, I guess Adaptec did buy those guys. Adaptec bought DPT, not Advansys. In any case, you've got a low end Adaptec controller, with a 7850. > > Try tosha or cdda2wav and report back on whether or not it works. dd has > > never been a supported way to read audio tracks, for the reasons outlined > > above. It may be possible in some situations, but it was probably just a > > fluke. > > root@zippy-> tosha -t 1 > Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20" > > track playing start end raw size mp3 size # of track > number time sector sector in bytes 128 kbps frames type > --------------------------------------------------------------------- > 1 3:57'58 32 17864 41943216 3805208 9103 audio > error sending SCSI command: Invalid argument > [and on the console] > (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 > (pass0:ahc0:0:4:0): Invalid field in parameter list > > (I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just > for fun, but they were invalid ops for this drive). Okay, I just looked through the cdda2wav soure, and it appears that "SAF" stands for "Smart and Friendly". Apparantly some of its drives may be Sony OEM (or act like it) and some may be Teac OEM (or act like them). Yours isn't listed. See if cdda2wav (part of the cdrecord port) works with your drive. It has a little broader device support than tosha. Also, you might want to try mailing Oliver Fromme (the author of tosha) and see if he has any idea what it would take to get your drive to function. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 17:59:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id CB1C215785; Thu, 6 Jan 2000 17:59:39 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA39715; Thu, 6 Jan 2000 18:20:04 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 18:20:04 -0700 From: "Kenneth D. Merry" To: "Karsten W. Rohrbach" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106182004.B39324@panzer.kdm.org> References: <5510.947202451@zippy.cdrom.com> <20000107020327.B68369@nacamar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000107020327.B68369@nacamar.net>; from rohrbach@nacamar.net on Fri, Jan 07, 2000 at 02:03:29AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 02:03:29 +0100, Karsten W. Rohrbach wrote: > reading raw audio data off a cd with dd did never work for me... See my response to Jordan -- it has never been a supported way to read audio tracks. > anyway, it would be a good thing(TM) if there was a tool such as > cdparanoia under l*n*x that has all that fancy jitter and scratch > detection and removal (real goodd error correction) and this ones also > really fast (10x speed) when youre reading on a plextor drive (such as > my pxw4220t) or something else that has a native mode for extracting > audio. > > i think, theres a port of tosha available, but the last time i tried > this one it wouldnt work for me so i used the l*n*x box next to my > workstation... Both tosha and cdda2wav are supported, and both work with my plextor drives. Why didn't tosha work with your drive? Did you contact the author (Oliver Fromme)? Many of the opinions I've seen recently are that you jitter correction isn't necessary for most newer CDROM drives. If you want jitter correction, you can port cdd to CAM. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18: 1: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id F33271577F; Thu, 6 Jan 2000 18:00:56 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id BAA44385; Fri, 7 Jan 2000 01:20:37 GMT (envelope-from joe) Date: Fri, 7 Jan 2000 01:20:37 +0000 From: Josef Karthauser To: Christian Kuhtz Cc: Mike Smith , current@FreeBSD.org, committers@FreeBSD.org Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000107012037.C43650@florence.pavilion.net> References: <20000106190416.E1293@ns1.arch.bellsouth.net> <200001070032.QAA01812@mass.cdrom.com> <20000106193759.L1293@ns1.arch.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000106193759.L1293@ns1.arch.bellsouth.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 07:37:59PM -0500, Christian Kuhtz wrote: > > Yes. As a matter of fact, I have. > > So, where is the email which specifically states the reasons why it will not > be integrated? I apparently missed something in this flurry of email. I don't know if you realise, I most of IPv6 _IS_ currently in 4.x if you compile your kernel with INET6 enabled: genius% uname -a FreeBSD genius.systems.pavilion.net 4.0-CURRENT FreeBSD 4.0-CURRENT #32: Sun Jan 2 18:15:42 GMT 2000 joe@genius.systems.pavilion.net:/usr/src/sys/compile/GENIUS i386 genius% ifconfig -a lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80:2::1 prefixlen 64 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 ep0: flags=8843 mtu 1500 inet6 fe80:3::260:8ff:fe95:a83c prefixlen 64 inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:60:08:95:a8:3c media: 10baseT/UTP supported media: 10base2/BNC 10baseT/UTP 10base5/AUI genius% ping6 usage: ping6 [-dfnqRrvwW] [-a [alsg]] [-b sockbufsiz] [-c count] [-I interface] [-i wait] [-l preload] [-p pattern] [-s packetsize] [-h hoplimit] host [hosts...] genius% traceroute6 usage: traceroute6 [-dlnrv] [-m max_hops] [-p port#] [-q nqueries] [-s src_addr] [-g gateway] [-w wait] host [data size] From route(8): For AF_INET6, the -prefixlen qualifier is available instead of the -mask qualifier because non-continuous masks are not allowed in IPv6. For ex- ample, -prefixlen 32 specifies network mask of ffff:ffff:0000:0000:0000:0000:0000:0000 to be used. The default value of prefixlen is 64 to get along with the aggregatable address. But 0 is as- sumed if default is specified. Note that the qualifier works only for AF_INET6 address family. I don't understand how you can say that it _isn't integrated! Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:16: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6A0B8157B0; Thu, 6 Jan 2000 18:15:57 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA40331; Thu, 6 Jan 2000 19:10:51 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 19:10:51 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106191051.A40270@panzer.kdm.org> References: <20000106173035.A39324@panzer.kdm.org> <6143.947208503@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6143.947208503@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 05:28:23PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 17:28:23 -0800, Jordan K. Hubbard wrote: > > You mean an Adaptec controller, right? > > Yes, I guess Adaptec did buy those guys. > > > Try tosha or cdda2wav and report back on whether or not it works. dd has > > never been a supported way to read audio tracks, for the reasons outlined > > above. It may be possible in some situations, but it was probably just a > > fluke. > > root@zippy-> tosha -t 1 > Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20" > > track playing start end raw size mp3 size # of track > number time sector sector in bytes 128 kbps frames type > --------------------------------------------------------------------- > 1 3:57'58 32 17864 41943216 3805208 9103 audio > error sending SCSI command: Invalid argument > [and on the console] > (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 > (pass0:ahc0:0:4:0): Invalid field in parameter list > > (I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just > for fun, but they were invalid ops for this drive). In addition to trying cdda2wav, here's something else you can try in your tosharc: "SAF" "" "" 0x28 1 0x82 0 10 0 or: "SAF" "" "" 0x28 0 0x00 0 10 0 The first one is probably what you tried. The second one disables the mode select. It would be highly unusual if that drive didn't require a mode select. Every other drive that tosha supports that uses a standard read command needs a mode select. But, if your drive doesn't need a mode select, that might explain why dd worked. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:20:50 2000 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 4E70314EFC for ; Thu, 6 Jan 2000 18:20:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA14061; Thu, 6 Jan 2000 19:16:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA81656; Thu, 6 Jan 2000 19:16:03 -0700 (MST) Message-Id: <200001070216.TAA81656@harmony.village.org> To: Peter Jeremy Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: Steve Ames , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Jan 2000 10:16:25 +1100." <00Jan7.101628est.40323@border.alcanet.com.au> References: <00Jan7.101628est.40323@border.alcanet.com.au> <38746AEC.167EB0E7@elischer.org> <20000106094511.A30328@virtual-voodoo.com> Date: Thu, 06 Jan 2000 19:16:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00Jan7.101628est.40323@border.alcanet.com.au> Peter Jeremy writes: : Maybe I misunderstood Jordan's original announcement, but this was : also a surprise for me. Jordan originally stated that there'd be a : feature freeze from 15th December 1999. I got the impression that : this was going to be in effect for several months and would allow any : code updates, but prevent the introduction of new features. This : would then be followed by a _CODE_ freeze sometime in 2000Q1, leading : to 4.0-RELEASE late in 2000Q1. (My understanding of the difference is : that during the code freeze, only changes that demonstrably fix known : bugs, without deleterious side effects, are allowed). This was my understanding as well... Don't feel bad. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:21:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A09F214C24; Thu, 6 Jan 2000 18:21:04 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id UAA30607; Thu, 6 Jan 2000 20:28:05 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Thu, 6 Jan 2000 20:28:05 -0500 (EST) From: Adam To: "Karsten W. Rohrbach" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-Reply-To: <20000107020327.B68369@nacamar.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 believe the cdrdao port had the abilities and some of the code from paranoia in it. On Fri, 7 Jan 2000, Karsten W. Rohrbach wrote: >reading raw audio data off a cd with dd did never work for me... >anyway, it would be a good thing(TM) if there was a tool such as >cdparanoia under l*n*x that has all that fancy jitter and scratch >detection and removal (real goodd error correction) and this ones also >really fast (10x speed) when youre reading on a plextor drive (such as >my pxw4220t) or something else that has a native mode for extracting >audio. > >i think, theres a port of tosha available, but the last time i tried >this one it wouldnt work for me so i used the l*n*x box next to my >workstation... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:31:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from BSDpc.geek4food.org (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id 1F6BA15735 for ; Thu, 6 Jan 2000 18:31:49 -0800 (PST) (envelope-from andy@geek4food.org) Received: from mega.geek4food.org (mega.geek4food.org [192.168.1.57]) by BSDpc.geek4food.org (Postfix) with ESMTP id 46D5511B85 for ; Thu, 6 Jan 2000 18:26:34 -0800 (PST) Received: (from andy@localhost) by mega.geek4food.org (8.9.3/8.9.3) id SAA90858 for current@FreeBSD.ORG; Thu, 6 Jan 2000 18:26:30 -0800 (PST) (envelope-from andy@geek4food.org) Date: Thu, 6 Jan 2000 18:26:30 -0800 From: Andy Sparrow To: current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106182630.A90750@mega.geek4food.org> References: <5510.947202451@zippy.cdrom.com> <20000107020327.B68369@nacamar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000107020327.B68369@nacamar.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 02:03:29AM +0100, Karsten W. Rohrbach wrote: > detection and removal (real goodd error correction) and this ones also > really fast (10x speed) when youre reading on a plextor drive (such as > my pxw4220t) or something else that has a native mode for extracting > audio. One of the main reasons for springing the extra $$$ for a Plextor is that they (unlike most other CDDA implementations) actually got the firmware right: the beast does jitter correction in firmware, /and/ reads at near-data speeds whilst it does it. Many CD drives with buggy implementations jitter like crazy, and/or won't deliver CDDA much quicker than 1x, regardless of what the rated data speed is. http://www.tardis.ed.ac.uk/~psyche/cdda is a good resource for software links and reviews of various models of CD-ROM drives, if CD-DA ripping is of interest. Most good CDR drives also do a good job of CD-DA ripping (Philips CDD-2000, Toshiba CW-7502, from my direct experience), but you probably don't want to wear 'em out doing CD-DA - at least, I know I don't ;-). Personally, I found that tosha worked perfectly even on a Plextor 6x (the only Plextor with flawed firmware, this is pretty well-known). :-) Something like cdparanoia would probably be good for those cheap IDE CD-ROMs (I bought a couple of 16x Hitachi drives cheap - they don't do CD-DA very well at all). Cheers, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:38:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail9.fujitsu.co.jp (fgwmail9.fujitsu.co.jp [192.51.44.39]) by hub.freebsd.org (Postfix) with ESMTP id F3C8D14EFC; Thu, 6 Jan 2000 18:38:30 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from fgwmail5.fujitsu.co.jp by fgwmail9.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id LAA23083; Fri, 7 Jan 2000 11:33:59 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id LAA00196; Fri, 7 Jan 2000 11:27:23 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id LAA09039; Fri, 7 Jan 2000 11:27:22 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id LAA29025; Fri, 7 Jan 2000 11:27:21 +0900 (JST) To: joe@pavilion.net Cc: ck@arch.bellsouth.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-Reply-To: <20000107012037.C43650@florence.pavilion.net> References: <200001070032.QAA01812@mass.cdrom.com> <20000106193759.L1293@ns1.arch.bellsouth.net> <20000107012037.C43650@florence.pavilion.net> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000107112758F.shin@nd.net.fujitsu.co.jp> Date: Fri, 07 Jan 2000 11:27:58 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > genius% ping6 > usage: ping6 [-dfnqRrvwW] [-a [alsg]] [-b sockbufsiz] [-c count] [-I interface] > [-i wait] [-l preload] [-p pattern] [-s packetsize] > [-h hoplimit] host [hosts...] There are suggestions that ping6 should be integrated into ping for users could naturally use IPv6, so I would also like to do it before 15th, if there are time for it. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:49:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id F412515090; Thu, 6 Jan 2000 18:49:26 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA08235; Thu, 6 Jan 2000 17:50:27 -0800 (PST) Message-Id: <200001070150.RAA08235@implode.root.com> To: asami@FreeBSD.ORG (fifi - the hamster - asami) Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "06 Jan 2000 16:27:27 PST." From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Jan 2000 17:50:27 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * From: "Jordan K. Hubbard" > > * How do you think things "get included" in the OS? Do you think one > * just moves the KAME bits into a directory next to /usr/src, goes away > * for 24 hours to let them bits do their thing, and then comes back to > * find that nature has done the rest of the work? Sorry, it might work > * that way for hamsters but it doesn't work that way for code! Somebody > >dear mr. hubbard, > >please do not insult hamsters. it doesn't work that way for hamsters >either. we are fully aware of our surroundings and plan our lives >accordingly. in fact, satoshi is out picking oranges now so i have >full access to his computer. (ooohh nude hamster pics....) > >that said, i don't think you need to push back the release date. > >sincerely, >fifi > >p.s. pardon the lack of capital letters but my paws can't quite reach > the shift key and the alphabet keys at the same time.... If that is true, then how were you able to push the paren keys? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 18:49:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id AAE3E156A5; Thu, 6 Jan 2000 18:49:30 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA08297; Thu, 6 Jan 2000 18:03:22 -0800 (PST) Message-Id: <200001070203.SAA08297@implode.root.com> To: Mike Smith Cc: Christian Kuhtz , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: IPv6 (Re: 4.0 code freeze scheduled for Jan 15th) In-reply-to: Your message of "Thu, 06 Jan 2000 16:32:21 PST." <200001070032.QAA01812@mass.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Jan 2000 18:03:22 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Get IPv6 into the tree. Now. Thank you. > >I don't know quite what makes you think that we came down in the last >shower of rain, but has it ever occurred to you that we're not >_completely_ stupid? > >Do you _always_ assume that anyone other than yourself is a complete >moron? What makes you think that we don't want this code integrated, or >that we don't care about it? Have you bothered to actually read those >sides of this discussion that have come from the release engineering team? > >Wouldn't it be much more sensible of you to assume that there are good >and valid reasons for things being the way they are? Wouldn't it be much >more sensible of you to enquire as to what these reasons are, or perhaps >to even have paid attention to all the discussions and progress that have >gone on over the last few months (or even just stayed up to date in the >last week, where the whole matter has been discussed)? > >Or are you just too lazy? Too lazy to pay attention? Too lazy to >actually participate in this process? Too lazy to do anything other than >to wait until it's too late to do anything, and then randomly sling blame >around? What _do_ you think you achieve with this? How do you think >that insulting the people that are actually trying to do the work while >you sit on the sidelines is going to help the process? > >It's been said before, and I'm sure it'll be said again; if you can't >or won't offer support or assistance, the very least you can do is avoid >being actively destructive. Take a few moments to think about what it is >that you and we want to achieve, and how best to get there. And take a >hint; insulting us is not how to go about it. Mike, I think this is just a bit over the top and doesn't belong in our mailing lists. Please stop doing that. It really isn't fair to blame the FreeBSD developer base at large, and users as well for the slowness of the integration. The KAME team has never asked for integration help as far as I can recall and the primary reason for the delay was actually due to their attentions being focused on NetBSD (with the justification that they were about to freeze for a release). This all said, I don't think we are that far away from having a functional IPv6 implementation in FreeBSD. Most (all?) of the stack is there and what is needed now is the completion of support in the various system utilities. I think this part of the merger could be completed in an amount of time that is measured in weeks if the KAME developers can find the time to put into it right now. If not, then this whole discussion is a waste of bandwidth and everyone should just stop gritching over it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 19: 5:59 2000 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 B561215784; Thu, 6 Jan 2000 19:05:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA14078; Thu, 6 Jan 2000 19:20:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA81685; Thu, 6 Jan 2000 19:20:21 -0700 (MST) Message-Id: <200001070220.TAA81685@harmony.village.org> To: rohrbach@nacamar.net Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Cc: "Jordan K. Hubbard" , current@freebsd.org, phk@freebsd.org, gibbs@freebsd.org In-reply-to: Your message of "Fri, 07 Jan 2000 02:03:29 +0100." <20000107020327.B68369@nacamar.net> References: <20000107020327.B68369@nacamar.net> <5510.947202451@zippy.cdrom.com> Date: Thu, 06 Jan 2000 19:20:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000107020327.B68369@nacamar.net> "Karsten W. Rohrbach" writes: : i think, theres a port of tosha available, but the last time i tried : this one it wouldnt work for me so i used the l*n*x box next to my : workstation... Last time I tried Tosha it worked w/o a hitch for me and my 1x cdrom changer :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 19:12: 3 2000 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 740B214E1E; Thu, 6 Jan 2000 19:12:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA06145; Thu, 6 Jan 2000 17:28:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 17:30:35 MST." <20000106173035.A39324@panzer.kdm.org> Date: Thu, 06 Jan 2000 17:28:23 -0800 Message-ID: <6143.947208503@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You mean an Adaptec controller, right? Yes, I guess Adaptec did buy those guys. > Try tosha or cdda2wav and report back on whether or not it works. dd has > never been a supported way to read audio tracks, for the reasons outlined > above. It may be possible in some situations, but it was probably just a > fluke. root@zippy-> tosha -t 1 Device: /dev/cd0c -- "SAF" "CD-R8020" "1.20" track playing start end raw size mp3 size # of track number time sector sector in bytes 128 kbps frames type --------------------------------------------------------------------- 1 3:57'58 32 17864 41943216 3805208 9103 audio error sending SCSI command: Invalid argument [and on the console] (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (pass0:ahc0:0:4:0): Invalid field in parameter list (I've also tried read codes 0xD4 and 0xD8 in addition to 0x28, just for fun, but they were invalid ops for this drive). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 19:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 0DB5F14C16 for ; Thu, 6 Jan 2000 19:41:35 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id MAA13567 for ; Fri, 7 Jan 2000 12:36:51 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id MAA17466; Fri, 7 Jan 2000 12:36:51 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA02020 for ; Fri, 7 Jan 2000 12:36:50 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: [solicite review and confirmation of tcp for IPv6 patches] In-Reply-To: <20000103012633S.shin@nd.net.fujitsu.co.jp> References: <20000103012633S.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000107123727P.shin@nd.net.fujitsu.co.jp> Date: Fri, 07 Jan 2000 12:37:27 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I prepared tcp for IPv6 patches to the current. > I would like it to be reviewed and confirmed in many > environment before committing it, because I think updating tcp > code is very critical to system stability. > The patches are placed below. > > http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.20000103 > http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228 I found a bug at tcp_reass() and there might be a problem in e.g. large file transport case. (If tcp segments don't arrive in order it is not processed.) I fixed the bug and using the patched machine from remote. Now it seems to be working well. I also simplified the patch to nfs_socket.c. Updated patches are below. (patches to trpt is same as last version.) http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/kernel-tcp.20000107 http://paradise.kame.net/v6proxy/diana2/shin/work/freebsd/trpt.19991228 Please try these patches anyone interested. If it seems to be working well also in other environment, I'll commit them into the repository. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id E49F715087; Thu, 6 Jan 2000 20:00:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA12947; Thu, 6 Jan 2000 17:34:59 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA14368; Thu, 6 Jan 2000 17:34:59 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id RAA21645; Thu, 6 Jan 2000 17:33:46 -0800 (PST) Message-ID: <3875437F.329C8A15@softweyr.com> Date: Thu, 06 Jan 2000 18:38:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Darren Reed , Steve Ames , committers@freebsd.org, current@freebsd.org Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001062325.PAA00710@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > In some email I received from Steve Ames, sie wrote: > > > > > > *shudder* I really, really dislike the idea of -RELEASE actually being a > > > wide beta so that some code can get a workout. LAbel it beta and more people > > > will use it than currently do anyway. Any reason not to release and ship a > > > 4.0-beta? -CURRENT = development which scares people. Beta means most bugs > > > already ironed out and looking for test by larger audience. -RELEASE should > > > not be a beta, ever. > > > > What do you think 3.0-RELEASE was ? > > This seems to be how FreeBSD works now. > > It's how FreeBSD's users seem to want it to work, since they have utterly > refused to cooperate with any other arrangement. Those of us behind the > release-engineering effort have tried everything realistic that's been > suggested (and a great many other things); history speaks for itself as > to the results. Alpha, Beta, 4.0, are all just semantic labels anyhow. Every product, or at least every producer of software, develops their own terminology for how software is released to "customers." In the FreeBSD world, it has evolved that .0 means "ready to run, but not in production" and .1 or .2 means "now ready for prime time." While this may differ from whatever other system you are used to, it doesn't make it wrong, just different. Release 4.0 won't be a beta, it will just be a .0 release. Thank everyone that unlike most web browsers, we at least do >.0 releases. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:23:51 2000 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 35F31156ED for ; Thu, 6 Jan 2000 20:22:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA75303; Thu, 6 Jan 2000 20:05:00 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 20:05:00 -0800 (PST) From: Matthew Dillon Message-Id: <200001070405.UAA75303@apollo.backplane.com> To: current@FreeBSD.ORG Subject: New kernel no longer boots on one of my machines... ata, other problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well guys, I tried upgrading one of my older machines today to the latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). I've included the dmesg output from the (successfully booting) older kernel at the end. The newer kernel locks up in several ways: * First, it locks up with process 0 stuck in 'atawait' while trying to scan the CDRom on the second IDE bus. This is after it has successfully scanned the hard drive on the first IDE bus. * Second, if I remove the 'ata1' config entry it gets past the initial ata probe but then locks up in 'conifhk' which is in the run_interrupt_driven_config_hooks() procedure in kern/subr_autoconf.c It locks up here after printing 'waiting 15 seconds for SCSI devices to settle'. Several minutes later it's still waiting :-(. * If I remove the second ata device AND I remove the SCSI devices and controllers so it detects no SCSI devices, it gets all the way to where it says "Mounting root on wd0s4a", then gets an error 6, then says "Mounting root on wd0a", then just stops. Breaking into DDB and doing a ps shows 'init' and 'sh' both blocked in 'wait'. The hard drive appears to work -- panic does sync the disks. * The second time I did this when I CTL-ALT-ESC'd into DDB I suddenly got a whole bunch of console startup output. I 'cont'd from DDB, and nothing... CTL-ALT-ESC'd into DDB and got some more console output from the normal startup sequence before it gave me the DDB prompt. 'cont'd. nothing. I got it to the point where ping works but nothing else does. HEEEEELP! Whats happening!!! :-( :-( :-( At the moment I am stymied. I switched to a GENERIC kernel and got the same results, so it isn't anything weird that I have done in my own kernel config. I was hoping that someone would have an idea. -Matt Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Mon Nov 29 22:10:35 PST 1999 dillon@apollo.backplane.com:/FreeBSD/FreeBSD-4.x/src/sys/compile/ARCHIVE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 66751430 Hz CPU: Pentium/P54C (66.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping = 4 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 61698048 (60252K bytes) Preloaded elf kernel "kernel.bak" at 0xc0335000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ign0 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 vga-pci0: irq 10 at device 6.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 9 at device 12.0 on pci0 xl0: Ethernet address: 00:10:5a:e0:82:29 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ncr0: irq 11 at device 14.0 on pci0 devclass_alloc_unit: npx0 already exists, using next available unit number fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 12970MB (26563824 sectors), 26353 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (atapi): , removable, ovlap, dma, iordis wcd0: drive speed 2066KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA, packet track wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:wd0s4a Root mount failed: 6 Mounting root from ufs:wd0a link_elf: symbol splash_register undefined cd0 at ncr0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:26:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B8DD3157F4; Thu, 6 Jan 2000 20:26:13 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA41111; Thu, 6 Jan 2000 21:21:23 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 21:21:23 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106212123.B40879@panzer.kdm.org> References: <20000106191051.A40270@panzer.kdm.org> <6956.947217921@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6956.947217921@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 08:05:21PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 20:05:21 -0800, Jordan K. Hubbard wrote: > Also, I can now add that cdda2wav does work (hurrah), but it does yelp > that it can't read the CD TOC. Weird. What does cdda2wav identify the drive as? Can you send the output? (verbose, if there's a verbose switch) That may help determine what cdda2wav is doing that tosha isn't. > Of course, the mystery is that tosha no longer works yet was not > changed, nor was the ripit script I call tosha from, so something on > our side of the fence also moved with respect to this drive. > > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. tosha works fine for me (I've got a Plextor 12x CDROM drive). Have you recompiled tosha between the time it worked and the time it didn't? It could be the problem was introduced in tosha-0.6. (The previous version was tosha-0.5 with CAM patches.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:29:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7B6C61578E; Thu, 6 Jan 2000 20:29:27 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA40954; Thu, 6 Jan 2000 21:11:23 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 21:11:23 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106211123.A40879@panzer.kdm.org> References: <20000106191051.A40270@panzer.kdm.org> <6924.947217754@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6924.947217754@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 08:02:34PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 20:02:34 -0800, Jordan K. Hubbard wrote: > > In addition to trying cdda2wav, here's something else you can try in your > > tosharc: > > > > "SAF" "" "" 0x28 1 0x82 0 10 0 > > > > or: > > > > "SAF" "" "" 0x28 0 0x00 0 10 0 > > Yep, tried both - no go. > > The first produces: > > (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 > (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 > (pass0:ahc0:0:4:0): Invalid field in parameter list > > And the second: > > (pass0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 > (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0 > (pass0:ahc0:0:4:0): Illegal mode for this track > > Which is kind of interesting in that it means that the very first > command to the drive is going south, be it the mode select or (if > that's disabled) the read. I think what is actually going on is that it doesn't like the 0x82 density code that most other drives use. So that's what the first error message likely tells us. (the density is given in the mode select parameter list, thus the invalid field) The second error message likely means that it needs a mode select of some sort in order to function. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:32:18 2000 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 A3C1515253; Thu, 6 Jan 2000 20:32:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA07060; Thu, 6 Jan 2000 20:28:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 21:11:23 MST." <20000106211123.A40879@panzer.kdm.org> Date: Thu, 06 Jan 2000 20:28:40 -0800 Message-ID: <7058.947219320@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think what is actually going on is that it doesn't like the 0x82 density > code that most other drives use. So that's what the first error message > likely tells us. (the density is given in the mode select parameter list, > thus the invalid field) > > The second error message likely means that it needs a mode select of some > sort in order to function. Hmmm. That's another reasonable explanation for the behavior, yes. :) I'll try playing with different density codes, perhaps. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:43:51 2000 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 6E68B156AA; Thu, 6 Jan 2000 20:43:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA06958; Thu, 6 Jan 2000 20:05:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 19:10:51 MST." <20000106191051.A40270@panzer.kdm.org> Date: Thu, 06 Jan 2000 20:05:21 -0800 Message-ID: <6956.947217921@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also, I can now add that cdda2wav does work (hurrah), but it does yelp that it can't read the CD TOC. Of course, the mystery is that tosha no longer works yet was not changed, nor was the ripit script I call tosha from, so something on our side of the fence also moved with respect to this drive. Any other SCSI CD owners here currently using tosha? I'd be quite interested to know if this is drive-specific. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:43:54 2000 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 2ADE11522B; Thu, 6 Jan 2000 20:43:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA06926; Thu, 6 Jan 2000 20:02:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 19:10:51 MST." <20000106191051.A40270@panzer.kdm.org> Date: Thu, 06 Jan 2000 20:02:34 -0800 Message-ID: <6924.947217754@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In addition to trying cdda2wav, here's something else you can try in your > tosharc: > > "SAF" "" "" 0x28 1 0x82 0 10 0 > > or: > > "SAF" "" "" 0x28 0 0x00 0 10 0 Yep, tried both - no go. The first produces: (pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 c 0 (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (pass0:ahc0:0:4:0): Invalid field in parameter list And the second: (pass0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 20 0 0 a 0 (pass0:ahc0:0:4:0): ILLEGAL REQUEST asc:64,0 (pass0:ahc0:0:4:0): Illegal mode for this track Which is kind of interesting in that it means that the very first command to the drive is going south, be it the mode select or (if that's disabled) the read. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:43:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 015F015607; Thu, 6 Jan 2000 20:43:49 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA41242; Thu, 6 Jan 2000 21:31:35 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 21:31:34 -0700 From: "Kenneth D. Merry" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106213134.A41219@panzer.kdm.org> References: <20000106211123.A40879@panzer.kdm.org> <7058.947219320@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <7058.947219320@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 06, 2000 at 08:28:40PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 20:28:40 -0800, Jordan K. Hubbard wrote: > > I think what is actually going on is that it doesn't like the 0x82 density > > code that most other drives use. So that's what the first error message > > likely tells us. (the density is given in the mode select parameter list, > > thus the invalid field) > > > > The second error message likely means that it needs a mode select of some > > sort in order to function. > > Hmmm. That's another reasonable explanation for the behavior, yes. :) > I'll try playing with different density codes, perhaps. I think it's a 1 byte field, so you've got 256 possibilities. It may take a while. Another possibility is that this is a MMC compliant CD-R drive. cdda2wav can apparantly handle MMC drives. From the spec, MMC drives use a different read command that includes an "expected sector type", which you can set to CD-DA. Anyway, verbose output from cdda2wav might help me figure out whether that is indeed the case. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:53: 9 2000 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 3D8A81505F for ; Thu, 6 Jan 2000 20:53:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA78338; Thu, 6 Jan 2000 20:43:05 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 20:43:05 -0800 (PST) From: Matthew Dillon Message-Id: <200001070443.UAA78338@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : * First, it locks up with process 0 stuck in 'atawait' while ^^^^ I meant 'atacmd' here. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 20:59:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 7AB1114CD0 for ; Thu, 6 Jan 2000 20:59:27 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id OAA13025; Fri, 7 Jan 2000 14:54:14 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd012991; Fri Jan 7 14:54:04 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA07957; Fri, 7 Jan 2000 14:53:41 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id OAA07045; Fri, 7 Jan 2000 14:53:40 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id OAA13694; Fri, 7 Jan 2000 14:53:39 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200001070453.OAA13694@nymph.detir.qld.gov.au> To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Small fix to netstat argument processing References: <200001061006.UAA21698@nymph.detir.qld.gov.au> <20000106210255C.shin@nd.net.fujitsu.co.jp> In-Reply-To: <20000106210255C.shin@nd.net.fujitsu.co.jp> from Yoshinobu Inoue at "Thu, 06 Jan 2000 21:02:55 +0900" Date: Fri, 07 Jan 2000 14:53:39 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 6th January 2000, Yoshinobu Inoue wrote: >Does these patches fix your problem, or should another better >fix is desired? Please give me any opinions. It passes all my tests. Please commit it. Thank you! And earlier you wrote: >Because now there is interface statistics display mode, when, e.g. > > netstat -s -I bar0 -f inet6 > >is specified. (though this is inet6 only now.) I see where you are going now. The syntax of netstat, already complex, is becoming even more complex. More detail in the man page will be necessary soon. Also, the "iflag" variable might have too many uses now. But this can wait, now that the immediate difficulties have been resolved. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 21: 1:10 2000 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 1AE081522B for ; Thu, 6 Jan 2000 21:01:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA78510; Thu, 6 Jan 2000 20:57:16 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 20:57:16 -0800 (PST) From: Matthew Dillon Message-Id: <200001070457.UAA78510@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001070443.UAA78338@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :: * First, it locks up with process 0 stuck in 'atawait' while : ^^^^ : : I meant 'atacmd' here. : : -Matt From what I can tell so far, something during the kernel boot is disabling the timer interrupt. The ATA probe does a tsleep() which never times out. Output is queued to the console during the boot sequence which is never printed (until I CTL-ALT-ESC)... has someone messed with spl*()'s anywhere recently? -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 Jan 6 21:37:36 2000 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 82BD815253 for ; Thu, 6 Jan 2000 21:37:31 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id GAA60726; Fri, 7 Jan 2000 06:33:47 +0100 (CET) (envelope-from olli) Date: Fri, 7 Jan 2000 06:33:47 +0100 (CET) Message-Id: <200001070533.GAA60726@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? X-Newsgroups: list.freebsd-current In-Reply-To: <853ht9$td8$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Kenneth D. Merry wrote in list.freebsd-current: > Also, you might want to try mailing Oliver Fromme > (the author of tosha) and see if he > has any idea what it would take to get your drive to function. I'm reading this thread, and no, I have no idea. :-) To be honest, I've never heard about an "SAF" drive. If I had such a stubborn drive, I would start trying a bunch of "typical" parameter sets that are known to work with other drives, and then try to interpret the results. Maybe try to contact the vendor and ask for docs, but that's pretty much fruitless, as experience shows. If all else fails, make a brute-force attack on density codes... Jordan, if you can get that drive to work with tosha somehow, please let me know, so I ca add it to the regular tosha distribution. Regards Oliver PS: The email address that Ken mentioned isn't valid, please use . -- 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 Jan 6 21:45:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5E61A15553 for ; Thu, 6 Jan 2000 21:45:44 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA41986; Thu, 6 Jan 2000 22:42:48 -0700 (MST) (envelope-from ken) Date: Thu, 6 Jan 2000 22:42:48 -0700 From: "Kenneth D. Merry" To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Message-ID: <20000106224248.A41951@panzer.kdm.org> References: <853ht9$td8$1@atlantis.rz.tu-clausthal.de> <200001070533.GAA60726@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001070533.GAA60726@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Fri, Jan 07, 2000 at 06:33:47AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 06:33:47 +0100, Oliver Fromme wrote: > Kenneth D. Merry wrote in list.freebsd-current: > > Also, you might want to try mailing Oliver Fromme > > (the author of tosha) and see if he > > has any idea what it would take to get your drive to function. > > I'm reading this thread, and no, I have no idea. :-) > To be honest, I've never heard about an "SAF" drive. > > If I had such a stubborn drive, I would start trying a bunch > of "typical" parameter sets that are known to work with other > drives, and then try to interpret the results. Maybe try to > contact the vendor and ask for docs, but that's pretty much > fruitless, as experience shows. If all else fails, make a > brute-force attack on density codes... > > Jordan, if you can get that drive to work with tosha somehow, > please let me know, so I ca add it to the regular tosha > distribution. I suspect that it may be a MMC drive. I took a look at the spec, and the cdda2wav source, and I've got a patch that may do the trick. Once Jordan sends output from cdda2wav, I'll know more. > PS: The email address that Ken mentioned isn't valid, please > use . Then why are you still using it? This is from the headers on your message: From: Oliver Fromme Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 21:47:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id A837A1555B for ; Thu, 6 Jan 2000 21:46:44 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.218.93.188] helo=kan.ne.mediaone.net) by mx3.mail.ru with esmtp (Exim 3.02 #114) id 126RqK-0006d3-00; Fri, 07 Jan 2000 08:21:48 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id AAA01854; Fri, 7 Jan 2000 00:23:17 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <6956.947217921@zippy.cdrom.com> Date: Fri, 07 Jan 2000 00:23:17 -0500 (EST) From: "Alexander N. Kabaev" To: "Jordan K. Hubbard" Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have TOSHIBA DVD-ROM SD-M1201 1R08 on Adaptec 2440U2W and tosha works fine with it. I used to get the same error messages from tosha just a couple weeks ago. cdd2wav worked OK. I upgraded to the latest firmware on both the controller and the drive and error messages disappeared. Kernel and world cvsupped on on Jan 4. BTW, running dd on my DVD fails with the following error: # dd if=/dev/rcd0a bs=2k of=/dev/null dd: /dev/rcd0a: Invalid argument 0+0 records in 0+0 records out 0 bytes transferred in 0.001683 secs (0 bytes/sec) Jan 7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 Jan 7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): ILLEGAL REQUEST asc:64,0 Jan 7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): Illegal mode for this track Jan 7 00:04:51 kan /kernel: (cd0:ahc0:0:6:0): cddone: got error 0x16 back J Is that something to be expected? How to copy a complete CD-ROM image into ISO file then? On 07-Jan-00 Jordan K. Hubbard wrote: > > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22: 3:51 2000 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 83C6715085 for ; Thu, 6 Jan 2000 22:03:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA07658; Thu, 6 Jan 2000 22:03:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Fri, 07 Jan 2000 06:33:47 +0100." <200001070533.GAA60726@dorifer.heim3.tu-clausthal.de> Date: Thu, 06 Jan 2000 22:03:01 -0800 Message-ID: <7656.947224981@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm reading this thread, and no, I have no idea. :-) > To be honest, I've never heard about an "SAF" drive. It's a "Smart and Friendly CD-R8020", also sold as the "CD Rocket Recorder" here in the U.S. It does 20X reads, 8X writes and 4X re-writes. And no, I don't usually waste my CDR heads on reading audio data, but in this case it's a mid-tower case with lots of disks in it and I can only fit one CD drive in. :) > Jordan, if you can get that drive to work with tosha somehow, > please let me know, so I ca add it to the regular tosha > distribution. I'll certainly be happy to do that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22: 5:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id E560814D08; Thu, 6 Jan 2000 22:05:13 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id BAA75917; Fri, 7 Jan 2000 01:04:52 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001070604.BAA75917@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, phk@FreeBSD.ORG, gibbs@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? References: <6956.947217921@zippy.cdrom.com> In-reply-to: Your message of "Thu, 06 Jan 2000 20:05:21 PST." <6956.947217921@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 01:04:52 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. I've used tosha with a "TOSHIBA CD-ROM XM-6201TA 1037" SCSI drive to read audio data for subsequent mp3 conversion with no problems. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22:15:37 2000 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 D7C661555B for ; Thu, 6 Jan 2000 22:15:23 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id HAA63042; Fri, 7 Jan 2000 07:15:17 +0100 (CET) (envelope-from olli) Date: Fri, 7 Jan 2000 07:15:17 +0100 (CET) Message-Id: <200001070615.HAA63042@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives X-Newsgroups: list.freebsd-current In-Reply-To: <853vh6$15rc$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Alexander N. Kabaev wrote in list.freebsd-current: > Is that something to be expected? How to copy a complete CD-ROM image into ISO > file then? You can also use tosha to read a CD-ROM track to make an ISO image. It supports CD-ROM data tracks as well as audio and video (VCD) tracks. 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 Jan 6 22:17:35 2000 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 8958A15579 for ; Thu, 6 Jan 2000 22:17:28 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id HAA63193; Fri, 7 Jan 2000 07:17:23 +0100 (CET) (envelope-from olli) Date: Fri, 7 Jan 2000 07:17:23 +0100 (CET) Message-Id: <200001070617.HAA63193@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? X-Newsgroups: list.freebsd-current In-Reply-To: <853vel$15pd$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Kenneth D. Merry wrote in list.freebsd-current: > [...] >> PS: The email address that Ken mentioned isn't valid, please >> use . > > Then why are you still using it? This is from the headers on your message: > > From: Oliver Fromme I upgraded the hardware and OS of this box recently, and not everything is configured correctly yet (not enough time)... There _should_ be a valid Reply-To line in my email messages. 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 Jan 6 22:21: 9 2000 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 70019154F6 for ; Thu, 6 Jan 2000 22:20:57 -0800 (PST) (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.9.3) with ESMTP id WAA49348; Thu, 6 Jan 2000 22:19:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001070619.WAA49348@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives In-reply-to: Your message of "Fri, 07 Jan 2000 07:15:17 +0100." <200001070615.HAA63042@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 22:19:49 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG say do you know how to create an audio cd? I want to extract tracts from different audio cds and create my own audio cd. I have a Yamaha scsi cd writer. Tnks! -- 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 Jan 6 22:25:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id A77201552F for ; Thu, 6 Jan 2000 22:25:24 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA24812; Fri, 7 Jan 2000 16:55:06 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001070619.WAA49348@rah.star-gate.com> Date: Fri, 07 Jan 2000 16:55:05 +1030 (CST) From: "Daniel O'Connor" To: Amancio Hasty Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives Cc: freebsd-current@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG, Oliver Fromme Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-00 Amancio Hasty wrote: > say do you know how to create an audio cd? > I want to extract tracts from different audio cds and create my > own audio cd. I have a Yamaha scsi cd writer. Use a tool to rip the audio (tosha, cdd, cdda2wav, etc etc).. Get all the tracks you want. Then run cdrecord like so -> cdrecord -dev=x,y,z -speed=a -audio track1.wav track2.wav ... Easy! :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22:33:24 2000 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 9004315087 for ; Thu, 6 Jan 2000 22:33:15 -0800 (PST) (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.9.3) with ESMTP id WAA49458; Thu, 6 Jan 2000 22:32:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001070632.WAA49458@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG, Oliver Fromme Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives In-reply-to: Your message of "Fri, 07 Jan 2000 16:55:05 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Jan 2000 22:32:44 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Tnks for the tip! I just thought that I would need to add an audio intergap between tracks but hey if cdrecord can do it great! Tnks! -- 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 Jan 6 22:37:17 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B2F02155B4; Thu, 6 Jan 2000 22:36:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 924F11CD823 for ; Thu, 6 Jan 2000 22:36:43 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 6 Jan 2000 22:36:43 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: HEADS UP: SHA-1 password support gone 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 As warned yesterday, I've just removed the ability for libcrypt to understand SHA-1 passwords. This was present but undocumented in the tree for the past few months and was removed so it can be reimplemented properly as part of a revamped libcrypt at a later date. Anyone who was actually making use of the feature will have to update their passwords back to MD5 before they reinstall the library. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22:44: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (Postfix) with ESMTP id D7EAD14CCD for ; Thu, 6 Jan 2000 22:43:56 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.3/8.9.3) id HAA98309; Fri, 7 Jan 2000 07:43:46 +0100 (CET) Date: Fri, 7 Jan 2000 07:43:46 +0100 (CET) Message-Id: <200001070643.HAA98309@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives From: Ronald Kuehn X-Newsreader: NN version 6.5.0 CURRENT #120 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > Hi > Tnks for the tip! > I just thought that I would need to add an audio intergap between tracks > but hey if cdrecord can do it great! Hi, you can also use cdrdao (ports/audio/cdrdao) which has support for DAO (control over gaps between tracks). The xcdrdao tool provides a graphical user interface too. Bye, Ronald -- Give a man a fish, and you feed him for a day. Tell him he should learn how to fish himself, and he'll hate you for a lifetime. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22:52:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9C99C155B5 for ; Thu, 6 Jan 2000 22:52:39 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA25156; Fri, 7 Jan 2000 17:19:38 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001070632.WAA49458@rah.star-gate.com> Date: Fri, 07 Jan 2000 17:19:38 +1030 (CST) From: "Daniel O'Connor" To: Amancio Hasty Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives Cc: Oliver Fromme Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-00 Amancio Hasty wrote: > I just thought that I would need to add an audio intergap between > tracks > but hey if cdrecord can do it great! Well, if you are burning in Track-At-Once mode then there is a 2 second gap between the tracks (and you can't do anything about it). To remove or change the intertrack gaps you need to burn in Disk-At-Once mode.. cdrdao and the newer versions of cdrecord support DAO. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 22:55:20 2000 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 BA903150C6 for ; Thu, 6 Jan 2000 22:55:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA82937; Thu, 6 Jan 2000 22:55:12 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 22:55:12 -0800 (PST) From: Matthew Dillon Message-Id: <200001070655.WAA82937@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other problems) References: <200001070443.UAA78338@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : From what I can tell so far, something during the kernel boot is : disabling the timer interrupt. The ATA probe does a tsleep() which : never times out. Output is queued to the console during the boot : sequence which is never printed (until I CTL-ALT-ESC)... : : has someone messed with spl*()'s anywhere recently? : Another datapoint: When I DDB the machine and 'print *ticks', it comes up 0, and when I panic it it says "uptime 0s". If I remove the 'ata' drivers I get the bootconf screen since there is no root - but *ticks is incrementing! If I add 'ata' back in, buckus (DDB> print *ticks yields 0, machine is screwed up). When I remove 'ata' and enable the 'wd' driver, everything works normally. The machine boots up fine. I think there's something weird going on with the ata driver but I'll be damned if I know what it is. As much as I like the idea of updating the wd driver, I think removing it as the default is a big mistake. The ATA driver is *NOT* ready for prime time yet. It certainly isn't ready for the warning that 'config' gives you if you have 'wd' configured --- that warning is what caused me not to even *try* to go back to the 'wd' device for three or four hours. -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 Jan 6 23:34:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AD3F9155E9 for ; Thu, 6 Jan 2000 23:34:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA17640; Fri, 7 Jan 2000 08:34:02 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001070734.IAA17640@freebsd.dk> Subject: Re: HEADS UP! wormcontrol and sys/dvdio.h users In-Reply-To: <20000107002820.A34994@cichlids.cichlids.com> from Alexander Langer at "Jan 7, 2000 00:28:20 am" To: alex@big.endian.de (Alexander Langer) Date: Fri, 7 Jan 2000 08:34:02 +0100 (CET) Cc: 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 Alexander Langer wrote: > Thus spake Soren Schmidt (sos@freebsd.dk): > > > The DVD ioctl's has changed numbers, so those using that > > should recompile thier apps. > > Wormcontrol and related files will be removed soon. > > I saw changes for the ioctl for the ata*, but not for the wd* > stuff. > > Could wormcontrol at least stay as the wd* drivers stay? Sure, I dont se why not, but it adds to the confusion... > ata* doesn't work for me at the moment, thus I'm using the wd drivers. What is your problem ?? > Or am I wrong? Can I use burncd with the wd drivers? No. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 6 23:46:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 12C5D1522B for ; Thu, 6 Jan 2000 23:46:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA20488; Fri, 7 Jan 2000 08:46:09 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001070746.IAA20488@freebsd.dk> Subject: Re: Found it --- 'ata' driver screwing up the machine (was Re: New kernel no longer boots on one of my machines... ata, other proble In-Reply-To: <200001070655.WAA82937@apollo.backplane.com> from Matthew Dillon at "Jan 6, 2000 10:55:12 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 7 Jan 2000 08:46:09 +0100 (CET) Cc: 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 Matthew Dillon wrote: > > : From what I can tell so far, something during the kernel boot is > : disabling the timer interrupt. The ATA probe does a tsleep() which > : never times out. Output is queued to the console during the boot > : sequence which is never printed (until I CTL-ALT-ESC)... > : > : has someone messed with spl*()'s anywhere recently? > > Another datapoint: When I DDB the machine and 'print *ticks', > it comes up 0, and when I panic it it says "uptime 0s". > > If I remove the 'ata' drivers I get the bootconf screen > since there is no root - but *ticks is incrementing! > > If I add 'ata' back in, buckus (DDB> print *ticks yields 0, machine > is screwed up). > > When I remove 'ata' and enable the 'wd' driver, everything works > normally. The machine boots up fine. Thats to be expected, the wd driver doesn't use config_intrhook_establish() to hook in the probes when interrupts should be running. From your previous mail it looked like you had both ATA & SCSI in there, then tried without SCSI and it kindof worked. The error 6 problem has been up here before, but I dont remember the solution off hand, but you should use /dev/ad* entries in you fstab, and have MAKEDEV'd them fairly resently, new bootblocks and loader are also a must. My best guess is that config_intrhook_establish() screws up something when more than one consumer uses it to hook into the boot process... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 0:13:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 787B314D10 for ; Fri, 7 Jan 2000 00:13:35 -0800 (PST) (envelope-from Etienne.DeBruin@KryptoKom.DE) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.3) id JAA06298 for ; Fri, 7 Jan 2000 09:12:26 +0100 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa06296; Fri Jan 07 09:12:16 2000 Received: from nt-notes.kryptokom.de (nt-notes.kryptokom.de [192.168.6.247]) by cirdan.kryptokom.de (8.9.3/8.9.3) with SMTP id JAA19244 for ; Fri, 7 Jan 2000 09:12:16 +0100 Received: by nt-notes.kryptokom.de(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id C125685F.002D36D4 ; Fri, 7 Jan 2000 09:13:51 +0100 X-Lotus-FromDomain: UTIMACO From: "Etienne De Bruin" To: current@freebsd.org Message-ID: Date: Fri, 7 Jan 2000 09:13:46 +0100 Subject: Compiling 3.4 Problems Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker complains about not finding the following symbols: s_strlen s_strcmp vis_str short2str This all takes place during my attempt to do a make buildworld with the 3_4_0_RELEASE sources. Regards eT P.S. please reply to me as I am not subscribed to -current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 0:26: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5664C155E6 for ; Fri, 7 Jan 2000 00:25:58 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA29548; Fri, 7 Jan 2000 09:24:48 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001070824.JAA29548@freebsd.dk> Subject: Re: ATA driver problems In-Reply-To: <00Jan7.100119est.40323@border.alcanet.com.au> from Peter Jeremy at "Jan 7, 2000 10:01:19 am" To: peter.jeremy@alcatel.com.au (Peter Jeremy) Date: Fri, 7 Jan 2000 09:24:48 +0100 (CET) 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 Peter Jeremy wrote: > On 2000-Jan-06 10:38:51 +1100, I wrote: > ["dd if=/dev/rad0c of=/dev/null bs=64k" dies with an error] > > I did some poking around and found that there are two bugs which > conspire together to cause this: > 1) diskstrategy() does not detect dscheck() returning EOF, instead > passing a zero-length request to the underlying driver. > 2) The ata-disk driver doesn't check for (and ignore) zero-length > requests, instead passing them onto the disk. > > See kern/15956 for details and patches. Thanks! I'll take a look at it! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 0:41:29 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2544714A1D; Fri, 7 Jan 2000 00:41:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 161BA1CD823; Fri, 7 Jan 2000 00:41:28 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 7 Jan 2000 00:41:28 -0800 (PST) From: Kris Kennaway To: Etienne De Bruin Cc: current@freebsd.org Subject: Re: Compiling 3.4 Problems 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 Fri, 7 Jan 2000, Etienne De Bruin wrote: > When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, > the linker complains about not finding the following symbols: And this has exactly what to do with FreeBSD 4.0-CURRENT? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 0:47:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4333114EB1 for ; Fri, 7 Jan 2000 00:47:12 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA21186 for ; Fri, 7 Jan 2000 00:47:12 -0800 Date: Fri, 7 Jan 2000 00:47:11 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: installing over the wire with a tulip card... 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 Umm- I know I've done this before, but maybe this is something stupid I've forgotten.... I went home to my shiny new 400Mhz intel with the 40GB IBM drive in hand.. I'd pulled a couple of the 4.0 snapshot floppy sets off off current.freebsd.org... boot the floppies- they see the de0 card I have in the probe messages (which is connected to the DSL modem ...), but only present sl0/ppp0 as network install media. What have I forgotten that makes me a bonehead here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 1:10:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id B4C1314F6A for ; Fri, 7 Jan 2000 01:10:34 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id EAA33856; Fri, 7 Jan 2000 04:10:29 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Fri, 7 Jan 2000 04:10:29 -0500 (EST) From: Adam To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... 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 Is this the pnp-os switch in bios thing? On Fri, 7 Jan 2000, Matthew Jacob wrote: > >Umm- I know I've done this before, but maybe this is something stupid I've >forgotten.... I went home to my shiny new 400Mhz intel with the 40GB IBM >drive in hand.. I'd pulled a couple of the 4.0 snapshot floppy sets off >off current.freebsd.org... boot the floppies- they see the de0 card I have >in the probe messages (which is connected to the DSL modem ...), but only >present sl0/ppp0 as network install media. > >What have I forgotten that makes me a bonehead here? > > > > > > > >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 Jan 7 1:22:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id B27FF14F6A for ; Fri, 7 Jan 2000 01:22:11 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id KAA03892; Fri, 7 Jan 2000 10:22:37 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001070922.KAA03892@info.iet.unipi.it> Subject: ipfw optimizations To: current@freebsd.org Date: Fri, 7 Jan 2000 10:22:34 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i am looking at (minor) optimizations of the ipfw code in order to reduce the running time in the common cases. I have a few ideas (mostly along the lines of optimizing for the most commonly-used rules). An obvious candidate is the 'match all' rule (all from any to any), but can people suggest other common usage of rules in ipfw ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 1:49: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 5401014F09; Fri, 7 Jan 2000 01:49:03 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.241]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA39F6; Fri, 7 Jan 2000 10:49:00 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA50834; Fri, 7 Jan 2000 10:33:31 +0100 (CET) (envelope-from asmodai) Date: Fri, 7 Jan 2000 10:33:30 +0100 From: Jeroen Ruigrok/Asmodai To: Poul-Henning Kamp Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000107103330.A44355@daemon.ninth-circle.org> References: <20000106152026.A98222@virtual-voodoo.com> <670.947193259@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <670.947193259@critter.freebsd.dk>; from phk@critter.freebsd.dk on Thu, Jan 06, 2000 at 10:14:19PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000107 00:01], Poul-Henning Kamp (phk@critter.freebsd.dk) wrote: >In message <20000106152026.A98222@virtual-voodoo.com>, Steve Ames writes: > >>> On the other hand, there are *plenty* of things already in 4.0 that really >>> need to get out there and get a workout by a larger audience. >>> Delaying *them* is a big mistake. >> >>*shudder* I really, really dislike the idea of -RELEASE actually being a >>wide beta so that some code can get a workout. > >Who said anything about -RELEASE being a beta ? Some parts of a release >will always be new, but the majority of it is the same code we released >as 3.X, 2.X and even 1.X. > >We need for people to stop thinking of FreeBSD as commercial software >which comes in "natural number" style enumerable packets. While I agree with the sentiment Poul-Henning, the fact that Walnut Creek actually packages a given CVS tag as being the 4.0-RELEASE or whatever as a CD-ROM product gives it a commercial taste, no denying that. >FreeBSD style is "real number", it is a continuously evolving >quantity which every now and then passes a natural number on the >way to infinity. > >We can now spot a milestone called 4.0 and that's very nice, but we >are not going to stop, because the road goes on past 4.0. I think everyone knows that and acknowledges that, but the only thing I tasted from the multitude of mails I just read and evaluated was that people are satisfied with 4.0, but just want IPv6 support to be there, in it's most finished state as possible, and not some half-rushed thinghy which is there, but which is unusable. I think that that is only fair. BUT! Given Shin's RFC on his KAME patches and the answers he got, it almost looks like I was one of the very, very few to actually review his patches (until I got sick and all that). From those demanding IPv6 support in FreeBSD I have yet to see active testing and feedback to Shin. It seems people think the developers are here to do everything. Well, this is your wake-up call guys, it doesn't work that way. We only have the ability to use CVS on the sourcetree directly and we will do a lot of stuff out of ourselves, but we need the community to test, tinker and blow-up stuff and then report this back to the community with general ideas of how and what if you are not that much of a coder, or with patches if you can whoop them up. FreeBSD's Quality Assurance is something in which we all take place. Not just Walnut Creek or any of the committers. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project ...fools rush in where Daemons fear to tread. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 2:28:39 2000 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 AD11F14C45; Fri, 7 Jan 2000 02:28:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA03379; Fri, 7 Jan 2000 11:28:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-reply-to: Your message of "Thu, 06 Jan 2000 16:02:14 PST." Date: Fri, 07 Jan 2000 11:28:16 +0100 Message-ID: <3377.947240896@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthe w Jacob writes: > >Hmm! Better hold the 4.0 Code Freeze until this sorts out! "No" -- 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 Jan 7 3:22:21 2000 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 0754F155D9 for ; Fri, 7 Jan 2000 03:22:19 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Jan 2000 11:22:17 +0000 (GMT) To: current@freebsd.org Subject: Lint still broken in -current (due to cpp). X-Request-Do: Date: Fri, 07 Jan 2000 11:22:17 +0000 From: David Malone Message-ID: <200001071122.aa81066@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried lint again since David O'Brien committed the new /usr/bin/cpp, but it turns out that lint is hardwried to use /usr/libexec/cpp. I changed it to use /usr/bin/cpp, and it works, but gives some error messages. Is this still on the list of things to fix, or should I get more details and send-pr? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 3:30: 8 2000 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 6331615678 for ; Fri, 7 Jan 2000 03:30:01 -0800 (PST) (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.11 #1) id 126XaB-0003Uc-00; Fri, 07 Jan 2000 13:29:27 +0200 From: Sheldon Hearn To: David Malone Cc: current@FreeBSD.ORG Subject: Re: Lint still broken in -current (due to cpp). In-reply-to: Your message of "Fri, 07 Jan 2000 11:22:17 GMT." <200001071122.aa81066@salmon.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <13427.947244565.0@axl.noc.iafrica.com> Date: Fri, 07 Jan 2000 13:29:27 +0200 Message-ID: <13429.947244567@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13427.947244565.1@axl.noc.iafrica.com> On Fri, 07 Jan 2000 11:22:17 GMT, David Malone wrote: > I tried lint again since David O'Brien committed the new /usr/bin/cpp, > but it turns out that lint is hardwried to use /usr/libexec/cpp. > I changed it to use /usr/bin/cpp, and it works, but gives some > error messages. I submitted a patch on the cvs-all list yesterday. No feedback yet. Ciao, Sheldon. ------- =_aaaaaaaaaa0 Content-Type: message/rfc822 Content-ID: <13427.947244565.2@axl.noc.iafrica.com> From: Sheldon Hearn To: "David E. O'Brien" cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin Makefile src/usr.bin/cpp Makefile cpp.notraditional.sh cpp.sh src/gnu/usr.bin/cc Makefile src/gnu/usr.bin/cc/cpp Makefile In-reply-to: Your message of "Mon, 03 Jan 2000 19:48:09 PST." <200001040348.TAA76858@freefall.freebsd.org> Date: Thu, 06 Jan 2000 16:46:31 +0200 Message-ID: <2295.947169991@axl.noc.iafrica.com> Sender: sheldonh@axl.noc.iafrica.com On Mon, 03 Jan 2000 19:48:09 PST, "David E. O'Brien" wrote: > Modified files: > usr.bin Makefile > gnu/usr.bin/cc Makefile > gnu/usr.bin/cc/cpp Makefile > Removed files: > usr.bin/cpp Makefile cpp.notraditional.sh cpp.sh > Log: > Turn on a new /usr/bin/cpp that is a true binary rather than a shell script > wrapper. /usr/bin/cpp knows about all the GCC predefined symbols and has > the functionality of the previous EGCS 1.1.2 /usr/libexec/cpp. I think lint(1) might work with this given the following small patch. Ciao, Sheldon. Index: xlint.c =================================================================== RCS file: /home/ncvs/src/usr.bin/xlint/xlint/xlint.c,v retrieving revision 1.7 diff -u -d -r1.7 xlint.c --- xlint.c 1999/01/25 11:25:24 1.7 +++ xlint.c 2000/01/06 14:03:29 @@ -321,7 +321,6 @@ libsrchpath = xcalloc(1, sizeof (char *)); appcstrg(&cppflags, "-lang-c"); - appcstrg(&cppflags, "-undef"); appcstrg(&cppflags, "-$"); appcstrg(&cppflags, "-C"); appcstrg(&cppflags, "-Wcomment"); ------- =_aaaaaaaaaa0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 3:45:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 4881B14E1F for ; Fri, 7 Jan 2000 03:45:20 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA08747; Fri, 7 Jan 2000 12:45:12 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: <20000106190528.F1293@ns1.arch.bellsouth.net> Date: Fri, 7 Jan 2000 11:37:10 +0100 To: Randy Bush , Christian Kuhtz From: Brad Knowles Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: FreeBSD Current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:14 PM -0800 2000/1/6, Randy Bush wrote: > my point is that we can only wait politely and appreciatively for the kame > folk to continue their work to a point where it is more fully rounded. > until then, we should not forget that other features are also driving the > 4.0 release train. I'd like to point out that if full IPv6 or IPSec support isn't ready for us within this timeframe, I highly doubt that it's going to be ready for anyone else in that same timeframe. On that basis, if anyone else ships with any support for IPv6 or IPSec, it's likely to be incomplete, buggy, and probably cause more problems than it's worth. If there is not even a snowball's chance in Hell that these things will be ready in the timeframe we're going to do 4.0-RELEASE in, then we should go ahead and not wait for them, and instead integrate them in under 4.1-RELEASE, or whenever they're actually ready. If there is something that kinda, semi, sorta works today, then it should either be a port or you should at least be able to get the source and put it on the system and get it to compile and install yourself, right? How is this any different than if we ship sendmail 8.9.3 as the default MTA today, but if you want to go get and use postfix instead, you're welcome to do so? -- 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 Fri Jan 7 4:12:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as1-008.rp-plus.de [149.221.236.8]) by hub.freebsd.org (Postfix) with ESMTP id 3D60315611 for ; Fri, 7 Jan 2000 04:12:28 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 16E22AB92; Fri, 7 Jan 2000 12:09:36 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA01209; Fri, 7 Jan 2000 12:09:33 +0100 (CET) (envelope-from alex) Date: Fri, 7 Jan 2000 12:09:33 +0100 From: Alexander Langer To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: HEADS UP! wormcontrol and sys/dvdio.h users Message-ID: <20000107120933.B1123@cichlids.cichlids.com> Mail-Followup-To: Soren Schmidt , current@FreeBSD.ORG References: <20000107002820.A34994@cichlids.cichlids.com> <200001070734.IAA17640@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001070734.IAA17640@freebsd.dk>; from sos@freebsd.dk on Fri, Jan 07, 2000 at 08:34:02AM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Soren Schmidt (sos@freebsd.dk): > > Could wormcontrol at least stay as the wd* drivers stay? > Sure, I dont se why not, but it adds to the confusion... ok. nice. > > ata* doesn't work for me at the moment, thus I'm using the wd drivers. > What is your problem ?? I posted this to the -current ml 3 weeks ago, when I wanted to switch. See the "ata: Mount root failure: 6"-thread. I just don't know, what's wrong. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:28:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 42176154B3 for ; Fri, 7 Jan 2000 04:28:49 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA47370; Fri, 7 Jan 2000 13:28:45 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Pascal Hofstee Cc: freebsd-current@FreeBSD.ORG Subject: Re: GDB Problems ! References: <20000106120506.A31489@shadowmere.student.utwente.nl> From: Dag-Erling Smorgrav Date: 07 Jan 2000 13:28:44 +0100 In-Reply-To: Pascal Hofstee's message of "Thu, 6 Jan 2000 12:05:06 +0100" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pascal Hofstee writes: > just noticed this again. And considering 4.0 is coming up soon, I really > Compiling this program with -ggdb will give normal results (a list of i = > 0, upto i = 9). However when running the program through gdb Every Value > you can print is completely Bogus, which makes debugging impossible. For the record, I'm seeing the same problem. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:38:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 981A215611 for ; Fri, 7 Jan 2000 04:38:54 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id HAA00479; Fri, 7 Jan 2000 07:38:16 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5683.947203693@zippy.cdrom.com> Date: Fri, 07 Jan 2000 07:38:12 -0500 (EST) From: will andrews To: "Jordan K. Hubbard" Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: current@FreeBSD.ORG, Peter Jeremy , mjacob@feral.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-00 Jordan K. Hubbard wrote: > It's a feature freeze, sorry. I still expect the loose-ends that are > in place as of that date to be tied up afterwards. Doesn't this statement make the entire thread about IPv6 + PC-Card support entirely moot? Feature freezes don't mean we can't improve those two areas, right? Right? :-) If so, the entire thread could die right about now and I'd be happy. :) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:45:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 40EF715667 for ; Fri, 7 Jan 2000 04:45:28 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id MAA02298; Fri, 7 Jan 2000 12:45:25 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma002295; Fri, 7 Jan 00 12:45:00 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id XAA05570; Fri, 7 Jan 2000 23:44:59 +1100 (EST) From: Darren Reed Message-Id: <200001071244.XAA05570@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: randy@psg.com (Randy Bush) Date: Fri, 7 Jan 100 23:44:59 +1100 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Randy Bush" at Jan 6, 0 03:41:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Randy Bush, sie wrote: > > > 4.0-RELEASE sounds like it will start becoming available at about the same > > time as other OS's make new releases *with* IPv6/IPSec. You work it out > > whether or not FreeBSD will win or lose from those two being there or not > > there. > > what if the choice is > o release at the same time with lots-o-features but not all of v6 > o release _considerably later_ with all of v6, well most of it? > > where's your competitive advanatge in the latter? You don't have to re-release the same year pushing IPv6. Some have suggested 4.1 for IPv6 - bah. That'd be like how RedHat tried to make a big deal out of 6.y (see what I mean ?) vs someone else's new X. Then again, it seems FreeBSD releases are driven by marchitecture rather than architecture. mmm, theregister Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:47: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id B2BDD15627; Fri, 7 Jan 2000 04:46:57 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id MAA02304; Fri, 7 Jan 2000 12:46:55 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma002301; Fri, 7 Jan 00 12:46:52 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id XAA05593; Fri, 7 Jan 2000 23:46:50 +1100 (EST) From: Darren Reed Message-Id: <200001071246.XAA05593@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: imp@village.org (Warner Losh) Date: Fri, 7 Jan 100 23:46:49 +1100 (EST) Cc: joe@pavilion.net, darrenr@reed.wattle.id.au, dillon@apollo.backplane.com, committers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <200001062246.PAA80310@harmony.village.org> from "Warner Losh" at Jan 6, 0 03:46:22 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Warner Losh, sie wrote: > > In message <20000106212050.D95011@florence.pavilion.net> Josef Karthauser writes: > : My 3c589d works just fine now, along with suspend/resume :) (under 4.0). > > The issue with the 3c589d is with its speed. It is falling back to > the timeout routine to send data rather than getting an interrupt when > the tx has happened (or something like this, I'm reporting second hand > stuff). Whatever it is, results in ping times being 1000ms then 10ms then 1000ms then 10ms...when it responds. i.e. it's a mistake to use FreeBSD 3.x with the 3c589d. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:47:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from onizuka.vmunix.org (onizuka.vmunix.org [194.221.152.19]) by hub.freebsd.org (Postfix) with ESMTP id 7AE3B15901 for ; Fri, 7 Jan 2000 04:47:16 -0800 (PST) (envelope-from torstenb@vmunix.org) Received: from localhost (1276 bytes) by onizuka.vmunix.org via sendmail with stdio (sender: ) (ident using unix) id for ; Fri, 7 Jan 2000 13:48:17 +0100 (CET) Message-Id: Date: Fri, 7 Jan 2000 13:48:17 +0100 (CET) To: patrick@mindstep.com Cc: freebsd-current@freebsd.org From: torstenb@FreeBSD.org Reply-To: torstenb@vmunix.org Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001060927.UAA03779@avalon.reed.wattle.id.au> <006001bf586a$409b4b00$c80aa8c0@local.mindstep.com> X-Newsreader: NN version 6.5.3 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current patrick@mindstep.com wrote: >Maybe I am wrong, but it seems to me that there is already quite a bit of >IPv6 and IPSec stuff in the tree. Most of the kernel stuff is there (albeit >seriously lacking documentation). To me this is not *too* critical right >now. I see the point for the research community though. It's not just the research community. RIPE, ARIN and APNIC assign "official" (ie. non 6bone) sTLA space. I've spoken to many people and the demand for IPv6 grows. The only limiting factor is the implementation. Someone already mentioned in this thread that Sun will release SunOS 5.8/Solaris 8 with IPv6 (it's in beta at the moment). I strongly suggest to not release 4.0 till the IPv6 import has been finished. Beside the need for IPv6 it would be wrong to ship a release with a half- complete implementation. my 0.02 (euro cents of course ;-) -tb (2001:0650::/35) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:51:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7EE3714E33 for ; Fri, 7 Jan 2000 04:50:52 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA89622; Fri, 7 Jan 2000 13:50:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001071250.NAA89622@freebsd.dk> Subject: Re: HEADS UP! wormcontrol and sys/dvdio.h users In-Reply-To: <20000107120933.B1123@cichlids.cichlids.com> from Alexander Langer at "Jan 7, 2000 12:09:33 pm" To: alex@big.endian.de (Alexander Langer) Date: Fri, 7 Jan 2000 13:50:34 +0100 (CET) Cc: 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 Alexander Langer wrote: > > > ata* doesn't work for me at the moment, thus I'm using the wd drivers. > > What is your problem ?? > > I posted this to the -current ml 3 weeks ago, when I wanted to switch. > See the "ata: Mount root failure: 6"-thread. Hmm, that one, I thought (wrongly) that it got solved. Seems to me to be a bootblock/loader/fstab/MAKEDEV inconsistency somehow. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 4:53:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from darren2.lnk.telstra.net (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 73964155E6; Fri, 7 Jan 2000 04:53:03 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by darren2.lnk.telstra.net (8.9.1/8.8.7) id MAA02334; Fri, 7 Jan 2000 12:52:55 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V2.1) id xma002332; Fri, 7 Jan 00 12:52:36 GMT Received: (from darrenr@localhost) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) id XAA05648; Fri, 7 Jan 2000 23:52:34 +1100 (EST) From: Darren Reed Message-Id: <200001071252.XAA05648@avalon.reed.wattle.id.au> Subject: Re: 4.0 code freeze scheduled for Jan 15th To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 7 Jan 100 23:52:34 +1100 (EST) Cc: steve@virtual-voodoo.com, dillon@apollo.backplane.com, scanner@jurai.net, darrenr@reed.wattle.id.au, shin@nd.net.fujitsu.co.jp, louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org In-Reply-To: <670.947193259@critter.freebsd.dk> from "Poul-Henning Kamp" at Jan 6, 0 10:14:19 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Poul-Henning Kamp, sie wrote: [...] > In the meantime please enjoy: > > NTFS filesytem > > Netware support > > Jail facility > > Tons of new device drivers > > Netgraph > > etc, etc > > Isn't that just that very incomplete list worth a release ? In light of IPv6 missing, at the start of the 21st century, when just about every other major OS is getting ready to include it in their next release ? I'd say no. btw, Apple have announced IPv6 support in MacOS-X. Anyway, I'm now sorry I brought this issue up. Maybe I should have stayed quiet and not gotten people worked up about this and let FreeBSD go ahead and release 4.0 without IPv6. At last then the other BSD's might have been able to grab some market share. Like I said in a post elsewhere, the people driving FreeBSD seem more interested in goals other than those which are significant milestones for FreeBSD and the Internet. Apologies, Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 5: 5:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 5AD0215774 for ; Fri, 7 Jan 2000 05:05:10 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 67262 invoked by uid 1001); 7 Jan 2000 13:05:05 +0000 (GMT) To: darrenr@reed.wattle.id.au Cc: imp@village.org, joe@pavilion.net, dillon@apollo.backplane.com, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 7 Jan 100 23:46:49 +1100 (EST)" References: <200001071246.XAA05593@avalon.reed.wattle.id.au> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 07 Jan 2000 14:05:05 +0100 Message-ID: <67260.947250305@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Whatever it is, results in ping times being 1000ms then 10ms then 1000ms > then 10ms...when it responds. > > i.e. it's a mistake to use FreeBSD 3.x with the 3c589d. FWIW, I'm using the 3c589d with 3.2-STABLE + PAO, and it's working just fine. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 5:10: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id EB0B615704 for ; Fri, 7 Jan 2000 05:09:56 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id OAA50974; Fri, 7 Jan 2000 14:09:47 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) X-Authentication-Warning: jfh00.fernuni-hagen.de: jfh set sender to fritz.heinrichmeyer@fernuni-hagen.de using -f To: freebsd-current@freebsd.org Subject: some problem with atapi-all.c From: Fritz Heinrichmeyer Date: 07 Jan 2000 14:09:46 +0100 Message-ID: Lines: 10 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.2 (Millenium) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried the ATA_ENABLE_ATAPI_DMA option, it gave: ../../dev/ata/atapi-all.c: In function `atapi_attach': ../../dev/ata/atapi-all.c:150: syntax error before `)' -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 5:16:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1766214F91 for ; Fri, 7 Jan 2000 05:16:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA95662; Fri, 7 Jan 2000 14:15:55 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001071315.OAA95662@freebsd.dk> Subject: Re: some problem with atapi-all.c In-Reply-To: from Fritz Heinrichmeyer at "Jan 7, 2000 02:09:46 pm" To: fritz.heinrichmeyer@fernuni-hagen.de (Fritz Heinrichmeyer) Date: Fri, 7 Jan 2000 14:15:54 +0100 (CET) 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 Fritz Heinrichmeyer wrote: > > I tried the ATA_ENABLE_ATAPI_DMA option, it gave: > > ../../dev/ata/atapi-all.c: In function `atapi_attach': > ../../dev/ata/atapi-all.c:150: syntax error before `)' fixed. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 5:48:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id AD70515682 for ; Fri, 7 Jan 2000 05:48:21 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-252.ix.netcom.com [209.109.235.252]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id FAA60561; Fri, 7 Jan 2000 05:48:16 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id FAA56267; Fri, 7 Jan 2000 05:48:11 -0800 (PST) To: dg@root.com Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: <200001070150.RAA08235@implode.root.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 07 Jan 2000 05:48:09 -0800 In-Reply-To: David Greenman's message of "Thu, 06 Jan 2000 17:50:27 -0800" Message-ID: Lines: 13 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yikes! Seems fifi got out of the cage again. How did she figure out the combination for the lock.... * From: David Greenman * >p.s. pardon the lack of capital letters but my paws can't quite reach * > the shift key and the alphabet keys at the same time.... * * If that is true, then how were you able to push the paren keys? The tail, I guess. It's not easy but it's doable. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 6:34: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 1AC9014FBD for ; Fri, 7 Jan 2000 06:34:00 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA02768 for freebsd-current@freebsd.org; Fri, 7 Jan 2000 15:33:58 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id NAA43918 for freebsd-current@freebsd.org; Fri, 7 Jan 2000 13:29:14 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Date: 7 Jan 2000 13:29:13 +0100 Message-ID: <854m6p$1as0$1@bigeye.rhein-neckar.de> References: <20000106191051.A40270@panzer.kdm.org> <6956.947217921@zippy.cdrom.com> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. Works for me. 4.0-CURRENT from December 19, Toshiba CD-ROM XM-3601TA 0175, tosha-0.6. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 7:36:25 2000 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 35FE015785 for ; Fri, 7 Jan 2000 07:36:19 -0800 (PST) (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 D76A6370F; Fri, 7 Jan 2000 09:36:14 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id JAA10513; Fri, 7 Jan 2000 09:36:13 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Fri, 7 Jan 2000 09:36:13 -0600 (CST) From: Thomas Veldhouse To: Adam Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... 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 Why can't the driver enable the card instead. I can not shut the PNP OS settings off on my mobo because of a Compaq "hack". Because of that my Asante 10 does not start up - it does get detected though. Under Linux, it detects that the card has not been enabled by the BIOS and then it does it for me. That would be a really great feature for the FreeBSD driver as well. It would probably be nice with Sound Cards too. Tom Veldhouse veldy@visi.com On Fri, 7 Jan 2000, Adam wrote: > Is this the pnp-os switch in bios thing? > > On Fri, 7 Jan 2000, Matthew Jacob wrote: > > > > >Umm- I know I've done this before, but maybe this is something stupid I've > >forgotten.... I went home to my shiny new 400Mhz intel with the 40GB IBM > >drive in hand.. I'd pulled a couple of the 4.0 snapshot floppy sets off > >off current.freebsd.org... boot the floppies- they see the de0 card I have > >in the probe messages (which is connected to the DSL modem ...), but only > >present sl0/ppp0 as network install media. > > > >What have I forgotten that makes me a bonehead here? > > > > > > > > > > > > > > > >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 7:58:53 2000 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 EFE1215715; Fri, 7 Jan 2000 07:58:40 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA41655; Fri, 7 Jan 2000 10:58:19 -0500 (EST) (envelope-from wollman) Date: Fri, 7 Jan 2000 10:58:19 -0500 (EST) From: Garrett Wollman Message-Id: <200001071558.KAA41655@khavrinen.lcs.mit.edu> To: Darren Reed Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), steve@virtual-voodoo.com, dillon@apollo.backplane.com, scanner@jurai.net, shin@nd.net.fujitsu.co.jp, louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001071252.XAA05648@avalon.reed.wattle.id.au> References: <670.947193259@critter.freebsd.dk> <200001071252.XAA05648@avalon.reed.wattle.id.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > In light of IPv6 missing Will you please get it through your skull that IPv6 is NOT MISSING! Thank you. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 8:25:21 2000 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 E5DC6157D4 for ; Fri, 7 Jan 2000 08:25:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA58072 for ; Fri, 7 Jan 2000 08:25:14 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA96160 for current@freebsd.org; Fri, 7 Jan 2000 08:25:14 -0800 (PST) (envelope-from obrien) Date: Fri, 7 Jan 2000 08:25:13 -0800 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** chown&chgrp moved again Message-ID: <20000107082513.A96136@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i 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 heads up to let you know that you need to rm -f /sbin/chwon /bin/chgrp after your next `make world'. Additionally you need to install a new /dev/MAKEDEV (mergmaster(8) will assist you in this). A while back I moved the install location for chown and chgrp from /usr/sbin and /usr/bin to /sbin and /bin. This was because of MAKEDEV(8)'s dependence on them, and thus forced /usr to be mounted for correct operation of MAKEDEV(8). Of course that is bad since you could easily be trying to create the device node to even mount /usr. This week, I have added chown-like functionality to mknod(8) and restored chown & chgrp back to their previous locations. MAKEDEV has been updated to use the new functionality of mknod(8). However, do to this moving around of chown & chgrp's install location, you may easily have stale versions in /sbin and /bin. -- -- 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 Fri Jan 7 8:37:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 2BDD815818 for ; Fri, 7 Jan 2000 08:37:42 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup4-31.iptelecom.net.ua [212.9.226.223]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA01321 for ; Fri, 7 Jan 2000 18:40:54 +0200 (EET) Message-ID: <3876166A.32988173@altavista.net> Date: Fri, 07 Jan 2000 18:38:02 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Problems with DGA on XFree86 (broken?) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anybody successfully using any DGA-based programs on recently recompiled Xfree 3.3.5? I have a problem with it and for me it seems broken. For example standart XFree86 test program 'dga' returns following error on my two -current machines (Mach64 and C&T 65554 servers recompiled yesterday). Other DGA applications doesn't work too. bash-2.03# /usr/X11R6/bin/dga X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 78 (X_CreateColormap) Serial number of failed request: 12 Current serial number in output stream: 269 bash-2.03# Sincerely, Maxim P.S. Of course I'm running -current rebuilt several days ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 8:54:45 2000 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 96FB915822; Fri, 7 Jan 2000 08:54:42 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id IAA39021; Fri, 7 Jan 2000 08:54:41 -0800 (PST) (envelope-from mph) Date: Fri, 7 Jan 2000 08:54:41 -0800 From: Matthew Hunt To: Satoshi - Ports Wraith - Asami Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000107085441.A38383@wopr.caltech.edu> References: <200001070150.RAA08235@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from asami@FreeBSD.ORG on Fri, Jan 07, 2000 at 05:48:09AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 05:48:09AM -0800, Satoshi Asami wrote: > Yikes! Seems fifi got out of the cage again. How did she figure out > the combination for the lock.... I'm not sure, but I suspect she factored your private key. Maybe if you didn't keep putting them in the INDEX commit logs... -- 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 Fri Jan 7 9:28:24 2000 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 1C62914F93; Fri, 7 Jan 2000 09:28:22 -0800 (PST) (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 KAA19884; Fri, 7 Jan 2000 10:28:21 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA05460; Fri, 7 Jan 2000 10:28:20 -0700 Date: Fri, 7 Jan 2000 10:28:20 -0700 Message-Id: <200001071728.KAA05460@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** chown&chgrp moved again In-Reply-To: <20000107082513.A96136@dragon.nuxi.com> References: <20000107082513.A96136@dragon.nuxi.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 > This week, I have added chown-like functionality to mknod(8) and restored > chown & chgrp back to their previous locations. MAKEDEV has been > updated to use the new functionality of mknod(8). Thanks for doing this David! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 9:28:58 2000 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 ABCA4157E8 for ; Fri, 7 Jan 2000 09:28:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA58363; Fri, 7 Jan 2000 09:28:53 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA97231; Fri, 7 Jan 2000 09:28:47 -0800 (PST) (envelope-from obrien) Date: Fri, 7 Jan 2000 09:28:47 -0800 From: "David O'Brien" To: David Malone , current@FreeBSD.ORG Subject: Re: Lint still broken in -current (due to cpp). Message-ID: <20000107092847.A97211@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001071122.aa81066@salmon.maths.tcd.ie> <13429.947244567@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <13429.947244567@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Fri, Jan 07, 2000 at 01:29:27PM +0200 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 Fri, Jan 07, 2000 at 01:29:27PM +0200, Sheldon Hearn wrote: > I think lint(1) might work with this given the following small patch. I agree that lint might should continue to use /usr/libexec/cpp rather than switch to /usr/bin/cpp. But not knowing anything about our lint, I can't really say. -- -- 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 Fri Jan 7 9:40:59 2000 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 4ADF91570A for ; Fri, 7 Jan 2000 09:40:55 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA11758; Fri, 7 Jan 2000 09:40:34 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001071740.JAA11758@gndrsh.dnsmgr.net> Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: from "torstenb@FreeBSD.ORG" at "Jan 7, 2000 01:48:17 pm" To: torstenb@vmunix.org Date: Fri, 7 Jan 2000 09:40:34 -0800 (PST) Cc: patrick@mindstep.com, 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 ... > > I strongly suggest to not release 4.0 till the IPv6 import has been finished. > Beside the need for IPv6 it would be wrong to ship a release with a half- > complete implementation. I expect every person that has made similiar statements here and bore all the developers with the additional workload of reading them to download 4.0-current, enable INETV6 and start applying every patch that the KAME group posts to the -committers list and have complete review feedback within 48 hours of such patches being posted. If you, the users, are not ready to do this, STOP asking those to be the folks so described: ``We the willing have been doing so much with so little for so long that we are now qualified to do anything with absolutely nothing at all''. -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 9:48: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 35B8214FEE for ; Fri, 7 Jan 2000 09:47:55 -0800 (PST) (envelope-from khetan@freebsd.os.org.za) Received: by kg.ops.uunet.co.za (Postfix, from userid 1000) id B5A3416E6E; Fri, 7 Jan 2000 19:47:47 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by kg.ops.uunet.co.za (Postfix) with ESMTP id 5B6F71134C; Fri, 7 Jan 2000 19:47:47 +0200 (SAST) Date: Fri, 7 Jan 2000 19:47:46 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@kg.ops.uunet.co.za To: "Kenneth D. Merry" Cc: current@freebsd.org Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? In-Reply-To: <20000106182004.B39324@panzer.kdm.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 Around Yesterday, "Kenneth D. Merry" wrote : >Many of the opinions I've seen recently are that you jitter correction >isn't necessary for most newer CDROM drives. If you want jitter >correction, you can port cdd to CAM. cdda2wav does jitter correction - -P sectors --set-overlap sets the initial number of overlap sectors for jit- ter correction Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za/ * http://www.freebsd.org/ * information at System Administration * http://link.os.org.za/ * kg+details@os.org.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 9:48:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 36C1F14FFE for ; Fri, 7 Jan 2000 09:48:26 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA22951; Fri, 7 Jan 2000 09:48:23 -0800 Date: Fri, 7 Jan 2000 09:48:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Thomas Veldhouse Cc: Adam , freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... 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 This shouldn't be a PNP-OS issue because this is a PCI card- the card is seen during booting- which means it's getting detected. I don't know why 'ifconfig -l' doesn't see it though. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 9:49:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id C21B514F81 for ; Fri, 7 Jan 2000 09:49:43 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 51889 invoked from network); 7 Jan 2000 17:49:37 -0000 Received: from dhcp-mtl-200.local.mindstep.com (HELO patrak) (192.168.10.200) by jacuzzi.local.mindstep.com with SMTP; 7 Jan 2000 17:49:37 -0000 Message-ID: <003301bf5937$90b0c340$c80aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Luigi Rizzo" Cc: References: <200001070922.KAA03892@info.iet.unipi.it> Subject: Re: ipfw optimizations Date: Fri, 7 Jan 2000 12:49:37 -0500 Organization: MindStep Corporation 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 Hi Luigi, > i am looking at (minor) optimizations of the ipfw code in order to reduce > the running time in the common cases. > > I have a few ideas (mostly along the lines of optimizing for the > most commonly-used rules). An obvious candidate is the 'match all' > rule (all from any to any), but can people suggest other common > usage of rules in ipfw ? One of the things I would do to optimize ipfw is: - instead of keeping one list with all the rules, split the list (the internal one) by interface and by direction (one list for ed1 incoming, one list for ed1 outgoing, etc.). - then eventually you could be doing the same thing by IP protocol number, but it might not be worth it (with regard to the amount of work required). I think that it is a better way to optimize ipfw than optimize the "match all" rule, since in any security conscious this is likely to be a deny rule, and who cares if it takes a little longer to deny a packet ? My goal usually is to accept legitimate packets as early as possible, reject really obvious stuff also fairly early and then handle the less common stuff. At last there is my match all deny rule, but it does not get exercised that often. One advantage of having a compiled ruleset for each interface would speed up quite a bit the processing by not going over rules that are not applicable. I looked once at doing that on the 3.x-STABLE ipfw, and even if it did not seem to be *too* complicated to do, I did not have the time to go further. Any thoughts ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 9:58: 3 2000 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 7BD7C14FE2 for ; Fri, 7 Jan 2000 09:58:00 -0800 (PST) (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 25A2237F8; Fri, 7 Jan 2000 11:57:55 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id LAA23413; Fri, 7 Jan 2000 11:57:54 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Fri, 7 Jan 2000 11:57:54 -0600 (CST) From: Thomas Veldhouse To: Matthew Jacob Cc: Adam , freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... 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 wouldn't think so. However, the problem disappears when the PNP OS setting is set to OFF on another box - and it reappears when I turn it back on. When Linux boots - it says something to the extent that the card has not been initialized by the BIOS - and then it does it - this is when the driver detects it. Oddly, it does have an IRQ under FreeBSD - it just doesn't work [with PNP OS on]. I used to get this problem [Not PNP OS related though] with "auto" under the interfaces section of /etc/rc.conf. Overriding that with "lo0 de0" has not fixed the problem. I had to get a different card for my box without the option to run PNP OS off, a PNIC II based Linksys card. Tom Veldhouse veldy@visi.com On Fri, 7 Jan 2000, Matthew Jacob wrote: > > This shouldn't be a PNP-OS issue because this is a PCI card- the card is > seen during booting- which means it's getting detected. I don't know why > 'ifconfig -l' doesn't see it though. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10: 0:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5AF3315024 for ; Fri, 7 Jan 2000 10:00:54 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA23041; Fri, 7 Jan 2000 10:00:46 -0800 Date: Fri, 7 Jan 2000 10:00:44 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Thomas Veldhouse Cc: Adam , freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... 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 Hmm. Very interesting and subtle. I'll check this out. Gawd, PCs are *soooo* lame.... On Fri, 7 Jan 2000, Thomas Veldhouse wrote: > I wouldn't think so. However, the problem disappears when the PNP OS > setting is set to OFF on another box - and it reappears when I turn it > back on. When Linux boots - it says something to the extent that the card > has not been initialized by the BIOS - and then it does it - this is when > the driver detects it. Oddly, it does have an IRQ under FreeBSD - it just > doesn't work [with PNP OS on]. I used to get this problem [Not PNP > OS related though] with "auto" under the interfaces section of > /etc/rc.conf. Overriding that with "lo0 de0" has not fixed the problem. > > I had to get a different card for my box without the option to > run PNP OS off, a PNIC II based Linksys card. > > Tom Veldhouse > veldy@visi.com > > On Fri, 7 Jan 2000, Matthew Jacob wrote: > > > > > This shouldn't be a PNP-OS issue because this is a PCI card- the card is > > seen during booting- which means it's getting detected. I don't know why > > 'ifconfig -l' doesn't see it though. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10: 2:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 0545D15052 for ; Fri, 7 Jan 2000 10:02:13 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA05558; Fri, 7 Jan 2000 19:02:33 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001071802.TAA05558@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <003301bf5937$90b0c340$c80aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Jan 7, 2000 12:49:37 pm" To: Patrick Bihan-Faou Date: Fri, 7 Jan 2000 19:02:33 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One of the things I would do to optimize ipfw is: > - instead of keeping one list with all the rules, split the list (the > internal one) by interface and by direction (one list for ed1 incoming, > one list for ed1 outgoing, etc.). one skipto rule is enough to switch between two rulesets depending on direction, so this is not really worthwhile. I agree that having a `switch' type of rule for selecting interfaces would be a reasonable gain of efficiency (but then again.. how many interfaces is one using!) The problem with current rule format is that you can detect a non-match very early, but in order to have a real match you have to test all the fields (addresses, ports, interfaces, ...) and even if this only means testing flags, it is still some 8-10 tests and 8-10 jumps. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10: 6:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from onizuka.vmunix.org (onizuka.vmunix.org [194.221.152.19]) by hub.freebsd.org (Postfix) with ESMTP id 3613514CA9 for ; Fri, 7 Jan 2000 10:06:27 -0800 (PST) (envelope-from torstenb@vmunix.org) Received: from localhost (1271 bytes) by onizuka.vmunix.org via sendmail with stdio (sender: ) (ident using unix) id for ; Fri, 7 Jan 2000 19:07:29 +0100 (CET) Message-Id: From: torstenb@vmunix.org (Torsten Blum) Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001071740.JAA11758@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Jan 7, 2000 09:40:34 am" To: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes) Date: Fri, 7 Jan 2000 19:07:29 +0100 (CET) Cc: torstenb@vmunix.org, patrick@mindstep.com, 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 Rodney W. Grimes wrote: [complaining that people just complain instead of doing the work] > If you, the users, are not ready to do this, STOP asking those to be > the folks so described: > > ``We the willing have been doing so much with so little for so long > that we are now qualified to do anything with absolutely nothing at all''. Rod, please, I can only speak for myself, but I already run IPv6 on my 3.x machines and my 4.0-current development box is running with INET6 enabled. While probably not everybody who complained is actually doing some work, there are people who do it and complain because they realize how important it is. Thanks -tb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10: 9:54 2000 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 7A6B815784 for ; Fri, 7 Jan 2000 10:09:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA06726; Fri, 7 Jan 2000 19:09:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luigi Rizzo Cc: Patrick Bihan-Faou , freebsd-current@FreeBSD.org Subject: Re: ipfw optimizations In-reply-to: Your message of "Fri, 07 Jan 2000 19:02:33 +0100." <200001071802.TAA05558@info.iet.unipi.it> Date: Fri, 07 Jan 2000 19:09:31 +0100 Message-ID: <6724.947268571@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001071802.TAA05558@info.iet.unipi.it>, Luigi Rizzo writes: >> One of the things I would do to optimize ipfw is: >> - instead of keeping one list with all the rules, split the list (the >> internal one) by interface and by direction (one list for ed1 incoming, >> one list for ed1 outgoing, etc.). > >one skipto rule is enough to switch between two rulesets depending >on direction, so this is not really worthwhile. >I agree that having a `switch' type of rule for selecting interfaces >would be a reasonable gain of efficiency (but then again.. how >many interfaces is one using!) I still think we should split the current "one huge list of rules" into several lists: Two lists per interface: one list of rules for inbound packets one list of rules for outbound packets Two lists for the IP stack: one list of rules for incoming packets one list of rules for outgoing packets One list for forwarding of packets. in theory one could also: Two lists for the UDP stack: one list of rules for incoming packets one list of rules for outgoing packets Two lists for the TCP stack: one list of rules for incoming packets one list of rules for outgoing packets -- 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 Jan 7 10:12:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 923E1157D6 for ; Fri, 7 Jan 2000 10:12:39 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA05606; Fri, 7 Jan 2000 19:13:00 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001071813.TAA05606@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <6724.947268571@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 7, 2000 07:09:31 pm" To: Poul-Henning Kamp Date: Fri, 7 Jan 2000 19:13:00 +0100 (CET) Cc: Patrick Bihan-Faou , freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I still think we should split the current "one huge list of rules" > into several lists: > Two lists per interface: > one list of rules for inbound packets > one list of rules for outbound packets > > Two lists for the IP stack: > one list of rules for incoming packets > one list of rules for outgoing packets > > One list for forwarding of packets. aren't these three classes combined in some H-shaped way ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:16:37 2000 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 72941158FF for ; Fri, 7 Jan 2000 10:16:12 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA06779; Fri, 7 Jan 2000 19:15:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luigi Rizzo Cc: Patrick Bihan-Faou , freebsd-current@FreeBSD.org Subject: Re: ipfw optimizations In-reply-to: Your message of "Fri, 07 Jan 2000 19:13:00 +0100." <200001071813.TAA05606@info.iet.unipi.it> Date: Fri, 07 Jan 2000 19:15:58 +0100 Message-ID: <6777.947268958@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001071813.TAA05606@info.iet.unipi.it>, Luigi Rizzo writes: >> I still think we should split the current "one huge list of rules" >> into several lists: > >> Two lists per interface: >> one list of rules for inbound packets >> one list of rules for outbound packets >> >> Two lists for the IP stack: >> one list of rules for incoming packets >> one list of rules for outgoing packets >> >> One list for forwarding of packets. > >aren't these three classes combined in some H-shaped way ? Could be, the forwarding branch could be a good place to hook up natd(8) for instance... -- 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 Jan 7 10:20:50 2000 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 53D7A157FA for ; Fri, 7 Jan 2000 10:20:43 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA11875; Fri, 7 Jan 2000 10:20:32 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001071820.KAA11875@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <003301bf5937$90b0c340$c80aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Jan 7, 2000 12:49:37 pm" To: patrick@mindstep.com (Patrick Bihan-Faou) Date: Fri, 7 Jan 2000 10:20:32 -0800 (PST) Cc: luigi@info.iet.unipi.it (Luigi Rizzo), 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 [Charset iso-8859-1 unsupported, filtering to ASCII...] > Hi Luigi, > > > > i am looking at (minor) optimizations of the ipfw code in order to reduce > > the running time in the common cases. > > > > I have a few ideas (mostly along the lines of optimizing for the > > most commonly-used rules). An obvious candidate is the 'match all' > > rule (all from any to any), but can people suggest other common > > usage of rules in ipfw ? > > One of the things I would do to optimize ipfw is: > - instead of keeping one list with all the rules, split the list (the > internal one) by interface and by direction (one list for ed1 incoming, > one list for ed1 outgoing, etc.). I often do this manually in long rule sets by using things like ipfw add 1000 skipto 10000 from any to any via de0 ipfw add 1001 skipto 20000 from any to any via de1 ... ipfw add 10000 skipto 15000 from any to any in via de0 #process outbound on de0 rules here ipfw add 15000 blah blah # processing inbound on de0 rules here Do similiar things at 20000... You can reduce the number of skipto's by using a more explicit set of rules at 1000, such as doing full 4 way branch: ipfw add 1000 skipto 10000 from any to any in via de0 ipfw add 1001 skipto 15000 from any to any out via de0 ipfw add 1002 skipto 20000 from any to any in via de1 ipfw add 1003 skipto 25000 from any to any out via de1 Anotherwords, don't burden the ipfw with code that can easily be done by an intellegent user, and some more examples/documentation... -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 10:22:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.dogwood.com (white.dogwood.com [209.24.60.226]) by hub.freebsd.org (Postfix) with ESMTP id CF25D159A7 for ; Fri, 7 Jan 2000 10:22:05 -0800 (PST) (envelope-from dave@dogwood.com) Received: (from dave@localhost) by white.dogwood.com (8.9.3/8.9.3) id KAA97702; Fri, 7 Jan 2000 10:21:56 -0800 (PST) (envelope-from dave) From: Dave Cornejo Message-Id: <200001071821.KAA97702@white.dogwood.com> Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001071252.XAA05648@avalon.reed.wattle.id.au> from Darren Reed at "Jan 7, 2000 11:52:34 pm" To: Darren Reed Date: Fri, 7 Jan 2000 10:21:56 -0800 (PST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You know, the people reading this list are *not* the typical FreeBSD users. The fact that releases occur at all is a concession to the realities of the world - WCCDROM needs to pay it's bills by selling CDROMs, and their business pressures require new updates on time and to be as stable as possible (to minimize tech support). You have no idea how expensive it was for them to slip the date a month as it already has to include the features that will go into 4.0. Additionally, despite what you think, I'd bet 99+% of the FreeBSD users in the world could give a rats *ss about IPv6. I run many FreeBSD systems and not one of the ISPs I deal with has announced any plans to move to IPv6 yet. I don't see much, if any, market pressure to move yet, and I suspect that v4 will be perfectly adequate to the needs of a vast majority of FreeBSD users for at least the next year, if not longer. If you want v6, run current, don't make the people waiting for 4.0 wait longer. This is much more likely to cause lost users than no v6. -- Dave Cornejo - Dogwood Media, Fremont, California General Magician & Registered Be Developer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:27:20 2000 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 6E213158CC for ; Fri, 7 Jan 2000 10:27:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA11683; Fri, 7 Jan 2000 10:25:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: will andrews Cc: current@FreeBSD.ORG, Peter Jeremy , mjacob@feral.com Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Fri, 07 Jan 2000 07:38:12 EST." Date: Fri, 07 Jan 2000 10:25:44 -0800 Message-ID: <11681.947269544@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doesn't this statement make the entire thread about IPv6 + PC-Card support > entirely moot? Feature freezes don't mean we can't improve those two areas, > right? Right? :-) PC-card, perhaps, but I think IPv6 still needs "improvement" far less that it needs significant integration. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:34:22 2000 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 B51E4157C4; Fri, 7 Jan 2000 10:34:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA11742; Fri, 7 Jan 2000 10:33:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Darren Reed Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), steve@virtual-voodoo.com, dillon@apollo.backplane.com, scanner@jurai.net, shin@nd.net.fujitsu.co.jp, louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: Your message of "Fri, 07 Jan 0100 23:52:34 +1100." <200001071252.XAA05648@avalon.reed.wattle.id.au> Date: Fri, 07 Jan 2000 10:33:30 -0800 Message-ID: <11740.947270010@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you'd do far better to stop bitching and simply start helping. The people I've heard yell the very loudest in this discussion are also the people who: a) Have not helped Yoshinobu Inoue to any great extent during his calls for patch testing. b) Have not volunteered to help with the integration, merely retreating into calls that release should happen "when it's finished" and conveniently side-stepping the fact that somebody has to finish it first. In other words, this is a clear-cut case of back-seat driving by people who aren't even willing to climb into the front seat and drive foward the issue they're complaining about, they just want to yell from the relative safety of the back seat. Cut it out! If you, Darren, want to find something useful to do then go maintain your ipfilter code and stop relying on others to do it for you in FreeBSD. I've already made this point in private email and I won't elaborate further on it here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:37:25 2000 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 87881157AA for ; Fri, 7 Jan 2000 10:37:18 -0800 (PST) (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 LAA20593; Fri, 7 Jan 2000 11:37:04 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA06133; Fri, 7 Jan 2000 11:37:02 -0700 Date: Fri, 7 Jan 2000 11:37:02 -0700 Message-Id: <200001071837.LAA06133@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Luigi Rizzo Cc: Patrick Bihan-Faou , freebsd-current@FreeBSD.ORG Subject: Re: ipfw optimizations In-Reply-To: <200001071802.TAA05558@info.iet.unipi.it> References: <003301bf5937$90b0c340$c80aa8c0@local.mindstep.com> <200001071802.TAA05558@info.iet.unipi.it> 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 > > One of the things I would do to optimize ipfw is: > > - instead of keeping one list with all the rules, split the list (the > > internal one) by interface and by direction (one list for ed1 incoming, > > one list for ed1 outgoing, etc.). > > one skipto rule is enough to switch between two rulesets depending > on direction, so this is not really worthwhile. > I agree that having a `switch' type of rule for selecting interfaces > would be a reasonable gain of efficiency (but then again.. how > many interfaces is one using!) It doesn't matter, it has to do the lookup on a per-interface basis. On my firewall box, I have 11 interfaces. Two ethernet, one loopback, 4 slip, and 4 tunnel. I could easily see a speedup from using per-interface lists. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:38:26 2000 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 3D9C6155B5 for ; Fri, 7 Jan 2000 10:38:23 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA05546; Fri, 7 Jan 2000 10:38:19 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id KAA00524; Fri, 7 Jan 2000 10:37:52 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200001071837.KAA00524@whistle.com> Subject: Re: New kernel no longer boots on one of my machines... ata, other problems In-Reply-To: <200001070405.UAA75303@apollo.backplane.com> from Matthew Dillon at "Jan 6, 2000 08:05:00 pm" To: Matthew Dillon Date: Fri, 7 Jan 2000 10:37:52 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: | Well guys, I tried upgrading one of my older machines today to the | latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). I ran into a similar problem when upgrading my server at home. It is an old 486 with an Intel Saturn chipset. I found the IDE drive via ad0 and failed the mount with error 6 or whatever. I then put the same drive in a machine with a P5 & Intel TX chipset. In this setup ad0 was found and it mounted the rootfs with no trouble. Since this is a machine that needs to be up I switched to the wd driver which worked like charm except for re-enabling it. So in my configuration it is not a MAKDEV/fstab stale issue (I rebuild all of that) and it works with a PCI driver but not with the Saturn ISA driver. My successful boot and probe is: wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , multi-block-16 wd0: 12897MB (26414640 sectors), 26205 cyls, 16 heads, 63 S/T, 512 B/S Now I recall in discussions about pcmcia stuff and the various patches flying around that there was a 32/16 bit access mode issue. Also I think while the pcmcia was in 32 bit mode hard disk access stopped working and maybe flash (since my external IDE hard drive work then it didn't then it did again). I think this correlated to when it was switched to 16 bit then it started working again. Anyways more work and lots of testing needs to be done. Even though I like the new ata stuff and use it on all machines (except for one) this is scary since a bunch of 4.0 users could get screwed with older good hardware. Tonight I will try to define ATA_16BIT_ONLY in my kernel and try to boot with ata. This may have to be set in GENERIC for installs to work ... or the ata driver learn how to figure this out automatically on the fly. BTW this almost hosed me. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 10:40:18 2000 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 BD134157B4 for ; Fri, 7 Jan 2000 10:40:14 -0800 (PST) (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 NAA12990 for ; Fri, 7 Jan 2000 13:40:08 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17833; Fri, 7 Jan 2000 13:40:00 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id NAA71417 for freebsd-current@FreeBSD.org; Fri, 7 Jan 2000 13:39:59 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001071839.NAA71417@bb01f39.unx.sas.com> Subject: make world failure (libcrypt) To: freebsd-current@FreeBSD.org Date: Fri, 7 Jan 2000 13:39:59 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm seeing the following error, and don't see any fixes in the cvs repository yet. I am however, about an hour behind since I get my updates from a standard mirror. My sources are current as of about an hour ago... If this is already fixed, just ignore.... Thanks, John ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so cd /usr/src/lib; make depend; make all; make install ===> csu/i386-elf ===> libcom_err ===> libcom_err/doc ===> msun ===> libmd ===> libcrypt ===> ../secure/lib/libcrypt make: don't know how to make crypt-shs.c. Stop *** Error code 2 Stop in /usr/src/lib. *** 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 Fri Jan 7 10:43: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id EE92D158F6 for ; Fri, 7 Jan 2000 10:42:54 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id NAA23378; Fri, 7 Jan 2000 13:42:39 -0500 (EST) Date: Fri, 7 Jan 2000 13:42:37 -0500 (EST) From: Bosko Milekic To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: panic at kern/uipc_socket2.c In-Reply-To: <14450.6126.709759.19547O@localhost.sky.rim.or.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 Wed, 5 Jan 2000, Jun Kuriyama wrote: >From: Bosko Milekic >> You don't happen to have a backtrace? > >I don't have it. When my box gives no reaction, I've hit some keys, >keys, keys...and rebooted automatically. At that time, I could not >switch to VT1 from X with [Ctrl]+[Alt]+[F1]. > >> Was anything particular happening at the time of the crash? Do you >> have any way to not necessarily directly reproduce the panic but rather >> "force" it to happen (e.g. as a consequence of execution of something or, >> even as a result of some external "trigger")? > >I think I used XEmacs, Netscape Communicator and many console works >with ssh'ed remote login. I have no idea which one made this. > > >Jun Kuriyama // kuriyama@sky.rim.or.jp > // kuriyama@FreeBSD.org > Can you look at kern/10872 and see if your hardware matches Bob's? (e.g. The infamous fxp and ncr combo.) and regardless, attempt executing the script that is provided and note whether or not you can reproduce the panic in sbdrop()? If so, a backtrace and a `print *sb' would be helpful, certainly. It looks as though some mbufs are literally being `zapped' off of sb_mb while sb_cc and sb_mbcnt are still greater than zero. Either that, or something's not adjusting sb_cc and/or sb_mbcnt under the proper spl which may lead to an interrupt eventually leading to the sbdrop with an sb_cc and sb_mb that just don't go together. -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 11: 3:26 2000 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 353D31583E for ; Fri, 7 Jan 2000 11:03:20 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA11964; Fri, 7 Jan 2000 11:02:53 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001071902.LAA11964@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <6724.947268571@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 7, 2000 07:09:31 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 7 Jan 2000 11:02:52 -0800 (PST) Cc: luigi@info.iet.unipi.it (Luigi Rizzo), patrick@mindstep.com (Patrick Bihan-Faou), 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 > In message <200001071802.TAA05558@info.iet.unipi.it>, Luigi Rizzo writes: > >> One of the things I would do to optimize ipfw is: > >> - instead of keeping one list with all the rules, split the list (the > >> internal one) by interface and by direction (one list for ed1 incoming, > >> one list for ed1 outgoing, etc.). > > > >one skipto rule is enough to switch between two rulesets depending > >on direction, so this is not really worthwhile. > >I agree that having a `switch' type of rule for selecting interfaces > >would be a reasonable gain of efficiency (but then again.. how > >many interfaces is one using!) > > I still think we should split the current "one huge list of rules" > into several lists: > > Two lists per interface: > one list of rules for inbound packets > one list of rules for outbound packets ... I use to think this was the way to do it too, until I went and figured out how to do the exact same thing using the current setup. What we have now is actually more flexiable than this proposed configuration in that it allows a superset of this, plus you don't have to duplicate rules in multiple sets, ie: ipfw add 1000 deny ip from 10.0.0.0/8 to any ipfw add 1001 deny ip from any to 10.0.0.0/8 covers all interfaces, I don't have to add those and the 6 others to every interface rule set like we do on the Ciscos. The skipto situation may be slightly ineffecient due to the number of comparisons needed, perhaps adding the ability to dispatch more directly rather than a chain of skipto's, though I can't come up with a simple syntax for this off the top of my head. :-( -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 11: 9: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 972FC14F63 for ; Fri, 7 Jan 2000 11:08:55 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 52031 invoked from network); 7 Jan 2000 19:08:47 -0000 Received: from dhcp-mtl-200.local.mindstep.com (HELO patrak) (192.168.10.200) by jacuzzi.local.mindstep.com with SMTP; 7 Jan 2000 19:08:47 -0000 Message-ID: <007d01bf5942$a0216540$c80aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Rodney W. Grimes" Cc: "Luigi Rizzo" , References: <200001071820.KAA11875@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations Date: Fri, 7 Jan 2000 14:08:47 -0500 Organization: MindStep Corporation 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 Hi, > > One of the things I would do to optimize ipfw is: > > - instead of keeping one list with all the rules, split the list (the > > internal one) by interface and by direction (one list for ed1 incoming, > > one list for ed1 outgoing, etc.). > > I often do this manually in long rule sets by using things like > > ipfw add 1000 skipto 10000 from any to any via de0 > ipfw add 1001 skipto 20000 from any to any via de1 > ... > ipfw add 10000 skipto 15000 from any to any in via de0 > #process outbound on de0 rules here > ipfw add 15000 blah blah # processing inbound on de0 rules here [...] > Anotherwords, don't burden the ipfw with code that can easily be done > by an intellegent user, and some more examples/documentation... Yep, and there happens to be a rule that you would like to be tested in every case, but you don't want to test it at the begining (before the switch) but sometime in the middle. With your scheme (which is the only reasonable one currently), you have to duplicate that rule for every branch. This is fine, but if now you need to modify the rule somewhat, don't forget to modify it everywhere. This can rapidly become a maintenance nightmare. What I was proposing is that the per-interface switch be done implicitely by ipfw. So if you do: ipfw add allow ip from joe to bob via de0 ipfw add allow ip from arthur to joe in recv de0 ipfw add allow ip from john to any You get the proper rule tree generated: -> ed0 RX: allow ip from joe to bob allow ip from arhur to joe allow ip from john to any -> ed0 TX: allow ip from joe to bob allow ip from john to any -> ed1 (TX or RX) allow ip from john to any By the way, in terms of optimization you will save: - 2 * number of interfaces rules (the skiptos) that have to be tested for most packets - 2 tests for each rule after (you don't need to retest the interface nor the direction, it has been. If you go further in that logic and implement a per protocol switch, you reduce the number of test even more. To answer a previous question about the number of interfaces, I use FreeBSD as a gateway with 2 ethernet interfaces and 3 tunnel interfaces (ipsec) to remote locations. I guess that most cases where you really worry about ipfw is in gateways where a minimum of 2 interfaces seems reasonable. Again, I am not saying that you can not implement a similar behaviour with ipfw as it is now, I am just saying that if you want to optimize it, you want to reduce the number of test you perform for each rule. What I am proposing is one way of doing it (and as a side effect, it makes managing a tree like set of rule easier). Patrick. matched already) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 11:18:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 5153714E22 for ; Fri, 7 Jan 2000 11:18:47 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id UAA18144; Fri, 7 Jan 2000 20:18:10 +0100 (CET) Message-ID: <20000107201809.B17766@foobar.franken.de> Date: Fri, 7 Jan 2000 20:18:09 +0100 From: Harold Gutch To: Nate Williams , Luigi Rizzo Cc: Patrick Bihan-Faou , freebsd-current@FreeBSD.ORG Subject: Re: ipfw optimizations References: <003301bf5937$90b0c340$c80aa8c0@local.mindstep.com> <200001071802.TAA05558@info.iet.unipi.it> <200001071837.LAA06133@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001071837.LAA06133@mt.sri.com>; from Nate Williams on Fri, Jan 07, 2000 at 11:37:02AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 11:37:02AM -0700, Nate Williams wrote: > > > One of the things I would do to optimize ipfw is: > > > - instead of keeping one list with all the rules, split the list (the > > > internal one) by interface and by direction (one list for ed1 incoming, > > > one list for ed1 outgoing, etc.). > > > > one skipto rule is enough to switch between two rulesets depending > > on direction, so this is not really worthwhile. > > I agree that having a `switch' type of rule for selecting interfaces > > would be a reasonable gain of efficiency (but then again.. how > > many interfaces is one using!) > > It doesn't matter, it has to do the lookup on a per-interface basis. On > my firewall box, I have 11 interfaces. > > Two ethernet, one loopback, 4 slip, and 4 tunnel. > > I could easily see a speedup from using per-interface lists. I haven't looked at the firewalling-code in the kernel, but couldn't you gain exactly this speedup by issuing this stuff manually? Add a bunch of "skipto" rules at the very beginning of your ruleset and have them branch to rule 5000, 10000, 15000 etc. and then setup your per-interface rules beginning at exactly these rules. In fact, isn't that what Linux' "ipchains" are all about? You split up the rules and branch to one of your rulesets at the beginning. I've never seen anything special in this feature, since ipfw does that as well (you just don't have magical names for your rules but numbers instead). bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 11:19:21 2000 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 0AFE715846 for ; Fri, 7 Jan 2000 11:19:19 -0800 (PST) (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 D0C9836CB for ; Fri, 7 Jan 2000 13:19:08 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id NAA27452 for ; Fri, 7 Jan 2000 13:19:08 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Fri, 7 Jan 2000 13:19:08 -0600 (CST) From: Thomas Veldhouse To: freebsd-current@freebsd.org Subject: Re: ipfw optimizations In-Reply-To: <007d01bf5942$a0216540$c80aa8c0@local.mindstep.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 Something else I would like to see someday [assuming I haven't missed it and it already exists], is TOS optimizations in much the same way that Linux's ipchains utility can optimize protocols such as nntp, telnet, etc. Since the thread is entitled ipfw optimizations - I thought I would add my two cents worth [as worthless as two cents are now days :-] 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 Fri Jan 7 11:39: 5 2000 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 CB3DC14BE9 for ; Fri, 7 Jan 2000 11:38:47 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA12079; Fri, 7 Jan 2000 11:38:34 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001071938.LAA12079@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <007d01bf5942$a0216540$c80aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Jan 7, 2000 02:08:47 pm" To: patrick@mindstep.com (Patrick Bihan-Faou) Date: Fri, 7 Jan 2000 11:38:33 -0800 (PST) Cc: luigi@info.iet.unipi.it (Luigi Rizzo), 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 [Charset iso-8859-1 unsupported, filtering to ASCII...] > Hi, > > > > One of the things I would do to optimize ipfw is: > > > - instead of keeping one list with all the rules, split the list (the > > > internal one) by interface and by direction (one list for ed1 > incoming, > > > one list for ed1 outgoing, etc.). > > > > I often do this manually in long rule sets by using things like > > > > ipfw add 1000 skipto 10000 from any to any via de0 > > ipfw add 1001 skipto 20000 from any to any via de1 > > ... > > ipfw add 10000 skipto 15000 from any to any in via de0 > > #process outbound on de0 rules here > > ipfw add 15000 blah blah # processing inbound on de0 rules here > > [...] > > > Anotherwords, don't burden the ipfw with code that can easily be done > > by an intellegent user, and some more examples/documentation... > > Yep, and there happens to be a rule that you would like to be tested in > every case, but you don't want to test it at the begining (before the > switch) but sometime in the middle. With your scheme (which is the only > reasonable one currently), you have to duplicate that rule for every branch. > This is fine, but if now you need to modify the rule somewhat, don't forget > to modify it everywhere. This can rapidly become a maintenance nightmare. Thats what m4 is for :-) I don't normally write direct rule sets as a simple list of ipfw commands, but as a combination of sh script that is actually written by an m4 input file. I never write the same line twice, and even lines that are similar either end up being a m4 macro, or a shell function for more complicated ones with lots of arguments. > > What I was proposing is that the per-interface switch be done implicitely by > ipfw. So if you do: > > ipfw add allow ip from joe to bob via de0 > ipfw add allow ip from arthur to joe in recv de0 > ipfw add allow ip from john to any > > You get the proper rule tree generated: (Which also happes to be very far from optimal rule set with meaningless rules being run) > > -> ed0 RX: > allow ip from joe to bob More than likely from joe to bob is only either a RX or TX packet, infact unless your using multiple IP addresses on ed0 by definition of routing it would have to be one or the other, otherwise this box should never see that packet as it is not routing it. > allow ip from arhur to joe > allow ip from john to any > > -> ed0 TX: > allow ip from joe to bob > allow ip from john to any > > -> ed1 (TX or RX) > allow ip from john to any The ``from john'' rule probably only applies to one of the 3 interfaces, unless john happens to be multiple routed. > > > By the way, in terms of optimization you will save: > > - 2 * number of interfaces rules (the skiptos) that have to be tested for > most packets And your scheme could easily end up with 100's of rules that don't even make since for that interface/that direction. Attempting to build these lists with intelegence has been tried in the past, and I have yet to see one that doesn't produce far more rules than are actually needed. > - 2 tests for each rule after (you don't need to retest the interface nor > the direction, it has been. > > > If you go further in that logic and implement a per protocol switch, you > reduce the number of test even more. The ipfw dispatch command I mentioned in other email would be an effecient optimization... what I see here would probably be far from optimal as explained above. > > > To answer a previous question about the number of interfaces, I use FreeBSD > as a gateway with 2 ethernet interfaces and 3 tunnel interfaces (ipsec) to > remote locations. I guess that most cases where you really worry about ipfw > is in gateways where a minimum of 2 interfaces seems reasonable. We use it here with 4 to 8 ethenets per box... and larger rule sets run into the 300 to 400 range in count. > > Again, I am not saying that you can not implement a similar behaviour with > ipfw as it is now, I am just saying that if you want to optimize it, you > want to reduce the number of test you perform for each rule. What I am > proposing is one way of doing it (and as a side effect, it makes managing a > tree like set of rule easier). Having to managed systems that do it both ways (basically your trying to go to a Cisco acess-list model) I can say that ipfw actually produces a smaller set of rules (or at least for what we are doing it does.) And a rule set that is easier to figure out what is going on. What we do with about 12 rules in ipfw takes me 12 rules per interface on a cisco, and your scheme would duplicate it to that same 12*interface set, but run it no faster. (Yes, I use m4 to write the cisco rule set too so it's not that big a deal except when your on the router itself trying to figure out what is going wrong :-() How about this for a start/stab at syntax for a dispatch command: ipfw add dispatch interface de0=10000,de1=20000,ed0=30000 # Note we fall pass the above rule if no interface match ipfw add dispatch direction input=2000,output=3000 # I don't know that we could ever fall past this rule, perhaps a # host originated packet could? Or if output or input was left off. ipfw add dispatch protocol tcp=5000,udp=7000,ospf=50000,2=60000 # Fall pass this rule if protocol does not match any in list We actually do that now using skipto rules, but this should reduce the number of comparisons that would need done, and take advantage of things being in registers instead of reloaded from memory as it steps over the rules due to subroutine calls/etc. -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 11:44:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from lorien.odc.net (lorien.odc.net [207.137.42.14]) by hub.freebsd.org (Postfix) with ESMTP id 46DCF154E1 for ; Fri, 7 Jan 2000 11:44:55 -0800 (PST) (envelope-from nwestfal@lorien.odc.net) Received: from localhost (nwestfal@localhost) by lorien.odc.net (8.9.3/8.9.3) with ESMTP id LAA22129 for ; Fri, 7 Jan 2000 11:44:52 -0800 Date: Fri, 7 Jan 2000 11:44:51 -0800 (PST) From: Neal Westfall To: current@freebsd.org Subject: world broken in libcrypt 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 cvsup'd as of 10am PST... sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 libutil.so.2 /usr/obj/usr/src/i386/usr/lib ln -sf libutil.so.2 /usr/obj/usr/src/i386/usr/lib/libutil.so cd /usr/src/lib; make depend; make all; make install ===> csu/i386-elf ===> libcom_err ===> libcom_err/doc ===> msun ===> libmd ===> libcrypt ===> ../secure/lib/libcrypt make: don't know how to make crypt-shs.c. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 -- Neal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 11:54:38 2000 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 D09C114BE9 for ; Fri, 7 Jan 2000 11:54:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA88936; Fri, 7 Jan 2000 11:54:17 -0800 (PST) (envelope-from dillon) Date: Fri, 7 Jan 2000 11:54:17 -0800 (PST) From: Matthew Dillon Message-Id: <200001071954.LAA88936@apollo.backplane.com> To: Doug Ambrisko Cc: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001071837.KAA00524@whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Anyways more work and lots of testing needs to be done. Even though I like :the new ata stuff and use it on all machines (except for one) this is scary :since a bunch of 4.0 users could get screwed with older good hardware. : :Tonight I will try to define : ATA_16BIT_ONLY :in my kernel and try to boot with ata. This may have to be set in GENERIC :for installs to work ... or the ata driver learn how to figure this out :automatically on the fly. : :BTW this almost hosed me. : :Doug A. I've already tried ATA_16BIT_ONLY - no effect on my problem. I also tried turning on DMA, which also had no effect. I'm also pretty sure that my SCSI stuff is not creating any issues since I still get lockups and a non-working timer interrupt ('ticks' doesn't increment) when I take the SCSI out. The weird thing is that what the ata driver appears to be doing is preventing the timer interrupt from working. The driver itself does appear to work in terms of issuing commands and getting responses, at least when there is a drive on the bus for it to probe. To me this points to cockpit trouble in the driver code somewhere. The box this trouble is occuring on for me is an old Pentium 90. It's the oldest working box I still own (but it makes a wonderful backup machine and CVS respository!). -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 Fri Jan 7 11:55:57 2000 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 C3E9214D75 for ; Fri, 7 Jan 2000 11:55:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA17593; Fri, 7 Jan 2000 12:55:46 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA87732; Fri, 7 Jan 2000 12:55:45 -0700 (MST) Message-Id: <200001071955.MAA87732@harmony.village.org> To: Doug Ambrisko Subject: Re: New kernel no longer boots on one of my machines... ata, other problems Cc: Matthew Dillon , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Jan 2000 10:37:52 PST." <200001071837.KAA00524@whistle.com> References: <200001071837.KAA00524@whistle.com> Date: Fri, 07 Jan 2000 12:55:45 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001071837.KAA00524@whistle.com> Doug Ambrisko writes: : Tonight I will try to define : ATA_16BIT_ONLY : in my kernel and try to boot with ata. This may have to be set in GENERIC : for installs to work ... or the ata driver learn how to figure this out : automatically on the fly. Look at my ata flash patches to see a start at forcing ata to learn this dynamically. It should never do 32 bit I/O for isa or pccard devices. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 12:10:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 299F015926 for ; Fri, 7 Jan 2000 12:09:03 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (usr1-29.cybcon.com [205.147.75.30]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id MAA25501 for ; Fri, 7 Jan 2000 12:09:01 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 07 Jan 2000 12:10:13 -0800 (PST) From: William Woods To: freebsd-current@freebsd.org Subject: IPv6 testing...willing to help Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a DEC Alpha at home running 4.0-current and am willing to help out with the testing. I am not the worlds greatest coder, but am willing to do what I can ---------------------------------- E-Mail: William Woods Date: 07-Jan-00 Time: 12:09:03 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 12:46:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 220A314C8F; Fri, 7 Jan 2000 12:46:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01482; Fri, 7 Jan 2000 12:52:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001072052.MAA01482@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Darren Reed Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: 3c589d problem In-reply-to: Your message of "Fri, 07 Jan 0100 23:46:49 +1100." <200001071246.XAA05593@avalon.reed.wattle.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 12:52:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The issue with the 3c589d is with its speed. It is falling back to > > the timeout routine to send data rather than getting an interrupt when > > the tx has happened (or something like this, I'm reporting second hand > > stuff). > > Whatever it is, results in ping times being 1000ms then 10ms then 1000ms > then 10ms...when it responds. This is typical for interrupt misconfiguration for this driver. When you get the interrupt configuration right, it works fine. (No, getting the interrupt configuration right is not a trivial task.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 13: 1:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 74421154E1 for ; Fri, 7 Jan 2000 13:00:49 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id WAA06141; Fri, 7 Jan 2000 22:00:49 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001072100.WAA06141@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <20000107201809.B17766@foobar.franken.de> from Harold Gutch at "Jan 7, 2000 08:18:09 pm" To: Harold Gutch Date: Fri, 7 Jan 2000 22:00:49 +0100 (CET) Cc: Nate Williams , Patrick Bihan-Faou , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I agree that having a `switch' type of rule for selecting interfaces > > > would be a reasonable gain of efficiency (but then again.. how > > > many interfaces is one using!) > > > > It doesn't matter, it has to do the lookup on a per-interface basis. On > > my firewall box, I have 11 interfaces. > > Two ethernet, one loopback, 4 slip, and 4 tunnel. i meant, if you only have 2-3 interfaces which are used 90% of the times, then you really have 1-2 extra rules to look for. But, in any case, it seems reasonably clear that a 'switch' statement would simplify rule writing in a number of situations, and i agree with Rod that the way ipfw does (having all rules potentially applicable for all cases) is very very flexible and probably more convenient than per-interface lists in many cases. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 13: 2: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from front2m.grolier.fr (front2m.grolier.fr [195.36.216.52]) by hub.freebsd.org (Postfix) with ESMTP id 31FD714F65; Fri, 7 Jan 2000 13:01:45 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-223-192.villette.club-internet.fr [195.36.223.192]) by front2m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id VAA12512; Fri, 7 Jan 2000 21:58:42 +0100 (MET) Date: Fri, 7 Jan 2000 22:28:44 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost Reply-To: Gerard Roudier To: Michael Reifenberger Cc: FreeBSD-SCSI , FreeBSD-Current Subject: Re: Problem exposed with sym driver In-Reply-To: Message-ID: 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 On Fri, 7 Jan 2000, Michael Reifenberger wrote: > Hi, > after enabling the sym-driver I get drive-lockups after some time of acce= ssing > the disks hanging on the sym-driver. > It seems that at least on disk hangs up (steady disk light) until a bus-r= eset > "(noperiph:sym0:0:-1:-1): SCSI BUS reset detected" occurs. >=20 > A difference between ncr and sym-driver is that the sym-driver probes the= disks > as (excerpt from dmesg_sym.txt): >=20 > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing = Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) >=20 > whereas the ncr-driver probes as (excerpt from dmesg_ncr.txt): >=20 > da1 at ncr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing = Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) >=20 > Usually the IBM-FAQ suspects a cabling/termination Problem if one has a P= roblem > at 40MHZ. Any SCSI related FAQ will suggest the same, in my opinion. But some SCSI devices may have larger margin than some others regarding cabling / termination problems and can be able to accomodate tiny problems. Some other devices may just fail in same situations. > But I have the 4 disks in a external case from kingston with a proper kab= le and > terminator and furthermore LVD-drives should have a better signal quality= =2E > Furthermore I have zero problems at 20MHZ. FYI, I have seen UltraWide SCSI Buses (single-ended) that continued work reasonnably well with a terminator just missing (was intentionnal for testing purpose). As a strangeness, only a single disk (had 4 on the BUS)= =20 required to decrease speed at 33 MB/s (16.? MHz wide) for it to work apparently (seems actually) well. As you can see, even a serious BUS problem may, in some situations, allow the SCSI system to work by just lowering speed of some devices on the bus. > You can see in neg_before.txt the output of a 'camcontrol neg' which look= right, > in neg_after.txt the output of the same command after the disk hang up an= d > the bus reseted. > neg_ncr.txt contains the output using the ncr-driver. >=20 > BTW: I have the same problems with the ncr-driver when using the kernel-c= onfig > parameter: SCSI_NCR_DFLT_SYNC=3D10=20 >=20 > And now the question: Whats going wrong? Probably something related to the SCSI BUS (or devices), but not to software drivers, in my opinion.=20 > If it is the HW, how can it be proven? Are it the IBM-disks? Kabel?... > Is it the Software? > If I want to live with 40MB/s is there a knob to pre-set the speed in the > kernel-config or at boot-time? For the sym driver, you just have to configure SCSI devices accordingly in the NVRAM. The sym driver hears from you by reading the NVRAM when it is able to understand its layout and your kernel log messages let me think it was able to read the controller NVRAM. (Ctrl/C at boot-up for the SYMBIOS SDMS BIOS, and then configure your device settings).=20 > Any clues? Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 13:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by hub.freebsd.org (Postfix) with ESMTP id BD200154E1 for ; Fri, 7 Jan 2000 13:13:49 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm8d36.iae.nl [212.61.1.35]) by iaehv.iae.nl (Postfix) with ESMTP id 9E54A7DA1; Fri, 7 Jan 2000 22:13:47 +0100 (CET) Message-ID: <3876570B.37E7EEE9@iae.nl> Date: Fri, 07 Jan 2000 22:13:47 +0100 From: Hans Ottevanger X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001070405.UAA75303@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Well guys, I tried upgrading one of my older machines today to the > latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). > ...... > HEEEEELP! Whats happening!!! :-( :-( :-( > > At the moment I am stymied. I switched to a GENERIC kernel and got the > same results, so it isn't anything weird that I have done in my own > kernel config. > > I was hoping that someone would have an idea. > > -Matt I also have one of those old Pentiums, with an Intel motherboard and a Mercury chipset. And I have similar problems with CURRENT of a few days ago. When I configure my kernel to use the new ata driver, it hangs when booting. I plan to reproduce this problem this weekend, with a more recent CURRENT. I think the problem is caused by the RZ1000 EIDE controller on this type of motherboard. I suspect that the new ata driver deals with interrupts in ways somewhat different from the old wd driver. According to the Intel documentation, interrupts during data transfers may cause data corruption. This RZ1000 issue has been discussed on this list a few weeks ago, without a real solution. Kind regards, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 13:18:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (Postfix) with ESMTP id 05A11150E6 for ; Fri, 7 Jan 2000 13:18:16 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (root@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id PAA91277; Fri, 7 Jan 2000 15:18:15 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.3/8.9.1) id PAA52625; Fri, 7 Jan 2000 15:18:52 -0600 (CST) Date: Fri, 7 Jan 2000 16:18:52 -0500 From: Nathan Dorfman To: Matthew Jacob Cc: Thomas Veldhouse , Adam , freebsd-current@FreeBSD.ORG Subject: Re: installing over the wire with a tulip card... Message-ID: <20000107161852.A52010@rtfm.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Matthew Jacob on Fri, Jan 07, 2000 at 09:48:22AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 09:48:22AM -0800, Matthew Jacob wrote: > > This shouldn't be a PNP-OS issue because this is a PCI card- the card is > seen during booting- which means it's getting detected. I don't know why > 'ifconfig -l' doesn't see it though. I had an identical problem with de0 and 3.4 installation disks. Setting the PNP-OS to NO in BIOS resolved the issue. -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 13:32: 3 2000 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 A4BE115854 for ; Fri, 7 Jan 2000 13:31:57 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id WAA02950 for current@FreeBSD.org; Fri, 7 Jan 2000 22:14:55 +0100 (CET) (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: Fri, 07 Jan 2000 22:14:53 +0100 From: Marcel Moolenaar Message-ID: <3876574D.C0411037@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: world broken in libcrypt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neal Westfall wrote: > > ===> ../secure/lib/libcrypt > make: don't know how to make crypt-shs.c. Stop > *** Error code 2 Fixed. Thanks! -- 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 Fri Jan 7 14: 7:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 563F6150A0 for ; Fri, 7 Jan 2000 14:07:36 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 52520 invoked from network); 7 Jan 2000 22:07:34 -0000 Received: from dhcp-mtl-200.local.mindstep.com (HELO patrak) (192.168.10.200) by jacuzzi.local.mindstep.com with SMTP; 7 Jan 2000 22:07:34 -0000 Message-ID: <011d01bf595b$99929640$c80aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Luigi Rizzo" , "Harold Gutch" , Cc: "Nate Williams" References: <200001072100.WAA06141@info.iet.unipi.it> Subject: Re: ipfw optimizations Date: Fri, 7 Jan 2000 17:07:33 -0500 Organization: MindStep Corporation 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 (don't you love all that quoting...) > > > > I agree that having a `switch' type of rule for selecting interfaces > > > > would be a reasonable gain of efficiency (but then again.. how > > > > many interfaces is one using!) > > > > > > It doesn't matter, it has to do the lookup on a per-interface basis. On > > > my firewall box, I have 11 interfaces. > > > Two ethernet, one loopback, 4 slip, and 4 tunnel. > > i meant, if you only have 2-3 interfaces which are used 90% of the times, > then you really have 1-2 extra rules to look for. > But, in any case, it seems reasonably clear that a 'switch' > statement would simplify rule writing in a number of situations, > and i agree with Rod that the way ipfw does (having all rules > potentially applicable for all cases) is very very flexible > and probably more convenient than per-interface lists in many > cases. Yes I agree, I love ipfw functionality. You were asking for ideas on how to optimize ipfw. What I suggested is that in its INTERNAL representation of the rules, ipfw could split the rules on a per interface/direction basis. This means that you will not look at the rules that are known to not apply to your interface AND direction, hence saving some time. Again I am not asking for modification of the "user interface" of ipfw which is nice and to the point. As you and Rod mention, the ability to have rules applicable to all interfaces in one shot is great. What I was thinking about is when you build the "per-interface" list of rules, use what is provided in the interface part of the rule to determine where it belongs: ipfw add allow ip from joe to bob in recv ed0 => this rule is to be added only in the inbound list for interface ed0 ipfw add allow ip from joe to bob via ed0 => this rule is to be added to both inbound and outbound lists for i/f ed0 ipfw add allow ip from joe to bob => this rule is to be added to the inbound and outbound lists for all i/fs In the future we could also use negative logic to add a rule to all interfaces except the one mentioned... Also as I said earlier, you don't have to do anymore interface checking when it is implemented this way. The fact that you use such or such list is enough. Also to respond to some comments from Rod, this scheme duplicates the rules, but it does so behind the scene, so it does not add more complexity to the way you configure ipfw. Actually it remains completely compatible with the current behaviour of ipfw. Is that SO unreasonable ???? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 14:11:14 2000 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 76A0E14BF5 for ; Fri, 7 Jan 2000 14:11:02 -0800 (PST) (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 RAA19464 for ; Fri, 7 Jan 2000 17:11:00 -0500 (EST) Received: from newlgn49.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08940; Fri, 7 Jan 2000 17:10:30 -0500 From: Brad Chisholm Received: by newlgn49.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA10196; Fri, 7 Jan 2000 17:10:30 -0500 Message-Id: <200001072210.AA10196@newlgn49.unx.sas.com> Subject: Adaptec AAC-364 RAID controller support To: freebsd-current@FreeBSD.ORG Date: Fri, 7 Jan 2000 17:10:30 -0500 (EST) X-Mailer: ELM [version 2.5 PL0] 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 see from the FreeBSD driver database at http://www.posi.net/freebsd/drivers that support for the Adaptec AAC-364 RAID controller (aka Dell PERC 2) has been proposed, but it is stalled waiting on documentation from Adaptec. For what it's worth, you can add us to the list of people who have these cards and would very much like to use them under FreeBSD. Is there someone at Adaptec I could contact to "encourage" them to release the documentation we require? At the very least, it might be worthwhile to let them know there's interest in using their cards with FreeBSD. Once the development is able to proceed, I'd be happy to lend a hand where possible, even if only to test development versions of the driver. We're currently running different arrays with: 1) DPT SmartRAID IV 2) AMI MegaRAID Enterprise 1200 3) Vinum (raid 10) The Adaptec card looks like it might provide a superior solution. What's best way to proceed when trying to get documentation support from vendors? -- Brad Chisholm SAS Institute, 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 Jan 7 14:20: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 422F314BD5 for ; Fri, 7 Jan 2000 14:20:04 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 17416 invoked by uid 1001); 7 Jan 2000 22:19:20 -0000 Date: Fri, 7 Jan 2000 14:19:20 -0800 From: Jason Evans To: current@freebsd.org Subject: __sigisempty() undefined if "cc -g" used. Message-ID: <20000107141920.J4938@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g (and later CFLAGS=-g3), but ran into linker problems as a result. blitz:~> gcc poll.c -pthread /usr/lib/libc_r.so: undefined reference to `__sigisempty' Even the simplest of C programs will get this linker error if using the -pthread option. So, __sigisempty is an inline function, defined in /usr/include/sys/signalvar.h: extern __inline int __sigisempty(sigset_t *set) { int i; for (i = 0; i < _SIG_WORDS; i++) { if (set->__bits[i]) return (0); } return (1); } __sigisempty() is used in the expansion of SIGNOTEMPTY in /usr/src/lib/libc_r/uthread/uthread_sig[wait].c. SIGNOTEMPTY is: #define SIGNOTEMPTY(set) (!__sigisempty(&(set))) Both of those files correctly #include . If I compile those two files without the -g flag, the linker error goes away. In summary, it seems that using the -g flag to gcc can cause inline functions to be ignored. Can anyone shed some light on this? Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 14:23:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id F349214C9A for ; Fri, 7 Jan 2000 14:23:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02863; Fri, 7 Jan 2000 14:29:34 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001072229.OAA02863@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Chisholm Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec AAC-364 RAID controller support In-reply-to: Your message of "Fri, 07 Jan 2000 17:10:30 EST." <200001072210.AA10196@newlgn49.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 14:29:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see from the FreeBSD driver database at http://www.posi.net/freebsd/drivers > that support for the Adaptec AAC-364 RAID controller (aka Dell PERC 2) has > been proposed, but it is stalled waiting on documentation from Adaptec. > > For what it's worth, you can add us to the list of people who have these > cards and would very much like to use them under FreeBSD. Is there someone > at Adaptec I could contact to "encourage" them to release the documentation > we require? At the very least, it might be worthwhile to let them know > there's interest in using their cards with FreeBSD. I've tried most of the avenues available to me so far; things were looking sort-of OK until they acquired DPT, at which point the entire division had some sort of falling seizure. If you're a sizeable Dell customer, I do believe that there are two people at Dell that have access to the requisite information as well as authorisation to release it. You may consider that avenue of approach as well. > We're currently running different arrays with: > > 1) DPT SmartRAID IV > 2) AMI MegaRAID Enterprise 1200 > 3) Vinum (raid 10) > > The Adaptec card looks like it might provide a superior solution. The aac-364 is likely to offer similar performance to the AMI MegaRAID Enterprise 1500 and the Mylex eXtremeRAID 1164 controllers, both of which we're currently supporting. I'm hesitant to pursue the Adaptec controller particularly aggressively just now given the availability of documented and functional alternatives (although I'd happy work on a driver should documentation come my way). > What's > best way to proceed when trying to get documentation support from vendors? I've typically had the best results with a friendly contact inside the organisation; once you have someone that actually knows how the organisation works you have a chance of tracking down the relevant people to get the information you need. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 14:35: 6 2000 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 CB82B14BF5 for ; Fri, 7 Jan 2000 14:35:00 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA13343; Fri, 7 Jan 2000 14:34:19 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001072234.OAA13343@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <011d01bf595b$99929640$c80aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Jan 7, 2000 05:07:33 pm" To: patrick@mindstep.com (Patrick Bihan-Faou) Date: Fri, 7 Jan 2000 14:34:19 -0800 (PST) Cc: luigi@info.iet.unipi.it (Luigi Rizzo), logix@foobar.franken.de (Harold Gutch), freebsd-current@FreeBSD.ORG, nate@mt.sri.com (Nate Williams) 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 I agree, I love ipfw functionality. You were asking for ideas on how to > optimize ipfw. What I suggested is that in its INTERNAL representation of > the rules, ipfw could split the rules on a per interface/direction basis. > This means that you will not look at the rules that are known to not apply > to your interface AND direction, hence saving some time. > > Again I am not asking for modification of the "user interface" of ipfw which > is nice and to the point. > > As you and Rod mention, the ability to have rules applicable to all > interfaces in one shot is great. > > What I was thinking about is when you build the "per-interface" list of > rules, use what is provided in the interface part of the rule to determine > where it belongs: > > > ipfw add allow ip from joe to bob in recv ed0 > => this rule is to be added only in the inbound list for interface ed0 > > ipfw add allow ip from joe to bob via ed0 > => this rule is to be added to both inbound and outbound lists for i/f > ed0 > > ipfw add allow ip from joe to bob > => this rule is to be added to the inbound and outbound lists for all > i/fs Now I see what you are getting at. > > In the future we could also use negative logic to add a rule to all > interfaces except the one mentioned... > > Also as I said earlier, you don't have to do anymore interface checking when > it is implemented this way. The fact that you use such or such list is > enough. Gotcha, this could potentially eliminate a lot of compare operations. > Also to respond to some comments from Rod, this scheme duplicates the rules, > but it does so behind the scene, so it does not add more complexity to the > way you configure ipfw. Actually it remains completely compatible with the > current behaviour of ipfw. > > Is that SO unreasonable ???? No, this is completly reasonable now that I understand what it is your proposing. Even the memory footprint is minimal if pointers to the actual rules is all we store in the per interface list, my largest set duplicated over 8 interfaces would only be 3200 rules. Stored as pointers to rules this would be all of 12.8kbytes, certainly not enough to worry about :-). Come up with some patches and I'll be glad to test and review them for you... -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 14:36:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id E967F14DF9; Fri, 7 Jan 2000 14:36:20 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.21.69] (dialup581.brussels.skynet.be [195.238.21.69]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA06988; Fri, 7 Jan 2000 23:36:19 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001072229.OAA02863@mass.cdrom.com> References: <200001072229.OAA02863@mass.cdrom.com> Date: Fri, 7 Jan 2000 23:35:26 +0100 To: Mike Smith , Brad Chisholm From: Brad Knowles Subject: Re: Adaptec AAC-364 RAID controller support Cc: freebsd-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 2:29 PM -0800 2000/1/7, Mike Smith wrote: > The aac-364 is likely to offer similar performance to the AMI MegaRAID > Enterprise 1500 and the Mylex eXtremeRAID 1164 controllers, both of which > we're currently supporting. I'd be very interested to see a comparison of these controllers against the DPT SmartRAID V and SmartRAID VI controllers, drivers for which I believe should be available (or available very shortly). -- 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 Fri Jan 7 14:36:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 4B17B14E5B for ; Fri, 7 Jan 2000 14:36:21 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.21.69] (dialup581.brussels.skynet.be [195.238.21.69]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA06976; Fri, 7 Jan 2000 23:36:10 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001072210.AA10196@newlgn49.unx.sas.com> References: <200001072210.AA10196@newlgn49.unx.sas.com> Date: Fri, 7 Jan 2000 23:33:20 +0100 To: Brad Chisholm , freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: Adaptec AAC-364 RAID controller support Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:10 PM -0500 2000/1/7, Brad Chisholm wrote: > The Adaptec card looks like it might provide a superior solution. What's > best way to proceed when trying to get documentation support from vendors? Look long and hard at software solutions with vinum before you wed yourself to a particular hardware RAID controller. At the very least, I'd encourage you to extensively benchmark all the candidate solutions in your environment, before you make a choice. You can see my own benchmarks that I've done so far at . -- 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 Fri Jan 7 14:48:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 2A18915887 for ; Fri, 7 Jan 2000 14:48:19 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 52643 invoked from network); 7 Jan 2000 22:48:15 -0000 Received: from dhcp-mtl-200.local.mindstep.com (HELO patrak) (192.168.10.200) by jacuzzi.local.mindstep.com with SMTP; 7 Jan 2000 22:48:15 -0000 Message-ID: <014501bf5961$48cc6dc0$c80aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Rodney W. Grimes" Cc: "Luigi Rizzo" , "Harold Gutch" , , "Nate Williams" References: <200001072234.OAA13343@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations Date: Fri, 7 Jan 2000 17:48:15 -0500 Organization: MindStep Corporation 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 > No, this is completly reasonable now that I understand what it is your > proposing. Even the memory footprint is minimal if pointers to the > actual rules is all we store in the per interface list, my largest set > duplicated over 8 interfaces would only be 3200 rules. Stored as > pointers to rules this would be all of 12.8kbytes, certainly not > enough to worry about :-). Good.... I felt like I was stupid for a while here ;-) > Come up with some patches and I'll be glad to test and review them > for you... I'll get on that as soon as I am done with that paying job I am doing now :(. Which probably means sometime next week. (don't you hate to have these bills to pay ?) Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 15:40:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 21410157C4 for ; Fri, 7 Jan 2000 15:40:51 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id AAA06578; Sat, 8 Jan 2000 00:40:54 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001072340.AAA06578@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <200001072234.OAA13343@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Jan 7, 2000 02:34:19 pm" To: "Rodney W. Grimes" Date: Sat, 8 Jan 2000 00:40:53 +0100 (CET) Cc: Patrick Bihan-Faou , Harold Gutch , freebsd-current@FreeBSD.ORG, Nate Williams X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, this is completly reasonable now that I understand what it is your > proposing. Even the memory footprint is minimal if pointers to the > actual rules is all we store in the per interface list, my largest set > duplicated over 8 interfaces would only be 3200 rules. Stored as I'd be curious to know what your 400-rule set looks like, what is the longest search path through that ruleset, and whether that ruleset could be made more efficient to run by implementing some kind of switch() statement (eg. for selecting based on interfaces), or hash tables (e.g. you want to allow/deny to a list of random addresses...). cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 15:53:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from gate.consol.de (gate.consol.de [194.221.87.10]) by hub.freebsd.org (Postfix) with ESMTP id 11C6B14DC1 for ; Fri, 7 Jan 2000 15:53:48 -0800 (PST) (envelope-from Michael.Elbel@consol.de) X-Envelope-Sender-Is: Michael.Elbel@consol.de (at relayer gate.consol.de) Received: from msgsrv.bb.consol.de (root@msgsrv.bb.consol.de [10.250.0.100]) by gate.consol.de (8.9.3/8.9.1) with ESMTP id AAA99833; Sat, 8 Jan 2000 00:53:45 +0100 (CET) From: Michael.Elbel@consol.de Received: from vscanner.bb.consol.de (root@vscanner.bb.consol.de [10.250.0.120]) by msgsrv.bb.consol.de (8.8.8/8.8.8) with ESMTP id AAA27436; Sat, 8 Jan 2000 00:53:48 +0100 Received: from fourier.int.consol.de (fourier.int.consol.de [10.0.1.17]) by vscanner.bb.consol.de (8.9.3/8.9.3) with ESMTP id AAA01482; Sat, 8 Jan 2000 00:53:11 +0100 Received: (from me@localhost) by fourier.int.consol.de (8.9.3/8.8.7) id AAA88807; Sat, 8 Jan 2000 00:53:26 +0100 (CET) (envelope-from me) Date: Sat, 8 Jan 2000 00:53:26 +0100 (CET) X-Amavis-approved: Yes Message-Id: <200001072353.AAA88807@fourier.int.consol.de> To: jkh@zippy.cdrom.com Cc: current@freebsd.org Subject: Re: So, tell me again why we can't read audio CDs in SCSI drives? Newsgroups: lists.freebsd.current References: <6956.947217921@zippy.cdrom.com> Reply-To: me@freebsd.org X-Newsreader: NN version 6.5.0 CURRENT #123 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In lists.freebsd.current you write: >Any other SCSI CD owners here currently using tosha? I'd be >quite interested to know if this is drive-specific. Works perfectly for me: cd0: Removable CD-ROM SCSI-2 device Michael -- \|/ -O- Michael Elbel, ConSol* GmbH, - me@consol.de - 089 / 45841-256 /|\ Fermentation fault (coors dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 16:31:29 2000 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 3BA2214BCC for ; Fri, 7 Jan 2000 16:31:25 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id QAA13581; Fri, 7 Jan 2000 16:31:00 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001080031.QAA13581@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <200001072340.AAA06578@info.iet.unipi.it> from Luigi Rizzo at "Jan 8, 2000 00:40:53 am" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Fri, 7 Jan 2000 16:31:00 -0800 (PST) Cc: patrick@mindstep.com (Patrick Bihan-Faou), logix@foobar.franken.de (Harold Gutch), freebsd-current@FreeBSD.ORG, nate@mt.sri.com (Nate Williams) 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 > > No, this is completly reasonable now that I understand what it is your > > proposing. Even the memory footprint is minimal if pointers to the > > actual rules is all we store in the per interface list, my largest set > > duplicated over 8 interfaces would only be 3200 rules. Stored as > > I'd be curious to know what your 400-rule set looks like, what is > the longest search path through that ruleset, and whether that > ruleset could be made more efficient to run by implementing some > kind of switch() statement (eg. for selecting based on interfaces), > or hash tables (e.g. you want to allow/deny to a list of random > addresses...). If you search the archives you'll find a function I wrote in /bin/sh called clnsrv is what creates 90% of the rules. Ahh.. hech.. here... # clnsrv(action, proto, sport, dport, clients, servers) clnsrv() { action=$1; shift proto=$1; shift sport=$1; shift dport=$1; shift clients=$1; shift servers=$1; shift if [ X"${proto}" = X"tcp" ]; then setup="setup" base=10000 else setup="" base=40000 fi if [ X"${dport}" = X"" ]; then ruleoffset=${sport} else ruleoffset=${dport} fi if [ ${ruleoffset} -gt 1899 ]; then ruleoffset=1900 fi rule=`expr ${base} + \( ${ruleoffset} \* 10 \)` for cln in ${clients} ; do for srv in ${servers} ; do ${fadd} ${rule} ${action} ${proto} \ from ${cln} ${sport} to ${srv} ${dport} ${setup} done done rule=`expr ${rule} + 9` ${fadd} ${rule} ${CLASS} log ${proto} from any ${sport} to any ${dport} } Then this is called like so: clnsrv "allow " tcp 20 "" "${tcp_ftpdata_c}" "${tcp_ftpdata_s}" clnsrv "allow " tcp "" 21 "${tcp_ftp_c}" "${tcp_ftp_s}" clnsrv "allow " tcp "" 22 "${tcp_ssh_c}" "${tcp_ssh_s}" clnsrv "allow " tcp "" 23 "${tcp_telnet_c}" "${tcp_telnet_s}" clnsrv "allow " tcp "" 25 "${tcp_smtp_c}" "${tcp_smtp_s}" clnsrv "allow " tcp "" 43 "${tcp_nicname_c}" "${tcp_nicname_s}" clnsrv "allow " tcp "" 53 "${tcp_domain_c}" "${tcp_domain_s}" clnsrv "allow " tcp "" 79 "${tcp_finger_c}" "${tcp_finger_s}" clnsrv "allow " tcp "" 80 "${tcp_http_c}" "${tcp_http_s}" clnsrv "allow " tcp "" 110 "${tcp_pop3_c}" "${tcp_pop3_s}" clnsrv "allow " tcp "" 111 "${tcp_sunrpc_c}" "${tcp_sunrpc_s}" clnsrv "allow " tcp "" 113 "${tcp_ident_c}" "${tcp_ident_s}" ... on and on up to the 1024 and then a few splattered after that. Note that those variables ``tcp_ftp_c'' are often long lists of IP prefixes, and tcp_ftp_s is a single IP or ``any'', dependent on where this firewall is in the network topology, so these calls can quickly build into fairly long ipfw lists. Often the _c and _s will be lists, causing the double nested loop to product a few not so meaningful rules, but that has been fairly rare, bgp being the big exception :-). Also this same routine is called again for a whole pile of udp ports. The single largest optimization would probably be a dispatch based on source or destination port, the latter being more prevelent. I can't easily send out the actual IP firewall list, it may expose what ever router I grabbed it off of to an attack :-) -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 7 16:36:16 2000 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 CD41714C13 for ; Fri, 7 Jan 2000 16:36:12 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id TAA05054; Fri, 7 Jan 2000 19:36:11 -0500 (EST) (envelope-from luoqi) Date: Fri, 7 Jan 2000 19:36:11 -0500 (EST) From: Luoqi Chen Message-Id: <200001080036.TAA05054@lor.watermarkgroup.com> To: current@FreeBSD.ORG, jasone@canonware.com Subject: Re: __sigisempty() undefined if "cc -g" used. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > (and later CFLAGS=-g3), but ran into linker problems as a result. > > blitz:~> gcc poll.c -pthread > /usr/lib/libc_r.so: undefined reference to `__sigisempty' > > Even the simplest of C programs will get this linker error if using the > -pthread option. > > So, __sigisempty is an inline function, defined in > /usr/include/sys/signalvar.h: > > extern __inline int > __sigisempty(sigset_t *set) > { > int i; > > for (i = 0; i < _SIG_WORDS; i++) { > if (set->__bits[i]) > return (0); > } > return (1); > } > It doesn't make much sense to have an "extern" inline function, gcc probably was confused by this, change "extern" to "static" and try again. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 17: 9:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 37ABA1599D for ; Fri, 7 Jan 2000 17:09:12 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 17992 invoked by uid 1001); 8 Jan 2000 01:08:27 -0000 Date: Fri, 7 Jan 2000 17:08:27 -0800 From: Jason Evans To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: __sigisempty() undefined if "cc -g" used. Message-ID: <20000107170827.S4938@sturm.canonware.com> References: <200001080036.TAA05054@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001080036.TAA05054@lor.watermarkgroup.com>; from luoqi@watermarkgroup.com on Fri, Jan 07, 2000 at 07:36:11PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 07:36:11PM -0500, Luoqi Chen wrote: > > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > > (and later CFLAGS=-g3), but ran into linker problems as a result. > > > > blitz:~> gcc poll.c -pthread > > /usr/lib/libc_r.so: undefined reference to `__sigisempty' > > > > Even the simplest of C programs will get this linker error if using the > > -pthread option. > > > > So, __sigisempty is an inline function, defined in > > /usr/include/sys/signalvar.h: > > > > extern __inline int > > __sigisempty(sigset_t *set) > > { > > int i; > > > > for (i = 0; i < _SIG_WORDS; i++) { > > if (set->__bits[i]) > > return (0); > > } > > return (1); > > } > > > It doesn't make much sense to have an "extern" inline function, gcc probably > was confused by this, change "extern" to "static" and try again. Yep, that fixed it. Thanks! I just committed the change. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 19:43:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id A3E80152A9 for ; Fri, 7 Jan 2000 19:43:47 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ivebet.dialup.mindspring.com [165.247.45.221]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id WAA18993 for ; Fri, 7 Jan 2000 22:43:38 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id WAA02407 for freebsd-current@FreeBSD.ORG; Fri, 7 Jan 2000 22:43:31 -0500 (EST) (envelope-from vsilyaev) Date: Fri, 7 Jan 2000 22:43:31 -0500 From: "Vladimir N. Silyaev" To: freebsd-current@FreeBSD.ORG Subject: world broken in dialog Message-ID: <20000107224331.A2379@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... install -c -o root -g wheel -m 444 README /usr/share/examples/dialog install: README: No such file or directory *** Error code 71 The following patch fixed the problem: --- gnu/usr.bin/dialog/TESTS/Makefile.orig Fri Jan 7 22:35:43 2000 +++ gnu/usr.bin/dialog/TESTS/Makefile Fri Jan 7 22:36:09 2000 @@ -5,7 +5,7 @@ beforeinstall: .for file in ${FILES} - ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 444 ${file} \ + ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 444 ${.CURDIR}/${file} \ ${DESTDIR}/usr/share/examples/dialog .endfor -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 20: 9:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 6236214F1E for ; Fri, 7 Jan 2000 20:09:12 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA13409 for ; Fri, 7 Jan 2000 23:09:06 -0500 (EST) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA13611 for ; Fri, 7 Jan 2000 23:09:09 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA13607 for ; Fri, 7 Jan 2000 23:09:09 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Fri, 7 Jan 2000 23:09:09 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: anyone else...? 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 wondering if anyone else was having trouble making world lately. Mine stops at wlconfig with no explanation... it just says Error 1 a couple of times and quits after it says echo wlconfig: /usr/src....libc.a I don't remember the exact line because I was in single user mode and booted from there. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems 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 Fri Jan 7 20:30:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id B3FF71512E for ; Fri, 7 Jan 2000 20:30:46 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA25232; Sat, 8 Jan 2000 13:30:42 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA00575; Sat, 8 Jan 2000 13:30:41 +0900 (JST) Received: from localhost ([192.168.245.38]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id NAA08887; Sat, 8 Jan 2000 13:30:39 +0900 (JST) To: freebsd@cybcon.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000108133114L.shin@nd.net.fujitsu.co.jp> Date: Sat, 08 Jan 2000 13:31:14 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 90 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a DEC Alpha at home running 4.0-current and am willing to help out with > the testing. I am not the worlds greatest coder, but am willing to do what I can Thanks! The 1st thing I want to be tested is that, a kernel with following additions to the config file options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_IPV6FWD #IP security tunnel for IPv6 options IPSEC_DEBUG #debug for IP security pseudo-device gif 4 #IPv6 and IPv4 tunneling pseudo-device faith 1 #for IPv6 and IPv4 translation just works fine, and also all apps on your environments which you are usually using still works fine on that kernel. Then, I would like to know if IPv6 addresses and routes are successfully installed. These can be checked by, ifconfig -a netstat -rn -f inet6 And if ping6 or traceroute6 to those addrs are successful. Then, I think something like following tests are desirable, but to do these checks, more than 1 host is necessary. Here I'll just give rough explanation. (1)IPv6 host autoconfiguration router side needs to run usr.sbin/rtadvd with rtadvd.conf config file which includes address information to be auto configured. rtadvd -c rtadvd.conf bar0 host needs to do following, sysctl -w net.inet6.ip6.accept_rtadv=1 rtsol bar0 bar0 is any interface that either of the host and the router is connected. Details are in rtadvd(8), rtadvd.conf(5), rtsol(8) (2)IPv6 communication via IPv6 router Besides (1), router needs to run IPv6 routing daemon. Currently there is usr.sbin/route6d. Also, several global addr should be assigned to each of routers interface. If no global addr, then site local addr can be used for testing.(such as fec0:0:0:1::1) You can use ifconfig or prefix command to assign them. If assigning site local addr using prefix command, prefix bar0 fec0:0:0:1000:: prefix bar1 fec0:0:0:2000:: sysctl -w net.inet6.ip6.forwarding=1 route6d -l Details are in route6d(8) (3)IPsec between 2 hosts (IPsec transport mode) Setup IPsec association using usr.sbin/setkey on each host. Specify IPsec policy for apps which would like to use IPsec. Those apps must have an option which specify IPsec policy. Usually it is -P option. (currently, only supported by ping and some daemons) Or specify IPsec policy using usr.sbin/setkey on each host. Details are in setkey(8), ping(8), ipsec_set_policy(3) (4)IPsec between 2 routers (IPsec tunnel mode) Setup IPsec association and IPsec policy using usr.sbin/setkey on each routers. Also the default route is need to be installed on each routers, due to some current IPsec tunnel mode implementation issue. Details are in setkey(8), ipsec_set_policy(3) If there is any unclear things, please ask me. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 20:40:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id E21AE15207 for ; Fri, 7 Jan 2000 20:40:34 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-5.cybcon.com [205.147.75.6]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id UAA03878; Fri, 7 Jan 2000 20:40:01 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000108133114L.shin@nd.net.fujitsu.co.jp> Date: Fri, 07 Jan 2000 20:41:43 -0800 (PST) From: William Woods To: Yoshinobu Inoue Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The 1st thing I want to be tested is that, a kernel with > following additions to the config file > > options INET6 #IPv6 communications protocols > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > options IPSEC_DEBUG #debug for IP security > > pseudo-device gif 4 #IPv6 and IPv4 tunneling > pseudo-device faith 1 #for IPv6 and IPv4 translation > > just works fine, > and also all apps on your environments which you are usually > using still works fine on that kernel. I am compiling with these options now. I will let you know how it goes. ---------------------------------- E-Mail: William Woods Date: 07-Jan-00 Time: 20:40:33 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 20:53:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 61FEE1509B for ; Fri, 7 Jan 2000 20:53:29 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-5.cybcon.com [205.147.75.6]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id UAA04705; Fri, 7 Jan 2000 20:53:26 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000108133114L.shin@nd.net.fujitsu.co.jp> Date: Fri, 07 Jan 2000 20:55:08 -0800 (PST) From: William Woods To: Yoshinobu Inoue Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > options INET6 #IPv6 communications protocols > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > options IPSEC_DEBUG #debug for IP security > > pseudo-device gif 4 #IPv6 and IPv4 tunneling > pseudo-device faith 1 #for IPv6 and IPv4 translation Well, kernel compiled and booted just fine with these and all seems well. > ifconfig -a > netstat -rn -f inet6 Here is the output from ifconfig -a: bash-2.03$ ifconfig -a de0: flags=8843 mtu 1500 inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80:1::200:f8ff:fe23:5cb5 prefixlen 64 ether 00:00:f8:23:5c:b5 media: autoselect (10baseT/UTP) status: active supported media: autoselect 10base5/AUI manual 10baseT/UTP 10baseT/UTP sl0: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80:4::1 prefixlen 64 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010 mtu 1280 inet6 fe80:5::200:f8ff:fe23:5cb5 prefixlen 64 gif1: flags=8010 mtu 1280 inet6 fe80:6::200:f8ff:fe23:5cb5 prefixlen 64 gif2: flags=8010 mtu 1280 inet6 fe80:7::200:f8ff:fe23:5cb5 prefixlen 64 gif3: flags=8010 mtu 1280 inet6 fe80:8::200:f8ff:fe23:5cb5 prefixlen 64 faith0: flags=8002 mtu 1500 and the output from netstat -rn -f inet bash-2.03$ netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.0.1 UGSc de0 127.0.0.1 127.0.0.1 UH lo0 192.168 link#1 UC de0 => 192.168.0.1 0:50:4:f1:b5:7b UHLW de0 1024 > And if ping6 or traceroute6 to those addrs are successful. bash-2.03$ ping6 192.168.0.1 ping6: No address associated with hostname All tests were done on a DEC Alphastation 233, running: 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Sat Jan 8 18:46:15 PST 2000 ---------------------------------- E-Mail: William Woods Date: 07-Jan-00 Time: 20:50:41 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 20:59:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 8C34C14F1E for ; Fri, 7 Jan 2000 20:59:43 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p114.rlz.netvision.net.il [62.0.168.116]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id GAA26792; Sat, 8 Jan 2000 06:59:09 +0200 (IST) Message-ID: <3876C4C9.538309A3@freenet.co.uk> Date: Sat, 08 Jan 2000 05:02:01 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: William Woods Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > and the output from netstat -rn -f inet6 > > bash-2.03$ netstat -rn -f inet ^^^^^ inet6? > Routing tables > > Internet: > Destination Gateway Flags Netif Expire > default 192.168.0.1 UGSc de0 > 127.0.0.1 127.0.0.1 UH lo0 > 192.168 link#1 UC de0 => > 192.168.0.1 0:50:4:f1:b5:7b UHLW de0 1024 > > > And if ping6 or traceroute6 to those addrs are successful. > > bash-2.03$ ping6 192.168.0.1 > ping6: No address associated with hostname 192.168.0.1 is not a valid IPv6 address. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 21: 7:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 6BE2614FB8 for ; Fri, 7 Jan 2000 21:07:16 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-5.cybcon.com [205.147.75.6]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id VAA05489; Fri, 7 Jan 2000 21:07:04 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3876C4C9.538309A3@freenet.co.uk> Date: Fri, 07 Jan 2000 21:08:46 -0800 (PST) From: William Woods To: Alex Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sorry... bash-2.03# netstat -rn -f inet6 Routing tables Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::@de0/64 link#1 UC de0 fe80::@lo0/64 fe80::1@lo0 Uc lo0 fe80::@gif0/64 fe80::200:f8ff:fe23:5cb5@gif0 Uc gif0 fe80::200:f8ff:fe23:5cb5@gif0 ::1 UH lo0 fe80::@gif1/64 fe80::200:f8ff:fe23:5cb5@gif1 Uc gif1 fe80::200:f8ff:fe23:5cb5@gif1 ::1 UH lo0 fe80::@gif2/64 fe80::200:f8ff:fe23:5cb5@gif2 Uc gif2 fe80::200:f8ff:fe23:5cb5@gif2 ::1 UH lo0 fe80::@gif3/64 fe80::200:f8ff:fe23:5cb5@gif3 Uc gif3 fe80::200:f8ff:fe23:5cb5@gif3 ::1 UH lo0 ff01::/32 ::1 U lo0 ff02::@de0/32 link#1 UC de0 ff02::@lo0/32 fe80::1@lo0 UC lo0 ff02::@gif0/32 fe80::200:f8ff:fe23:5cb5@gif0 UC gif0 ff02::@gif1/32 fe80::200:f8ff:fe23:5cb5@gif1 UC gif1 ff02::@gif2/32 fe80::200:f8ff:fe23:5cb5@gif2 UC gif2 ff02::@gif3/32 fe80::200:f8ff:fe23:5cb5@gif3 UC gif3 and bash-2.03# ping6 fe80::200:f8ff:fe23:5cb5@gif0 PING6(64=40+8+16 bytes) fe80::200:f8ff:fe23:5cb5 --> fe80::200:f8ff:fe23:5cb5 24 bytes from fe80::200:f8ff:fe23:5cb5, icmp_seq=0 hlim=64 time=0.956 ms 24 bytes from fe80::200:f8ff:fe23:5cb5, icmp_seq=1 hlim=64 time=0.458 ms 24 bytes from fe80::200:f8ff:fe23:5cb5, icmp_seq=2 hlim=64 time=0.441 ms and bash-2.03# traceroute6 fe80::200:f8ff:fe23:5cb5@gif0 traceroute6: unknown host fe80::200:f8ff:fe23:5cb5@gif0 Forgive mistakes, just trying to help....... On 08-Jan-00 Alex wrote: > William Woods wrote: >> and the output from netstat -rn -f inet6 >> >> bash-2.03$ netstat -rn -f inet > ^^^^^ > > inet6? > > > >> Routing tables >> >> Internet: >> Destination Gateway Flags Netif Expire >> default 192.168.0.1 UGSc de0 >> 127.0.0.1 127.0.0.1 UH lo0 >> 192.168 link#1 UC de0 => >> 192.168.0.1 0:50:4:f1:b5:7b UHLW de0 1024 >> >> > And if ping6 or traceroute6 to those addrs are successful. >> >> bash-2.03$ ping6 192.168.0.1 >> ping6: No address associated with hostname > > > 192.168.0.1 is not a valid IPv6 address. > > Alex ---------------------------------- E-Mail: William Woods Date: 07-Jan-00 Time: 21:05:37 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 21:17:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id CBE6C1514A for ; Fri, 7 Jan 2000 21:17:10 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id OAA19287; Sat, 8 Jan 2000 14:16:42 +0900 (JST) To: William Woods Cc: Alex , freebsd-current@FreeBSD.ORG In-reply-to: freebsd's message of Fri, 07 Jan 2000 21:08:46 PST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6 testing...willing to help From: itojun@iijlab.net Date: Sat, 08 Jan 2000 14:16:42 +0900 Message-ID: <19285.947308602@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >bash-2.03# traceroute6 fe80::200:f8ff:fe23:5cb5@gif0 >traceroute6: unknown host fe80::200:f8ff:fe23:5cb5@gif0 >Forgive mistakes, just trying to help....... sorry traceroute6 is not friendly with "fe80::1@ef0" format. i'll be updating it in kame tree and shin can bring it back to freebsd. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 21:21:17 2000 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 81E3114F0C for ; Fri, 7 Jan 2000 21:21:15 -0800 (PST) (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.9.3) with ESMTP id VAA04508 for ; Fri, 7 Jan 2000 21:20:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001080520.VAA04508@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: atap cd? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 21:20:49 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG {root} mount -t cd9660 /dev/acd0a /cdrom cd9660: Block device required {root} mount /dev/acd0a /cdrom mount: Block device required Partial dmesg output: acd0: CDROM drive at ata0 as slave acd0: read 7562KB/s (7562KB/s), 128KB buffer, UDMA33 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked config file: controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives options ATA_ENABLE_ATAPI_DMA ls -ald /dev/acd0c brw-r----- 1 root operator 19, 2 Jan 7 20:27 /dev/acd0c -- 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 Fri Jan 7 22:35:11 2000 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 2EBAE14F82 for ; Fri, 7 Jan 2000 22:35:08 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:V8uMPUe9403ThaidjpsxgwsZp2m4OJgI@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id PAA14474; Sat, 8 Jan 2000 15:35:03 +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 PAA15557; Sat, 8 Jan 2000 15:40:27 +0900 (JST) Message-Id: <200001080640.PAA15557@zodiac.mech.utsunomiya-u.ac.jp> To: "Allen Pulsifer" Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: console support (was RIDE for BSD) In-reply-to: Your message of "Tue, 04 Jan 2000 11:05:03 EST." References: Date: Sat, 08 Jan 2000 15:40:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I second this. I'm not a linux user, but as a FreeBSD newbie >I had a lot of trouble getting anywhere with console programs, >esp. emacs and various IDE's that I tried to install. The key >board mapping was difficult/impossible to figure out, and it [...] If the program in question is written so that it will properly use termcap, and your TERM environment variable is set correctly, this sort of thing shouldn't be happening. Emacs definitely works on cons25. If it isn't, there must be something wrong with your terminal settings. If the program dosn't work because it assumes a particular terinal type, it won't work on many serial terminal and X terminal emulators. This is not the way the UNIX program should be written. I would rather blame the programmer who wrote such programs... >> -----Original Message----- >> From: owner-freebsd-questions@FreeBSD.ORG >> [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jonathon >> McKitrick >> Sent: Tuesday, January 04, 2000 9:42 AM >> To: Alexey N. Dokuchaev >> Cc: Adam; freebsd-questions@FreeBSD.ORG >> Subject: Re: RIDE for BSD >> >> On Tue, 4 Jan 2000, Alexey N. Dokuchaev wrote: >> >> >Probably improving terminal would be one of the things Fbsd might consider >> >for future releases? >> > >> >And one more thing: until I wait for cool FreeBSD native terminal support, >> >I consider copying linux-terminal descrition for my linux box termcap. Did >> >anyone do anything like this before? What problems/pitfalls should I >> >encounter? Copying the linux terminal description won't solve anything, because the Linux console and the FreeBSD console drivers are DIFFERENT. Importing the termcap entry of the linux console and use it for FreeBSD console simply won't work. >> I must admit, this is one concept i do not understand. I mean, it makes >> sense to leave the system freely configurable, but wouldn't it make sense >> that the default config be useable? For exampl,e little things, like >> linux uses bash as the default shell. [...] You can use bash in FreeBSD as well, and it works. Only that bash is not the default shell in FreeBSD :-) This is because of licensing reason. And I believe bash will not be made to default in the future too. The default configuration in FreeBSD is usable. It is unfortunate that you don't like this default configuration because it doesn't look like Linux. But, what should we do? We cannot please everybody. You see, if we adopt one configuration, I am sure someone will say "Why on earth? I don't like this configuration." If there is a sound technical reason to use one particular configuration, we can persuade people. But, if it concerns people's preference, we are in LOOSE-LOOSE situation. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 22:35:52 2000 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 E793615273 for ; Fri, 7 Jan 2000 22:35:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2BB311CC6; Sat, 8 Jan 2000 14:35:43 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: anyone else...? In-Reply-To: Message from Kenneth Wayne Culver of "Fri, 07 Jan 2000 23:09:09 EST." Date: Sat, 08 Jan 2000 14:35:43 +0800 From: Peter Wemm Message-Id: <20000108063543.2BB311CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > Just wondering if anyone else was having trouble making world lately. Mine > stops at wlconfig with no explanation... it just says Error 1 a couple of > times and quits after it says > > echo wlconfig: /usr/src....libc.a Just as a reality check.. when you've got strange problems like this, be sure to *not* use '-j' when building as this makes it very hard to see exactly what happened. The actual failure can be several screens back. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 23: 2:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax1-220.dialup.optusnet.com.au [198.142.190.220]) by hub.freebsd.org (Postfix) with ESMTP id E4CB1158AB for ; Fri, 7 Jan 2000 23:02:35 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id D7FFB5599 for ; Sat, 8 Jan 2000 18:02:30 +1100 (EST) Message-Id: <4.2.2.20000108173713.00a34f00@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 08 Jan 2000 18:02:22 +1100 To: freebsd-current@FreeBSD.ORG From: james Subject: 4.0 slower than 3.4? 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 Hi, I upgraded a few days ago from 3.4-STABLE to 4.0-CURRENT, and without really any change in configuration, anything tcp/ip is much slower. Just a standard "ping localhost" has gone from ~0.155ms to ~0.195ms. Averages for "ping -f localhost" have gone from ~0.100ms to ~0.160ms. FTP over my lan "vr0" has slipped from 7.7MB/s down to 4.8MB/s (!). I've got hardly anything running on my machine (natd, samba, postfix, pppd). 'top' shows 99-100% idle pretty much all the time. Load averages are all 0.00. CPU usage goes upto 100% during the ftp transfer. Here's the output of my dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Jan 7 00:14:59 EST 2000 death@void.dynip.com:/usr/src/sys/compile/DEATH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30040064 (29336K bytes) Preloaded elf kernel "kernel" at 0xc028b000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vr0: irq 9 at device 18.0 on pci0 vr0: Ethernet address: 00:80:c8:d8:19:b7 miibus0: on vr0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vga-pci0: irq 11 at device 19.0 on pci0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default DUMMYNET initialized (990811) IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.3 ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad2: ATA-0 disk at ata1 as master ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 Mounting root from ufs:/dev/wd0s1a Here's my kernel config: machine i386 cpu I586_CPU ident DEATH maxusers 64 options INET options FFS options FFS_ROOT options MSDOSFS options PROCFS options COMPAT_43 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options SYSVSHM options SYSVMSG options SYSVSEM controller isa0 controller pci0 controller ata0 at isa? port IO_WD1 irq 14 controller ata1 at isa? port IO_WD2 irq 15 device atadisk0 options ATA_STATIC_ID options ATA_ENABLE_ATAPI_DMA controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x20 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 controller miibus0 device vr0 pseudo-device loop pseudo-device ether pseudo-device ppp 2 pseudo-device tun 1 pseudo-device pty 16 pseudo-device md pseudo-device bpf 4 pseudo-device snp 4 options MD5 options PPP_BSDCOMP options PPP_DEFLATE options PPP_FILTER 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 IPSTEALTH options TCP_DROP_SYNFIN options TCP_RESTRICT_RST options ICMP_BANDLIM options DUMMYNET options SOFTUPDATES options NSWAPDEV=2 options QUOTA pseudo-device gzip Here's the first 4 relevant ipfw rules: 00050 allow icmp from any to any 00100 divert 8668 ip from 192.168.1.2 to any out xmit ppp0 00100 divert 8668 ip from any to any in recv ppp0 00200 allow tcp from any to any established I used the same config for 3.4. The only difference is in using ata instead of wd for my hard drives. And the new miibus controller for my ethernet card. I would've thought that 4.0 would be faster. Is it supposed to be? Does anybody know of any major difference in 4.0 that would give me these speed decreases? And possibly how to fix them? Your help is much appreciated. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 23: 7:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id 40FED15887 for ; Fri, 7 Jan 2000 23:07:15 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.218.93.188] helo=kan.ne.mediaone.net) by mx3.mail.ru with esmtp (Exim 3.02 #114) id 126pw9-000Kpa-00; Sat, 08 Jan 2000 10:05:22 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id CAA00551; Sat, 8 Jan 2000 02:06:51 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000108133114L.shin@nd.net.fujitsu.co.jp> Date: Sat, 08 Jan 2000 02:06:51 -0500 (EST) From: "Alexander N. Kabaev" To: Yoshinobu Inoue Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG These are my results: % ifconfig -a xl0: flags=8843 mtu 1500 inet6 fe80:1::250:daff:fe20:495b prefixlen 64 inet 24.218.93.188 netmask 0xfffffc00 broadcast 24.218.95.255 ether 00:50:da:20:49:5b media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10bas P 10baseT/UTP 100baseTX sl0: flags=c010 mtu 552 sl1: flags=c010 mtu 552 ppp0: flags=8010 mtu 1500 ppp1: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80:6::1 prefixlen 64 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010 mtu 1280 inet6 fe80:7::250:daff:fe20:495b prefixlen 64 gif1: flags=8010 mtu 1280 inet6 fe80:8::250:daff:fe20:495b prefixlen 64 gif2: flags=8010 mtu 1280 inet6 fe80:9::250:daff:fe20:495b prefixlen 64 gif3: flags=8010 mtu 1280 inet6 fe80:a::250:daff:fe20:495b prefixlen 64 faith0: flags=8002 mtu 1500 ds0: flags=8008 mtu 65532 % netstat -rn -f inet6 Routing tables Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::@xl0/64 link#1 UC xl0 fe80::250:daff:fe20:495b@xl0 0:50:da:20:49:5b UHLW lo0 fe80::@lo0/64 fe80::1@lo0 Uc lo0 fe80::@gif0/64 fe80::250:daff:fe20:495b@gif0 Uc gif0 fe80::250:daff:fe20:495b@gif0 ::1 UH lo0 fe80::@gif1/64 fe80::250:daff:fe20:495b@gif1 Uc gif1 fe80::250:daff:fe20:495b@gif1 ::1 UH lo0 fe80::@gif2/64 fe80::250:daff:fe20:495b@gif2 Uc gif2 fe80::250:daff:fe20:495b@gif2 ::1 UH lo0 fe80::@gif3/64 fe80::250:daff:fe20:495b@gif3 Uc gif3 fe80::250:daff:fe20:495b@gif3 ::1 UH lo0 ff01::/32 ::1 U lo0 ff02::@xl0/32 link#1 UC xl0 ff02::@lo0/32 fe80::1@lo0 UC lo0 ff02::@gif0/32 fe80::250:daff:fe20:495b@gif0 UC gif0 ff02::@gif1/32 fe80::250:daff:fe20:495b@gif1 UC gif1 ff02::@gif2/32 fe80::250:daff:fe20:495b@gif2 UC gif2 ff02::@gif3/32 fe80::250:daff:fe20:495b@gif3 UC gif3 % traceroute6 fe80:1::250:daff:fe20:495b traceroute to fe80:1::250:daff:fe20:495b (fe80:1::250:daff:fe20:495b), 30 hops max, 12 byte packets 1 fe80::250:daff:fe20:495b 0.171 ms 0.144 ms 0.091 ms % ping6 fe80:1::250:daff:fe20:495b PING6(56=40+8+8 bytes) fe80::250:daff:fe20:495b --> fe80:1::250:daff:fe20:495b 16 bytes from fe80::250:daff:fe20:495b, icmp_seq=0 hlim=64 time=0.178 ms 16 bytes from fe80::250:daff:fe20:495b, icmp_seq=1 hlim=64 time=0.129 ms 16 bytes from fe80::250:daff:fe20:495b, icmp_seq=2 hlim=64 time=0.138 ms 16 bytes from fe80::250:daff:fe20:495b, icmp_seq=3 hlim=64 time=0.133 ms ^C --- fe80:1::250:daff:fe20:495b ping6 statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.129/0.144/0.178 ms To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 7 23:52:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id A9DB115135 for ; Fri, 7 Jan 2000 23:52:25 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA27388; Sat, 8 Jan 2000 18:52:16 +1100 Date: Sat, 8 Jan 2000 18:52:12 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Luoqi Chen Cc: current@FreeBSD.ORG, jasone@canonware.com Subject: Re: __sigisempty() undefined if "cc -g" used. In-Reply-To: <200001080036.TAA05054@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 Fri, 7 Jan 2000, Luoqi Chen wrote: > > In an effort to chase down a libc_r bug, I compiled libc_r with CFLAGS=-g > > (and later CFLAGS=-g3), but ran into linker problems as a result. > > > > blitz:~> gcc poll.c -pthread > > /usr/lib/libc_r.so: undefined reference to `__sigisempty' > > > > Even the simplest of C programs will get this linker error if using the > > -pthread option. > > > > So, __sigisempty is an inline function, defined in > > /usr/include/sys/signalvar.h: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ should not be used outside of the kernel. Especially not kernel inline functions in it. User servicable parts should be in . > > extern __inline int ^^^^^^ Bug. This also breaks compiling the kernel with -O. You apparently clobbered -O in CFLAGS by setting CFLAGS=-g. -g normally needs to be added to CC to avoid breaking CFLAGS (CC='cc -g'). > > __sigisempty(sigset_t *set) > > { > > int i; > > > > for (i = 0; i < _SIG_WORDS; i++) { > > if (set->__bits[i]) > > return (0); > > } > > return (1); > > } > > > It doesn't make much sense to have an "extern" inline function, gcc probably > was confused by this, change "extern" to "static" and try again. `extern' makes sense (see gcc.info), and is extensively used in Linux, but usually it does the same things `static' except it breaks compiling with -O. It prevents zillions of copies of the function being produced (non-inline) in certain cases where inlining is not done (e.g., with -O). A normal non-inline extern version of the function must be provided to handle these cases. Sloppy use of `extern inline' doesn't provide the extern function. Forcing use of the extern version may be useful for profiling and similar instrumentation (-finstrument-functions?), and for debugging. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0: 1:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id 9D256151B3 for ; Sat, 8 Jan 2000 00:01:42 -0800 (PST) (envelope-from jyoung@accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Sat, 8 Jan 2000 02:01:38 -0600 Message-ID: From: Jason Young To: 'james' , freebsd-current@FreeBSD.ORG Subject: RE: 4.0 slower than 3.4? Date: Sat, 8 Jan 2000 02:01:38 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, several possible issues.. It probably isn't the best of all ideas to have BOTH IP firewalling solutions installed and running at once. This will add some overhead. Pick one and stick with it. And why do you have DUMMYNET running? There is a new version of IPFilter in -CURRENT if I recall correctly, and this may be related to your timing issues. Really you ought to just take IPFILTER out of your configuration. Aside from that, you'll need to use 'top' or some similar utility to find out where and why you're CPU-bound for FTP transfers. Find out if you're primarily stuck in the kernel, or if some userland utility is sucking it up (like natd, but your ipfw rules tend to rule out accidentally running ethernet traffic through natd). Jason Young accessUS Chief Network Engineer > -----Original Message----- > From: james [mailto:death@southcom.com.au] > Sent: Saturday, January 08, 2000 1:02 AM > To: freebsd-current@FreeBSD.ORG > Subject: 4.0 slower than 3.4? > > > > Hi, > > I upgraded a few days ago from 3.4-STABLE to 4.0-CURRENT, and without > really any change in configuration, anything tcp/ip is much > slower. Just a > standard "ping localhost" has gone from ~0.155ms to ~0.195ms. > Averages for > "ping -f localhost" have gone from ~0.100ms to ~0.160ms. FTP > over my lan > "vr0" has slipped from 7.7MB/s down to 4.8MB/s (!). > > I've got hardly anything running on my machine (natd, samba, postfix, > pppd). 'top' shows 99-100% idle pretty much all the time. > Load averages are > all 0.00. CPU usage goes upto 100% during the ftp transfer. > > Here's the output of my dmesg: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > FreeBSD 4.0-CURRENT #0: Fri Jan 7 00:14:59 EST 2000 > death@void.dynip.com:/usr/src/sys/compile/DEATH > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P54C (166.19-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > Features=0x1bf > real memory = 33554432 (32768K bytes) > avail memory = 30040064 (29336K bytes) > Preloaded elf kernel "kernel" at 0xc028b000. > Intel Pentium detected, installing workaround for F00F bug > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > vr0: irq 9 at device 18.0 on pci0 > vr0: Ethernet address: 00:80:c8:d8:19:b7 > miibus0: on vr0 > amphy0: on miibus0 > amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vga-pci0: irq 11 at > device 19.0 on pci0 > ata-isa0: already registered as ata0 > ata-isa1: already registered as ata1 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3b0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > IP packet filtering initialized, divert enabled, rule-based > forwarding > enabled, default to accept, logging limited to 100 > packets/entry by default > DUMMYNET initialized (990811) > IP Filter: initialized. Default = pass all, Logging = enabled > IP Filter: v3.3.3 > ad0: ATA-4 disk at ata0 as master > ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, WDMA2 > ad2: ATA-0 disk at ata1 as master > ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S > ad2: 16 secs/int, 1 depth queue, WDMA2 > Mounting root from ufs:/dev/wd0s1a > > > Here's my kernel config: > > machine i386 > cpu I586_CPU > ident DEATH > maxusers 64 > > options INET > options FFS > options FFS_ROOT > options MSDOSFS > options PROCFS > options COMPAT_43 > options UCONSOLE > options USERCONFIG > options VISUAL_USERCONFIG > options SYSVSHM > options SYSVMSG > options SYSVSEM > > controller isa0 > controller pci0 > > controller ata0 at isa? port IO_WD1 irq 14 > controller ata1 at isa? port IO_WD2 irq 15 > device atadisk0 > options ATA_STATIC_ID > options ATA_ENABLE_ATAPI_DMA > > controller atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > > device vga0 at isa? port ? conflicts > > device sc0 at isa? > > device npx0 at nexus? port IO_NPX irq 13 > > device apm0 at nexus? disable flags 0x20 > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > > controller miibus0 > device vr0 > > pseudo-device loop > pseudo-device ether > pseudo-device ppp 2 > pseudo-device tun 1 > pseudo-device pty 16 > pseudo-device md > > pseudo-device bpf 4 > pseudo-device snp 4 > > options MD5 > options PPP_BSDCOMP > options PPP_DEFLATE > options PPP_FILTER > 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 IPSTEALTH > options TCP_DROP_SYNFIN > options TCP_RESTRICT_RST > options ICMP_BANDLIM > options DUMMYNET > options SOFTUPDATES > options NSWAPDEV=2 > options QUOTA > pseudo-device gzip > > > Here's the first 4 relevant ipfw rules: > > 00050 allow icmp from any to any > 00100 divert 8668 ip from 192.168.1.2 to any out xmit ppp0 > 00100 divert 8668 ip from any to any in recv ppp0 > 00200 allow tcp from any to any established > > > I used the same config for 3.4. The only difference is in > using ata instead > of wd for my hard drives. And the new miibus controller for > my ethernet card. > > I would've thought that 4.0 would be faster. Is it supposed > to be? Does > anybody know of any major difference in 4.0 that would give > me these speed > decreases? And possibly how to fix them? > > Your help is much appreciated. > > Cheers > > > > > 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 Sat Jan 8 0: 1:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id BA78F14E67 for ; Sat, 8 Jan 2000 00:01:37 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id AAA04448; Sat, 8 Jan 2000 00:01:31 -0800 (PST) (envelope-from ab@astralblue.com) Date: Sat, 8 Jan 2000 00:01:31 -0800 (PST) From: "Eugene M. Kim" To: Yoshinobu Inoue Cc: freebsd@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: <20000108133114L.shin@nd.net.fujitsu.co.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 Sat, 8 Jan 2000, Yoshinobu Inoue wrote: | > I have a DEC Alpha at home running 4.0-current and am willing to help out with | > the testing. I am not the worlds greatest coder, but am willing to do what I can | | Thanks! | | The 1st thing I want to be tested is that, a kernel with | following additions to the config file | | options INET6 #IPv6 communications protocols | options IPSEC #IP security | options IPSEC_ESP #IP security (crypto; define w/ IPSEC) | options IPSEC_IPV6FWD #IP security tunnel for IPv6 | options IPSEC_DEBUG #debug for IP security | | pseudo-device gif 4 #IPv6 and IPv4 tunneling | pseudo-device faith 1 #for IPv6 and IPv4 translation | | just works fine, | and also all apps on your environments which you are usually | using still works fine on that kernel. I've done this this morning and found that all of a sudden natd and related stuff stopped working; it leads to a kernel panic whenever a machine inside natd tries to access the Internet. IIRC, the kernel option IPDIVERT was documented to be incompatible in KAME LINT; maybe this should be documented in our LINT as well? For now, I've reverted to my previous kernel (because my mom would get upset if the Internet gets inaccessible from her Win98 box), but if you give further direction, I can do some testing while she's off the computer. :-) Thank you, Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0: 3:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 6822114F0E for ; Sat, 8 Jan 2000 00:03:31 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id RAA11588; Sat, 8 Jan 2000 17:02:47 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id RAA24973; Sat, 8 Jan 2000 17:02:46 +0900 (JST) Received: from localhost ([192.168.245.199]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id RAA14460; Sat, 8 Jan 2000 17:02:45 +0900 (JST) To: freebsd@cybcon.com, kabaev@mail.ru Cc: ak@freenet.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: References: <3876C4C9.538309A3@freenet.co.uk> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000108170322G.shin@nd.net.fujitsu.co.jp> Date: Sat, 08 Jan 2000 17:03:22 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for IPv6 checkings. Addresses and routes look fine. (:-) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0: 8:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 04558151B3 for ; Sat, 8 Jan 2000 00:08:31 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id JAA09575; Sat, 8 Jan 2000 09:08:30 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001080808.JAA09575@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <200001080031.QAA13581@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Jan 7, 2000 04:31:00 pm" To: "Rodney W. Grimes" Date: Sat, 8 Jan 2000 09:08:29 +0100 (CET) Cc: Patrick Bihan-Faou , Harold Gutch , freebsd-current@FreeBSD.ORG, Nate Williams X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > clnsrv "allow " tcp "" 43 "${tcp_nicname_c}" "${tcp_nicname_s}" > clnsrv "allow " tcp "" 53 "${tcp_domain_c}" "${tcp_domain_s}" ... > ... on and on up to the 1024 and then a few splattered after that. looks like the search path can become extremely long!. > The single largest optimization would probably be a dispatch based on > source or destination port, the latter being more prevelent. ok... dispatch on ports is easy to implement, easier than dispatch on (masked) IP's. > I can't easily send out the actual IP firewall list, it may expose > what ever router I grabbed it off of to an attack :-) understand -- this is why i just asked only about the structure of the ruleset and the length of the longest search path. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0: 9:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id D3F0615A1D for ; Sat, 8 Jan 2000 00:09:46 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-5.cybcon.com [205.147.75.6]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id AAA15070; Sat, 8 Jan 2000 00:09:33 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000108170322G.shin@nd.net.fujitsu.co.jp> Date: Sat, 08 Jan 2000 00:11:15 -0800 (PST) From: William Woods To: Yoshinobu Inoue Subject: Re: IPv6 testing...willing to help Cc: freebsd-current@FreeBSD.ORG, ak@freenet.co.uk, kabaev@mail.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I can do any more testing, let me know. On 08-Jan-00 Yoshinobu Inoue wrote: > Thanks for IPv6 checkings. > Addresses and routes look fine. (:-) > > Yoshinobu Inoue ---------------------------------- E-Mail: William Woods Date: 08-Jan-00 Time: 00:10:52 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0:13:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 16EC415140 for ; Sat, 8 Jan 2000 00:13:06 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id JAA09599; Sat, 8 Jan 2000 09:13:17 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001080813.JAA09599@info.iet.unipi.it> Subject: Re: 4.0 slower than 3.4? In-Reply-To: from Jason Young at "Jan 8, 2000 02:01:38 am" To: Jason Young Date: Sat, 8 Jan 2000 09:13:17 +0100 (CET) Cc: "'james'" , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think i saw something similar -- while testing pieces of ipfw code using rdtsc() calls around the section of code of interest, i notice that 4.0 seems to lose a couple of microseconds (over 8-10) wrt/ the same code in 3.4. No idea though on what is going on. > It probably isn't the best of all ideas to have BOTH IP firewalling > solutions installed and running at once. This will add some overhead. Pick > one and stick with it. And why do you have DUMMYNET running? he has both configured but none running (at least -- not dummynet, according to his ruleset, and he does not say anything about ipfilter). cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0:13:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id F0808158E8 for ; Sat, 8 Jan 2000 00:13:16 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id AAA04603 for ; Sat, 8 Jan 2000 00:13:16 -0800 (PST) (envelope-from ab@astralblue.com) Date: Sat, 8 Jan 2000 00:13:16 -0800 (PST) From: "Eugene M. Kim" To: FreeBSD-current Mailing List Subject: Status of DEVFS? 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, Yesterday I decided to convert to DEVFS, compiled a kernel with `option DEVFS' and added the fstab line necessary to mount it on /dev. Most things work fine, but I get some subtle errors like permission denied on chown()ing ptys, failure to add entry to /dev with errno 17 (maybe double registration?), and some devices not appearing in /dev (I have to edit rc.devfs so that it can make some symbolic links from /dev.bak :-p). (Nothing fatal happens though; I can use the machine as before) What is the current status of DEVFS? Is this still a `good feature to have but oh well...'-sort of thing so it is not supported by many drivers, or is some serious effort on track to round the sharp edges and make it usable? TIA, Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 0:34:57 2000 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 2A9AD15859 for ; Sat, 8 Jan 2000 00:34:54 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA14383; Sat, 8 Jan 2000 00:34:31 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001080834.AAA14383@gndrsh.dnsmgr.net> Subject: Re: ipfw optimizations In-Reply-To: <200001080808.JAA09575@info.iet.unipi.it> from Luigi Rizzo at "Jan 8, 2000 09:08:29 am" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Sat, 8 Jan 2000 00:34:31 -0800 (PST) Cc: patrick@mindstep.com (Patrick Bihan-Faou), logix@foobar.franken.de (Harold Gutch), freebsd-current@FreeBSD.ORG, nate@mt.sri.com (Nate Williams) 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 > > clnsrv "allow " tcp "" 43 "${tcp_nicname_c}" "${tcp_nicname_s}" > > clnsrv "allow " tcp "" 53 "${tcp_domain_c}" "${tcp_domain_s}" > ... > > ... on and on up to the 1024 and then a few splattered after that. > > looks like the search path can become extremely long!. Yes, on under powered routers I sometimes take a dump of ``ipfw -a'' and take a look at the counts and reorder the rules. Note that 95% of tcp traffic hits a rule before all of these that is ``tcp.... established'', so the only time we run down through the search is on a setup packet. Most of our routers running this have plenty of CPU power due to the demands of gated/bgp/ospf so this has not become an issue. I can always add a few skipto's as well that would speed things up if I needed to :-) ipfw add 5000 skipto 20000 tcp from any to any 22-113 > > > The single largest optimization would probably be a dispatch based on > > source or destination port, the latter being more prevelent. > > ok... dispatch on ports is easy to implement, easier than dispatch > on (masked) IP's. A Patricia tree might work well here, it would defanitly work well for any attempt to dispatch on masked IP's. > > I can't easily send out the actual IP firewall list, it may expose > > what ever router I grabbed it off of to an attack :-) > > understand -- this is why i just asked only about the structure of the > ruleset and the length of the longest search path. :-) Even a 50% loaded set of T-1's running the 300 rule set on an old Pentium-II 300 uses more CPU time doing bgp/ospf than it does doing the firewall rules :-) One thing has hit me about your implementation of this scattered rule set, nahhh.. shouldn't be a problem if done as pointers to rules, but the couting of packets and bytes must be done in the pre-exploded rule set. Also have you thought about adding a special interface device name to handle packets as they traverse ip_forward? I know Poul's or someone elses drawing of the H style firewall could be implemented if we had a way to apply rules as they traverse the ip_forward code and an easy way to expand your scheme to include that would be to add something like ``via fwd, in via fwd, out via fwd''. Note that I _think_ but am not certain that NAT tapping/injection occurs in ip_forward so this could be of benefit to those doing NAT. Anotherwords the full blown H style 2 interface firewall has 6 nodes: 1 2 | | | | 5--6 | | | | 3 4 Nodes 1/2 are the input/output of one interface, 3/4 are the input/output of the other interface and 5/6 are the input/output side of the forward/translator engine. -- Rod Grimes - KD7CAX @ CN85sl - (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 Jan 8 0:44:32 2000 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 948B614D6D for ; Sat, 8 Jan 2000 00:44:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA13117; Sat, 8 Jan 2000 09:42:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Rodney W. Grimes" Cc: luigi@info.iet.unipi.it (Luigi Rizzo), patrick@mindstep.com (Patrick Bihan-Faou), logix@foobar.franken.de (Harold Gutch), freebsd-current@FreeBSD.ORG, nate@mt.sri.com (Nate Williams) Subject: Re: ipfw optimizations In-reply-to: Your message of "Sat, 08 Jan 2000 00:34:31 PST." <200001080834.AAA14383@gndrsh.dnsmgr.net> Date: Sat, 08 Jan 2000 09:42:39 +0100 Message-ID: <13115.947320959@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001080834.AAA14383@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes : >handle packets as they traverse ip_forward? I know Poul's or someone >elses drawing of the H style firewall could be implemented if we had >a way to apply rules as they traverse the ip_forward code and an easy >way to expand your scheme to include that would be to add something >like ``via fwd, in via fwd, out via fwd''. Note that I _think_ but >am not certain that NAT tapping/injection occurs in ip_forward so this >could be of benefit to those doing NAT. I think the general syntax would be if you could say "for one of my own IP#" that would be very powerful: add allow tcp from any to me 22 add deny tcp from any to not me 22 -- 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 Jan 8 0:57:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax1-220.dialup.optusnet.com.au [198.142.190.220]) by hub.freebsd.org (Postfix) with ESMTP id 44DDF14D6D for ; Sat, 8 Jan 2000 00:57:03 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 905B35599; Sat, 8 Jan 2000 19:56:59 +1100 (EST) Message-Id: <4.2.2.20000108193516.00a37800@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 08 Jan 2000 19:56:49 +1100 To: Jason Young From: james Subject: RE: 4.0 slower than 3.4? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: 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 02:01 8/1/2000 -0600, Jason Young wrote: >Well, several possible issues.. > >It probably isn't the best of all ideas to have BOTH IP firewalling >solutions installed and running at once. This will add some overhead. Pick >one and stick with it. And why do you have DUMMYNET running? I had ipfilter and dummynet in there just to experiment with if i got bored. I haven't even touched or enabled them yet. I just assumed they were disabled unless i did something with them. I had them both in my 3.4 kernel too. >There is a new version of IPFilter in -CURRENT if I recall correctly, and >this may be related to your timing issues. Really you ought to just take >IPFILTER out of your configuration. Ok, i'll try that. Or perhaps i should remove IPFIREWALL. I'm really not too sure on which one i should use.. Do you know which is better? IPFILTER looks more configurable - something i definitely like. >Aside from that, you'll need to use 'top' or some similar utility to find >out where and why you're CPU-bound for FTP transfers. Find out if you're >primarily stuck in the kernel, or if some userland utility is sucking it up >(like natd, but your ipfw rules tend to rule out accidentally running >ethernet traffic through natd). user is around 1-3%, system 50-60%, interrupt 35-45%, idle 0-1%. The only program that has a cpu usage that isn't 0% is ftpd. It climbs up to 25% and then the transfer finishes. I'm only transferring a 25 meg file as i want it to go from the cache on one machine into /dev/null on freebsd to really test the network speed. Cheers >Jason Young >accessUS Chief Network Engineer > > > > -----Original Message----- > > From: james [mailto:death@southcom.com.au] > > Sent: Saturday, January 08, 2000 1:02 AM > > To: freebsd-current@FreeBSD.ORG > > Subject: 4.0 slower than 3.4? > > > > > > > > Hi, > > > > I upgraded a few days ago from 3.4-STABLE to 4.0-CURRENT, and without > > really any change in configuration, anything tcp/ip is much > > slower. Just a > > standard "ping localhost" has gone from ~0.155ms to ~0.195ms. > > Averages for > > "ping -f localhost" have gone from ~0.100ms to ~0.160ms. FTP > > over my lan > > "vr0" has slipped from 7.7MB/s down to 4.8MB/s (!). > > > > I've got hardly anything running on my machine (natd, samba, postfix, > > pppd). 'top' shows 99-100% idle pretty much all the time. > > Load averages are > > all 0.00. CPU usage goes upto 100% during the ftp transfer. > > > > Here's the output of my dmesg: > > > > Copyright (c) 1992-2000 The FreeBSD Project. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All > > rights reserved. > > FreeBSD 4.0-CURRENT #0: Fri Jan 7 00:14:59 EST 2000 > > death@void.dynip.com:/usr/src/sys/compile/DEATH > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium/P54C (166.19-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > > Features=0x1bf > > real memory = 33554432 (32768K bytes) > > avail memory = 30040064 (29336K bytes) > > Preloaded elf kernel "kernel" at 0xc028b000. > > Intel Pentium detected, installing workaround for F00F bug > > md0: Malloc disk > > npx0: on motherboard > > npx0: INT 16 interface > > pcib0: on motherboard > > pci0: on pcib0 > > isab0: at device 7.0 on pci0 > > isa0: on isab0 > > ata-pci0: at device 7.1 on pci0 > > ata-pci0: Busmastering DMA supported > > ata0 at 0x01f0 irq 14 on ata-pci0 > > ata1 at 0x0170 irq 15 on ata-pci0 > > vr0: irq 9 at device 18.0 on pci0 > > vr0: Ethernet address: 00:80:c8:d8:19:b7 > > miibus0: on vr0 > > amphy0: on miibus0 > > amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > vga-pci0: irq 11 at > > device 19.0 on pci0 > > ata-isa0: already registered as ata0 > > ata-isa1: already registered as ata1 > > atkbdc0: at port 0x60-0x6f on isa0 > > atkbd0: irq 1 on atkbdc0 > > vga0: at port 0x3b0-0x3df iomem > > 0xa0000-0xbffff on isa0 > > sc0: on isa0 > > sc0: VGA <16 virtual consoles, flags=0x200> > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A > > IP packet filtering initialized, divert enabled, rule-based > > forwarding > > enabled, default to accept, logging limited to 100 > > packets/entry by default > > DUMMYNET initialized (990811) > > IP Filter: initialized. Default = pass all, Logging = enabled > > IP Filter: v3.3.3 > > ad0: ATA-4 disk at ata0 as master > > ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, WDMA2 > > ad2: ATA-0 disk at ata1 as master > > ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S > > ad2: 16 secs/int, 1 depth queue, WDMA2 > > Mounting root from ufs:/dev/wd0s1a > > > > > > Here's my kernel config: > > > > machine i386 > > cpu I586_CPU > > ident DEATH > > maxusers 64 > > > > options INET > > options FFS > > options FFS_ROOT > > options MSDOSFS > > options PROCFS > > options COMPAT_43 > > options UCONSOLE > > options USERCONFIG > > options VISUAL_USERCONFIG > > options SYSVSHM > > options SYSVMSG > > options SYSVSEM > > > > controller isa0 > > controller pci0 > > > > controller ata0 at isa? port IO_WD1 irq 14 > > controller ata1 at isa? port IO_WD2 irq 15 > > device atadisk0 > > options ATA_STATIC_ID > > options ATA_ENABLE_ATAPI_DMA > > > > controller atkbdc0 at isa? port IO_KBD > > device atkbd0 at atkbdc? irq 1 > > > > device vga0 at isa? port ? conflicts > > > > device sc0 at isa? > > > > device npx0 at nexus? port IO_NPX irq 13 > > > > device apm0 at nexus? disable flags 0x20 > > > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > > device sio1 at isa? port IO_COM2 irq 3 > > > > controller miibus0 > > device vr0 > > > > pseudo-device loop > > pseudo-device ether > > pseudo-device ppp 2 > > pseudo-device tun 1 > > pseudo-device pty 16 > > pseudo-device md > > > > pseudo-device bpf 4 > > pseudo-device snp 4 > > > > options MD5 > > options PPP_BSDCOMP > > options PPP_DEFLATE > > options PPP_FILTER > > 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 IPSTEALTH > > options TCP_DROP_SYNFIN > > options TCP_RESTRICT_RST > > options ICMP_BANDLIM > > options DUMMYNET > > options SOFTUPDATES > > options NSWAPDEV=2 > > options QUOTA > > pseudo-device gzip > > > > > > Here's the first 4 relevant ipfw rules: > > > > 00050 allow icmp from any to any > > 00100 divert 8668 ip from 192.168.1.2 to any out xmit ppp0 > > 00100 divert 8668 ip from any to any in recv ppp0 > > 00200 allow tcp from any to any established > > > > > > I used the same config for 3.4. The only difference is in > > using ata instead > > of wd for my hard drives. And the new miibus controller for > > my ethernet card. > > > > I would've thought that 4.0 would be faster. Is it supposed > > to be? Does > > anybody know of any major difference in 4.0 that would give > > me these speed > > decreases? And possibly how to fix them? > > > > Your help is much appreciated. > > > > Cheers > > > > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 1:29:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 686E915246 for ; Sat, 8 Jan 2000 01:29:18 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id KAA09763; Sat, 8 Jan 2000 10:29:26 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001080929.KAA09763@info.iet.unipi.it> Subject: Re: ipfw optimizations In-Reply-To: <13115.947320959@critter.freebsd.dk> from Poul-Henning Kamp at "Jan 8, 2000 09:42:39 am" To: Poul-Henning Kamp Date: Sat, 8 Jan 2000 10:29:25 +0100 (CET) Cc: "Rodney W. Grimes" , Patrick Bihan-Faou , Harold Gutch , freebsd-current@FreeBSD.ORG, Nate Williams X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the general syntax would be if you could say "for one of my > own IP#" that would be very powerful: > > add allow tcp from any to me 22 > add deny tcp from any to not me 22 the 'me' thing is relatively simple to implement, it suffices to scan the list of IP associated with all interfaces. Can be time-consuming. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 1:33:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 64BDE150EB for ; Sat, 8 Jan 2000 01:33:27 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id SAA29235; Sat, 8 Jan 2000 18:33:19 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id SAA05879; Sat, 8 Jan 2000 18:33:18 +0900 (JST) Received: from localhost ([192.168.245.10]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id SAA17021; Sat, 8 Jan 2000 18:33:16 +0900 (JST) To: ab@astralblue.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: References: <20000108133114L.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000108183353S.shin@nd.net.fujitsu.co.jp> Date: Sat, 08 Jan 2000 18:33:53 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 43 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've done this this morning and found that all of a sudden natd and > related stuff stopped working; it leads to a kernel panic whenever a > machine inside natd tries to access the Internet. IIRC, the kernel > option IPDIVERT was documented to be incompatible in KAME LINT; maybe > this should be documented in our LINT as well? Thanks for checking. I thought I should have fixed that, but there seems to be a mistake. > For now, I've reverted to my previous kernel (because my mom would get > upset if the Internet gets inaccessible from her Win98 box), but if you > give further direction, I can do some testing while she's off the > computer. :-) Could you please try following patch when she got tired of computer. :-) Index: ip_divert.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_divert.c,v retrieving revision 1.41 diff -u -r1.41 ip_divert.c --- ip_divert.c 1999/12/22 19:13:20 1.41 +++ ip_divert.c 2000/01/08 09:27:00 @@ -297,7 +297,7 @@ ipstat.ips_rawout++; /* XXX */ error = ip_output(m, inp->inp_options, &inp->inp_route, (so->so_options & SO_DONTROUTE) | - IP_ALLOWBROADCAST | IP_RAWOUTPUT | IP_SOCKINMRCVIF, + IP_ALLOWBROADCAST | IP_RAWOUTPUT, inp->inp_moptions); } else { struct ifaddr *ifa; If the patch doesn't work, I would like to try same configuration as yours. In that case, could you please give me some of your related configuration files if possible? Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 1:48: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-112.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.240]) by hub.freebsd.org (Postfix) with ESMTP id 9EE37152DD; Sat, 8 Jan 2000 01:47:53 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA99461; Sat, 8 Jan 2000 09:47:47 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA00514; Fri, 7 Jan 2000 14:32:10 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001071432.OAA00514@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: obrien@NUXI.com Cc: Warner Losh , committers@FreeBSD.org, current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: Message from "David O'Brien" of "Thu, 06 Jan 2000 08:53:26 PST." <20000106085326.B1417@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 14:32:10 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > `ep' is seriously wounded for some with 3c589d cards as it isn't getting > interrupts and only works via the watchdog timer. Also, with a 3c589c, hot plugging is like playing Russian Roulette with five of the six chambers full at the moment. Just booting with a pccard inserted sometimes crashes the machine. I think most peoples view of the current pccard stuff would be that it's far inferior to RELENG_3. I'm not taking a swipe at Warner - he's done a lot of work here... the code's just not ready yet IMHO (oldpccard or newpccard). > -- > -- David (obrien@NUXI.com) -- 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 Sat Jan 8 1:48: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-112.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.240]) by hub.freebsd.org (Postfix) with ESMTP id E61DD15816; Sat, 8 Jan 2000 01:47:48 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA99467; Sat, 8 Jan 2000 09:47:47 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA01463; Fri, 7 Jan 2000 08:32:19 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001070832.IAA01463@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.org Cc: obrien@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: hak.lan.Awfulhak.org daily run output In-Reply-To: Message from God of "Fri, 07 Jan 2000 01:59:00 GMT." <200001070159.BAA00909@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 08:32:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Anyone know what's changed with `calendar' ? I suspect it's the recent cpp changes. I have more than one entry in my calendar files something like Jan 1: Blah ('60) [.....] > Running calendar: > In file included from :1: > birthdays:3: unterminated character constant > birthdays:6: unterminated character constant > birthdays:7: unterminated character constant > birthdays:10: unterminated character constant > birthdays:13: unterminated character constant > birthdays:15: unterminated character constant > birthdays:17: unterminated character constant > birthdays:18: unterminated character constant > birthdays:19: unterminated character constant > birthdays:22: unterminated character constant > birthdays:24: unterminated character constant > birthdays:25: unterminated character constant > birthdays:27: unterminated character constant > birthdays:28: unterminated character constant > birthdays:29: unterminated character constant > birthdays:30: unterminated character constant > birthdays:32: unterminated character constant > birthdays:35: unterminated character constant > birthdays:37: unterminated character constant > birthdays:38: unterminated character constant > birthdays:39: unterminated character constant > birthdays:40: unterminated character constant > birthdays:44: unterminated character constant > birthdays:46: unterminated character constant > birthdays:48: unterminated character constant > birthdays:49: unterminated character constant > birthdays:50: unterminated character constant > birthdays:51: unterminated character constant > birthdays:52: unterminated character constant > birthdays:53: unterminated character constant > birthdays:55: unterminated character constant > birthdays:56: unterminated character constant > birthdays:58: unterminated character constant > birthdays:59: unterminated character constant > birthdays:60: unterminated character constant > birthdays:62: unterminated character constant > birthdays:68: unterminated character constant > birthdays:69: unterminated character constant > birthdays:70: unterminated character constant > birthdays:71: unterminated character constant > birthdays:73: unterminated character constant > birthdays:74: unterminated character constant > birthdays:75: unterminated character constant > birthdays:77: unterminated character constant > birthdays:78: unterminated character constant > In file included from :2: > weddings:2: unterminated character constant > weddings:3: unterminated character constant > weddings:4: unterminated character constant > weddings:5: unterminated character constant > weddings:6: unterminated character constant > In file included from :3: > contracts:1: unterminated character constant > contracts:2: unterminated character constant > contracts:3: unterminated character constant > contracts:4: unterminated character constant > contracts:5: unterminated character constant > contracts:8: unterminated character constant > contracts:9: unterminated character constant > contracts:10: unterminated character constant > contracts:11: unterminated character constant > contracts:12: unterminated character constant > :5: unterminated character constant > :6: unterminated character constant > :7: unterminated character constant > :9: unterminated character constant > :10: unterminated character constant > :11: unterminated character constant > :13: unterminated character constant > :14: unterminated character constant > :15: unterminated character constant > :17: unterminated character constant [.....] -- 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 Sat Jan 8 2:20:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4485B150EB for ; Sat, 8 Jan 2000 02:20:56 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA01355; Sat, 8 Jan 2000 11:20:50 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081020.LAA01355@freebsd.dk> Subject: Re: atap cd? In-Reply-To: <200001080520.VAA04508@rah.star-gate.com> from Amancio Hasty at "Jan 7, 2000 09:20:49 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 8 Jan 2000 11:20:49 +0100 (CET) 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 Amancio Hasty wrote: > {root} mount -t cd9660 /dev/acd0a /cdrom > cd9660: Block device required > {root} mount /dev/acd0a /cdrom > mount: Block device required > > ls -ald /dev/acd0c > brw-r----- 1 root operator 19, 2 Jan 7 20:27 /dev/acd0c > If this is current it should be: crw-rw-rw- 1 root operator 117, 2 Dec 2 22:52 /dev/acd0c -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 Jan 8 2:41:16 2000 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 7FC3D150F0 for ; Sat, 8 Jan 2000 02:41:14 -0800 (PST) (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.9.3) with ESMTP id CAA06788; Sat, 8 Jan 2000 02:40:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001081040.CAA06788@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: atap cd? In-reply-to: Your message of "Sat, 08 Jan 2000 11:20:49 +0100." <200001081020.LAA01355@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Jan 2000 02:40:42 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks Yes, I am running current as of today . also while trying to read a DVD I think that your driver is not setting cap.dvdrom flag so when I ask for report key it returns with failure. Just wondering if you her of such a problem currently. I am more than happy to hack the driver to read the key 8) Cheers -- 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 Sat Jan 8 2:44: 2 2000 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 4A1BC14DA4 for ; Sat, 8 Jan 2000 02:44:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA13451; Sat, 8 Jan 2000 11:43:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luigi Rizzo Cc: "Rodney W. Grimes" , Patrick Bihan-Faou , Harold Gutch , freebsd-current@FreeBSD.ORG, Nate Williams Subject: Re: ipfw optimizations In-reply-to: Your message of "Sat, 08 Jan 2000 10:29:25 +0100." <200001080929.KAA09763@info.iet.unipi.it> Date: Sat, 08 Jan 2000 11:43:25 +0100 Message-ID: <13449.947328205@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001080929.KAA09763@info.iet.unipi.it>, Luigi Rizzo writes: >> I think the general syntax would be if you could say "for one of my >> own IP#" that would be very powerful: >> >> add allow tcp from any to me 22 >> add deny tcp from any to not me 22 > >the 'me' thing is relatively simple to implement, it suffices to scan >the list of IP associated with all interfaces. Can be time-consuming. But less so that having one ipfw rule for each interface :-) -- 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 Jan 8 3:19:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2586414CC1 for ; Sat, 8 Jan 2000 03:19:22 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA17004; Sat, 8 Jan 2000 12:19:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081119.MAA17004@freebsd.dk> Subject: Re: atap cd? In-Reply-To: <200001081040.CAA06788@rah.star-gate.com> from Amancio Hasty at "Jan 8, 2000 02:40:42 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 8 Jan 2000 12:19:16 +0100 (CET) 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 Amancio Hasty wrote: > Tnks > > Yes, I am running current as of today . also while trying to read a DVD > I think that your driver is not setting cap.dvdrom flag so when I ask for > report key it returns with failure. Just wondering if you her of such > a problem currently. I am more than happy to hack the driver to read > the key 8) Erhm, if thats the drive you posted the dmesg from, that is a CDROM drive, it cannot read DVD's. I know that cap.dvdrom is set when used on DVD drives and have no reports telling otherwise. The driver works for all thats needed to read/play a DVD given that you use the right tools. Look at freebsd.dk/pub/DVD for the patches needed to css-auth (you have to get the source form somewhere else) and a ported nist player. Remember that I just changed the DVD ioctls, so if you use older compiled tools they wont work... -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 Jan 8 3:19:57 2000 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 800A515A1E for ; Sat, 8 Jan 2000 03:19:45 -0800 (PST) (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.9.3) with ESMTP id DAA07031; Sat, 8 Jan 2000 03:19:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001081119.DAA07031@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: atap cd? In-reply-to: Your message of "Sat, 08 Jan 2000 02:40:42 PST." <200001081040.CAA06788@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Jan 2000 03:19:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh wow that looks cool -- Oh excuse me : Never mind about the problem with report_key not working . Back to watching ... Tnks! -- 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 Sat Jan 8 3:39:23 2000 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 8809B152DD for ; Sat, 8 Jan 2000 03:39:19 -0800 (PST) (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.9.3) with ESMTP id DAA07219; Sat, 8 Jan 2000 03:38:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001081138.DAA07219@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: atap cd? In-reply-to: Your message of "Sat, 08 Jan 2000 12:19:16 +0100." <200001081119.MAA17004@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 08 Jan 2000 03:38:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Amancio Hasty wrote: > > Tnks = > > = > > Yes, I am running current as of today . also while trying to read a D= VD = > > I think that your driver is not setting cap.dvdrom flag so when I ask= for > > report key it returns with failure. Just wondering if you her of suc= h = > > a problem currently. I am more than happy to hack the driver to read > > the key 8) > = > Erhm, if thats the drive you posted the dmesg from, that is a CDROM > drive, it cannot read DVD's. I know that cap.dvdrom is set when used > on DVD drives and have no reports telling otherwise. > The driver works for all thats needed to read/play a DVD given that > you use the right tools. Look at freebsd.dk/pub/DVD for the patches > needed to css-auth (you have to get the source form somewhere else) > and a ported nist player. > Remember that I just changed the DVD ioctls, so if you use older > compiled tools they wont work... > = I did a fresh re-install and all is working well over here. Now my real h= acking begins that is to modify the DVD mpeg player to use the brand new spankin= g functions in XFree86 to do yuv->rgb + scaling with hardware assist 8) ----------------------------------------------------------- If any of you are running XFree86 3.9.17 I have a modified mpeg player which should work with a matrox mga 200 or matrox mga 400 vga with = hardware assist yuv->rgb + scaling : ftp://rah.star-gate.com/pub/mpeg_play.tar.gz Thats a quick hacked up mpeg_play to use XvPutImage which does the yuv-rgb + scaling magic. So we can now watch video at 1600x1200 at any color depth well at least a= t 8, 15,16, 24, 32 8) If mpeg_play with XFree86 3.9.17 and an mga 200 or mga 400 doesn't work = for you = just let me know cause I am running XFree86 -current . Have Fun Guys -- = 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 Sat Jan 8 3:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id BE3A4154E1; Sat, 8 Jan 2000 03:45:01 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id MAA10204; Sat, 8 Jan 2000 12:45:27 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001081145.MAA10204@info.iet.unipi.it> Subject: kind-of heads-up -- ipfw and dummynet To: current@freebsd.org Date: Sat, 8 Jan 2000 12:45:26 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [sorry for the blind crosspost to -net, but i think this is relevant there as well...] Hi, I have just committed to -current a few modifications to ipfw and dummynet and i would like people to check them and submit feedback. (everything is mostly backward compatible, you only need to recompile ipfw if you want to use the new dummynet features, but the syntax remains the same). They are listed below: REWRITTEN MANPAGE, trying to make it more readable. Please let me know if i succeeded or not. DUMMYNET now supports dynamically-created per-flow queues. E.g. if you want to limit each /24 subnet to your web server to 100Kbit/s you can do now: ifpw add pipe 1 tcp from my-ip 80 to any ipfw pipe 1 config bw 100Kbit/s mask dst-ip 0xffffff00 and so on. The manpage gives more examples. User interface is fully backward compatible. This work sponsored by Akamba Corp. As a side effect, the new dummynet code also fixes one bug in the previous code which could cause large bursts of packets. DUMMYNET should also work on the alpha, because i have fixed the interface problems which prevented this on the past. IPFW now supports masks on TCP/UDP ports, which can be useful for some simulation purposes and does not impact performance. Feedback appreciated. If there are no objections, i would like to put these things into -stable soon, as there are important fixes to existing features. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 3:47:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4B254158EB for ; Sat, 8 Jan 2000 03:47:11 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA24518; Sat, 8 Jan 2000 12:47:07 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081147.MAA24518@freebsd.dk> Subject: Re: atap cd? In-Reply-To: <200001081138.DAA07219@rah.star-gate.com> from Amancio Hasty at "Jan 8, 2000 03:38:48 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 8 Jan 2000 12:47:07 +0100 (CET) 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 Amancio Hasty wrote: > I did a fresh re-install and all is working well over here. Now my real hacking > begins that is to modify the DVD mpeg player to use the brand new spanking > functions in XFree86 to do yuv->rgb + scaling with hardware assist 8) You should look at the livid site, they have a new player thats much faster than the nist one, it also has backends for various video HW, including ATI cards which is nice since thats what I've got here :) -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 Jan 8 4:27: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id C6FD314FB3 for ; Sat, 8 Jan 2000 04:27:02 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id EAA05936; Sat, 8 Jan 2000 04:26:59 -0800 (PST) (envelope-from ab@astralblue.com) Date: Sat, 8 Jan 2000 04:26:58 -0800 (PST) From: "Eugene M. Kim" To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: <20000108183353S.shin@nd.net.fujitsu.co.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 Thanks! Your patch worked so now there's no problem getting outside using natd. I've gone through the checklist in your original message as well, and have found so far: 0) gif seems to work well (I use freenet6.net as my primary uplink connection for IPv6) 1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the ``default'' route. I've used this command to establish my default route: route -n add -inet6 -net default -prefixlen 0 -interface gif0 2) Here's the output you requested: * ifconfig -a: ep0: flags=8843 mtu 1500 inet 209.76.108.39 netmask 0xffffff00 broadcast 209.76.108.255 inet6 fe80:1::220:afff:fe1d:bc36 prefixlen 64 ether 00:20:af:1d:bc:36 media: 10baseT/UTP supported media: 10baseT/UTP 10base5/AUI lo0: flags=8049 mtu 16384 inet6 fe80:2::1 prefixlen 64 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8051 mtu 1280 inet6 fe80:3::220:afff:fe1d:bc36 prefixlen 64 inet6 3ffe:b00:c18:1fff::165 --> 3ffe:b00:c18:1fff::164 prefixlen 127 gif1: flags=8010 mtu 1280 inet6 fe80:4::220:afff:fe1d:bc36 prefixlen 64 gif2: flags=8010 mtu 1280 inet6 fe80:5::220:afff:fe1d:bc36 prefixlen 64 gif3: flags=8010 mtu 1280 inet6 fe80:6::220:afff:fe1d:bc36 prefixlen 64 faith0: flags=8002 mtu 1500 fxp0: flags=8843 mtu 1500 inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 inet6 fe80:8::2a0:c9ff:feaa:106 prefixlen 64 ether 00:a0:c9:aa:01:06 media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP tun0: flags=8010 mtu 1500 inet6 fe80:9::220:afff:fe1d:bc36 prefixlen 64 Opened by PID 5749 tun1: flags=8051 mtu 1500 inet 10.0.0.4 --> 10.0.2.2 netmask 0xffffff00 Opened by PID 460 * netstat -nrfinet6: Routing tables Internet6: Destination Gateway Flags Netif Expire default gif0 USc gif0 ::1 ::1 UH lo0 3ffe:b00:c18:1fff::164 3ffe:b00:c18:1fff::165 UH gif0 3ffe:b00:c18:1fff::165 ::1 UH lo0 fe80::@ep0/64 link#1 UC ep0 fe80::@lo0/64 fe80::1@lo0 Uc lo0 fe80::@gif0/64 fe80::220:afff:fe1d:bc36@gif0 Uc gif0 fe80::220:afff:fe1d:bc36@gif0 ::1 UH lo0 fe80::@gif1/64 fe80::220:afff:fe1d:bc36@gif1 Uc gif1 fe80::220:afff:fe1d:bc36@gif1 ::1 UH lo0 fe80::@gif2/64 fe80::220:afff:fe1d:bc36@gif2 Uc gif2 fe80::220:afff:fe1d:bc36@gif2 ::1 UH lo0 fe80::@gif3/64 fe80::220:afff:fe1d:bc36@gif3 Uc gif3 fe80::220:afff:fe1d:bc36@gif3 ::1 UH lo0 fe80::@fxp0/64 link#8 UC fxp0 fe80::@tun0/64 fe80::220:afff:fe1d:bc36@tun0 Uc tun0 fe80::220:afff:fe1d:bc36@tun0 ::1 UH lo0 ff01::/32 ::1 U lo0 ff02::@ep0/32 link#1 UC ep0 ff02::@lo0/32 fe80::1@lo0 UC lo0 ff02::@gif0/32 fe80::220:afff:fe1d:bc36@gif0 UC gif0 ff02::@gif1/32 fe80::220:afff:fe1d:bc36@gif1 UC gif1 ff02::@gif2/32 fe80::220:afff:fe1d:bc36@gif2 UC gif2 ff02::@gif3/32 fe80::220:afff:fe1d:bc36@gif3 UC gif3 ff02::@fxp0/32 link#8 UC fxp0 ff02::@tun0/32 fe80::220:afff:fe1d:bc36@tun0 UC tun0 3) IPv6 host autoconfiguration: tried w/o establishing the default route, but couldn't have my box learn new routes. (Perhaps freenet6.net doesn't support autoconfig; their setup script explicitly calls route(8) to add the default route) In near future, I'll enable IPv6 on another machine inside my box (which is acting as a router) and try to run rtadvd/rtsol on these two boxes. But currently still unsure whether it is allowed to run such a thing on my machine; I'm not that familiar with the IPv6 addressing scheme (i.e. I don't even know which address to assign to my internal machine), but FreeNet6 might not like it if I run any routing daemon on my machine). 4) IPv6 communication via IPv6 router: for the same reason as in 3), I didn't set my machine as IPv6 router (yet). I'll try this time and circumstances permitting. 5) IPsec between 2 hosts/routers: still studying these topics. :-) Things have changed since last time I tried IPsec tunneling using KAME, so I can't set it up quickly (at least it seems that spdadd command of setkey(8) has been extended a lot). If there's anything else I can do, I'd be glad to. Thanks, Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 4:47: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 08BEE14BE5 for ; Sat, 8 Jan 2000 04:47:02 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 6224486; Sat, 8 Jan 2000 13:47:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 532DB85 for ; Sat, 8 Jan 2000 13:47:00 +0100 (CET) Date: Sat, 8 Jan 2000 13:47:00 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: freebsd-current@freebsd.org Subject: ATA driver timeout 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 still can't seem to be able to boot -CURRENT with the ATA driver, much as I'd like to, due to the `timeout-resetting device' error, which I've seen more people report. I've sacrificed some dead trees to give you the exact boot messages: ad0: ATA-0 disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad1: ATA-3 disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 . . Mounting root from ufs:/dev/ad0s1a ad0: ad_timeout: lost disk contact - reseting ata0: resetting devices .. After which the machine hangs _hard_ (i.e. no respone except to the reset key). The information given is mostly correct: The second drive is UDMA33 and can handle it with the WD driver. Also, when this drive is removed, the error still occurs. I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4', is that the same as WDMA2? Could the harddisk be reporting the wrong value, even though the BIOS is giving the correct one? I'm just grasping at straws here. /^\ | Theo van Klaveren /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 5: 5:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 35CAA158DA for ; Sat, 8 Jan 2000 05:05:28 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA44258; Sat, 8 Jan 2000 14:05:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081305.OAA44258@freebsd.dk> Subject: Re: ATA driver timeout In-Reply-To: from Theo van Klaveren at "Jan 8, 2000 01:47:00 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Sat, 8 Jan 2000 14:05:16 +0100 (CET) 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 Theo van Klaveren wrote: > > I still can't seem to be able to boot -CURRENT with the ATA driver, > much as I'd like to, due to the `timeout-resetting device' error, which > I've seen more people report. I've sacrificed some dead trees to give > you the exact boot messages: > > ad0: ATA-0 disk at ata0 as master > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, WDMA2 > ad1: ATA-3 disk at ata0 as slave > ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > . > . > Mounting root from ufs:/dev/ad0s1a > ad0: ad_timeout: lost disk contact - reseting > ata0: resetting devices .. > > After which the machine hangs _hard_ (i.e. no respone except to the > reset key). > > The information given is mostly correct: The second drive is > UDMA33 and can handle it with the WD driver. Also, when this drive > is removed, the error still occurs. > > I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4', > is that the same as WDMA2? Could the harddisk be reporting the wrong > value, even though the BIOS is giving the correct one? I'm just grasping > at straws here. Mode 4 is PIO4 that is no DMA, it could very well be the problem, WD has made a lot of problematic drives in this area. You could try to comment out the dmainit call in ata-disk.c and see if that helps you. And yes, I'm working on a way to set this from useland... -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 Jan 8 5:19: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 146FE1500A for ; Sat, 8 Jan 2000 05:19:05 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 1DC023B; Sat, 8 Jan 2000 14:19:04 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 1520532; Sat, 8 Jan 2000 14:19:04 +0100 (CET) Date: Sat, 8 Jan 2000 14:19:03 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Soren Schmidt Cc: Theo van Klaveren , freebsd-current@FreeBSD.ORG Subject: Re: ATA driver timeout In-Reply-To: <200001081305.OAA44258@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 Sat, 8 Jan 2000, Soren Schmidt wrote: > It seems Theo van Klaveren wrote: > > > > I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4', > > is that the same as WDMA2? Could the harddisk be reporting the wrong > > value, even though the BIOS is giving the correct one? I'm just grasping > > at straws here. > > Mode 4 is PIO4 that is no DMA, it could very well be the problem, > WD has made a lot of problematic drives in this area. > You could try to comment out the dmainit call in ata-disk.c and > see if that helps you. That helps me, but if I'm not mistaken it also disabled UDMA33 on the second drive. Ah well.. at least I can boot an ATA kernel now. > And yes, I'm working on a way to set this from useland... That'd be really nice, though if the kernel doesn't even boot to single user mode, I don't see how this would help users with this problem, as you'd have to do it before reboot. Thanks for the swift reply, /^\ | Theo van Klaveren /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 5:24:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 8D6D1158DB for ; Sat, 8 Jan 2000 05:24:22 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id WAA23369; Sat, 8 Jan 2000 22:24:15 +0900 (JST) To: "Eugene M. Kim" Cc: Yoshinobu Inoue , freebsd-current@FreeBSD.ORG In-reply-to: ab's message of Sat, 08 Jan 2000 04:26:58 PST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6 testing...willing to help From: itojun@iijlab.net Date: Sat, 08 Jan 2000 22:24:15 +0900 Message-ID: <23367.947337855@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Thanks! Your patch worked so now there's no problem getting outside >using natd. >I've gone through the checklist in your original message as well, and >have found so far: >1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the >``default'' route. I've used this command to establish my default >route: route -n add -inet6 -net default -prefixlen 0 -interface gif0 I believe this should be bringed in. http://www2.kame.net/dev/cvsweb.cgi/kame/freebsd3/sbin/route/route.c.diff?r1=1.4&r2=1.5 itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 5:56: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 274EE158F7 for ; Sat, 8 Jan 2000 05:56:03 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA56905; Sat, 8 Jan 2000 14:56:00 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081356.OAA56905@freebsd.dk> Subject: Re: ATA driver timeout In-Reply-To: from Theo van Klaveren at "Jan 8, 2000 02:19:03 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Sat, 8 Jan 2000 14:56:00 +0100 (CET) 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 Theo van Klaveren wrote: > > > > Mode 4 is PIO4 that is no DMA, it could very well be the problem, > > WD has made a lot of problematic drives in this area. > > You could try to comment out the dmainit call in ata-disk.c and > > see if that helps you. > > That helps me, but if I'm not mistaken it also disabled UDMA33 on the > second drive. Yup, it was more to determine is DMA really was your problem... > Ah well.. at least I can boot an ATA kernel now. > > > And yes, I'm working on a way to set this from useland... > > That'd be really nice, though if the kernel doesn't even boot to single > user mode, I don't see how this would help users with this problem, as > you'd have to do it before reboot. The idea is to boot in non-DMA mode, and then have a script setup the wanted modes from etc/rc*. That way you can always boot into singleuser mode and change the access modes... -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 Jan 8 5:56: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 692BB14EB4 for ; Sat, 8 Jan 2000 05:56:04 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA56905; Sat, 8 Jan 2000 14:56:00 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001081356.OAA56905@freebsd.dk> Subject: Re: ATA driver timeout In-Reply-To: from Theo van Klaveren at "Jan 8, 2000 02:19:03 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Sat, 8 Jan 2000 14:56:00 +0100 (CET) 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 Theo van Klaveren wrote: > > > > Mode 4 is PIO4 that is no DMA, it could very well be the problem, > > WD has made a lot of problematic drives in this area. > > You could try to comment out the dmainit call in ata-disk.c and > > see if that helps you. > > That helps me, but if I'm not mistaken it also disabled UDMA33 on the > second drive. Yup, it was more to determine is DMA really was your problem... > Ah well.. at least I can boot an ATA kernel now. > > > And yes, I'm working on a way to set this from useland... > > That'd be really nice, though if the kernel doesn't even boot to single > user mode, I don't see how this would help users with this problem, as > you'd have to do it before reboot. The idea is to boot in non-DMA mode, and then have a script setup the wanted modes from etc/rc*. That way you can always boot into singleuser mode and change the access modes... -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 Jan 8 6: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id BC285158F9 for ; Sat, 8 Jan 2000 06:00:27 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 8A549183; Sat, 8 Jan 2000 15:00:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 8120E182; Sat, 8 Jan 2000 15:00:26 +0100 (CET) Date: Sat, 8 Jan 2000 15:00:26 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Soren Schmidt Cc: Theo van Klaveren , freebsd-current@FreeBSD.ORG Subject: Re: ATA driver timeout In-Reply-To: <200001081356.OAA56905@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 Sat, 8 Jan 2000, Soren Schmidt wrote: > It seems Theo van Klaveren wrote: > > > > That helps me, but if I'm not mistaken it also disabled UDMA33 on the > > second drive. > > Yup, it was more to determine is DMA really was your problem... It was :) > > > > That'd be really nice, though if the kernel doesn't even boot to single > > user mode, I don't see how this would help users with this problem, as > > you'd have to do it before reboot. > > The idea is to boot in non-DMA mode, and then have a script setup > the wanted modes from etc/rc*. That way you can always boot into > singleuser mode and change the access modes... > Ah, that'd be very cool. Thinking of it, wouldn't FreeBSD be the only OS around that could switch DMA modes on the fly? ;-) /^\ | Theo van Klaveren /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 6: 9:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id D38AA158F8 for ; Sat, 8 Jan 2000 06:09:47 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 5266D183; Sat, 8 Jan 2000 15:09:47 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 496B4182 for ; Sat, 8 Jan 2000 15:09:47 +0100 (CET) Date: Sat, 8 Jan 2000 15:09:47 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: freebsd-current@freebsd.org Subject: NewPCM issue 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 Second in the series of errors recompiling current after a month is a bug I noticed in the NewPCM driver. It skips the last half second or so of its output. This isn't noticeable when playing music, but sound effects really suck. Relevant dmesg output: . sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 . The card is a Creative SoundBlaster AWE32. It worked about a month ago. Does this also have something to do with the buffering issues I've seen coming by on -current? /^\ | Theo van Klaveren /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 6:17:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from radio.kabsi.at (mx.kabelsignal.at [195.202.129.3]) by hub.freebsd.org (Postfix) with ESMTP id 0366314F56 for ; Sat, 8 Jan 2000 06:17:22 -0800 (PST) (envelope-from entropy@kabsi.at) Received: from darkstar ([195.202.172.28]) by radio.kabsi.at (8.9.1/8.9.1) with SMTP id PAA04224 for ; Sat, 8 Jan 2000 15:17:12 +0100 From: "Alexander Sanda" To: Subject: RE: 4.0 slower than 3.4? Date: Sat, 8 Jan 2000 15:17:11 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Young wrote: Saturday, January 08, 2000 9:02 AM > It probably isn't the best of all ideas to have BOTH IP firewalling > solutions installed and running at once. This will add some > overhead. Pick one and stick with it. And why do you have DUMMYNET > running? > > There is a new version of IPFilter in -CURRENT if I recall > correctly, and this may be related to your timing issues. Really > you ought to just take IPFILTER out of your configuration. To my understanding, both IPFW (ipfw.ko) and IPFILTER (ipl.ko) can be built as modules. I have made some lmbench tests and they show that ipfilter actually adds more latency than ipfw. Here are some lmbench results taken on a P3-500, -current (2 days old) First, plain (no module loaded): UDP latency using localhost: 65 microseconds TCP latency using localhost: 67 microseconds RPC/udp latency using localhost: 111 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 71.97 MB/sec Now, ipl.ko loaded (ipfilter), no rulesets UDP latency using localhost: 80 microseconds TCP latency using localhost: 85 microseconds RPC/udp latency using localhost: 129 microseconds RPC/tcp latency using localhost: 155 microseconds TCP/IP connection cost to localhost: 145 microseconds Socket bandwidth using localhost: 67.72 MB/sec The following is for ipfw.ko loaded (default policy to accept, no other rules). UDP latency using localhost: 68 microseconds TCP latency using localhost: 73 microseconds RPC/udp latency using localhost: 115 microseconds RPC/tcp latency using localhost: 143 microseconds TCP/IP connection cost to localhost: 127 microseconds Socket bandwidth using localhost: 70.11 MB/sec And finally, both ipl.ko and ipfw.ko loaded (rather stupid imho, I think they're supposed to work as an either-or solution :) ). UDP latency using localhost: 84 microseconds TCP latency using localhost: 90 microseconds RPC/udp latency using localhost: 132 microseconds RPC/tcp latency using localhost: 160 microseconds TCP/IP connection cost to localhost: 152 microseconds Socket bandwidth using localhost: 66.04 MB/sec -- /"\ / \ / ASCII RIBBON CAMPAIGN / For every single problem you can X AGAINST HTML MAIL / find a solution, which is simple, / \ AND POSTINGS / neat and wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 6:48: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 310FE14E6F for ; Sat, 8 Jan 2000 06:48:07 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id JAA13056; Sat, 8 Jan 2000 09:48:01 -0500 (EST) From: "Allen Pulsifer" To: "Kazutaka YOKOTA" Cc: , Subject: RE: console support (was RIDE for BSD) Date: Sat, 8 Jan 2000 09:48:01 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001080640.PAA15557@zodiac.mech.utsunomiya-u.ac.jp> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazu, The comments on Linux were not mine. But I was echo'ing the orginal poster's request that the keyboard mapping and console (screen) settings be set to defaults that make sense vis-a-vis PC hardware and PC users' common expectations. That simply means that, to the extent possible, the ESC, ALT, BACKSPACE, INSERT, DELETE, HOME, END, PAGE UP, PAGE DOWN, and "arrow" keys, etc., should do something reasonable to a person who has PC experience, but no specific Unix or FreeBSD experience. It is my understanding that one of the goals of FreeBSD is to optimize the system for PC hardware. Whatever out-of-the-box behavior the system has, it should make sense to a *newbie*. The experienced user can of course take care of themself and remap the keys to anything they like. But you shouldn't have to spend hours learning the intimate details of the console, termcaps, keycaps, emacs and whatever else, just to get the ESC, ALT or BACKSPACE keys to do something useful. This is far from a "loose-loose" situation. The screen drawing problem I experienced is a separate issue. Like I said in my post: The IDE's (whose names I now forget) would often draw stuff on the screen randomly offset by one line or one column, and old stuff wouldn't get erased properly. They also threw funny characters up on the screen when it looked like they were trying to produce formatting such as colored or highlighted text. This made the tools impossible to use. At the time I wasn't sure if it was me, my setup, the tools, or something in FreeBSD. I know this isn't a very good bug report, but if someone is actively working on this stuff or if there are any plans to revisit it, let me know and I'll put in better bug reports if/when I get a chance to revisit it. The offer still stands. Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 7:14:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 85640152F5 for ; Sat, 8 Jan 2000 07:14:21 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA22582; Sat, 8 Jan 2000 10:14:14 -0500 (EST) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA04309; Sat, 8 Jan 2000 10:14:16 -0500 (EST) Received: from localhost (culverk@localhost) by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA04305; Sat, 8 Jan 2000 10:14:16 -0500 (EST) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Sat, 8 Jan 2000 10:14:16 -0500 (EST) From: Kenneth Wayne Culver To: Theo van Klaveren Cc: freebsd-current@freebsd.org Subject: Re: NewPCM issue 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've noticed the same thing on my Soundblaster Vibra 16X ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sat, 8 Jan 2000, Theo van Klaveren wrote: > > Second in the series of errors recompiling current after a month is a > bug I noticed in the NewPCM driver. It skips the last half second or so > of its output. This isn't noticeable when playing music, but sound effects > really suck. > > Relevant dmesg output: > . > sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq > 5 drq 1,5 on isa0 > sbc0: setting card to irq 5, drq 1, 5 > pcm0: on sbc0 > . > > The card is a Creative SoundBlaster AWE32. It worked about a month ago. > Does this also have something to do with the buffering issues I've seen > coming by on -current? > > /^\ | Theo van Klaveren > /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 > \_/-|-\_/ | > / | This email was powered by FreeBSD > > `He's the mad scientist, and I'm his beautiful daughter.' > - opening sentence from Heinlein's 'The number of the beast' > > > > 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 Sat Jan 8 7:26:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax1-220.dialup.optusnet.com.au [198.142.190.220]) by hub.freebsd.org (Postfix) with ESMTP id D0210151B6 for ; Sat, 8 Jan 2000 07:26:41 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id B731A5599 for ; Sun, 9 Jan 2000 02:26:35 +1100 (EST) Message-Id: <4.2.2.20000109021927.00dba250@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 09 Jan 2000 02:26:30 +1100 To: freebsd-current@FreeBSD.ORG From: james Subject: RE: 4.0 slower than 3.4? In-Reply-To: References: 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 Hi, Sorry.. It seems i've stuffed up here. Somehow ipf was enabled. Doing "ipf -D" has sped things up. However, i am still seeing a 10-20% speed decrease from 3.4-STABLE. FTP transfers are still only on 5.8MB/s - not 7.7MB/s like they used to be. It's interesting though how i had no ipf rules whatsoever, yet it introduced so much latency, as Alexander has pointed out in another email. Why is ipf so slow? I was planning on switching from ipfw/natd to ipf/ipnat, but i don't think i want to now - considering it's so darn slow. Would it make a speed difference if i have ipf sitting there but disabled with "ipf -D"? Once again, sorry for buggering up. :( Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 7:36:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 116BD15060 for ; Sat, 8 Jan 2000 07:36:32 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id AAA14035; Sun, 9 Jan 2000 00:36:23 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id AAA25065; Sun, 9 Jan 2000 00:36:23 +0900 (JST) Received: from localhost ([192.168.245.81]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id AAA26453; Sun, 9 Jan 2000 00:36:15 +0900 (JST) To: ab@astralblue.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: References: <20000108183353S.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000109003651V.shin@nd.net.fujitsu.co.jp> Date: Sun, 09 Jan 2000 00:36:51 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks! Your patch worked so now there's no problem getting outside > using natd. It is good info. I committed it. > I've gone through the checklist in your original message as well, and > have found so far: Thanks a lot. > 1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the > ``default'' route. I've used this command to establish my default > route: route -n add -inet6 -net default -prefixlen 0 -interface gif0 I tried the bug fix in recent KAME repository as itojun specified, and it seems to fix the problem, so I also commited it. Please try (1),(3) and (4) again with updated route command. > 2) Here's the output you requested: Thanks, everything seems fine. > 5) IPsec between 2 hosts/routers: still studying these topics. :-) > Things have changed since last time I tried IPsec tunneling using KAME, > so I can't set it up quickly (at least it seems that spdadd command of > setkey(8) has been extended a lot). Relatively new explanatioin about IPsec related configurations can be obtained from below. Please try it. http://www.kame.net/newsletter/19991007/ Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 7:45:23 2000 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 C7A7D15060; Sat, 8 Jan 2000 07:45:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA22953; Sat, 8 Jan 2000 08:45:04 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA41787; Sat, 8 Jan 2000 08:45:03 -0700 (MST) Message-Id: <200001081545.IAA41787@harmony.village.org> To: Brian Somers Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: obrien@NUXI.com, committers@FreeBSD.org, current@FreeBSD.org, brian@hak.lan.Awfulhak.org In-reply-to: Your message of "Fri, 07 Jan 2000 14:32:10 GMT." <200001071432.OAA00514@hak.lan.Awfulhak.org> References: <200001071432.OAA00514@hak.lan.Awfulhak.org> Date: Sat, 08 Jan 2000 08:45:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001071432.OAA00514@hak.lan.Awfulhak.org> Brian Somers writes: : Also, with a 3c589c, hot plugging is like playing Russian Roulette : with five of the six chambers full at the moment. Just booting with : a pccard inserted sometimes crashes the machine. I think most : peoples view of the current pccard stuff would be that it's far : inferior to RELENG_3. OK. I'm *VERY* interested in this. I've not seen these problems and would like to track them down. I've seen minor little things from time to time, but nothing as major as this. Please contact me off the list so that we can get this one killed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 8: 3:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7DE9415ACC for ; Sat, 8 Jan 2000 08:03:09 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA10786; Sat, 8 Jan 2000 17:03:29 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001081603.RAA10786@info.iet.unipi.it> Subject: ipf vs. ipfw In-Reply-To: <4.2.2.20000109021927.00dba250@mail.southcom.com.au> from james at "Jan 9, 2000 02:26:30 am" To: james Date: Sat, 8 Jan 2000 17:03:29 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is ipf so slow? I was planning on switching from ipfw/natd to > ipf/ipnat, but i don't think i want to now - considering it's so darn slow. ok, i have heard for a long time people claiming how much better is ipf over ipfw etc. etc. I have briefly looked at docs and source for ipf. I think the basic rulechecking algorithms in ipf are no better/faster than the ones in ipfw. If you want to switch from ipfw (no natd!) to ipf just for performance reasons, i think you are not going to get any significant advantage if any (i mean, if you write your ipfw rules in an intelligent way.). For sure the pair ipf/ipnat should be faster than ipfw/natd, but just because natd is a user-space thing and this means additional data movements between kernel and user space that ipf needs not. Other reasons for the switch could be the fact that ipf is stateful (but i am working on adding state to ipfw, if i find proper support - hint, hint), so you can build better things. In other words, if you want to switch, be motivated by features, not by performance! cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 10: 6:13 2000 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 50E2214D5C for ; Sat, 8 Jan 2000 10:06:11 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id NAA08667 for ; Sat, 8 Jan 2000 13:05:59 -0500 (EST) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA11681 for ; Sat, 8 Jan 2000 13:06:00 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA11677 for ; Sat, 8 Jan 2000 13:05:59 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sat, 8 Jan 2000 13:05:59 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: make world problem... 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 Alright, I've tried making each of the individual targets and I still get this error so I'm stumped... a gzipped copy of the make world log can be found at http://www.wam.umd.edu/~culverk/world.log.gz The error occurs while building kdump, and the error (of course) is at the end of the file. 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 Jan 8 10:23:32 2000 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 3456B15747 for ; Sat, 8 Jan 2000 10:23:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA72905; Sat, 8 Jan 2000 10:23:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA31708; Sat, 8 Jan 2000 10:23:12 -0800 (PST) (envelope-from obrien) Date: Sat, 8 Jan 2000 10:23:12 -0800 From: "David O'Brien" To: Brian Somers Cc: freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: hak.lan.Awfulhak.org daily run output Message-ID: <20000108102312.I1417@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <200001070832.IAA01463@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001070832.IAA01463@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Fri, Jan 07, 2000 at 08:32:19AM +0000 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 Fri, Jan 07, 2000 at 08:32:19AM +0000, Brian Somers wrote: > Anyone know what's changed with `calendar' ? I suspect it's the > recent cpp changes. Please test this patch. Index: io.c =================================================================== RCS file: /home/ncvs/src/usr.bin/calendar/io.c,v retrieving revision 1.12 diff -u -r1.12 io.c --- io.c 1999/08/28 00:59:17 1.12 +++ io.c 2000/01/08 18:22:00 @@ -274,7 +274,8 @@ warnx("setuid failed"); _exit(1); } - execl(_PATH_CPP, "cpp", "-P", "-I.", _PATH_INCLUDE, NULL); + execl(_PATH_CPP, "cpp", "-traditional", "-P","-nostdinc", + "-I.", _PATH_INCLUDE, NULL); warn(_PATH_CPP); _exit(1); } Index: pathnames.h =================================================================== RCS file: /home/ncvs/src/usr.bin/calendar/pathnames.h,v retrieving revision 1.2 diff -u -r1.2 pathnames.h --- pathnames.h 1996/02/02 06:02:41 1.2 +++ pathnames.h 2000/01/08 18:21:01 @@ -35,7 +35,7 @@ #include -#define _PATH_CPP "/usr/bin/cpp" +#define _PATH_CPP "/usr/libexec/cpp" /* XXX -- fix when cpp parses arguments rationally */ #define _PATH_INCLUDE "-I/usr/share/calendar" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 10:27:15 2000 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 2003C14D76 for ; Sat, 8 Jan 2000 10:27:13 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA51429; Sat, 8 Jan 2000 13:26:55 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 13:26:55 -0500 (EST) From: Garrett Wollman Message-Id: <200001081826.NAA51429@khavrinen.lcs.mit.edu> To: "Alexander Sanda" Cc: Subject: RE: 4.0 slower than 3.4? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > First, plain (no module loaded): You should also try it with `options COMPAT_IPFW=0' in your config file. -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 Sat Jan 8 10:32:40 2000 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 3EE8A15228 for ; Sat, 8 Jan 2000 10:32:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA51499; Sat, 8 Jan 2000 13:32:34 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 13:32:34 -0500 (EST) From: Garrett Wollman Message-Id: <200001081832.NAA51499@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: freebsd-current@FreeBSD.ORG Subject: Re: performance of FreeBSD-current as SMP In-Reply-To: <200001081602.KAA11960@cs.rice.edu> References: <20000108134110.B442@cichlids.cichlids.com> <200001081602.KAA11960@cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Not network-related; moved to -current.] < said: > Good Lord! This is the second time now. I even SAID in my last two mails that > there is only ONE processor. Theortically then, FreeBSD configured with/without > SMP support shouldn't make any difference. Yes it should. SMP support enables inter-processor locking code which does not exist in non-SMP kernels. Ergo, non-SMP kernels run uniprocessor tasks faster. -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 Sat Jan 8 10:34:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id DB3D81569D for ; Sat, 8 Jan 2000 10:34:29 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id MAA14332; Sat, 8 Jan 2000 12:34:24 -0600 (CST) From: Mohit Aron Message-Id: <200001081834.MAA14332@cs.rice.edu> Subject: Re: performance of FreeBSD-current as SMP To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Sat, 8 Jan 2000 12:34:24 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <200001081832.NAA51499@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Jan 8, 2000 01:32:34 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes it should. SMP support enables inter-processor locking code which > does not exist in non-SMP kernels. Ergo, non-SMP kernels run > uniprocessor tasks faster. > Well, some difference is to be expected. But 22% ???? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 10:38:32 2000 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 CCE331569D for ; Sat, 8 Jan 2000 10:38:29 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA51522; Sat, 8 Jan 2000 13:38:28 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 13:38:28 -0500 (EST) From: Garrett Wollman Message-Id: <200001081838.NAA51522@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@freebsd.org Subject: Re: performance of FreeBSD-current as SMP In-Reply-To: <200001081834.MAA14332@cs.rice.edu> References: <200001081832.NAA51499@khavrinen.lcs.mit.edu> <200001081834.MAA14332@cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Well, some difference is to be expected. But 22% ???? Flaws in the Intel SMP design make it more expensive than it ought to be. Things like atomic RMW cycles are very, very expensive. (We had a discussion about six months ago about how expensive something like a locked xchg instruction actually is.) -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 Sat Jan 8 10:38:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0A98514BFD for ; Sat, 8 Jan 2000 10:38:32 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id KAA60495; Sat, 8 Jan 2000 10:38:26 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000108103747.00aa1780@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 08 Jan 2000 10:38:26 -0800 To: obrien@NUXI.com, Brian Somers From: Manfred Antar Subject: Re: hak.lan.Awfulhak.org daily run output Cc: freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org In-Reply-To: <20000108102312.I1417@dragon.nuxi.com> References: <200001070832.IAA01463@hak.lan.Awfulhak.org> <200001070832.IAA01463@hak.lan.Awfulhak.org> 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:23 AM 1/8/00 -0800, David O'Brien wrote: >On Fri, Jan 07, 2000 at 08:32:19AM +0000, Brian Somers wrote: > > Anyone know what's changed with `calendar' ? I suspect it's the > > recent cpp changes. > >Please test this patch. I was having the same problem and the patch worked for me Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 11: 0: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3685914DCD for ; Sat, 8 Jan 2000 11:00:05 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.19.211] (dialup211.brussels.skynet.be [195.238.19.211]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA22758; Sat, 8 Jan 2000 19:59:56 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001081603.RAA10786@info.iet.unipi.it> References: <200001081603.RAA10786@info.iet.unipi.it> Date: Sat, 8 Jan 2000 19:40:07 +0100 To: Luigi Rizzo , james From: Brad Knowles Subject: Re: ipf vs. ipfw Cc: freebsd-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 5:03 PM +0100 2000/1/8, Luigi Rizzo wrote: > Other reasons for the switch could be the fact that ipf is stateful > (but i am working on adding state to ipfw, if i find proper support > - hint, hint), so you can build better things. I'm moving towards using ipfilter on our Solaris machines, primarily as a "super TCP-Wrappers" solution for improved host security, and what I've done so far it looks like the statefulness will be extremely useful. I really appreciate that ipfilter works on many different platforms, not just one. However, if I can get the good features of ipfilter with ipfw under FreeBSD, I'd consider that to be sufficient reason to consider using ipfw instead. -- 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 Sat Jan 8 11: 8:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id EF91D14E21; Sat, 8 Jan 2000 11:08:26 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas3-44-149.dial.proxad.net [212.27.44.149]) by postfix1.free.fr (Postfix) with ESMTP id A7A1C28362; Sat, 8 Jan 2000 20:04:05 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id VAA01905; Sat, 8 Jan 2000 21:12:52 +0100 (CET) (envelope-from nsouch) Message-ID: <20000108211251.44627@breizh.free.fr> Date: Sat, 8 Jan 2000 21:12:51 +0100 From: Nicolas Souchu To: committers@freebsd.org Cc: current@freebsd.org Subject: ppbus in 4.0-stable? (was: Re: 4.0 code freeze scheduled for Jan 15th) References: <28153.947101446@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <28153.947101446@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Jan 05, 2000 at 11:44:06AM -0800 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi committers! On Wed, Jan 05, 2000 at 11:44:06AM -0800, Jordan K. Hubbard wrote: > >And given that we've already slipped from December 15th, I think you >can treat this as a pretty hard deadline, to be further slipped only >grudgingly and in response to clear and dire need. > >10 days, folks! Make 'em count.. :) > As usual, the last wheel of the coach: ppbus. You may or may not know new-ppbus is now available for the newbus interfaces. It would make it really easier to maintain it if submitted before the -stable jump. http://www.freebsd.org/~nsouch/ppbus.html reports the improvements. Regression tests shows the newppbus is quite solid... but now I can't rely on a wild commit which would force everybody to test it :) So, please try it! And we'll decide. Thanks in advance, and sorry for being so late :( Nicholas. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sat Jan 8 11:10:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 446D914EE0; Sat, 8 Jan 2000 11:10:55 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas3-44-149.dial.proxad.net [212.27.44.149]) by postfix2.free.fr (Postfix) with ESMTP id E811374260; Sat, 8 Jan 2000 20:10:52 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id VAA01930; Sat, 8 Jan 2000 21:18:38 +0100 (CET) (envelope-from nsouch) Message-ID: <20000108211838.12590@breizh.free.fr> Date: Sat, 8 Jan 2000 21:18:38 +0100 From: Nicolas Souchu To: Maxim Sobolev Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> <20000104210015.63255@breizh.free.fr> <3873C990.70D294F7@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3873C990.70D294F7@altavista.net>; from Maxim Sobolev on Thu, Jan 06, 2000 at 12:45:36AM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 12:45:36AM +0200, Maxim Sobolev wrote: > >Nicolas Souchu wrote: > >> On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: >> > >> >Nicolas Souchu wrote: >> > >> >> Hi there! >> >> >> >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current >> >> >> >> A major ppbus(4) release is available for beta-testing. >> > >> >Good work! Now plip, which has been broken for ages, works perfectly - no more >> >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X >> >and NFS working over plip line, things which was impossible with oldppbus. >> >> Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) >> in you MACHINE config file would have done the job. > >Unfortunately it is not a solution because net,tty and bio keywords went away from >config(8) long time ago... I've only received `syntax error' message. Ooops! A really bad thing. I did not notice it. They did not use to manage compatibility issues like this before?! > >-Maxim > > > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sat Jan 8 11:30:47 2000 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 70E62150EF for ; Sat, 8 Jan 2000 11:30:45 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.3) with SMTP id TAA45421 for ; Sat, 8 Jan 2000 19:30:44 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.20000108112936.0095f440@localhost> X-Sender: kurt@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 08 Jan 2000 11:29:36 -0800 To: freebsd-current@freebsd.org From: "Kurt D. Zeilenga" Subject: PAM'ized su(1) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed that su(1) is not yet PAM'ized. Is anybody working on this? If so, I'm willing to test. If not and time permits, I'll see if I can whip up an appropriate patch. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 11:32:45 2000 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 94E5314EE0 for ; Sat, 8 Jan 2000 11:32:43 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA52181; Sat, 8 Jan 2000 14:32:41 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 14:32:41 -0500 (EST) From: Garrett Wollman Message-Id: <200001081932.OAA52181@khavrinen.lcs.mit.edu> To: "Kurt D. Zeilenga" Cc: freebsd-current@FreeBSD.ORG Subject: PAM'ized su(1) In-Reply-To: <3.0.5.32.20000108112936.0095f440@localhost> References: <3.0.5.32.20000108112936.0095f440@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I've noticed that su(1) is not yet PAM'ized. Is anybody > working on this? If so, I'm willing to test. If not > and time permits, I'll see if I can whip up an appropriate > patch. If you do this, please take care not to break WHEELSU (and its Kerberos equivalent), which has its fingers everywhere. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 11:56:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 7FB14151ED for ; Sat, 8 Jan 2000 11:55:56 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id OAA49349; Sat, 8 Jan 2000 14:53:38 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Sat, 8 Jan 2000 14:53:38 -0500 (EST) From: Adam To: Kenneth Wayne Culver Cc: Theo van Klaveren , freebsd-current@FreeBSD.ORG Subject: Re: NewPCM issue 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 believe I get the same thing too on my nonpnp SB16. Only noticed it when playing short au files (didn't test anything else because it wasnt noticable) On Sat, 8 Jan 2000, Kenneth Wayne Culver wrote: >I've noticed the same thing on my Soundblaster Vibra 16X > > >================================================================= >| Kenneth Culver | FreeBSD: The best OS around. | >| Unix Systems Administrator | ICQ #: 24767726 | >| and student at The | AIM: AgRSkaterq | >| The University of Maryland, | Website: (Under Construction) | >| College Park. | http://www.wam.umd.edu/~culverk/| >================================================================= > >On Sat, 8 Jan 2000, Theo van Klaveren wrote: > >> >> Second in the series of errors recompiling current after a month is a >> bug I noticed in the NewPCM driver. It skips the last half second or so >> of its output. This isn't noticeable when playing music, but sound effects >> really suck. >> >> Relevant dmesg output: >> . >> sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq >> 5 drq 1,5 on isa0 >> sbc0: setting card to irq 5, drq 1, 5 >> pcm0: on sbc0 >> . >> >> The card is a Creative SoundBlaster AWE32. It worked about a month ago. >> Does this also have something to do with the buffering issues I've seen >> coming by on -current? >> >> /^\ | Theo van Klaveren >> /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 >> \_/-|-\_/ | >> / | This email was powered by FreeBSD >> >> `He's the mad scientist, and I'm his beautiful daughter.' >> - opening sentence from Heinlein's 'The number of the beast' >> >> >> >> 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 12:44:29 2000 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 0406014FAC for ; Sat, 8 Jan 2000 12:44:18 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.3) with SMTP id UAA46052; Sat, 8 Jan 2000 20:44:06 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.20000108124258.0093bb90@localhost> X-Sender: kurt@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 08 Jan 2000 12:42:58 -0800 To: Garrett Wollman From: "Kurt D. Zeilenga" Subject: Re: PAM'ized su(1) Cc: freebsd-current@freebsd.org In-Reply-To: <200001081932.OAA52181@khavrinen.lcs.mit.edu> References: <3.0.5.32.20000108112936.0095f440@localhost> <3.0.5.32.20000108112936.0095f440@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:32 PM 1/8/00 -0500, Garrett wrote: >< said: > >> I've noticed that su(1) is not yet PAM'ized. Is anybody >> working on this? If so, I'm willing to test. If not >> and time permits, I'll see if I can whip up an appropriate >> patch. > >If you do this, please take care not to break WHEELSU (and its >Kerberos equivalent), which has its fingers everywhere. I would suggest: If NO_PAM, the behavior would be simple, traditional BSD behavior with very few optional features (such as WHEELSU). If PAM, then Kerberos and Skey support would be provided via appropriate PAM modules. This means that auth.conf can go away. WHEELSU can (and should) be provided by pam_wheel. So, the very first thing I would do to PAM'ize su.c would be to: mv su.c su.c.orig unifdef -UKERBEROS -USKEY < su.c.orig > su.c Then I would add in PAM calls behind #ifndef NO_PAM. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 12:59:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id C622A14E9A; Sat, 8 Jan 2000 12:59:30 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA16137; Sat, 8 Jan 2000 14:59:29 -0600 (CST) From: Mohit Aron Message-Id: <200001082059.OAA16137@cs.rice.edu> Subject: SMP kernel panics after calling acquire_timer0 To: freebsd-bugs@freebsd.org, freebsd-current@freebsd.org Date: Sat, 8 Jan 2000 14:59:29 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using FreeBSD-current (snapshot from Jan 3rd) which is configured with both SMP and APIC_IO support. This version panics upon calling acquire_timer0() (to modify the interrupt frequency of the 8254). On the other hand, if the kernel is not configured as an SMP, then it works fine. The panic reports some problem with some SMP lock - I can get more details if someone is interested in looking at the problem. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 13: 8:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 7E06515153 for ; Sat, 8 Jan 2000 13:08:27 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 2229534 invoked from network); 8 Jan 2000 21:12:44 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 8 Jan 2000 21:12:44 -0000 Message-ID: <3877A77B.F6E6CA@cybercable.fr> Date: Sat, 08 Jan 2000 22:09:15 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mohit Aron Cc: freebsd-bugs@freebsd.org, freebsd-current@freebsd.org Subject: Re: SMP kernel panics after calling acquire_timer0 References: <200001082059.OAA16137@cs.rice.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, You may want to upgrade to a more recent source tree : I've cvsupped from a 4.0-19991229-CURRENT snapshot to the sources around 01/05 21h00 GMT and SMP works fine on my machine (I have seen strange things with the snapshot : cvs did not want to check out the source tree ! not a pleasant discovery when wanting to update the sources) Is your machine specific in some ways ? (Compaq, for example) You may also post excerpts from your dmesg when booting as UP. TfH Mohit Aron wrote: > > Hi, > I'm using FreeBSD-current (snapshot from Jan 3rd) which is configured > with both SMP and APIC_IO support. This version panics upon calling > acquire_timer0() (to modify the interrupt frequency of the 8254). On the other > hand, if the kernel is not configured as an SMP, then it works fine. The panic > reports some problem with some SMP lock - I can get more details if someone > is interested in looking at the problem. > > - Mohit > > 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 Sat Jan 8 13:14:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id A949114DA4 for ; Sat, 8 Jan 2000 13:14:10 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id PAA16430; Sat, 8 Jan 2000 15:14:07 -0600 (CST) From: Mohit Aron Message-Id: <200001082114.PAA16430@cs.rice.edu> Subject: Re: SMP kernel panics after calling acquire_timer0 To: herbelot@cybercable.fr (Thierry Herbelot) Date: Sat, 8 Jan 2000 15:14:07 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <3877A77B.F6E6CA@cybercable.fr> from "Thierry Herbelot" at Jan 8, 2000 10:09:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You may want to upgrade to a more recent source tree : > I've cvsupped from a 4.0-19991229-CURRENT snapshot to the sources around > 01/05 21h00 GMT and SMP works fine on my machine (I have seen strange > things with the snapshot : cvs did not want to check out the source tree > ! not a pleasant discovery when wanting to update the sources) > Well, SMP does work fine otherwise - I was doing experiments with some past code that I ported over to FreeBSD-4.0. As soon as I make the call acquire_timer0, it panics. I'm sorry if my mail earlier made it appear as if I can't even bring up the machine as an SMP. > Is your machine specific in some ways ? (Compaq, for example) > Its a standard 500MHz Xeon processor in a server machine. I don't think there's anything specific. > You may also post excerpts from your dmesg when booting as UP. > Here are some if they help: Jan 8 00:33:43 idli /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 8 00:33:43 idli /kernel: CPU: Pentium III/Xeon (500.04-MHz 686-class CPU) Jan 8 00:33:43 idli /kernel: Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Jan 8 00:33:43 idli /kernel: Features=0x387fbff Jan 8 00:33:43 idli /kernel: real memory = 1342177280 (1310720K bytes) Jan 8 00:33:43 idli /kernel: avail memory = 1297195008 (1266792K bytes) Jan 8 00:33:43 idli /kernel: Preloaded elf kernel "kernel" at 0xc0382000. Jan 8 00:33:43 idli /kernel: Pentium Pro MTRR support enabled - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 13:43:34 2000 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 BCF2F15274 for ; Sat, 8 Jan 2000 13:43:19 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA52528; Sat, 8 Jan 2000 16:43:13 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 16:43:13 -0500 (EST) From: Garrett Wollman Message-Id: <200001082143.QAA52528@khavrinen.lcs.mit.edu> To: "Kurt D. Zeilenga" Cc: Garrett Wollman , freebsd-current@freebsd.org Subject: Re: PAM'ized su(1) In-Reply-To: <3.0.5.32.20000108124258.0093bb90@localhost> References: <3.0.5.32.20000108112936.0095f440@localhost> <200001081932.OAA52181@khavrinen.lcs.mit.edu> <3.0.5.32.20000108124258.0093bb90@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > can go away. WHEELSU can (and should) be provided by > pam_wheel. wollman@khavrinen(2996)$ ls /usr/lib/pam_*.so /usr/lib/pam_cleartext_pass_ok.so /usr/lib/pam_radius.so /usr/lib/pam_deny.so /usr/lib/pam_skey.so /usr/lib/pam_kerberosIV.so /usr/lib/pam_tacplus.so /usr/lib/pam_permit.so /usr/lib/pam_unix.so Hmmm. I don't see any such module. Or are you proposing to write one? (I'm clearly misunderstanding some fundamental part of PAM, since I don't see how, based on our current usage, anything like the proper `su' behavior for WHEELSU and Kerberos can be provided -- unless you provide all the N*M combination of modules required.) -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 Sat Jan 8 13:52:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 43F1F14C01; Sat, 8 Jan 2000 13:52:47 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id IAA17395; Sun, 9 Jan 2000 08:52:36 +1100 Date: Sun, 9 Jan 2000 08:52:33 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mohit Aron Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: SMP kernel panics after calling acquire_timer0 In-Reply-To: <200001082059.OAA16137@cs.rice.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 On Sat, 8 Jan 2000, Mohit Aron wrote: > Hi, > I'm using FreeBSD-current (snapshot from Jan 3rd) which is configured > with both SMP and APIC_IO support. This version panics upon calling > acquire_timer0() (to modify the interrupt frequency of the 8254). On the other > hand, if the kernel is not configured as an SMP, then it works fine. The panic > reports some problem with some SMP lock - I can get more details if someone > is interested in looking at the problem. This is cause by calling disable_intr() when a lock is held. disable_intr() is a funky macro in the SMP case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 14:15:40 2000 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 20B3414CB0 for ; Sat, 8 Jan 2000 14:15:38 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.3) with SMTP id WAA46754; Sat, 8 Jan 2000 22:15:18 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.20000108141410.00933c40@localhost> X-Sender: kurt@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 08 Jan 2000 14:14:10 -0800 To: Garrett Wollman From: "Kurt D. Zeilenga" Subject: Re: PAM'ized su(1) Cc: Garrett Wollman , freebsd-current@freebsd.org In-Reply-To: <200001082143.QAA52528@khavrinen.lcs.mit.edu> References: <3.0.5.32.20000108124258.0093bb90@localhost> <3.0.5.32.20000108112936.0095f440@localhost> <200001081932.OAA52181@khavrinen.lcs.mit.edu> <3.0.5.32.20000108124258.0093bb90@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:43 PM 1/8/00 -0500, Garrett Wollman wrote: >Hmmm. I don't see any such module. Or are you proposing to write >one? No. I'd just pull the pam_wheel from the Attic. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 15: 9: 3 2000 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 E397D14BED for ; Sat, 8 Jan 2000 15:09:00 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Jan 2000 23:08:36 +0000 (GMT) Date: Sat, 8 Jan 2000 23:08:35 +0000 From: David Malone To: "Kurt D. Zeilenga" Cc: Garrett Wollman , freebsd-current@freebsd.org Subject: Re: PAM'ized su(1) Message-ID: <20000108230835.A88514@walton.maths.tcd.ie> References: <3.0.5.32.20000108124258.0093bb90@localhost> <3.0.5.32.20000108112936.0095f440@localhost> <200001081932.OAA52181@khavrinen.lcs.mit.edu> <3.0.5.32.20000108124258.0093bb90@localhost> <200001082143.QAA52528@khavrinen.lcs.mit.edu> <3.0.5.32.20000108141410.00933c40@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.5.32.20000108141410.00933c40@localhost>; from Kurt@OpenLDAP.org on Sat, Jan 08, 2000 at 02:14:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 08, 2000 at 02:14:10PM -0800, Kurt D. Zeilenga wrote: > At 04:43 PM 1/8/00 -0500, Garrett Wollman wrote: > >Hmmm. I don't see any such module. Or are you proposing to write > >one? > > No. I'd just pull the pam_wheel from the Attic. If it came from the linux version of pam, then pam_wheel is broken. It uses the groups of the person listed in utmp as owning the tty, instead of the groups of the person running su. This breaks stuff like su'ing to a sysadmin and then su'ing to root from a normal users terminal, and means you can't su without a utmp entry. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 15:26: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 3298714EF5 for ; Sat, 8 Jan 2000 15:25:31 -0800 (PST) (envelope-from osa@ozz.freebsd.org.ru) Received: (from osa@localhost) by ozz.freebsd.org.ru (8.9.3/8.9.3) id CAA00845 for freebsd-current@FreeBSD.org; Sun, 9 Jan 2000 02:25:18 +0300 (MSK) (envelope-from osa) Date: Sun, 9 Jan 2000 02:25:17 +0300 From: Sergey Osokin To: freebsd-current@FreeBSD.org Subject: newpcm can't play wave files after cvsup+make world... Message-ID: <20000109022517.A443@freebsd.org.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I think after some -stable period -current stay now like current :-) I can't play wave files after upgrade my -current... % ls -al /dev/MAKEDEV -r-xr-xr-x 1 root wheel 35926 8 ÑÎ× 23:11 /dev/MAKEDEV % uname -a FreeBSD ozz.freebsd.org.ru 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 9 02:10:04 MSK 2000 osa@ozz.freebsd.org.ru:/usr/src/sys/compile/SONIC i386 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 9 2000 02:09:08 Installed devices: pcm0: at io 0xe800 irq 10 (1/1 channels duplex) % dmesg | grep pcm pcm0: port 0xe800-0xe83f irq 10 at device 11.0 on pci0 At kernel description of my card looks like this: device pcm0 # Sound Blaster 128 PCI device sbc0 # device joy0 at isa? port IO_GAME # Rgdz, Sergey A. Osokin aka oZZ, osa@FreeBSD.org.ru osa@etrust.ru http://www.freebsd.org.ru/~osa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 15:49:49 2000 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 BF97514ED3 for ; Sat, 8 Jan 2000 15:49:47 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.3/8.9.3) with SMTP id XAA47330; Sat, 8 Jan 2000 23:49:43 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.20000108154833.00932930@localhost> X-Sender: kurt@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 08 Jan 2000 15:48:33 -0800 To: David Malone From: "Kurt D. Zeilenga" Subject: Re: PAM'ized su(1) Cc: Garrett Wollman , freebsd-current@freebsd.org In-Reply-To: <20000108230835.A88514@walton.maths.tcd.ie> References: <3.0.5.32.20000108141410.00933c40@localhost> <3.0.5.32.20000108124258.0093bb90@localhost> <3.0.5.32.20000108112936.0095f440@localhost> <200001081932.OAA52181@khavrinen.lcs.mit.edu> <3.0.5.32.20000108124258.0093bb90@localhost> <200001082143.QAA52528@khavrinen.lcs.mit.edu> <3.0.5.32.20000108141410.00933c40@localhost> 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:08 PM 1/8/00 +0000, David Malone wrote: >On Sat, Jan 08, 2000 at 02:14:10PM -0800, Kurt D. Zeilenga wrote: >> At 04:43 PM 1/8/00 -0500, Garrett Wollman wrote: >> >Hmmm. I don't see any such module. Or are you proposing to write >> >one? >> >> No. I'd just pull the pam_wheel from the Attic. > >If it came from the linux version of pam, then pam_wheel is broken. Did you try the "use_uid" option? Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 16:58:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 1C5F615060 for ; Sat, 8 Jan 2000 16:58:10 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.254.39]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id TAA02365; Sat, 8 Jan 2000 19:57:59 -0500 (EST) Message-ID: <3877DD18.D8BF669F@acm.org> Date: Sat, 08 Jan 2000 19:58:00 -0500 From: Jim Bloom X-Mailer: Mozilla 4.7 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help References: <20000108133114L.shin@nd.net.fujitsu.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added the options a couple weeks ago. Everthing has been working fairly well. Two issues I have seen which I haven't verified if they are are related to INET6 or something else. First, ever since I added INET6, I have been seeing errors like looutput: af=0 unexpected (or something close to that) These are appearing frequently (several a minute). (There also is no newline after this error message in the kernel.) I ran cvsup around 15:00 EST today and built world and a new kernel. After rebooting, I started getting error messages from dhclient about unsupported address families. I haven't looked into this to determine if dhclient is working correctly and reporting warnings or is not working at all. I'll try to do some more checking later tonight or tomorrow. I'll also try to do more testing of INET6 in general. Starting in another week, I'll be unemployed and will use the time (when I'm not job hunting) to try and set up a network of a couple machines for testing. I can probably put a gateway in the middle as well. Jim Bloom bloom@acm.org Yoshinobu Inoue wrote: > > The 1st thing I want to be tested is that, a kernel with > following additions to the config file > > options INET6 #IPv6 communications protocols > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > options IPSEC_DEBUG #debug for IP security > > pseudo-device gif 4 #IPv6 and IPv4 tunneling > pseudo-device faith 1 #for IPv6 and IPv4 translation > > just works fine, > and also all apps on your environments which you are usually > using still works fine on that kernel. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 17:12: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from radio.kabsi.at (mx.kabelsignal.at [195.202.129.3]) by hub.freebsd.org (Postfix) with ESMTP id 4E91C1510F for ; Sat, 8 Jan 2000 17:12:02 -0800 (PST) (envelope-from entropy@kabsi.at) Received: from darkstar ([195.202.172.28]) by radio.kabsi.at (8.9.1/8.9.1) with SMTP id CAA09995; Sun, 9 Jan 2000 02:11:50 +0100 From: "Alexander Sanda" To: "Garrett Wollman" Cc: Subject: RE: 4.0 slower than 3.4? Date: Sun, 9 Jan 2000 02:11:49 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001081826.NAA51429@khavrinen.lcs.mit.edu> X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman [mailto:wollman@khavrinen.lcs.mit.edu] wrote: Sent: Saturday, January 08, 2000 7:27 PM > You should also try it with `options COMPAT_IPFW=0' in your config > file. Hm, what's this option for? When I put it into my kernel config, the config program complained about an "unknown option". A quick grep over the kernel sources also didn't find it anywhere. Anyway, since I'am using ipfilter as a module, I still have IPFILTER_LKM in my config file (it is required, otherwise the ipl.ko kernel module will not load and complain about a undefined function). This option is still in the source (ip_input.c and ip_output.c), but is missing in the configuration files (even in LINT) for some (?) reason. After removing IPFILTER_LKM, I ran the bench again and got following results. UDP latency using localhost: 63 microseconds TCP latency using localhost: 66 microseconds RPC/udp latency using localhost: 109 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 72.63 MB/sec - -------------------------------------------------------- To make comparing easier, here are the results I already posted yesterday. First, plain (no module loaded): UDP latency using localhost: 65 microseconds TCP latency using localhost: 67 microseconds RPC/udp latency using localhost: 111 microseconds RPC/tcp latency using localhost: 139 microseconds TCP/IP connection cost to localhost: 119 microseconds Socket bandwidth using localhost: 71.97 MB/sec Now, ipl.ko loaded (ipfilter), no rulesets UDP latency using localhost: 80 microseconds TCP latency using localhost: 85 microseconds RPC/udp latency using localhost: 129 microseconds RPC/tcp latency using localhost: 155 microseconds TCP/IP connection cost to localhost: 145 microseconds Socket bandwidth using localhost: 67.72 MB/sec The following is for ipfw.ko loaded (default policy to accept, no other rules). UDP latency using localhost: 68 microseconds TCP latency using localhost: 73 microseconds RPC/udp latency using localhost: 115 microseconds RPC/tcp latency using localhost: 143 microseconds TCP/IP connection cost to localhost: 127 microseconds Socket bandwidth using localhost: 70.11 MB/sec And finally, both ipl.ko and ipfw.ko loaded (rather stupid imho, I think they're supposed to work as an either-or solution :) ). UDP latency using localhost: 84 microseconds TCP latency using localhost: 90 microseconds RPC/udp latency using localhost: 132 microseconds RPC/tcp latency using localhost: 160 microseconds TCP/IP connection cost to localhost: 152 microseconds Socket bandwidth using localhost: 66.04 MB/sec -- /"\ / \ / ASCII RIBBON CAMPAIGN / For every single problem you can X AGAINST HTML MAIL / find a solution, which is simple, / \ AND POSTINGS / neat and wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 17:25:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from crash.ab.videon.ca (crash.ab.videon.ca [206.75.216.220]) by hub.freebsd.org (Postfix) with ESMTP id E23D914DFC for ; Sat, 8 Jan 2000 17:25:18 -0800 (PST) (envelope-from cwasser@v-wave.com) Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by crash.ab.videon.ca (8.9.2/8.9.2) with SMTP id SAA14745; Sat, 8 Jan 2000 18:23:55 -0700 (MST) From: Chris Wasser To: "Alexander Sanda" Cc: "Garrett Wollman" , Subject: Re: 4.0 slower than 3.4? Date: Sat, 08 Jan 2000 18:21:55 -0700 Reply-To: cwasser@v-wave.com Message-ID: References: <200001081826.NAA51429@khavrinen.lcs.mit.edu> In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 9 Jan 2000 02:11:49 +0100, you wrote: >After removing IPFILTER_LKM, I ran the bench again and got following >results. What benchmark utility are you using to measure these results with? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 18: 6:23 2000 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 9BAC214E44; Sat, 8 Jan 2000 18:06:17 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id DAA75669; Sun, 9 Jan 2000 03:06:15 +0100 (CET) (envelope-from olli) Date: Sun, 9 Jan 2000 03:06:15 +0100 (CET) Message-Id: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: load spike strangeness X-Newsgroups: list.freebsd-stable In-Reply-To: <85820f$qbq$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 FreeBSD wrote in list.freebsd-stable: > Overclocking is *NEVER* recommended Neither is posting anonymously (without a realname). (Sorry -- Back to the topic.) I have to admit that I've seen the same symptoms, and I have no idea what's causing it. It happenes very irregularly (and rarely), but it clearly _does_ happen sometimes. It doesn't seem to be related to any particular hardware or FreeBSD ver- sion, I have seen it on both 3.x and 4.0-current boxes. On some machines it never happened at all (including some busy servers), at least not while I was logged in and watched it (it's possible that it happened without me noticing at all). It _seems_ to happen preferably when a long-time CPU hog has run (and terminated) recently, such as setiathome. The load goes up to 1.0 and stays there for some time (could be a few minutes, or an hour maybe even a few hours), then drops back to 0.0 for no apparent reason. During that period of load 1.0, there is no activity. CPU is 100% idle. There is no process that consumes any significant amounts of CPU time. The box feels fast and responds quickly to interactive work. vmstat looks perfectly normal (like an idle machine). I have come to the conclusion that it must be a subtle bug somewhere in the kernel's calculation of the load averages. I tried to track it down in the kernel sources, but without success. Since it didn't seem to have any ill effects, but just being a cosmetic problem, I didn't bother to investigate further. I have to admit that I wasn't even motivated to submit a PR. Yeah, shame on me. Oh by the way, I think it happened once even on an OpenBSD/ Alpha box (not sure though, it was a long time ago). Maybe it's a long-standing BSD bug, or just strange coincidence. Please excuse me for forwarding this to -current as well, but I think it's important enough, and -current is affected, too. 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 Jan 8 18:25: 6 2000 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 264F814D86 for ; Sat, 8 Jan 2000 18:25:04 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA53215; Sat, 8 Jan 2000 21:24:55 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 21:24:55 -0500 (EST) From: Garrett Wollman Message-Id: <200001090224.VAA53215@khavrinen.lcs.mit.edu> To: "Alexander Sanda" Cc: "Garrett Wollman" , Subject: RE: 4.0 slower than 3.4? In-Reply-To: References: <200001081826.NAA51429@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> [I wrote:] >> You should also try it with `options COMPAT_IPFW=0' in your config >> file. > Hm, what's this option for? Well, somebody may have broken it (perhaps even me). But it was put there to provide those people who want fast networking an option to ensure that none of the firewall crap could possibly get in the way. -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 Sat Jan 8 18:29:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust52.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DD7B4151B0; Sat, 8 Jan 2000 18:29:31 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sat, 8 Jan 2000 21:29:29 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: sos@FreeBSD.org Cc: current@FreeBSD.org Subject: ATA CD-R problems, still... 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, I don't know about anyone else out there having the problems I'm having, but I might as well ask. I'm using the ATA driver with the following bugfix applied, otherwise the same. Index: atapi-cd.c =================================================================== RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-cd.c,v retrieving revision 1.33 diff -u -r1.33 atapi-cd.c --- atapi-cd.c 2000/01/07 12:01:00 1.33 +++ atapi-cd.c 2000/01/08 18:50:42 @@ -966,9 +966,12 @@ break; case CDRIOCCLOSEDISK: - if (!(cdp->flags & F_WRITTEN) || !(cdp->flags & F_DISK_OPEN)) { + if (!(cdp->flags & F_DISK_OPEN)) { error = EINVAL; printf("acd%d: sequence error (nothing to close)\n", cdp->lun); + } + else if (!(cdp->flags & F_WRITTEN)) { + cdp->flags &= ~(F_DISK_OPEN | F_TRACK_OPEN); } else { error = acd_close_disk(cdp); The problem manifests itself by now allowing me to write anything on any of my disks. Actually, it won't let me write data. Here is an example direct from vty0 (blank lines removed): {"/home2/tmp"}$ mkdir foo {"/home2/tmp"}$ cd foo {"/home2/tmp/foo"}$ dd if=/dev/zero bs=1m count=50 of=foo.iso 50+0 records in 50+0 records out 52428800 bytes transferred in 4.582966 secs (11439928 bytes/sec) {"/home2/tmp/foo"}$ burncd -s 2 data foo.iso fixate next writeable LBA 49652 writing from file foo.iso acd0: WRITE_BIG - ILLEGAL REQUEST asc=10 ascq=00 error=00 only wrote 0 of 65536 bytes fixating CD, please wait.. {"/home2/tmp/foo"}$ As you can see, I got an ILLEGAL REQUEST error printf(). The drive, which worked previously (in wormcontrol(8) days), is acd0 in the dmesg which follows. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #3: Sat Jan 8 21:17:33 EST 2000 green@green.dyndns.org:/usr/src/sys/compile/GREEN Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 124481536 (121564K bytes) Preloaded elf kernel "kernel" at 0xc02f9000. Preloaded elf module "vesa.ko" at 0xc02f909c. Preloaded elf module "usb.ko" at 0xc02f9138. Preloaded elf module "joy.ko" at 0xc02f91d4. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02dc102 (1000022) VESA: NVidia md0: Malloc disk apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 ohci0: mem 0xebfef000-0xebfeffff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered alpm0: at device 3.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: unknown card (vendor=0x10d9, dev=0x0531) at 16.0 irq 11 ata-pci1: port 0xd800-0xd8ff,0xddc8-0xddcb,0xddd0-0xddd7 irq 9 at device 18.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xddd0 irq 9 on ata-pci1 ata-pci2: port 0xda00-0xdaff,0xddf8-0xddfb,0xdde0-0xdde7 irq 9 at device 18.1 on pci0 ata-pci2: Busmastering DMA supported ata3 at 0xdde0 irq 9 on ata-pci2 vga-pci0: mem 0xcc000000-0xccffffff,0xef000000-0xefffffff irq 0 at device 20.0 on pci0 smbus0: on alsmb0 smb0: on smbus0 sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x16 on isa0 sbc0: setting card to irq 5, drq 1, 6 pcm0: on sbc0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pps0: on ppbus 0 unknown0: at iomem 0-0x9ffff,0xe0000-0xfffff on isa0 unknown: can't assign resources unknown1: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown4: at port 0xf0-0xff irq 13 on isa0 unknown5: at port 0x4d0-0x4d1,0xcf8-0xcff,0x3f7,0x4000-0x403f,0x5000-0x501f,0x480-0x49f,0x40b,0x4d6,0x73,0x92,0xb0-0xb3,0x10 iomem 0xfffe0000-0xffffffff,0x100000-0x7ffffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown6: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 unknown: can't assign resources DUMMYNET initialized (000106) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata1 as master ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-0 disk at ata3 as master ad2: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 acd0: CD-R drive at ata2 as master acd0: read 1377KB/s (1377KB/s) write 344KB/s (344KB/s), 512KB buffer, PIO3 acd0: Reads: CD-R, CD-DA stream acd0: Writes: CD-R, test write acd0: Audio: play, 2 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s1a dc0: port 0xde00-0xdeff mem 0xeefeff00-0xeefeffff irq 11 at device 16.0 on pci0 dc0: Ethernet address: 00:80:c6:f9:50:a6 dc0: supplying EUI64: 00:80:c6:ff:fe:f9:50:a6 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: starting DAD for fe80:0005::0280:c6ff:fef9:50a6 dc0: DAD complete for fe80:0005::0280:c6ff:fef9:50a6 - no duplicates found acd0: WRITE_BIG - ILLEGAL REQUEST asc=10 ascq=00 error=00 acd0: WRITE_BIG - ILLEGAL REQUEST asc=10 ascq=00 error=00 acd0: WRITE_BIG - ILLEGAL REQUEST asc=10 ascq=00 error=00 I don't have any non-default ATA options in my kernel config, by the way. Has anyone else experienced this, or does anyone know what it's all about? -- 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 Sat Jan 8 18:31:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id E6F9515003; Sat, 8 Jan 2000 18:31:20 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id SAA70561; Sat, 8 Jan 2000 18:31:19 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: , Cc: "freebsd-security@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 18:31:19 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Oliver Fromme > Sent: Saturday, January 08, 2000 6:06 PM > To: freebsd-stable@FreeBSD.ORG; freebsd-current@FreeBSD.ORG > Subject: Re: load spike strangeness > > > FreeBSD wrote in list.freebsd-stable: > > Overclocking is *NEVER* recommended > > Neither is posting anonymously (without a realname). > Since when does an E-mail address require a "realname"? Only a imbecile (IMHO) would use their real name on an e-mail that goes out to a public list. I don't want people to know my real name or SSN or any other personal info for that matter, NOR is it required, as far as I know. If it were to become required, I'd prefer to "unsubscribe" than to give that info out, as would any other intelligent person. I suggest you check your e-mail security information again before babbling nonsense. My e-mail addy is a REAL addy not one that goes through an anonymous re-mailer and I use it so IF I start getting Spam I can easily rmuser it and create another to resubscribe. Do you also use you real full name on IRC? To quote "Mr. T": "I pity da f00!" FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" P.S. To kill 2 birds with one stone... David Bushong: The info about overclocking was mentioned by Jordan, himself, on IRC in #FreeBSD (I'm not sure which network though) If you'd like, I can dig through IRC logs and try to find it but I'd prefer to take this to private e-mail instead. Let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 18:41:49 2000 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 721BE14EB3; Sat, 8 Jan 2000 18:41:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA14565; Sat, 8 Jan 2000 18:41:30 -0800 (PST) (envelope-from dillon) Date: Sat, 8 Jan 2000 18:41:30 -0800 (PST) From: Matthew Dillon Message-Id: <200001090241.SAA14565@apollo.backplane.com> To: "FreeBSD" Cc: , , "freebsd-security@FreeBSD. ORG" Subject: Re: RE: load spike strangeness References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :Since when does an E-mail address require a "realname"? Only a imbecile :(IMHO) would use their real name on an e-mail that goes out to a public :list. I don't want people to know my real name or SSN or any other personal :info for that matter, NOR is it required, as far as I know. If it were to :become required, I'd prefer to "unsubscribe" than to give that info out, as :would any other intelligent person. I suggest you check your e-mail security :information again before babbling nonsense. My e-mail addy is a REAL addy :not one that goes through an anonymous re-mailer and I use it so IF I start :getting Spam I can easily rmuser it and create another to resubscribe. Do :you also use you real full name on IRC? To quote "Mr. T": "I pity da f00!" : :FreeBSD :freebsd@gtonet.net : :"LinSUX is only free if your time is worthless" It depends on whether you want people to take you seriously or not. Frankly, not using your real name puts you at a disadvantage right off the bat. Personally speaking, I use my real name to add to the glory of all the Matt Dillon's out there in the world, so people will remember the name after I die, and be refering to me, myself, and I! I don't plan on going out as a red-shirt. :-) -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 Sat Jan 8 18:59: 3 2000 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 6CBF0151DD for ; Sat, 8 Jan 2000 18:58:55 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA53335; Sat, 8 Jan 2000 21:58:52 -0500 (EST) (envelope-from wollman) Date: Sat, 8 Jan 2000 21:58:52 -0500 (EST) From: Garrett Wollman Message-Id: <200001090258.VAA53335@khavrinen.lcs.mit.edu> To: "FreeBSD" Cc: Subject: RE: load spike strangeness In-Reply-To: References: <200001090206.DAA75669@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Multiple irrelevant mailing-lists snipped.] < said: > Since when does an E-mail address require a "realname"? As Sherlock Holmes once said: ``It is always unpleasant dealing with an alias.'' >plonk< -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 Sat Jan 8 19: 8:14 2000 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 0888214DCD; Sat, 8 Jan 2000 19:08:09 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id EAA79415; Sun, 9 Jan 2000 04:08:05 +0100 (CET) (envelope-from olli) Date: Sun, 9 Jan 2000 04:08:05 +0100 (CET) Message-Id: <200001090308.EAA79415@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: freebsd-chat@FreeBSD.ORG Subject: Re: load spike strangeness X-Newsgroups: list.freebsd-stable In-Reply-To: <858s5i$18nj$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 FreeBSD wrote in list.freebsd-stable: >> FreeBSD wrote in list.freebsd-stable: >> > Overclocking is *NEVER* recommended >> >> Neither is posting anonymously (without a realname). > > Since when does an E-mail address require a "realname"? It is not required, but it is a matter of good practice, politeness, and netiquette. It's a matter of being taken serious, and of encouraging people to communicate. This is not a security issue at all. > become required, I'd prefer to "unsubscribe" than to give that info out, as > would any other intelligent person. I suggest you check your e-mail security > information again before babbling nonsense. That's ridiculous. You're making a fool of yourself. You will not receive less spam when hiding your real name. And using a real name does not prevent you from creating a new account, if you think that's necessary. > Do > you also use you real full name on IRC? Yes, I do. For 5 years. And there is no reason to hide it. (I'm not a criminal who has to hide from the police or something like that.) > "LinSUX is only free if your time is worthless" While I'm at it: I don't like that quote either. :-) Goodbye 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 Jan 8 19:12:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from godfever.dccserver.com (godfever.dccserver.com [208.137.22.6]) by hub.freebsd.org (Postfix) with ESMTP id D269814F67; Sat, 8 Jan 2000 19:11:28 -0800 (PST) (envelope-from admin@dccserver.com) Received: from dccserver.att.com ([206.18.16.114]) by godfever.dccserver.com (Post.Office MTA v3.1.2 release (PO203-101c) ID# 0-44772U400L2S100) with SMTP id AVY19046; Thu, 14 Feb 2036 16:39:00 -0500 MIME-Version: 1.0 MIME-Version: 1.0 From: admin@dccserver.com Reply-To: admin@dccserver.com To: admin@dccserver.com Subject: Discount Capital For Commercial Equipment Content-Type: text/html; charset="us-ascii" Date: Thu, 14 Feb 2036 16:39:00 -0500 Message-ID: <20360214170857.AVY19046@dccserver.att.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG em general doc

Discount Capital

For

Equipment Leasing & Financing

 

We provide financing for Commercial Equipment, Upgrading or Expansion & High-Tech Equipment Leasing.

 

100% Financing on New & Used Equipment.

 

Sale Lease backs, Debt Consolidations,

 

Deferred Payment plans, lets you generate revenue with your new investment before you have to pay for it.

 

Financing programs for ALL credit profiles.

 

Use our Asset Location Division to help find the equipment you need.

Discount Capital Corp.

10101 Slater Ave. Suite 123-A

Fountain Valley, CA 92708

Phone: (877)346-MONY(6669) Fax: (714)593-0326

Don't Respond To This Address As It Is Not Monitored

E-Mail us @ info@discountcapital.net or visit out web site http://www.discountcapital.net/

To Stop Receiving Our Mail, Click On The Remove Link And Type

"Remove" In The Subject Line.           remove@discountcapital.net

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 19:41: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 8C48814C2B; Sat, 8 Jan 2000 19:41:00 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-21.blackbox-2.netaxs.com (dyn-21.blackbox-2.netaxs.com [207.106.60.21]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id WAA13910; Sat, 8 Jan 2000 22:40:57 -0500 (EST) Date: Sat, 8 Jan 2000 22:40:56 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Brian Fundakowski Feldman Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA CD-R problems, still... 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 Sat, 8 Jan 2000, Brian Fundakowski Feldman wrote: >Well, I don't know about anyone else out there having the problems I'm >having, but I might as well ask. I'm using the ATA driver with the >following bugfix applied, otherwise the same. > At the risk of sounding like an AOLer, me too. Prior to the most recent changes incorporating burncd, I was able to write to my HP 8250i using wormcontrol. Never burned a coaster, it was very reliable. Now when I use burncd, I get WRITE_BIG errors, and then the driver tries endlessly to reset. The only way out is to hit the big red reset button. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 19:46: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 83EC214D76 for ; Sat, 8 Jan 2000 19:45:58 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id TAA70811; Sat, 8 Jan 2000 19:45:56 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Garrett Wollman" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 19:45:56 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001090258.VAA53335@khavrinen.lcs.mit.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Garrett Wollman [mailto:wollman@khavrinen.lcs.mit.edu] > Sent: Saturday, January 08, 2000 6:59 PM > To: FreeBSD > Cc: freebsd-current@FreeBSD.ORG > Subject: RE: load spike strangeness > > > [Multiple irrelevant mailing-lists snipped.] > > < said: > > > Since when does an E-mail address require a "realname"? > > As Sherlock Holmes once said: ``It is always unpleasant dealing with > an alias.'' > > >plonk< > > -GAWollman > Mr. Holmes was a fictional character written in a time where there wasn't an internet. It's my belief that if he were real, and in our day and age, he would also take care in revealing to the mass public his true identity. FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 19:52:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id D80F5150E8; Sat, 8 Jan 2000 19:52:16 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id TAA70841; Sat, 8 Jan 2000 19:52:16 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: , , Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 19:52:16 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200001090308.EAA79415@dorifer.heim3.tu-clausthal.de> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Oliver Fromme > Sent: Saturday, January 08, 2000 7:08 PM > To: freebsd-stable@FreeBSD.ORG; freebsd-current@FreeBSD.ORG > Subject: Re: load spike strangeness > > > FreeBSD wrote in list.freebsd-stable: > >> FreeBSD wrote in list.freebsd-stable: > >> > Overclocking is *NEVER* recommended > >> > >> Neither is posting anonymously (without a realname). > > > > Since when does an E-mail address require a "realname"? > > It is not required, but it is a matter of good practice, > politeness, and netiquette. It's a matter of being taken > serious, and of encouraging people to communicate. This > is not a security issue at all. Suggesting people use their real names in mailing lists, seems like a security issue to me, while it's not an exploit, it's not safe or smart (again IMHO). > > > become required, I'd prefer to "unsubscribe" than to give that > info out, as > > would any other intelligent person. I suggest you check your > e-mail security > > information again before babbling nonsense. > > That's ridiculous. You're making a fool of yourself. You are entitled to your opinion. > > You will not receive less spam when hiding your real name. > And using a real name does not prevent you from creating a > new account, if you think that's necessary. No but it does help in preventing identity theft, however little. > > > Do > > you also use you real full name on IRC? > > Yes, I do. For 5 years. And there is no reason to hide it. > (I'm not a criminal who has to hide from the police or > something like that.) > > > "LinSUX is only free if your time is worthless" > > While I'm at it: I don't like that quote either. :-) > > Goodbye > Oliver > I really don't care if you like it. I'd suggest not quoting it then. Are you now the sig police? There are plenty of quotes I don't care for, but I'm not whining about it. I might suggest taking this off the lists if all you plan to do is flame. FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 19:57: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 384DE15168 for ; Sat, 8 Jan 2000 19:56:59 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.254.39]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id WAA06517; Sat, 8 Jan 2000 22:56:54 -0500 (EST) Message-ID: <38780706.1200D7AC@acm.org> Date: Sat, 08 Jan 2000 22:56:54 -0500 From: Jim Bloom X-Mailer: Mozilla 4.7 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help References: <20000108133114L.shin@nd.net.fujitsu.co.jp> <3877DD18.D8BF669F@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the problems I was seeing. I had an old configuration of dhclient dating from before it was integrated into FreeBSD. At that time, I just called dhclient without specifying the interface. (I only had one NIC.) Dhclient then tried using all interfaces it could find. One of the interfaces it tried to use was faith0 which generated all of the errors. I just fixed by network startup to specify the interface for dhclient and all of the error messages went away. Jim Bloom bloom@acm.org Jim Bloom wrote: > > I added the options a couple weeks ago. Everthing has been working fairly > well. Two issues I have seen which I haven't verified if they are are related > to INET6 or something else. > > First, ever since I added INET6, I have been seeing errors like > > looutput: af=0 unexpected (or something close to that) > > These are appearing frequently (several a minute). (There also is no newline > after this error message in the kernel.) > > I ran cvsup around 15:00 EST today and built world and a new kernel. After > rebooting, I started getting error messages from dhclient about unsupported > address families. I haven't looked into this to determine if dhclient is > working correctly and reporting warnings or is not working at all. I'll try to > do some more checking later tonight or tomorrow. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 19:59:38 2000 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 C89B415168 for ; Sat, 8 Jan 2000 19:59:34 -0800 (PST) (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 TAA11083; Sat, 8 Jan 2000 19:59:33 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA63459; Sat, 8 Jan 2000 19:59:32 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 8 Jan 2000 19:59:32 -0800 (PST) Message-Id: <200001090359.TAA63459@vashon.polstra.com> To: death@southcom.com.au Subject: Re: 4.0 slower than 3.4? In-Reply-To: <4.2.2.20000109021927.00dba250@mail.southcom.com.au> References: <4.2.2.20000109021927.00dba250@mail.southcom.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.2.2.20000109021927.00dba250@mail.southcom.com.au>, james wrote: > It's interesting though how i had no ipf rules whatsoever, yet it > introduced so much latency, as Alexander has pointed out in another email. > Why is ipf so slow? I was planning on switching from ipfw/natd to > ipf/ipnat, but i don't think i want to now - considering it's so darn slow. If you want to do NAT, I can tell you without even trying it that ipfilter's NAT will be much faster than natd's. With natd, every packet has to go out from the kernel to userland and back to have its headers rewritten. That's a lot of overhead. Not so with ipfilter -- it's all done inside the kernel. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 20: 8: 6 2000 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 0B0C714E7A for ; Sat, 8 Jan 2000 20:08:04 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id FAA16434; Sun, 9 Jan 2000 05:07:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "FreeBSD" Cc: "freebsd-current@FreeBSD. ORG" Subject: Re: load spike strangeness In-reply-to: Your message of "Sat, 08 Jan 2000 19:45:56 PST." Date: Sun, 09 Jan 2000 05:07:56 +0100 Message-ID: <16432.947390876@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "FreeBSD" writes: >> As Sherlock Holmes once said: ``It is always unpleasant dealing with >> an alias.'' > >Mr. Holmes was a fictional character written in a time where there wasn't an >internet. It's my belief that if he were real, and in our day and age, he >would also take care in revealing to the mass public his true identity. I think you are not only obnoxius, you are also dead wrong. Sherlock Holmes was *by principle* against anononymity. Anyway, into the mail-filter you go... -- 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 Jan 8 20:29:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 01CFD14A21 for ; Sat, 8 Jan 2000 20:29:11 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id UAA70989; Sat, 8 Jan 2000 20:29:05 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Poul-Henning Kamp" Cc: "freebsd-current@FreeBSD. ORG" Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 20:29:05 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <16432.947390876@critter.freebsd.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Poul-Henning Kamp > Sent: Saturday, January 08, 2000 8:08 PM > To: FreeBSD > Cc: freebsd-current@FreeBSD. ORG > Subject: Re: load spike strangeness > > I think you are not only obnoxius, you are also dead wrong. Sherlock > Holmes was *by principle* against anononymity. As I might have mentioned before, I really don't care what you think. I'm not here for a popularity contest. Holmes was still fictional and therefore not capable of having principles save the ones written for him. Since he was written in a time with NO internet, who do you think you are to say what he would have recommended for security's sake? At least *I* have the decency to say "It's my belief" whereas you are so high-and-mighty as to perpetrate that you KNOW what his character would do. Your omnipotence offends me and you, too, are the newest addition to my mail filter. > > Anyway, into the mail-filter you go... See above. > > -- > 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! Again, I ask, if all you want to do is flame, take it to private e-mail and let's leave the lists out of this. I will, however, reply to the list if you insist on continuing. While my original reply to this thread was relevant, your feeble attack is not and yes, I feel I have the right to reply to the list if you insist on attacking me there. Maybe Karl was right, some people in the FreeBSD organization really do think they are above the rest of us. I however do not share that belief. So, are you done? FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 20:31:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 22B4614C41 for ; Sat, 8 Jan 2000 20:31:17 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA20476; Sun, 9 Jan 2000 13:31:13 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA22872; Sun, 9 Jan 2000 13:31:12 +0900 (JST) Received: from localhost ([192.168.245.186]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id NAA09572; Sun, 9 Jan 2000 13:31:11 +0900 (JST) To: bloom@acm.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6 testing...willing to help In-Reply-To: <38780706.1200D7AC@acm.org> References: <20000108133114L.shin@nd.net.fujitsu.co.jp> <3877DD18.D8BF669F@acm.org> <38780706.1200D7AC@acm.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000109133146O.shin@nd.net.fujitsu.co.jp> Date: Sun, 09 Jan 2000 13:31:46 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 41 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found the problems I was seeing. I had an old configuration of dhclient > dating from before it was integrated into FreeBSD. At that time, I just called > dhclient without specifying the interface. (I only had one NIC.) Dhclient then > tried using all interfaces it could find. One of the interfaces it tried to use > was faith0 which generated all of the errors. I just fixed by network startup > to specify the interface for dhclient and all of the error messages went away. Thanks very much for your testing. After I read your last mail, I also reviewed the code and noticed it, and tried to fix it. The cause of the problem is that, the newly added dummy interface, faith, is actually using same routine for loopback interface. But it has BROADCAST flag set. And when dhclient is execed without argument, it sends DHCP requests to every interfaces which has BROADCAST flag set. And when it is sent to faith0 then it actually go to looutput(), and the log messages looutput: af=0 unexpected is printed there. Faith has LOOPBACK flag set before, but it is changed to BROADCAST to announce routes destined to faith interfaces via IPv6 routing daemon. Because usually routing daemons don't announce routes destined to interfaces which has LOOPBACK flag set. I just tried to remove even BROADCAST flag from faith, and it seems to work in my enviroments. Route6d still advertise routes destined to faith, and loooutput error messages are stopeed. I'll commit it now. Thanks, Yoshinobu Inoue > Jim Bloom > bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 20:58:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax2-059.dialup.optusnet.com.au [198.142.241.59]) by hub.freebsd.org (Postfix) with ESMTP id A203914C28 for ; Sat, 8 Jan 2000 20:58:18 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 929CB55BA; Sun, 9 Jan 2000 15:58:14 +1100 (EST) Message-Id: <4.2.2.20000109155625.00a3ff00@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 09 Jan 2000 15:58:03 +1100 To: Luigi Rizzo From: james Subject: Re: ipf vs. ipfw Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200001081603.RAA10786@info.iet.unipi.it> References: <4.2.2.20000109021927.00dba250@mail.southcom.com.au> 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 17:03 8/1/2000 +0100, Luigi Rizzo wrote: >I think the basic rulechecking algorithms in ipf are no better/faster >than the ones in ipfw. If you want to switch from ipfw (no natd!) >to ipf just for performance reasons, i think you are not going to get >any significant advantage if any (i mean, if you write your ipfw rules >in an intelligent way.). So far it's been a disadvantage. :( Even without any rules, ipf introduces about 50-100 microseconds latency, whereas ipfw only introduces about 25. >For sure the pair ipf/ipnat should be faster than ipfw/natd, but >just because natd is a user-space thing and this means additional >data movements between kernel and user space that ipf needs not. The only thing i use nat for is over a 56k modem. ;) So speed really isn't an issue there, but is over my LAN. >Other reasons for the switch could be the fact that ipf is stateful >(but i am working on adding state to ipfw, if i find proper support >- hint, hint), so you can build better things. > >In other words, if you want to switch, be motivated by features, not >by performance! Quite, ipf has some great features. :) Speaking of ipf, is there any reason why i shouldn't upgrade from the 3.3.3 that comes with 4.0-CURRENT, to 3.3.6? I upgraded already and haven't seen any problems - although my machine rebooted at one stage right after i typed a rule into ipnat. I couldn't reproduce it, and never found out why it rebooted. 3.3.6's speed is still as lousy as 3.3.3 too. :( Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 21:22:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C760D14A31; Sat, 8 Jan 2000 21:22:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B6DF41CD82B; Sat, 8 Jan 2000 21:22:49 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 8 Jan 2000 21:22:49 -0800 (PST) From: Kris Kennaway To: Boozy Cc: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: -current or 3.4 with KAME ??? 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, 6 Jan 2000, Boozy wrote: > How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it > stable? It's in the process of being integrated, and is therefore still incomplete. It's hoped that by the time of 4.0-RELEASE (not long away) it will be fully functional. If you need a fully functional IPv6 today, stick with FreeBSD 3.4 + KAME. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 21:35:48 2000 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 9F7791520A for ; Sat, 8 Jan 2000 21:35:22 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA25089; Sat, 8 Jan 2000 22:35:17 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA44959; Sat, 8 Jan 2000 22:35:16 -0700 (MST) Message-Id: <200001090535.WAA44959@harmony.village.org> To: "Eugene M. Kim" Subject: Re: Status of DEVFS? Cc: FreeBSD-current Mailing List In-reply-to: Your message of "Sat, 08 Jan 2000 00:13:16 PST." References: Date: Sat, 08 Jan 2000 22:35:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Eugene M. Kim" writes: : What is the current status of DEVFS? Is this still a `good feature to : have but oh well...'-sort of thing so it is not supported by many : drivers, or is some serious effort on track to round the sharp edges and : make it usable? Last time I tried it had all kinds of sharp edges that definitely made it untenable for normal use. I was using cam, and at the time it didn't support devfs entries. Chances are good that you'd best avoid it for now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 23: 8:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust252.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5950415036; Sat, 8 Jan 2000 23:08:44 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 9 Jan 2000 02:08:42 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bryan Liesner Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA CD-R problems, still... 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 Sat, 8 Jan 2000, Bryan Liesner wrote: > On Sat, 8 Jan 2000, Brian Fundakowski Feldman wrote: > > >Well, I don't know about anyone else out there having the problems I'm > >having, but I might as well ask. I'm using the ATA driver with the > >following bugfix applied, otherwise the same. > > > > At the risk of sounding like an AOLer, me too. Prior to the most > recent changes incorporating burncd, I was able to write to my HP > 8250i using wormcontrol. Never burned a coaster, it was very > reliable. Now when I use burncd, I get WRITE_BIG errors, and then > the driver tries endlessly to reset. The only way out is to hit the > big red reset button. To add a little bit to that, on the side-note area... Okay, first of all, the reason it keeps resetting is that when the timeout() is called (which resets the controller, see ata{,pi}_reset()), the timer which fires is in the kernel proper (!) and as such takes over all control of the CPU. E.g. you won't get your processes run very much (to make an understatement). I have been able to get a Ctrl+Alt+Del in at the right time (between the timer being set and being fired) to get the box rebooted, otherwise I have the same problem as you. Now, failing to address why the hardware is failing, there really needs to be a better way to reset controllers. Why don't we have timers fire in their own kthread, one per timeout()? I think that this would be a very useful change, and an important one that could be implemented before the "feature freeze" for 4.0. Does anyone have a better idea regarding that? But, don't let me take the focus away from the CD-R issue. It's pretty important to be able to figure out why some CD-Rs no longer work (obviously, Soren's work :) > -Bryan -- 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 Sat Jan 8 23:17:11 2000 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 937F014D8B for ; Sat, 8 Jan 2000 23:16:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AFD3B1CA0 for ; Sun, 9 Jan 2000 15:16:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Minor HEADS-UP re: config(8) Date: Sun, 09 Jan 2000 15:16:36 +0800 From: Peter Wemm Message-Id: <20000109071636.AFD3B1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This shouldn't cause any breakage if you don't do this, but you should change references to "controller" in your kernel configs to "device". Of course, don't do this before recompiling usr.sbin/config. I have bumped configversion as older configs will not appreciate this too much if you get them mixed up. The difference between 'controller' and 'device' has been a figment of config(8)'s imagination for quite some time - at least as far back as newbus, and quite probably as far back as FreeBSD 2.0. There have been some other changes and cleanups, but I don't expect there to be problems. One bonus is that the following comment about a quirk: - /* XXX: Why do we always get an entry such as: - * { '?', "ncr", '?', '?' }, - */ .. has been resolved and no longer happens. This was a misfeature of the partial cloning of parent "controllers". This would happen if you added an entry "device cd0 at scbus?". config(8) would create virtual devices with wildcards based on guesses and similarity to other things. ie: if there was a 'scbus0 at ncr0' and somebody referenced 'scbus?' it would guess that another 'scbus? at ncr?' would be needed. Nothing used this, except the old vax-style configuration mechanism that never(?) entered 386BSD/FreeBSD. (not newconfig, I'm talking about the really old oldconfig) Anyway, just change 'controller' to 'device' and be happy. :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 23:41:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id B278514EA8 for ; Sat, 8 Jan 2000 23:41:42 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id IAA76977 for ; Sun, 9 Jan 2000 08:41:36 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 9 Jan 2000 08:41:36 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: halt/reboot broken, ctrl-alt-del ok 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 both my current machines, I've problems rebooting. After executing reboot, the system "clings desperately to life". The behavior is not always the same, but I get 5-6 new login-prompts. Then sometimes "Some process would not die, ps axl adviced" Other times miscl panics. Lately its final words is - - - - - - - - - - Suncing disks .. done Pid 71454 (getty), uid 0 exited on signal 11 (core dumped) Pid 71455 (getty), uid 0 exited on signal 11 (core dumped) Panic: unmount: dangling vnode - - - - - - - - - - - Sometimes the disks are unmounted cleanly, sometimes not. If I use ctrl-alt-del, it just cleanly goes down and up again, as usual. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 23:49:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id DA8BB14F27 for ; Sat, 8 Jan 2000 23:49:16 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id IAA79298; Sun, 9 Jan 2000 08:49:03 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 9 Jan 2000 08:49:02 +0100 (CET) From: Leif Neland To: Dan Nelson Cc: Leif Neland , freebsd-current@FreeBSD.ORG, mysql@lists.mysql.com Subject: Re: 2 hours to compile mysql? In-Reply-To: <20000101133219.C612@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 Sat, 1 Jan 2000, Dan Nelson wrote: > In the last episode (Jan 01), Leif Neland said: > > So far it has been taking 2 hours to compile sql_yacc.cc from > > mysql3.22. > > > > I had to find an old disk for swap, and it's swapping all the time. > > > > top shows 156M size and 46M res., run time 20min's for cc1plus. That > > probably means it's been waiting for swapping in 1h40m... > > > > The box is a 333MHz PII, with 64M ram. Do I just need more ram to be > > able to compile in reasonable time, or is something broken? > > You probably need more RAM. sql_yacc.cc is one of those "worst-case" > programs as far as gcc is concerned; I don't think gcc can parse large > case statements like this efficiently. Adding "--with-low-memory" to > your port Makefile, in the CONFIGURE_ARGS line, will help. > I got 64M more RAM(1), so the system now has 128MB. Mysql now compiles in 10 minutes or so. Leif (1) My wife got the kids a new game for christmas. It was too demanding for their 486's, so I got 2 K6-3-400MHz/64MB motherboards for them. To preserve my self-esteem, I had to upgrade my own PII-333/64Mb somehow to be more powerfull than theirs... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 8 23:55:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 4F76E14F02 for ; Sat, 8 Jan 2000 23:55:28 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id IAA80485; Sun, 9 Jan 2000 08:54:47 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 9 Jan 2000 08:54:47 +0100 (CET) From: Leif Neland To: Yoshinobu Inoue Cc: freebsd@cybcon.com, freebsd-current@FreeBSD.ORG Subject: IPSEC broken, was Re: IPv6 testing...willing to help In-Reply-To: <20000108133114L.shin@nd.net.fujitsu.co.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 Sat, 8 Jan 2000, Yoshinobu Inoue wrote: > The 1st thing I want to be tested is that, a kernel with > following additions to the config file > > options INET6 #IPv6 communications protocols > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > options IPSEC_DEBUG #debug for IP security > Kernel build stops with "Don't know how to make sha1.c". sha was removed a few days ago, a "heads up" said. I've rebuilt world since, but I've had to remove the IPSEC options to make a kernel. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message